From: Xianwei Zhao <xianwei.zhao@amlogic.com>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] soc: amlogic: meson-gx-socinfo: add new SoCs id
Date: Tue, 18 Nov 2025 10:07:26 +0800 [thread overview]
Message-ID: <1114eb5a-d04c-4497-896a-789c02527eaa@amlogic.com> (raw)
In-Reply-To: <592374f6-6fb3-47a0-a834-ba6702f4b2a6@linaro.org>
Hi Neil,
Thanks for your reply
On 2025/11/17 18:19, Neil Armstrong wrote:
> [ EXTERNAL EMAIL ]
>
> Hi,
>
> On 11/17/25 11:17, Xianwei Zhao via B4 Relay wrote:
>> From: Xianwei Zhao <xianwei.zhao@amlogic.com>
>>
>> Add new definition for Amlogi SoCs, include S6, S7, S7D.
>>
>> Signed-off-by: Xianwei Zhao <xianwei.zhao@amlogic.com>
>> ---
>> drivers/soc/amlogic/meson-gx-socinfo.c | 7 ++++++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/soc/amlogic/meson-gx-socinfo.c
>> b/drivers/soc/amlogic/meson-gx-socinfo.c
>> index 7549f1644e5e..6fbb70c8922d 100644
>> --- a/drivers/soc/amlogic/meson-gx-socinfo.c
>> +++ b/drivers/soc/amlogic/meson-gx-socinfo.c
>> @@ -45,7 +45,9 @@ static const struct meson_gx_soc_id {
>> { "S4", 0x37 },
>> { "A5", 0x3c },
>> { "C3", 0x3d },
>> - { "A4", 0x40 },
>
> Why did you drop A4 ?
>
This was my mistake, thanks for pointing out, I will restore it.
>> + { "S7", 0x46 },
>> + { "S7D", 0x47 },
>> + { "S6", 0x48 },
>> };
>>
>> static const struct meson_gx_package_id {
>> @@ -86,6 +88,9 @@ static const struct meson_gx_package_id {
>> { "A311D2", 0x36, 0x1, 0xf },
>> { "A113X2", 0x3c, 0x1, 0xf },
>> { "A113L2", 0x40, 0x1, 0xf },
>> + { "S805X3", 0x46, 0x3, 0xf },
>> + { "S905X5M", 0x47, 0x1, 0xf },
>> + { "S905X5", 0x48, 0x1, 0xf },
>> };
>>
>> static inline unsigned int socinfo_to_major(u32 socinfo)
>>
>
> Thanks,
> Neil
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2025-11-18 2:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 10:16 [PATCH 0/5] soc: amlogic: Add new Amlogic SoCs info defines Xianwei Zhao via B4 Relay
2025-11-17 10:17 ` [PATCH 1/5] dt-bindings: arm: amlogic: meson-gx-ao-secure: support more SoCs Xianwei Zhao via B4 Relay
2025-11-17 19:25 ` Conor Dooley
2025-11-17 10:17 ` [PATCH 2/5] soc: amlogic: meson-gx-socinfo: add new SoCs id Xianwei Zhao via B4 Relay
2025-11-17 10:19 ` Neil Armstrong
2025-11-18 2:07 ` Xianwei Zhao [this message]
2025-11-17 10:17 ` [PATCH 3/5] arm64: dts: amlogic: s6: add ao secure node Xianwei Zhao via B4 Relay
2025-11-17 10:17 ` [PATCH 4/5] arm64: dts: amlogic: s7: " Xianwei Zhao via B4 Relay
2025-11-17 10:17 ` [PATCH 5/5] arm64: dts: amlogic: s7d: " Xianwei Zhao via B4 Relay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1114eb5a-d04c-4497-896a-789c02527eaa@amlogic.com \
--to=xianwei.zhao@amlogic.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome