public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Sandom <jsandom@axon.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] arm64: dts: qcom: qcs8550: add QCS8550 RB5Gen2 board support
Date: Tue, 7 Apr 2026 16:43:27 +0100	[thread overview]
Message-ID: <20260407154327.pbexm4jkttp6rdjl@linaro> (raw)
In-Reply-To: <s4g54pra266y6p2j3f4fps56naw4hm4vzuai5sgpf7sdbbewj2@3j2tkqd3qgdn>

On Tue, Apr 07, 2026 at 06:01:34PM +0300, Dmitry Baryshkov wrote:
> On Tue, Apr 07, 2026 at 12:39:25PM +0100, Joe Sandom wrote:
> > On Sun, Apr 05, 2026 at 12:20:23AM +0300, Dmitry Baryshkov wrote:
> > > On Sat, Apr 04, 2026 at 10:50:58AM +0100, Joe Sandom via B4 Relay wrote:
> > > > +
> > > > +	wcn7850-pmu {
> > > > +		compatible = "qcom,wcn7850-pmu";
> > > > +
> > > > +		pinctrl-names = "default";
> > > > +		pinctrl-0 = <&wlan_en>, <&bt_default>, <&pmk8550_sleep_clk>;
> > > 
> > > swctrl?
> > Bundled into bt_default since it's tied to BT
> 
> It's not. It's either WiFi or BT.
Ack. Will fix in v2.
> 
> > > 
> > > > +
> > > > +		wlan-enable-gpios = <&tlmm 80 GPIO_ACTIVE_HIGH>;
> > > > +		bt-enable-gpios = <&tlmm 81 GPIO_ACTIVE_HIGH>;
> > > 
> 
> [...]
> 
> > > > +	iommu-map = <0x0 &apps_smmu 0x1400 0x1>,
> > > > +		    <0x100 &apps_smmu 0x1401 0x1>,
> > > > +		    <0x208 &apps_smmu 0x1402 0x1>,
> > > > +		    <0x210 &apps_smmu 0x1403 0x1>,
> > > > +		    <0x218 &apps_smmu 0x1404 0x1>,
> > > > +		    <0x300 &apps_smmu 0x1407 0x1>,
> > > > +		    <0x400 &apps_smmu 0x1408 0x1>,
> > > > +		    <0x500 &apps_smmu 0x140c 0x1>,
> > > > +		    <0x501 &apps_smmu 0x140e 0x1>;
> > > > +
> > > > +	/delete-property/ msi-map;
> > > 
> > > Why?
> > I tried extending the msi-map to cover the RIDs from the QPS615
> > PCIe switch (matching the iommu-map entries), but this caused
> > ITS MAPD command timeouts. From what I could gather, deleting
> > msi-map forces the PCIe controller to fall back to the internal
> > iMSI-RX module, where this worked properly.
> > 
> > For reference, I checked the RB3gen2 since it also uses a QPS615
> > and there doesn't seem to be any msi-map defined (in kodiak.dtsi).
> > 
> > Any recommendations to resolve this properly?
> 
> Maybe Mani knows. Please mention this in the commit message at least.
> 
Will do.
> > > 
> > > > +
> > > > +	status = "okay";
> > > > +};
> > > > +
> 
> -- 
> With best wishes
> Dmitry
Thanks for the review Dmitry

  reply	other threads:[~2026-04-07 15:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-04  9:50 [PATCH 0/5] arm64: dts: qcom: add QCS8550 RB5Gen2 support Joe Sandom via B4 Relay
2026-04-04  9:50 ` [PATCH 1/5] arm64: dts: qcom: sm8550: add PCIe MHI register regions and port labels Joe Sandom via B4 Relay
2026-04-04 21:07   ` Dmitry Baryshkov
2026-04-07  8:53     ` Joe Sandom
2026-04-07 11:05   ` Konrad Dybcio
2026-04-07 11:43     ` Joe Sandom
2026-04-04  9:50 ` [PATCH 2/5] arm64: dts: qcom: sm8550-hdk: update PCIe port label reference Joe Sandom via B4 Relay
2026-04-04 21:07   ` Dmitry Baryshkov
2026-04-07  8:55     ` Joe Sandom
2026-04-05  8:11   ` Krzysztof Kozlowski
2026-04-04  9:50 ` [PATCH 3/5] arm64: dts: qcom: sm8550-qrd: " Joe Sandom via B4 Relay
2026-04-04  9:50 ` [PATCH 4/5] dt-bindings: arm: qcom: document QCS8550 RB5Gen2 board Joe Sandom via B4 Relay
2026-04-05  8:11   ` Krzysztof Kozlowski
2026-04-04  9:50 ` [PATCH 5/5] arm64: dts: qcom: qcs8550: add QCS8550 RB5Gen2 board support Joe Sandom via B4 Relay
2026-04-04 21:20   ` Dmitry Baryshkov
2026-04-07 11:39     ` Joe Sandom
2026-04-07 15:01       ` Dmitry Baryshkov
2026-04-07 15:43         ` Joe Sandom [this message]
2026-04-07 16:14       ` Manivannan Sadhasivam

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=20260407154327.pbexm4jkttp6rdjl@linaro \
    --to=jsandom@axon.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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