mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Elder <elder@riscstar.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, arnd@arndb.de,
	bhelgaas@google.com, abelvesa@kernel.org, daniel@riscstar.com,
	mohd.anwar@oss.qualcomm.com, lorenzo.bianconi@oss.qualcomm.com,
	devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/3] arm64: dts: qcom: qcs6490-rb3gen2: add endpoint buses
Date: Fri, 2 Oct 2026 08:16:47 +0200	[thread overview]
Message-ID: <2026100234-chaos-density-47c4@gregkh> (raw)
In-Reply-To: <9c426950-b3f3-42fd-b31d-f14085a7d2d1@riscstar.com>

On Thu, Oct 01, 2026 at 02:19:14PM -0500, Alex Elder wrote:
> On 10/1/26 7:06 AM, Greg KH wrote:
> > On Fri, Sep 18, 2026 at 10:26:58AM -0500, Alex Elder wrote:
> > > The TC9564 SoC incorporates a PCIe switch, which is connected via
> > > the second PCI segment (0001) on the RB3gen2 platform.  The third
> > > downstream port of that switch (pcie@3,0) has an embedded PCIe
> > > endpoint that implements two PCIe functions.
> > > 
> > > The SoC implements other peripherals, and they will be accessed via
> > > PCI endpoint bus.  Define the devicetree nodes representing these
> > > buses, including the mapping of each BAR's address range to its
> > > local address space.
> > > 
> > > The endpoint's ranges property must be defined, but it will be
> > > updated dynamically to include all BARs.  As a result of this update,
> > > the parent address portion of each range will reflect the specific
> > > address assigned to the BAR.
> > > 
> > > Co-developed-by: Daniel Thompson <daniel@riscstar.com>
> > > Signed-off-by: Daniel Thompson <daniel@riscstar.com>
> > > Signed-off-by: Alex Elder <elder@riscstar.com>
> > > ---
> > >   arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts | 30 ++++++++++++++++++++
> > >   1 file changed, 30 insertions(+)
> > > 
> > > diff --git a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts
> > > index 3bb5fca8e2b13..5b7f5292a8864 100644
> > > --- a/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts
> > > +++ b/arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts
> > > @@ -955,11 +955,41 @@ pcie@3,0 {
> > >   			bus-range = <0x5 0xff>;
> > >   			dev@0,0 {
> > > +				compatible = "pci1179,0220";
> > >   				reg = <0x50000 0x0 0x0 0x0 0x0>;
> > > +				#address-cells = <3>;
> > > +				#size-cells = <2>;
> > > +				/* Ranges will be updated dynamically */
> > > +				ranges = <0x0 0x0 0x0  0x83050000 0x0 0x0  0x0 0x4000>,
> > > +					 <0x2 0x0 0x0  0x83050000 0x0 0x4000  0x0 0x80000>,
> > > +					 <0x4 0x0 0x0  0x83050000 0x0 0x84000  0x0 0x200000>;
> > > +
> > > +				pci-ep-bus@4 {
> > > +					compatible = "simple-bus";
> > > +					#address-cells = <1>;
> > > +					#size-cells = <1>;
> > > +					/* Map 0x0-0x1fffff to BAR 4 */
> > > +					ranges = <0x0  0x4 0x0 0x0  0x200000>;
> > > +				};
> > >   			};
> > >   			dev@0,1 {
> > > +				compatible = "pci1179,0220";
> > >   				reg = <0x50100 0x0 0x0 0x0 0x0>;
> > > +				#address-cells = <3>;
> > > +				#size-cells = <2>;
> > > +				/* Ranges will be updated dynamically */
> > > +				ranges = <0x0 0x0 0x0  0x83050100 0x0 0x0  0x0 0x4000>,
> > > +					 <0x2 0x0 0x0  0x83050100 0x0 0x4000  0x0 0x80000>,
> > > +					 <0x4 0x0 0x0  0x83050100 0x0 0x84000  0x0 0x200000>;
> > > +
> > > +				pci-ep-bus@4 {
> > > +					compatible = "simple-bus";
> > > +					#address-cells = <1>;
> > > +					#size-cells = <1>;
> > > +					/* Map 0x0-0x1fffff to BAR 4 */
> > > +					ranges = <0x0  0x4 0x0 0x0  0x200000>;
> > > +				};
> > >   			};
> > >   		};
> > >   	};
> > > -- 
> > > 2.53.0
> > > 
> > 
> > This doesn't apply to the char-misc-testing branch :(
> 
> Sorry about that.  It does apply to to the for-next branch for
> Qualcomm, so this should probably get merged through that path.
> 
> https://lore.kernel.org/lkml/20260918152659.413268-1-elder@riscstar.com/

I suggest sending it to whoever maintains that tree.

      reply	other threads:[~2026-10-02  6:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 15:26 [PATCH v4 0/3] PCI: introduce TC9564 misc driver Alex Elder
2026-09-18 15:26 ` [PATCH v4 1/3] dt-bindings: misc: introduce pci1179,0220.yaml Alex Elder
2026-09-28 19:40   ` Rob Herring (Arm)
2026-09-18 15:26 ` [PATCH v4 2/3] misc: tc9564: introduce base PCI driver Alex Elder
2026-09-18 17:30   ` Bjorn Helgaas
2026-09-18 17:49     ` Alex Elder
2026-09-24 15:56       ` Herve Codina
2026-09-25  2:15         ` Alex Elder
2026-09-18 15:26 ` [PATCH v4 3/3] arm64: dts: qcom: qcs6490-rb3gen2: add endpoint buses Alex Elder
2026-10-01 12:06   ` Greg KH
2026-10-01 19:19     ` Alex Elder
2026-10-02  6:16       ` Greg KH [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=2026100234-chaos-density-47c4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=abelvesa@kernel.org \
    --cc=andersson@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel@riscstar.com \
    --cc=devicetree@vger.kernel.org \
    --cc=elder@riscstar.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.bianconi@oss.qualcomm.com \
    --cc=mohd.anwar@oss.qualcomm.com \
    --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

all inboxes | Powered by JetHome®