From: neil.armstrong@linaro.org
To: Alexey Romanov <avromanov@sberdevices.ru>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
khilman@baylibre.com, jbrunet@baylibre.com,
martin.blumenstingl@googlemail.com, linus.walleij@linaro.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@sberdevices.ru
Subject: Re: [PATCH v1 0/3] Meson A1 32-bit support
Date: Mon, 27 Feb 2023 09:15:04 +0100 [thread overview]
Message-ID: <8e5f9bfa-d612-cd43-d722-d04c40938c62@linaro.org> (raw)
In-Reply-To: <20230222115020.55867-1-avromanov@sberdevices.ru>
On 22/02/2023 12:50, Alexey Romanov wrote:
> Hello!
>
> This patchset adds support for 32-bit Meson A1 board.
Hi Alexev,
I'm aware Amlogic also runs their kernel as 32bit to gain a few kbytes
of memory, but those processors are ARMv8 and the arm64 arch code
has been designed for those CPUs.
So far I didn't find a single good reason to add 32bit support for
ARMv8 Amlogic based SoCs, if you have a solid reason please share.
And as Krzysztof stated, the support is incomplete and cannot work
without a dts file.
Neil
> We describe device tree with following components:
> CPU, GIC, IRQ, Timer, UART, PIN controller.
> It's capable of booting up into the serial console.
>
> We have tested this DTS and used drivers at our
> 32-bit Meson A1 board and it works correctly.
>
> Alexey Romanov (3):
> meson: pinctrl: use CONFIG_PINCTRL_A1 with CONFIG_ARM
> firmware: meson: use CONFIG_MESON_SM with CONFIG_ARM
> arch/arm: dts: introduce meson-a1 device tree
>
> arch/arm/boot/dts/meson-a1.dtsi | 151 ++++++++++++++++++++++++++++++++
> drivers/firmware/meson/Kconfig | 2 +-
> drivers/pinctrl/meson/Kconfig | 2 +-
> 3 files changed, 153 insertions(+), 2 deletions(-)
> create mode 100644 arch/arm/boot/dts/meson-a1.dtsi
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-02-27 8:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 11:50 [PATCH v1 0/3] Meson A1 32-bit support Alexey Romanov
2023-02-22 11:50 ` [PATCH v1 1/3] meson: pinctrl: use CONFIG_PINCTRL_A1 with CONFIG_ARM Alexey Romanov
2023-03-06 13:45 ` Linus Walleij
2023-03-06 13:49 ` neil.armstrong
2023-03-06 13:52 ` Linus Walleij
2023-02-22 11:50 ` [PATCH v1 2/3] firmware: meson: use CONFIG_MESON_SM " Alexey Romanov
2023-02-22 11:50 ` [PATCH v1 3/3] arch/arm: dts: introduce meson-a1 device tree Alexey Romanov
2023-02-23 9:08 ` Krzysztof Kozlowski
2023-02-23 9:09 ` Krzysztof Kozlowski
2023-02-27 14:39 ` Dmitry Rokosov
2023-02-27 14:41 ` Krzysztof Kozlowski
2023-02-27 8:15 ` neil.armstrong [this message]
2023-02-27 14:28 ` [PATCH v1 0/3] Meson A1 32-bit support Dmitry Rokosov
2023-02-27 14:46 ` neil.armstrong
2023-02-27 16:01 ` Dmitry Rokosov
2023-02-27 14:58 ` Arnd Bergmann
2023-02-27 15:51 ` Dmitry Rokosov
2023-02-27 16:15 ` Arnd Bergmann
2023-02-27 16:37 ` Dmitry Rokosov
2023-02-27 16:38 ` Neil Armstrong
2023-02-27 16:50 ` Dmitry Rokosov
2023-02-27 18:19 ` Arnd Bergmann
2023-02-28 8:49 ` Dmitry Rokosov
2023-03-09 21:52 ` Kevin Hilman
2023-03-10 15:20 ` 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=8e5f9bfa-d612-cd43-d722-d04c40938c62@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=avromanov@sberdevices.ru \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=kernel@sberdevices.ru \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.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=robh+dt@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