| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 14 Mar 2024 15:25:02 +0300 From: Viacheslav <adeep@...ina.in> To: Sudeep Holla <sudeep.holla@....com> Cc: Neil Armstrong <neil.armstrong@...aro.org>, Kevin Hilman <khilman@...libre.com>, Jerome Brunet <jbrunet@...libre.com>, Martin Blumenstingl <martin.blumenstingl@...glemail.com>, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-amlogic@...ts.infradead.org, Rob Herring <robh+dt@...nel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org> Subject: Re: [PATCH v3 0/4] soc: amlogic: add new meson-gx-socinfo-sm driver Hi! 14/03/2024 13.40, Sudeep Holla wrote: > On Thu, Mar 14, 2024 at 09:59:50AM +0300, Viacheslav Bocharov wrote: >> The Amlogic Meson SoC Secure Monitor implements a call to retrieve an >> unique SoC ID starting from the GX Family and all new families. >> But GX-family chips (e.g. GXB, GXL and newer) supports also 128-bit >> chip ID. 128-bit chip ID consists 32-bit SoC version and 96-bit OTP data. >> > > How old or new are these SoCs ? The reason I ask is that it is really > sad to see vendors still creating their custom interfaces for such things > despite the standard SMCCC interface SOC_ID introduced in SMCCC v1.2 some > time in 2020. Most of these SoC were created before 2020. > > Hopefully they migrated to the std interface and just use the driver in > the kernel without needing to add this every time they fancy playing > with the interface for no reason. > -- Best regards Viacheslav
Powered by blists - more mailing lists