From: Brian Masney <bmasney@redhat.com>
To: Johan Hovold <johan@kernel.org>
Cc: andersson@kernel.org, krzysztof.kozlowski+dt@linaro.org,
quic_shazhuss@quicinc.com, konrad.dybcio@linaro.org,
robh+dt@kernel.org, johan+linaro@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, ahalaney@redhat.com,
echanude@redhat.com
Subject: Re: [PATCH v3 4/7] arm64: dts: qcom: sc8280xp: add missing i2c nodes
Date: Fri, 23 Dec 2022 07:22:14 -0500 [thread overview]
Message-ID: <Y6WddnmaREQlt9gq@x1> (raw)
In-Reply-To: <Y6WEzkcP31S2JGrL@hovoldconsulting.com>
On Fri, Dec 23, 2022 at 11:37:02AM +0100, Johan Hovold wrote:
> On Tue, Dec 20, 2022 at 02:28:51PM -0500, Brian Masney wrote:
> > diff --git a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
> > index f1111cd7f679..a502d4e19d98 100644
> > --- a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
> > @@ -813,6 +813,38 @@ qup2: geniqup@8c0000 {
> >
> > status = "disabled";
> >
> > + i2c16: i2c@880000 {
> > + compatible = "qcom,geni-i2c";
> > + reg = <0 0x00880000 0 0x4000>;
> > + clocks = <&gcc GCC_QUPV3_WRAP2_S0_CLK>;
> > + clock-names = "se";
> > + interrupts = <GIC_SPI 373 IRQ_TYPE_LEVEL_HIGH>;
> > + #address-cells = <1>;
> > + #size-cells = <0>;
>
> I'm aware that the two current i2c nodes has these two properties here
> in the middle, but would you mind moving '#address-cells' and
> '#size-cells' after 'reg' instead where I'd expect them to be?
>
> Same for the spi patch.
>
> I can clean up the existing two nodes (and binding example) unless you
> want to do it.
I'll clean up the existing nodes, qcom,i2c-geni-qcom.yaml, and
qcom,geni-se.yaml in my next version.
Brian
next prev parent reply other threads:[~2022-12-23 12:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 19:28 [PATCH v3 0/7] dts: qcom: sc8280xp: add i2c, spi, and rng nodes Brian Masney
2022-12-20 19:28 ` [PATCH v3 1/7] arm64: dts: qcom: sc8280xp: rename qup2_uart17 to uart17 Brian Masney
2022-12-23 9:31 ` Johan Hovold
2022-12-20 19:28 ` [PATCH v3 2/7] arm64: dts: qcom: sc8280xp: rename qup2_i2c5 to i2c21 Brian Masney
2022-12-23 9:38 ` Johan Hovold
2022-12-20 19:28 ` [PATCH v3 3/7] arm64: dts: qcom: sc8280xp: rename qup0_i2c4 to i2c4 Brian Masney
2022-12-23 9:40 ` Johan Hovold
2022-12-20 19:28 ` [PATCH v3 4/7] arm64: dts: qcom: sc8280xp: add missing i2c nodes Brian Masney
2022-12-23 10:37 ` Johan Hovold
2022-12-23 12:22 ` Brian Masney [this message]
2022-12-23 12:42 ` Konrad Dybcio
2022-12-23 13:05 ` Johan Hovold
2022-12-23 13:05 ` Konrad Dybcio
2022-12-20 19:28 ` [PATCH v3 5/7] arm64: dts: qcom: sc8280xp: add missing spi nodes Brian Masney
2022-12-23 10:39 ` Johan Hovold
2022-12-20 19:28 ` [PATCH v3 6/7] arm64: dts: qcom: sa8540p-ride: add i2c nodes Brian Masney
2022-12-20 19:28 ` [PATCH v3 7/7] arm64: dts: qcom: sc8280xp: add rng device tree node Brian Masney
2022-12-21 20:44 ` Konrad Dybcio
2022-12-21 19:41 ` [PATCH v3 0/7] dts: qcom: sc8280xp: add i2c, spi, and rng nodes Steev Klimaszewski
2023-01-04 14:14 ` Brian Masney
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=Y6WddnmaREQlt9gq@x1 \
--to=bmasney@redhat.com \
--cc=ahalaney@redhat.com \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=echanude@redhat.com \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_shazhuss@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).