linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: neil.armstrong@linaro.org
To: Dmitry Rokosov <ddrokosov@sberdevices.ru>,
	arm@kernel.org, soc@kernel.org
Cc: 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,
	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 15:46:50 +0100	[thread overview]
Message-ID: <13cf3223-d3fb-1a3e-f13a-77db3b6d144c@linaro.org> (raw)
In-Reply-To: <20230227142809.kujmrraf3pcdhqyn@CAB-WSD-L081021>

On 27/02/2023 15:28, Dmitry Rokosov wrote:
> Hello Neil!
> 
> On Mon, Feb 27, 2023 at 09:15:04AM +0100, neil.armstrong@linaro.org wrote:
> 
> [...]
> 
>> 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.
> 
> I totally agree with you, but I suppose it's fully related to 'big'
> Amlogic SoC like S905_ or A311_ series. A113L (aka 'a1') is
> a cost-efficient dual-core SoC which is used for small, cheap solutions
> with cheap components. Every cent is important during BoM development.
> That's why usually ODMs install small ROM and RAM capacity, and each
> megabyte is important for RAM/ROM kernel and rootfs footprints.

Do you have figures ? is 32bit ARM kernel really lighter when ARM64 one is correctly configured ?

> Why am I talking about rootfs? For such small projects a good
> choice is buildroot rootfs assembling framework. Unfortunatelly,
> buildroot doesn't support 'compat' mode when kernel and userspace have
> a different bitness. 

well this is a buildroot problem... the kernel itself is perfectly capable
of running an AArch32 userspace.

> In the internal project, we save several
> percents of ROM/RAM free space using 32-bit configuration (mostly rootfs
> ROM space, to be honest). Therefore, for such 'little' cost-efficient
> SoCs we can make an exception and support 32-bit configuration, from my
> point of view.

32bit ARM is now "legacy", I would need to have an advice from the ARM SoC
maintainers, but AFAIK new ARMv8 SoCs should stay in arm64 arch.

Arnd ? Olof ? do you have an opinion on this ?

> 
> What do you think about that?

>>
>> And as Krzysztof stated, the support is incomplete and cannot work
>> without a dts file.
> 
> Agreed, we shouldn't merge dead code. But there are several question to
> discuss there. Please check my reply to Krzysztof message.
> 
> [...]
> 


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-02-27 14:47 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 ` [PATCH v1 0/3] Meson A1 32-bit support neil.armstrong
2023-02-27 14:28   ` Dmitry Rokosov
2023-02-27 14:46     ` neil.armstrong [this message]
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=13cf3223-d3fb-1a3e-f13a-77db3b6d144c@linaro.org \
    --to=neil.armstrong@linaro.org \
    --cc=arm@kernel.org \
    --cc=avromanov@sberdevices.ru \
    --cc=ddrokosov@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 \
    --cc=soc@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;
as well as URLs for NNTP newsgroup(s).