<snip> > > > > > > > > > >v14: > > > >Resent for retesting (because of suspected false negative). > > > > > > > >Series Acked-by: Jerin Jacob <jer...@marvell.com> Series Tested-by: > > > >Jerin Jacob <jer...@marvell.com> Series Tested-by: Dharmik Thakkar > > > ><dharmik.thak...@arm.com> Series Tested-by: Vimal Chungath > > > ><vcchu...@amazon.com> > > > > > > > > > > Series Tested-by: Pavan Nikhilesh <pbhagavat...@marvell.com> > > > > > > Also, I believe we need to take a look at ARCH_SOC_ID support coming > > > up in > > > 5.9 kernel. > > > > > > https://lore.kernel.org/linux-arm-kernel/20200506164411.3284-1- > > > sudeep.ho...@arm.com/ > > > > Agree, it can come after this series is merged. > > > > Note that it requires firmware with SMCCC v1.2 support in the > > underlying platform. > > > > I have a few questions to everyone: > Is there any comprehensive documentation about how to use this? Things > like where in Linux can I get the ARCH_SOC_ID and how are the ID's mapped > to socs? Kernel patch is at [1] - merged in Kernel 5.9 Makes use of SMCCC v1.2, SMCCC_ARCH_SOC_ID call. SMCCC v1.2 spec is at [2].
The SoC ID becomes available at: /sys/devices/socX/family /sys/devices/socX/soc_id /sys/devices/socX/revision SOC_ID makes use of JEP-106 code [3] for the SiP which makes it unique. [1] https://lkml.org/lkml/2020/6/25/208 [2] https://developer.arm.com/documentation/den0028/c [3] https://developer.arm.com/documentation/ka001301/1-0 > If the ID mappings are not public then the plaform owners would need to > add the support, right? I agree here. There are firmware changes required and we do not know the IDs as well. It will be good for Marvell/NXP/NVIDIA to do this. Pavan, is this ok for you?
