From: "Arnd Bergmann" <arnd@kernel.org>
To: "Alexander Sverdlin" <alexander.sverdlin@gmail.com>,
devicetree@vger.kernel.org
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Frank Rowand" <frowand.list@gmail.com>,
linux-kernel@vger.kernel.org,
"Nikita Shubin" <nikita.shubin@maquefel.me>,
"Hartley Sweeten" <hsweeten@visionengravers.com>,
"Lukasz Majewski" <lukma@denx.de>,
"Linus Walleij" <linusw@kernel.org>
Subject: Re: [PATCH] of: fdt: Honor CONFIG_CMDLINE* even without /chosen node
Date: Mon, 12 Dec 2022 08:29:55 +0100 [thread overview]
Message-ID: <bc3d7b6b-3f08-410f-bd43-b7157419d5a7@app.fastmail.com> (raw)
In-Reply-To: <11af73e05bad75e4ef49067515e3214f6d944b3d.camel@gmail.com>
On Mon, Dec 12, 2022, at 00:58, Alexander Sverdlin wrote:
> I do not read a strict requirement on /chosen node in either ePAPR or in
> Documentation/devicetree. Help text for CONFIG_CMDLINE and
> CONFIG_CMDLINE_EXTEND doesn't make their behavior explicitly dependent on
> the presence of /chosen or the presense of /chosen/bootargs.
>
> However the early check for /chosen and bailing out in
> early_init_dt_scan_chosen() skips CONFIG_CMDLINE handling which is not
> really related to /chosen node or the particular method of passing cmdline
> from bootloader.
>
> This leads to counterintuitive combinations (assuming
> CONFIG_CMDLINE_EXTEND=y):
>
> a) bootargs="foo", CONFIG_CMDLINE="bar" => cmdline=="foo bar"
> b) /chosen missing, CONFIG_CMDLINE="bar" => cmdline==""
> c) bootargs="", CONFIG_CMDLINE="bar" => cmdline==" bar"
>
> Move CONFIG_CMDLINE handling outside of early_init_dt_scan_chosen() so that
> cases b and c above result in the same cmdline.
>
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@gmail.com>
Thanks for debugging this and coming up with a fix. We probably want
to have an empty /chosen node in most dts files to stay compatible with
existing kernels, but fixing the kernel is a good idea regardless.
Acked-by: Arnd Bergmann <arnd@arndb.de>
and probably
Cc: stable@vger.kernel.org
next prev parent reply other threads:[~2022-12-12 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 23:58 [PATCH] of: fdt: Honor CONFIG_CMDLINE* even without /chosen node Alexander Sverdlin
2022-12-12 7:29 ` Arnd Bergmann [this message]
2022-12-13 8:51 ` Linus Walleij
2022-12-13 15:29 ` Rob Herring
2022-12-13 22:07 ` Alexander Sverdlin
2022-12-15 17:40 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2022-12-11 23:58 Alexander Sverdlin
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=bc3d7b6b-3f08-410f-bd43-b7157419d5a7@app.fastmail.com \
--to=arnd@kernel.org \
--cc=alexander.sverdlin@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=hsweeten@visionengravers.com \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukma@denx.de \
--cc=nikita.shubin@maquefel.me \
--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;
as well as URLs for NNTP newsgroup(s).