From: Dmitry Rokosov <ddrokosov@sberdevices.ru>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: =Xianwei Zhao <xianwei.zhao@amlogic.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-amlogic@lists.infradead.org>, <devicetree@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [RFC PATCH 1/2] arm64: amlogic: add new ARCH_AMLIPC for IPC SoC
Date: Wed, 19 Apr 2023 19:04:05 +0300 [thread overview]
Message-ID: <20230419160405.d7qfir3nv6tlxx2a@CAB-WSD-L081021> (raw)
In-Reply-To: <661cea17-a4dd-75d1-6a7e-16efa5aea52b@linaro.org>
On Wed, Apr 19, 2023 at 03:43:12PM +0200, Neil Armstrong wrote:
> On 19/04/2023 15:14, Dmitry Rokosov wrote:
> > On Wed, Apr 19, 2023 at 03:38:33PM +0800, =Xianwei Zhao wrote:
> > > From: Xianwei Zhao <xianwei.zhao@amlogic.com>
> > >
> > > The C series SoCs are designed for smart IP camera
> > > applications, which does not belong to Meson series.
> > > So, Add ARCH_AMLIPC for the new series.
> > >
> > > There are now multiple amlogic SoC seies supported, so group them under
> > > their own menu. we can easily add new platforms there in the future.
> > > Introduce ARCH_AMLOGIC to cover all Amlogic SoC series.
> > >
> > > No functional changes introduced.
> > >
> > > Signed-off-by: Xianwei Zhao <xianwei.zhao@amlogic.com>
> > > ---
> > > arch/arm64/Kconfig.platforms | 12 ++++++++++++
> > > arch/arm64/configs/defconfig | 2 ++
> > > 2 files changed, 14 insertions(+)
> > >
> > > diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> > > index 89a0b13b058d..bfbc817eef8f 100644
> > > --- a/arch/arm64/Kconfig.platforms
> > > +++ b/arch/arm64/Kconfig.platforms
> > > @@ -162,12 +162,24 @@ config ARCH_MEDIATEK
> > > This enables support for MediaTek MT27xx, MT65xx, MT76xx
> > > & MT81xx ARMv8 SoCs
> > > +menuconfig ARCH_AMLOGIC
> > > + bool "NXP SoC support"
> >
> > NXP? Did you mean "Amlogic"?
> >
> > > +
> > > +if ARCH_AMLOGIC
> > > +
> > > config ARCH_MESON
> > > bool "Amlogic Platforms"
> > > help
> > > This enables support for the arm64 based Amlogic SoCs
> > > such as the s905, S905X/D, S912, A113X/D or S905X/D2
> > > +config ARCH_AMLIPC
> >
> > Do we really need a different ARCH for Amlogic IPC?
> > I can imagine that it's not the Meson architecture at all.
> > But maybe a better solution is just to rename ARCH_MESON to ARCH_AMLOGIC?
>
> It should be changed treewide, and is it worth it ?
As far as I understand, the A1 and S4 families are not fully compatible
with the Meson architecture, and we haven't provided additional ARCH_*
for them.
In my opinion, it's a good time to split the Meson architecture into
proper subsets, or rename it treewide (maybe only config option
ARCH_MESON => ARCH_AMLOGIC).
> >
> > > + bool "Amlogic IPC Platforms"
> > > + help
> > > + This enables support for the arm64 based Amlogic IPC SoCs
> > > + such as the C302X, C308L
> > > +endif
> > > +
> > > config ARCH_MVEBU
> > > bool "Marvell EBU SoC Family"
> > > select ARMADA_AP806_SYSCON
> > > diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> > > index 7790ee42c68a..f231bd1723fd 100644
> > > --- a/arch/arm64/configs/defconfig
> > > +++ b/arch/arm64/configs/defconfig
> > > @@ -46,7 +46,9 @@ CONFIG_ARCH_LG1K=y
> > > CONFIG_ARCH_HISI=y
> > > CONFIG_ARCH_KEEMBAY=y
> > > CONFIG_ARCH_MEDIATEK=y
> > > +CONFIG_ARCH_AMLOGIC=y
> > > CONFIG_ARCH_MESON=y
> > > +CONFIG_ARCH_AMLIPC=y
> > > CONFIG_ARCH_MVEBU=y
> > > CONFIG_ARCH_NXP=y
> > > CONFIG_ARCH_LAYERSCAPE=y
> > > --
> > > 2.37.1
> > >
> > >
> > > _______________________________________________
> > > linux-amlogic mailing list
> > > linux-amlogic@lists.infradead.org
> > > http://lists.infradead.org/mailman/listinfo/linux-amlogic
> >
>
--
Thank you,
Dmitry
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-04-19 16:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 7:38 [RFC PATCH 0/2] Baisc devicetree support for Amlogic C3 =Xianwei Zhao
2023-04-19 7:38 ` [RFC PATCH 1/2] arm64: amlogic: add new ARCH_AMLIPC for IPC SoC =Xianwei Zhao
2023-04-19 7:45 ` Krzysztof Kozlowski
2023-04-19 10:22 ` Neil Armstrong
2023-04-19 13:14 ` Dmitry Rokosov
2023-04-19 13:43 ` Neil Armstrong
2023-04-19 16:04 ` Dmitry Rokosov [this message]
2023-04-19 16:25 ` Neil Armstrong
2023-04-19 17:00 ` Dmitry Rokosov
2023-04-20 8:43 ` Kelvin Zhang
2023-04-20 12:18 ` Neil Armstrong
2023-04-27 9:20 ` Kelvin Zhang
2023-04-20 12:39 ` Krzysztof Kozlowski
2023-04-27 9:23 ` Kelvin Zhang
2023-04-19 7:38 ` [RFC PATCH 2/2] arm64: dts: add support for C3 based Amlogic AW409 =Xianwei Zhao
2023-04-19 7:48 ` Krzysztof Kozlowski
2023-04-27 9:25 ` xianwei.zhao
[not found] ` <5a11ccfd-eafa-391a-e2b9-d032510c9e7b@amlogic.com>
2023-05-01 10:00 ` Krzysztof Kozlowski
2023-04-19 10:23 ` Neil Armstrong
2023-04-19 13:09 ` [RFC PATCH 0/2] Baisc devicetree support for Amlogic C3 Dmitry Rokosov
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=20230419160405.d7qfir3nv6tlxx2a@CAB-WSD-L081021 \
--to=ddrokosov@sberdevices.ru \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=will@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