From: Sumit Garg <sumit.garg@kernel.org>
To: neil.armstrong@linaro.org
Cc: u-boot-qcom@groups.io, u-boot@lists.denx.de, trini@konsulko.com,
casey.connolly@linaro.org, loic.minier@oss.qualcomm.com,
Sumit Garg <sumit.garg@oss.qualcomm.com>
Subject: Re: [PATCH] mach-snapdragon: Update fdtfile logic to work for RB1 and RB2
Date: Mon, 5 May 2025 15:01:25 +0530 [thread overview]
Message-ID: <aBiFbRyGffUus86w@sumit-X1> (raw)
In-Reply-To: <0469bb8b-042d-4c6f-974d-6d1879262e91@linaro.org>
On Mon, May 05, 2025 at 09:26:09AM +0200, neil.armstrong@linaro.org wrote:
> On 05/05/2025 09:23, Neil Armstrong via groups.io wrote:
> > Hi,
> >
> > On 23/04/2025 07:11, Sumit Garg wrote:
> > > From: Sumit Garg <sumit.garg@oss.qualcomm.com>
> > >
> > > RB1 and RB2 have three root compatibles where the last one can't be used
> > > to decode fdtfile name (qcm* vs qrb*). So rather just rely on the first
> > > compatible to retrieve the SoC name.
> >
> > OK, so "soc" would be qcm2290 instead of qrb2210, what's the problem since
> > you have "board" with "qrb2210-rb1" ?
> >
> > What is the difference between qcm2290 & qrb2210 that affects U-boot ?
> >
> > Same for qrb4210 vs sm4250.
> >
> > If you have a custom board code, you can still match on the root compatible.
>
> Forget my comment, it affects the fdtfile construction....
>
> >
> > Neil
> >
> > >
> > > Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
> > > ---
> > > arch/arm/mach-snapdragon/board.c | 12 ++++++++++--
> > > 1 file changed, 10 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/arch/arm/mach-snapdragon/board.c b/arch/arm/mach-snapdragon/board.c
> > > index deae4d32378..dc8220e89b4 100644
> > > --- a/arch/arm/mach-snapdragon/board.c
> > > +++ b/arch/arm/mach-snapdragon/board.c
> > > @@ -437,16 +437,24 @@ static void configure_env(void)
> > > /* The Qualcomm reference boards (RBx, HDK, etc) */
> > > if (!strncmp("qcom", buf, strlen("qcom"))) {
> > > + char *soc;
> > > +
> > > /*
> > > * They all have the first compatible as "qcom,<soc>-<board>"
> > > * (e.g. "qcom,qrb5165-rb5"). We extract just the part after
> > > * the dash.
> > > */
> > > - if (!strsep(&tmp, "-")) {
> > > + if (!strsep(&tmp, ",")) {
> > > + log_warning("compatible '%s' has no ','\n", buf);
> > > + return;
> > > + }
> > > + soc = strsep(&tmp, "-");
> > > + if (!soc) {
> > > log_warning("compatible '%s' has no '-'\n", buf);
> > > return;
> > > }
> > > - /* tmp is now "rb5" */
> > > +
> > > + env_set("soc", soc);
>
> OK, so you should move the other env_set("soc", ...) code in the other else branch
> to avoid having a double env_set("soc", ...)
Sure, I can do that in v2.
-Sumit
>
> > > env_set("board", tmp);
> > > } else {
> > > if (!strsep(&tmp, ",")) {
> >
> >
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Groups.io Links: You receive all messages sent to this group.
> > View/Reply Online (#1677): https://groups.io/g/u-boot-qcom/message/1677
> > Mute This Topic: https://groups.io/mt/112410772/900740
> > Group Owner: u-boot-qcom+owner@groups.io
> > Unsubscribe: https://groups.io/g/u-boot-qcom/leave/13197875/900740/1403832380/xyzzy [neil.armstrong@linaro.org]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
> >
>
prev parent reply other threads:[~2025-05-05 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 5:11 [PATCH] mach-snapdragon: Update fdtfile logic to work for RB1 and RB2 Sumit Garg
2025-05-05 5:23 ` Sumit Garg
2025-05-05 7:23 ` neil.armstrong
[not found] ` <183C90A92BBF63A5.32718@groups.io>
2025-05-05 7:26 ` neil.armstrong
2025-05-05 9:31 ` Sumit Garg [this message]
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=aBiFbRyGffUus86w@sumit-X1 \
--to=sumit.garg@kernel.org \
--cc=casey.connolly@linaro.org \
--cc=loic.minier@oss.qualcomm.com \
--cc=neil.armstrong@linaro.org \
--cc=sumit.garg@oss.qualcomm.com \
--cc=trini@konsulko.com \
--cc=u-boot-qcom@groups.io \
--cc=u-boot@lists.denx.de \
/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