From: Aswath Govindraju <a-govindraju@ti.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Rob Herring <robh+dt@kernel.org>, <linux-pci@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: PCI: ti,j721e: Add device id for J721S2
Date: Tue, 25 Jan 2022 12:06:16 +0530 [thread overview]
Message-ID: <ab490690-eac2-c714-1359-b4058e2f98ff@ti.com> (raw)
In-Reply-To: <20211130035608.13492-1-a-govindraju@ti.com>
Hi Bjorn,
On 30/11/21 9:26 am, Aswath Govindraju wrote:
> Document the device id of J721S2 SoC.
>
> Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
> ---
>
May I know if this patch can be picked up?
Thanks,
Aswath
> changes since v1:
> - changed (oneOf, items) into enum
>
> .../devicetree/bindings/pci/ti,j721e-pci-host.yaml | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pci/ti,j721e-pci-host.yaml b/Documentation/devicetree/bindings/pci/ti,j721e-pci-host.yaml
> index cc900202df29..41df8f1c2d4c 100644
> --- a/Documentation/devicetree/bindings/pci/ti,j721e-pci-host.yaml
> +++ b/Documentation/devicetree/bindings/pci/ti,j721e-pci-host.yaml
> @@ -64,13 +64,11 @@ properties:
> const: 0x104c
>
> device-id:
> - oneOf:
> - - items:
> - - const: 0xb00d
> - - items:
> - - const: 0xb00f
> - - items:
> - - const: 0xb010
> + enum:
> + - 0xb00d
> + - 0xb00f
> + - 0xb010
> + - 0xb013
>
> msi-map: true
>
>
next prev parent reply other threads:[~2022-01-25 6:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 3:56 [PATCH v2] dt-bindings: PCI: ti,j721e: Add device id for J721S2 Aswath Govindraju
2021-12-07 21:14 ` Rob Herring
2022-01-25 6:36 ` Aswath Govindraju [this message]
2022-01-27 15:23 ` Bjorn Helgaas
2022-01-27 18:25 ` Rob Herring
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=ab490690-eac2-c714-1359-b4058e2f98ff@ti.com \
--to=a-govindraju@ti.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).