From: Rajendra Nayak <rnayak@codeaurora.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Andy Gross <andy.gross@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
devicetree@vger.kernel.org, Stephen Boyd <sboyd@codeaurora.org>,
evgreen@chromium.org
Subject: Re: [PATCH v2 3/3] arm64: dts: sdm845: Add serial console support
Date: Wed, 7 Feb 2018 09:58:58 +0530 [thread overview]
Message-ID: <1696cf0f-dccc-3014-1c5f-70a7941bd8ff@codeaurora.org> (raw)
In-Reply-To: <CAD=FV=VwTZo2YOxw0W7JbuF_Dic8YHmQZ6_FAxiZG3BXiS_VEw@mail.gmail.com>
[]..
>> @@ -10,4 +10,46 @@
>> / {
>> model = "Qualcomm Technologies, Inc. SDM845 MTP";
>> compatible = "qcom,sdm845-mtp";
>> +
>> + aliases {
>> + serial0 = &qup_uart2;
>> + };
>> +
>> + chosen {
>> + stdout-path = "serial0";
>> + };
>> +
>> + soc {
>
> I don't know if there's an official position, but in general I'm seen
> people use the actual "soc" alias here. AKA at the top level of this
> dts, just do:
>
> &soc {
> ...
> };
>
> Normally doing stuff like that is useful so you don't need to
> replicate the whole hierarchy. In this case that's not a huge
> savings, but it can be nice to be consistent. In the very least it
> saves you a level of indentation.
>
>
>> + serial@a84000 {
>> + status = "okay";
>> + };
>
> Similarly here you can use the alias from the sdm845.dtsi file to
> avoid replicating the hierarchy. AKA at the top level do:
>
> &qup_uart2 {
> status = "okay";
> };
>
> In this case it saves you 2 levels of indentation.
Right. Andy/Bjorn, are there any preferences here?
I see we don't do this for the other board files, and I not sure
theres a specific reasoning for how its currently done and if we
need to stick to it.
>
>> +
>> + pinctrl@3400000 {
>> + qup_uart2_default: qup_uart2_default {
>
> I'm not sure how persnickety I should be, but according to
> <https://elinux.org/Device_Tree_Linux>:
>
> node names use dash "-" instead of underscore "_"
>
> ...but, of course, labels can't use dashes (and the same page says to
> use underscore for labels). This is why, in rk3288 for instance, you
> see:
>
> i2c2_xfer: i2c2-xfer {
> rockchip,pins = <6 9 RK_FUNC_1 &pcfg_pull_none>,
> <6 10 RK_FUNC_1 &pcfg_pull_none>;
> };
>
> AKA the label and the node name are the same but the label uses "_"
> and the node names use "-".
Sure, I'll fix these up.
[]
>> diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b/arch/arm64/boot/dts/qcom/sdm845.dtsi
>> index 02520f19e4ca..c4ce70840acf 100644
>> --- a/arch/arm64/boot/dts/qcom/sdm845.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi
>> @@ -4,6 +4,7 @@
>> */
>>
>> #include <dt-bindings/interrupt-controller/arm-gic.h>
>> +#include <dt-bindings/clock/qcom,gcc-sdm845.h>
>>
>> / {
>> model = "Qualcomm Technologies, Inc. SDM845";
>> @@ -273,5 +274,25 @@
>> cell-index = <0>;
>> };
>>
>> + qup_1: qcom,geni_se@ac0000 {
>> + compatible = "qcom,geni-se-qup";
>> + reg = <0xac0000 0x6000>;
>
> I think you may have mentioned this in another context, but this
> doesn't match the current bindings. Some clocks should be here.
> ...and it looks like the uart should be a subnode.
right, these were tested with the v1 set for serial. I will update them.
regards
Rajendra
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
prev parent reply other threads:[~2018-02-07 4:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 16:19 [PATCH v2 0/3] Add DTS for SDM845 SoC and MTP Rajendra Nayak
2018-01-31 16:19 ` [PATCH v2 1/3] Documentation: dt-bindings: arm: Document kryo385 cpu Rajendra Nayak
2018-02-05 6:08 ` Rob Herring
2018-01-31 16:19 ` [PATCH v2 2/3] arm64: dts: sdm845: Add minimal dts/dtsi files for sdm845 SoC and MTP Rajendra Nayak
2018-02-06 21:55 ` Doug Anderson
2018-02-07 4:49 ` Rajendra Nayak
2018-01-31 16:19 ` [PATCH v2 3/3] arm64: dts: sdm845: Add serial console support Rajendra Nayak
2018-02-06 19:35 ` Doug Anderson
2018-02-07 4:28 ` Rajendra Nayak [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=1696cf0f-dccc-3014-1c5f-70a7941bd8ff@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@codeaurora.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).