From: "Heiko Stübner" <heiko@sntech.de>
To: Rob Herring <robh@kernel.org>, Niklas Cassel <Niklas.Cassel@wdc.com>
Cc: "Niklas Cassel" <nks@flawful.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Shawn Lin" <shawn.lin@rock-chips.com>,
"Simon Xue" <xxm@rock-chips.com>,
"Damien Le Moal" <dlemoal@kernel.org>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Serge Semin" <fancer.lancer@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH v3 1/6] dt-bindings: PCI: dwc: rockchip: Add mandatory atu reg
Date: Fri, 27 Oct 2023 19:07:00 +0200 [thread overview]
Message-ID: <3040634.xgJ6IN8ObU@diego> (raw)
In-Reply-To: <ZTvh51PGCBhSjURY@x1-carbon>
Hi Niklas,
Am Freitag, 27. Oktober 2023, 18:14:32 CEST schrieb Niklas Cassel:
> On Fri, Oct 27, 2023 at 10:58:28AM -0500, Rob Herring wrote:
> > On Fri, Oct 27, 2023 at 9:56 AM Niklas Cassel <nks@flawful.org> wrote:
> > >
> > > From: Niklas Cassel <niklas.cassel@wdc.com>
> > >
> > > Even though rockchip-dw-pcie.yaml inherits snps,dw-pcie.yaml
> > > using:
> > >
> > > allOf:
> > > - $ref: /schemas/pci/snps,dw-pcie.yaml#
> > >
> > > and snps,dw-pcie.yaml does have the atu reg defined, in order to be
> > > able to use this reg, while still making sure 'make CHECK_DTBS=y'
> > > pass, we need to add this reg to rockchip-dw-pcie.yaml.
> > >
> > > All compatible strings (rockchip,rk3568-pcie and rockchip,rk3588-pcie)
> > > should have this reg.
> > >
> > > The regs in the example are updated to actually match pcie3x2 on rk3568.
> >
> > Breaking compatibility on these platforms is okay because ...?
>
> I don't follow, could you please elaborate?
you're adding the atu reg unconditionally as required element.
Newer kernel versions (strongly) _should_ work with older devicetrees.
So a kernel with that change should also work with a dtb build from the
old style.
DTBs are essentially part of the device firmware, so while some devices
can update theirs easily, you can't really require a dtb update.
I guess you could something like:
reg-names:
oneOf:
- deprecated: true
items:
- const: dbi
- const: apb
- const: config
- items:
- const: dbi
- const: apb
- const: config
- const: atu
(may not be accurate and to spec yet)
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Rob Herring <robh@kernel.org>, Niklas Cassel <Niklas.Cassel@wdc.com>
Cc: "Niklas Cassel" <nks@flawful.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Shawn Lin" <shawn.lin@rock-chips.com>,
"Simon Xue" <xxm@rock-chips.com>,
"Damien Le Moal" <dlemoal@kernel.org>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Serge Semin" <fancer.lancer@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH v3 1/6] dt-bindings: PCI: dwc: rockchip: Add mandatory atu reg
Date: Fri, 27 Oct 2023 19:07:00 +0200 [thread overview]
Message-ID: <3040634.xgJ6IN8ObU@diego> (raw)
In-Reply-To: <ZTvh51PGCBhSjURY@x1-carbon>
Hi Niklas,
Am Freitag, 27. Oktober 2023, 18:14:32 CEST schrieb Niklas Cassel:
> On Fri, Oct 27, 2023 at 10:58:28AM -0500, Rob Herring wrote:
> > On Fri, Oct 27, 2023 at 9:56 AM Niklas Cassel <nks@flawful.org> wrote:
> > >
> > > From: Niklas Cassel <niklas.cassel@wdc.com>
> > >
> > > Even though rockchip-dw-pcie.yaml inherits snps,dw-pcie.yaml
> > > using:
> > >
> > > allOf:
> > > - $ref: /schemas/pci/snps,dw-pcie.yaml#
> > >
> > > and snps,dw-pcie.yaml does have the atu reg defined, in order to be
> > > able to use this reg, while still making sure 'make CHECK_DTBS=y'
> > > pass, we need to add this reg to rockchip-dw-pcie.yaml.
> > >
> > > All compatible strings (rockchip,rk3568-pcie and rockchip,rk3588-pcie)
> > > should have this reg.
> > >
> > > The regs in the example are updated to actually match pcie3x2 on rk3568.
> >
> > Breaking compatibility on these platforms is okay because ...?
>
> I don't follow, could you please elaborate?
you're adding the atu reg unconditionally as required element.
Newer kernel versions (strongly) _should_ work with older devicetrees.
So a kernel with that change should also work with a dtb build from the
old style.
DTBs are essentially part of the device firmware, so while some devices
can update theirs easily, you can't really require a dtb update.
I guess you could something like:
reg-names:
oneOf:
- deprecated: true
items:
- const: dbi
- const: apb
- const: config
- items:
- const: dbi
- const: apb
- const: config
- const: atu
(may not be accurate and to spec yet)
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Rob Herring <robh@kernel.org>, Niklas Cassel <Niklas.Cassel@wdc.com>
Cc: "Niklas Cassel" <nks@flawful.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Shawn Lin" <shawn.lin@rock-chips.com>,
"Simon Xue" <xxm@rock-chips.com>,
"Damien Le Moal" <dlemoal@kernel.org>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Serge Semin" <fancer.lancer@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH v3 1/6] dt-bindings: PCI: dwc: rockchip: Add mandatory atu reg
Date: Fri, 27 Oct 2023 19:07:00 +0200 [thread overview]
Message-ID: <3040634.xgJ6IN8ObU@diego> (raw)
In-Reply-To: <ZTvh51PGCBhSjURY@x1-carbon>
Hi Niklas,
Am Freitag, 27. Oktober 2023, 18:14:32 CEST schrieb Niklas Cassel:
> On Fri, Oct 27, 2023 at 10:58:28AM -0500, Rob Herring wrote:
> > On Fri, Oct 27, 2023 at 9:56 AM Niklas Cassel <nks@flawful.org> wrote:
> > >
> > > From: Niklas Cassel <niklas.cassel@wdc.com>
> > >
> > > Even though rockchip-dw-pcie.yaml inherits snps,dw-pcie.yaml
> > > using:
> > >
> > > allOf:
> > > - $ref: /schemas/pci/snps,dw-pcie.yaml#
> > >
> > > and snps,dw-pcie.yaml does have the atu reg defined, in order to be
> > > able to use this reg, while still making sure 'make CHECK_DTBS=y'
> > > pass, we need to add this reg to rockchip-dw-pcie.yaml.
> > >
> > > All compatible strings (rockchip,rk3568-pcie and rockchip,rk3588-pcie)
> > > should have this reg.
> > >
> > > The regs in the example are updated to actually match pcie3x2 on rk3568.
> >
> > Breaking compatibility on these platforms is okay because ...?
>
> I don't follow, could you please elaborate?
you're adding the atu reg unconditionally as required element.
Newer kernel versions (strongly) _should_ work with older devicetrees.
So a kernel with that change should also work with a dtb build from the
old style.
DTBs are essentially part of the device firmware, so while some devices
can update theirs easily, you can't really require a dtb update.
I guess you could something like:
reg-names:
oneOf:
- deprecated: true
items:
- const: dbi
- const: apb
- const: config
- items:
- const: dbi
- const: apb
- const: config
- const: atu
(may not be accurate and to spec yet)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-27 17:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 14:54 [PATCH v3 0/6] rockchip DWC PCIe improvements Niklas Cassel
2023-10-27 14:54 ` [PATCH v3 1/6] dt-bindings: PCI: dwc: rockchip: Add mandatory atu reg Niklas Cassel
2023-10-27 15:58 ` Rob Herring
2023-10-27 16:14 ` Niklas Cassel
2023-10-27 17:03 ` Rob Herring
2023-10-27 17:03 ` Rob Herring
2023-10-27 17:03 ` Rob Herring
2023-10-28 12:11 ` Niklas Cassel
2023-10-28 12:11 ` Niklas Cassel
2023-10-28 12:11 ` Niklas Cassel
2023-10-30 17:39 ` Rob Herring
2023-10-30 17:39 ` Rob Herring
2023-10-30 17:39 ` Rob Herring
2023-10-27 17:07 ` Heiko Stübner [this message]
2023-10-27 17:07 ` Heiko Stübner
2023-10-27 17:07 ` Heiko Stübner
2023-10-27 14:54 ` [PATCH v3 2/6] dt-bindings: PCI: dwc: rockchip: Add optional dma interrupts Niklas Cassel
2023-10-30 17:40 ` Rob Herring
2023-10-30 17:40 ` Rob Herring
2023-10-30 17:40 ` Rob Herring
2023-10-31 1:10 ` Serge Semin
2023-10-31 1:10 ` Serge Semin
2023-10-31 1:10 ` Serge Semin
2023-10-31 15:51 ` Niklas Cassel
2023-10-31 15:51 ` Niklas Cassel
2023-10-31 15:51 ` Niklas Cassel
2023-11-01 22:23 ` Bjorn Helgaas
2023-11-01 22:23 ` Bjorn Helgaas
2023-11-01 22:23 ` Bjorn Helgaas
2023-10-27 14:54 ` [PATCH v3 3/6] arm64: dts: rockchip: drop unused properties num-{ib,ob}-windows Niklas Cassel
2023-10-31 1:14 ` Serge Semin
2023-10-31 1:14 ` Serge Semin
2023-10-31 1:14 ` Serge Semin
2023-10-27 14:54 ` [PATCH v3 4/6] arm64: dts: rockchip: add missing mandatory rk3568 PCIe atu reg Niklas Cassel
2023-10-27 14:54 ` [PATCH v3 5/6] arm64: dts: rockchip: add missing mandatory rk3588 " Niklas Cassel
2023-10-27 14:54 ` [PATCH v3 6/6] arm64: dts: rockchip: add missing rk3588 PCIe eDMA interrupts Niklas Cassel
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=3040634.xgJ6IN8ObU@diego \
--to=heiko@sntech.de \
--cc=Niklas.Cassel@wdc.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlemoal@kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=nks@flawful.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=shawn.lin@rock-chips.com \
--cc=xxm@rock-chips.com \
/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.