From: Krzysztof Kozlowski <krzk@kernel.org>
To: Lijuan Gao <quic_lijuang@quicinc.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
kernel@quicinc.com, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 6/6] arm64: dts: qcom: add base QCS615 RIDE dts
Date: Wed, 28 Aug 2024 11:34:18 +0200 [thread overview]
Message-ID: <90c98fee-770c-4b83-9e05-6f04866094c2@kernel.org> (raw)
In-Reply-To: <148451f2-6b1b-4616-b703-fd52e7afa2be@quicinc.com>
On 28/08/2024 11:31, Lijuan Gao wrote:
>>>>> +/ {
>>>>> + model = "Qualcomm Technologies, Inc. QCS615 Ride";
>>>>> + compatible = "qcom,qcs615-ride", "qcom,qcs615";
>>>>> +
>>>>> + chosen {
>>>>> + bootargs = "console=hvc0";
>>>>
>>>> Noooo, last time I agreed on this, you told me later it is different.
>>>>
>>> In the early stages, enabling HVC is to more easily verify clock and
>>> PMIC related functions, as it’s difficult to debug without the console
>>> log. After the clock and PMIC are ready, we will enable the UART console.
>>
>> Working serial is supposed to be part of the early submission.
>>
> Okay, I will remove it in the next patch.
Can you post next version with proper serial device?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-28 9:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 2:02 [PATCH 0/6] Add initial support for QCS615 Lijuan Gao
2024-08-28 2:02 ` [PATCH 1/6] dt-bindings: qcom,pdc: document QCS615 Power Domain Controller Lijuan Gao
2024-08-28 6:19 ` Krzysztof Kozlowski
2024-08-28 2:02 ` [PATCH 2/6] dt-bindings: arm: qcom: document QCS615 and the reference board Lijuan Gao
2024-08-28 6:19 ` Krzysztof Kozlowski
2024-08-28 2:02 ` [PATCH 3/6] dt-bindings: arm: qcom,ids: add SoC ID for QCS615 Lijuan Gao
2024-08-28 6:19 ` Krzysztof Kozlowski
2024-08-28 2:02 ` [PATCH 4/6] soc: qcom: socinfo: Add QCS615 SoC ID table entry Lijuan Gao
2024-08-28 6:19 ` Krzysztof Kozlowski
2024-08-28 2:02 ` [PATCH 5/6] arm64: dts: qcom: add initial support for QCS615 DTSI Lijuan Gao
2024-08-28 6:23 ` Krzysztof Kozlowski
2024-08-28 7:42 ` Lijuan Gao
2024-08-28 7:57 ` Krzysztof Kozlowski
2024-08-28 9:29 ` Lijuan Gao
2024-08-28 2:02 ` [PATCH 6/6] arm64: dts: qcom: add base QCS615 RIDE dts Lijuan Gao
2024-08-28 6:25 ` Krzysztof Kozlowski
2024-08-28 7:54 ` Lijuan Gao
2024-08-28 9:11 ` Krzysztof Kozlowski
2024-08-28 9:31 ` Lijuan Gao
2024-08-28 9:34 ` Krzysztof Kozlowski [this message]
2024-08-28 10:06 ` Lijuan Gao
2024-09-04 8:35 ` Lijuan Gao
2024-09-04 9:32 ` Krzysztof Kozlowski
2024-09-04 10:23 ` Konrad Dybcio
2024-09-05 5:29 ` Aiqun Yu (Maria)
2024-10-26 11:14 ` Konrad Dybcio
2024-08-28 11:12 ` 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=90c98fee-770c-4b83-9e05-6f04866094c2@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_lijuang@quicinc.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).