From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jae Hyun Yoo <quic_jaehyoo@quicinc.com>,
Rob Herring <robh+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>, Andrew Lunn <andrew@lunn.ch>
Cc: Jamie Iles <quic_jiles@quicinc.com>,
Graeme Gregory <quic_ggregory@quicinc.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH v3] ARM: dts: aspeed: add Nuvia DC-SCM BMC
Date: Mon, 28 Mar 2022 09:13:49 +0200 [thread overview]
Message-ID: <94377113-b51d-8fb2-56fe-6f2abcea8ed0@kernel.org> (raw)
In-Reply-To: <92b381f7-6a4b-1db1-ea00-7bbc8c4b0f84@quicinc.com>
On 27/03/2022 22:24, Jae Hyun Yoo wrote:
>
> [...]
>
>>> + chosen {
>>> + stdout-path = &uart5;
>>> + bootargs = "console=ttyS4,115200n8";
>>
>> After adding stdout-path, please remove bootargs.
>
> Can I keep the default bootargs for a case if CONFIG_CMDLINE_FORCE
> is enabled?
No, because you control the config, so just disable CMDLINE_FORCE if you
don't want it and such bootargs are not part of hardware description.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-28 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 19:02 [PATCH v3] ARM: dts: aspeed: add Nuvia DC-SCM BMC Jae Hyun Yoo
2022-03-27 18:55 ` Krzysztof Kozlowski
2022-03-27 20:24 ` Jae Hyun Yoo
2022-03-28 7:13 ` Krzysztof Kozlowski [this message]
2022-03-28 14:15 ` Jae Hyun Yoo
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=94377113-b51d-8fb2-56fe-6f2abcea8ed0@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@aj.id.au \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=quic_ggregory@quicinc.com \
--cc=quic_jaehyoo@quicinc.com \
--cc=quic_jiles@quicinc.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;
as well as URLs for NNTP newsgroup(s).