All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Bharat Kumar Gogada <bharatku@xilinx.com>
Cc: Michal Simek <michals@xilinx.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
	"bhelgaas@google.com" <bhelgaas@google.com>
Subject: Re: [PATCH v2] dt-bindings: PCI: xilinx-cpm: Fix reg property order
Date: Wed, 1 Jun 2022 14:53:48 -0500	[thread overview]
Message-ID: <20220601195348.GA320367-robh@kernel.org> (raw)
In-Reply-To: <BY5PR02MB69472D35FC4774C5B49FC19CA5D69@BY5PR02MB6947.namprd02.prod.outlook.com>

On Wed, May 25, 2022 at 11:03:32AM +0000, Bharat Kumar Gogada wrote:
> Hi Rob,
> 
> Can you please check this.

You can look at patchwork[1] and see where your patch is in the queue. 
No need to send me more emails.

Rob

[1] https://patchwork.ozlabs.org/project/devicetree-bindings/list/

> 
> Regards,
> Bharat
> 
> > 
> > On 5/16/22 12:22, Bharat Kumar Gogada wrote:
> > > All existing vendor DTSes are using "cpm_slcr" reg followed by "cfg" reg.
> > >
> > > This order is also suggested by node name which is pcie@fca10000 which
> > > suggests that cpm_slcr register should be the first.
> > >
> > > Driver itself is using devm_platform_ioremap_resource_byname() for
> > > both names that's why there is no functional change even on
> > > description which are using current order.
> > >
> > > But still prefer to change order to cover currently used description.
> > > Fixes: e22fadb1d014 ("PCI: xilinx-cpm: Add YAML schemas for Versal CPM
> > > Root Port")
> > >
> > > Signed-off-by: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
> > > ---
> > >   .../devicetree/bindings/pci/xilinx-versal-cpm.yaml     | 10 +++++-----
> > >   1 file changed, 5 insertions(+), 5 deletions(-)
> > >
> > > diff --git
> > > a/Documentation/devicetree/bindings/pci/xilinx-versal-cpm.yaml
> > > b/Documentation/devicetree/bindings/pci/xilinx-versal-cpm.yaml
> > > index 32f4641085bc..cca395317a4c 100644
> > > --- a/Documentation/devicetree/bindings/pci/xilinx-versal-cpm.yaml
> > > +++ b/Documentation/devicetree/bindings/pci/xilinx-versal-cpm.yaml
> > > @@ -18,13 +18,13 @@ properties:
> > >
> > >     reg:
> > >       items:
> > > -      - description: Configuration space region and bridge registers.
> > >         - description: CPM system level control and status registers.
> > > +      - description: Configuration space region and bridge registers.
> > >
> > >     reg-names:
> > >       items:
> > > -      - const: cfg
> > >         - const: cpm_slcr
> > > +      - const: cfg
> > >
> > >     interrupts:
> > >       maxItems: 1
> > > @@ -86,9 +86,9 @@ examples:
> > >                          ranges = <0x02000000 0x0 0xe0000000 0x0 0xe0000000 0x0
> > 0x10000000>,
> > >                                   <0x43000000 0x80 0x00000000 0x80 0x00000000 0x0
> > 0x80000000>;
> > >                          msi-map = <0x0 &its_gic 0x0 0x10000>;
> > > -                       reg = <0x6 0x00000000 0x0 0x10000000>,
> > > -                             <0x0 0xfca10000 0x0 0x1000>;
> > > -                       reg-names = "cfg", "cpm_slcr";
> > > +                       reg = <0x0 0xfca10000 0x0 0x1000>,
> > > +                             <0x6 0x00000000 0x0 0x10000000>;
> > > +                       reg-names = "cpm_slcr", "cfg";
> > >                          pcie_intc_0: interrupt-controller {
> > >                                  #address-cells = <0>;
> > >                                  #interrupt-cells = <1>;
> > 
> > Reviewed-by: Michal Simek <michal.simek@amd.com>
> > 
> > Thanks,
> > Michal

  reply	other threads:[~2022-06-01 20:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 10:22 [PATCH v2] dt-bindings: PCI: xilinx-cpm: Fix reg property order Bharat Kumar Gogada
2022-05-16 11:17 ` Michal Simek
2022-05-25 11:03   ` Bharat Kumar Gogada
2022-06-01 19:53     ` Rob Herring [this message]
2022-06-01 19:55 ` Rob Herring
2022-06-03  4:52   ` Bharat Kumar Gogada

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=20220601195348.GA320367-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=bharatku@xilinx.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=michals@xilinx.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.