Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: exxxxkc <exxxxkc@getgoogleoff.me>
To: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v5 4/5] pinctrl: qcom: ipq5018: allow it to be bulid on arm32
Date: Sat, 5 Oct 2024 03:25:08 +0800	[thread overview]
Message-ID: <7c08d987-bb73-4fec-afcb-4197fa78d4be@getgoogleoff.me> (raw)
In-Reply-To: <CACRpkdZnBBAEgHZ=HShwvaXaN-6icC5hzwHqDNWWy_PKJDh+Fw@mail.gmail.com>


On 10/4/24 7:44 PM, Linus Walleij wrote:
> On Thu, Oct 3, 2024 at 1:29 AM Karl Chan <exxxxkc@getgoogleoff.me> wrote:
>
>> There are some ipq5018 based device's firmware only can able to boot
>> arm32 but the pinctrl driver dont allow it to be compiled on
>> arm32.Therefore this patch needed for those devices.
>>
>> Signed-off-by: Karl Chan <exxxxkc@getgoogleoff.me>
> (...)
>> -       depends on ARM64 || COMPILE_TEST
>> +       depends on ARM || ARM64 || COMPILE_TEST
> Can we get some more context for this?
>
> Is this another one of those cases where the SoC is actually a
> 64bit core but vendors just choose to run it in 32bit mode because
> that is what they want or what is the reason here? AFAIK
> IPQ5018 is always Cortex-A53?
>
> I just want to know if this is something we should encourage
> or leave out-of-tree.
>
> Yours,
> Linus Walleij


Yeah it is like those MSM8916 based device that only has 32bit 
firmware.(e.g. samsung e5).
AFIK , other ipq5018 based linksys router has 64bit firmware but this 
one dont.
Also this router seem to be identical to linksys ER5500 but with 32bit 
firmware and isp exclusive.
(It is PCCW isp exclusive router (See 
https://support.linksys.com/kb/article/3723-en/) )



  reply	other threads:[~2024-10-04 19:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 23:27 [PATCH v5 0/5] arm: dts: qcom-ipq5018-linksys-jamaica: Include dts from arm64 Karl Chan
2024-10-02 23:28 ` [PATCH v5 1/5] dt-bindings: arm: qcom: add Linksys EA9350 V3 Karl Chan
2024-10-03  7:28   ` Krzysztof Kozlowski
2024-10-02 23:28 ` [PATCH v5 2/5] arm64: dts: " Karl Chan
2024-12-30 14:48   ` Konrad Dybcio
2024-10-02 23:28 ` [PATCH v5 3/5] clk: qcom: ipq5018: allow it to be bulid on arm32 Karl Chan
2024-10-02 23:28 ` [PATCH v5 4/5] pinctrl: " Karl Chan
2024-10-04 11:44   ` Linus Walleij
2024-10-04 19:25     ` exxxxkc [this message]
2024-10-07 15:32     ` Karl Chan
2024-10-07 15:36       ` Karl Chan
2024-10-02 23:28 ` [PATCH v5 5/5] arm: dts: qcom-ipq5018-linksys-jamaica: Include dts from arm64 Karl Chan
2024-10-06 20:14   ` Dmitry Baryshkov
2024-10-26 11:38     ` Konrad Dybcio
2024-10-28  6:33       ` Sricharan Ramabadhran
2024-10-28 10:24         ` Konrad Dybcio

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=7c08d987-bb73-4fec-afcb-4197fa78d4be@getgoogleoff.me \
    --to=exxxxkc@getgoogleoff.me \
    --cc=linux-arm-msm@vger.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