From: Xianwei Zhao via B4 Relay <devnull+xianwei.zhao.amlogic.com@kernel.org>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Xianwei Zhao <xianwei.zhao@amlogic.com>
Subject: [PATCH v3 2/6] soc: amlogic: meson-gx-socinfo: add new SoCs id
Date: Fri, 19 Jul 2024 16:08:10 +0800 [thread overview]
Message-ID: <20240719-soc_info-v3-2-020a3b687c0c@amlogic.com> (raw)
In-Reply-To: <20240719-soc_info-v3-0-020a3b687c0c@amlogic.com>
From: Xianwei Zhao <xianwei.zhao@amlogic.com>
Add new definition for Amlogi SoCs, include S4, C3, T7, A4, A5.
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Signed-off-by: Xianwei Zhao <xianwei.zhao@amlogic.com>
---
drivers/soc/amlogic/meson-gx-socinfo.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/soc/amlogic/meson-gx-socinfo.c b/drivers/soc/amlogic/meson-gx-socinfo.c
index 8809a948201a..7549f1644e5e 100644
--- a/drivers/soc/amlogic/meson-gx-socinfo.c
+++ b/drivers/soc/amlogic/meson-gx-socinfo.c
@@ -41,6 +41,11 @@ static const struct meson_gx_soc_id {
{ "G12B", 0x29 },
{ "SM1", 0x2b },
{ "A1", 0x2c },
+ { "T7", 0x36 },
+ { "S4", 0x37 },
+ { "A5", 0x3c },
+ { "C3", 0x3d },
+ { "A4", 0x40 },
};
static const struct meson_gx_package_id {
@@ -76,6 +81,11 @@ static const struct meson_gx_package_id {
{ "S905X3", 0x2b, 0x10, 0x3f },
{ "S905D3", 0x2b, 0x30, 0x3f },
{ "A113L", 0x2c, 0x0, 0xf8 },
+ { "S805X2", 0x37, 0x2, 0xf },
+ { "C308L", 0x3d, 0x1, 0xf },
+ { "A311D2", 0x36, 0x1, 0xf },
+ { "A113X2", 0x3c, 0x1, 0xf },
+ { "A113L2", 0x40, 0x1, 0xf },
};
static inline unsigned int socinfo_to_major(u32 socinfo)
--
2.37.1
next prev parent reply other threads:[~2024-07-19 8:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 8:08 [PATCH v3 0/6] Add new Amlogic SoCs info defines Xianwei Zhao via B4 Relay
2024-07-19 8:08 ` [PATCH v3 1/6] dt-bindings: arm: amlogic: meson-gx-ao-secure: support more SoCs Xianwei Zhao via B4 Relay
2024-07-19 8:08 ` Xianwei Zhao via B4 Relay [this message]
2024-07-19 8:08 ` [PATCH v3 3/6] arm64: dts: amlogic: s4: add ao secure node Xianwei Zhao via B4 Relay
2024-07-23 7:17 ` Neil Armstrong
2024-07-19 8:08 ` [PATCH v3 4/6] arm64: dts: amlogic: c3: " Xianwei Zhao via B4 Relay
2024-07-23 7:17 ` Neil Armstrong
2024-07-19 8:08 ` [PATCH v3 5/6] arm64: dts: amlogic: t7: " Xianwei Zhao via B4 Relay
2024-07-23 7:18 ` Neil Armstrong
2024-07-19 8:08 ` [PATCH v3 6/6] arm64: dts: amlogic: a4: " Xianwei Zhao via B4 Relay
2024-07-23 7:18 ` Neil Armstrong
2024-08-20 15:30 ` (subset) [PATCH v3 0/6] Add new Amlogic SoCs info defines Neil Armstrong
2024-08-20 15:33 ` Neil Armstrong
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=20240719-soc_info-v3-2-020a3b687c0c@amlogic.com \
--to=devnull+xianwei.zhao.amlogic.com@kernel.org \
--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 \
--cc=xianwei.zhao@amlogic.com \
/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;
as well as URLs for NNTP newsgroup(s).