From: Abel Vesa <abel.vesa@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Rajendra Nayak <quic_rjendra@quicinc.com>
Subject: Re: [PATCH 1/2] arm64: dts: qcom: x1e80100: Add all missing nodes
Date: Thu, 14 Dec 2023 17:33:54 +0200 [thread overview]
Message-ID: <ZXsgYl2h+MnTIz7D@linaro.org> (raw)
In-Reply-To: <9c8e887b-429c-4226-9851-5f1cbb93524a@linaro.org>
On 23-12-12 17:21:19, Konrad Dybcio wrote:
>
>
> On 12/12/23 11:24, Abel Vesa wrote:
> > Add all missing nodes which describe entire X1E80100 platform.
> "all" doesn't really mean all :|
>
Well, all the nodes where we have support working (for now).
But I'll re-word it to say "add some missing nodes".
> couple of patch-wide observations below
>
> [...]
>
> > + gpucc: clock-controller@3d90000 {
> > + compatible = "qcom,x1e80100-gpucc";
> > + reg = <0 0x3d90000 0 0xa000>;
> Please make sure the address part is padded to 8 hex digits
Will do.
> [...]
>
> > + usb_1_ss2_hsphy: phy@fde000 {
> > + compatible = "qcom,x1e80100-snps-eusb2-phy",
> > + "qcom,sm8550-snps-eusb2-phy";
> > + reg = <0x0 0x0fde000 0x0 0x154>;
> and please choose 0x0 vs 0 and stick to one (which seems to
> be 0 in this file)
I'll use 0x0 in all reg as I think this is more consistent.
>
> [...]
>
> > + pcie6a: pci@1bf8000 {
> > + device_type = "pci";
> > + compatible = "qcom,pcie-x1e80100";
> > + reg = <0x0 0x01bf8000 0x0 0x3000>,
> > + <0x0 0x70000000 0x0 0xf1d>,
> > + <0x0 0x70000f20 0x0 0xa8>,
> > + <0x0 0x70001000 0x0 0x1000>,
> > + <0x0 0x70100000 0x0 0x100000>;
> > + reg-names = "parf", "dbi", "elbi", "atu", "config";
> one per line, please
Will do.
>
> > + #address-cells = <3>;
> > + #size-cells = <2>;
> > + ranges = <0x01000000 0x0 0x00000000 0x0 0x70200000 0x0 0x100000>,
> > + <0x02000000 0x0 0x70300000 0x0 0x70300000 0x0 0x3d00000>;
> > + bus-range = <0x00 0xff>;
> > +
> > + dma-coherent;
> > +
> > + linux,pci-domain = <7>;
> > + num-lanes = <2>;
> > +
> > + interrupts = <GIC_SPI 773 IRQ_TYPE_LEVEL_HIGH>;
> > + interrupt-names = "msi";
> > +
> > + #interrupt-cells = <1>;
> > + interrupt-map-mask = <0 0 0 0x7>;
> > + interrupt-map = <0 0 0 1 &intc 0 0 0 843 IRQ_TYPE_LEVEL_HIGH>, /* int_a */
> > + <0 0 0 2 &intc 0 0 0 844 IRQ_TYPE_LEVEL_HIGH>, /* int_b */
> > + <0 0 0 3 &intc 0 0 0 845 IRQ_TYPE_LEVEL_HIGH>, /* int_c */
> > + <0 0 0 4 &intc 0 0 0 772 IRQ_TYPE_LEVEL_HIGH>; /* int_d */
> you can drop these comments
Will do.
> [...]
>
> > + clocks = <&gcc GCC_DISP_AHB_CLK>,
> > + <&gcc GCC_DISP_HF_AXI_CLK>,
> > + <&dispcc DISP_CC_MDSS_AHB_CLK>,
> > + <&dispcc DISP_CC_MDSS_MDP_LUT_CLK>,
> > + <&dispcc DISP_CC_MDSS_MDP_CLK>,
> > + <&dispcc DISP_CC_MDSS_VSYNC_CLK>;
> > + clock-names = "bus",
> > + "nrt_bus",
> > + "iface",
> > + "lut",
> > + "core",
> > + "vsync";
> you probably should list the ROT clock here too
Will look into it.
> [...]
>
> > + cpucp_mbox: mailbox@18830000 {
> > + compatible = "qcom,x1e80100-cpucp-mbox", "qcom,cpucp-mbox";
> This is not upstream
It's a new driver, so bindings patches will come with it.
>
> > + reg = <0 0x18830000 0 0x300>, <0 0x17430000 0 0x4C08>;
> lowercase hex
Will do.
>
> Konrad
next prev parent reply other threads:[~2023-12-14 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 10:24 [PATCH 0/2] arm64: dts: qcom: Add missing nodes to X1E80100 base dtsi and CRD dts Abel Vesa
2023-12-12 10:24 ` [PATCH 1/2] arm64: dts: qcom: x1e80100: Add all missing nodes Abel Vesa
2023-12-12 16:21 ` Konrad Dybcio
2023-12-14 15:33 ` Abel Vesa [this message]
2023-12-14 15:39 ` Krzysztof Kozlowski
2023-12-14 21:37 ` Abel Vesa
2023-12-12 10:24 ` [PATCH 2/2] arm64: dts: qcom: x1e80100: Add missing nodes for CRD Abel Vesa
2023-12-12 16:22 ` 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=ZXsgYl2h+MnTIz7D@linaro.org \
--to=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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_rjendra@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.