From: Bjorn Helgaas <helgaas@kernel.org>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Magnus Damm <magnus.damm@gmail.com>,
linux-pci@vger.kernel.org, linux-sh@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/4] PCI: rcar-gen2: Add device tree support for r8a7793
Date: Fri, 4 Dec 2015 15:26:50 -0600 [thread overview]
Message-ID: <20151204212649.GJ20125@localhost> (raw)
In-Reply-To: <1448954672-27236-3-git-send-email-horms+renesas@verge.net.au>
Hi Simon,
On Tue, Dec 01, 2015 at 04:24:30PM +0900, Simon Horman wrote:
> Simply document new compat strings.
> There appears to be no need for a driver updates.
>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> ---
> Documentation/devicetree/bindings/pci/pci-rcar-gen2.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/pci/pci-rcar-gen2.txt b/Documentation/devicetree/bindings/pci/pci-rcar-gen2.txt
> index b19be08a8113..7c231b3e5872 100644
> --- a/Documentation/devicetree/bindings/pci/pci-rcar-gen2.txt
> +++ b/Documentation/devicetree/bindings/pci/pci-rcar-gen2.txt
> @@ -8,6 +8,7 @@ OHCI and EHCI controllers.
> Required properties:
> - compatible: "renesas,pci-r8a7790" for the R8A7790 SoC;
> "renesas,pci-r8a7791" for the R8A7791 SoC;
> + "renesas,pci-r8a7793" for the R8A7793 SoC;
What's the benefit of adding a string here if the driver doesn't check
for it? Since the driver doesn't look for it, there's no way to test
anything.
It doesn't seem like this file is an authoritative source of names, so
if we add it here, there's the possibility the r8a7793 will be
canceled or renamed, and then we'd have to update this if the driver
ever did need an r8a7793-specific quirk. If we waited until the
driver actually needs a quirk, then we'd know exactly what name to
look for and we could update the driver, DT, and doc all together.
> "renesas,pci-r8a7794" for the R8A7794 SoC;
> "renesas,pci-gen2" for a generic R-Car Gen2 compatible device.
>
> --
> 2.1.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-12-04 21:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 7:24 [PATCH 0/4] PCI: rcar, rcar-gen2: More Gen2 compat strings Simon Horman
2015-12-01 7:24 ` [PATCH 1/4] PCI: rcar-gen2: Add generic compatibility string Simon Horman
[not found] ` <1448954672-27236-2-git-send-email-horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2015-12-01 8:41 ` Geert Uytterhoeven
2015-12-02 0:26 ` Simon Horman
2015-12-01 7:24 ` [PATCH 2/4] PCI: rcar-gen2: Add device tree support for r8a7793 Simon Horman
2015-12-04 21:26 ` Bjorn Helgaas [this message]
2015-12-05 10:38 ` Geert Uytterhoeven
2015-12-07 15:38 ` Bjorn Helgaas
2015-12-08 0:45 ` Simon Horman
2016-01-11 1:06 ` Simon Horman
2015-12-01 7:24 ` [PATCH 3/4] PCI: rcar: Add Gen2 fallback compatibility string Simon Horman
2015-12-07 15:39 ` Bjorn Helgaas
2015-12-01 7:24 ` [PATCH 4/4] PCI: rcar: Add device tree support for r8a7793 Simon Horman
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=20151204212649.GJ20125@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-pci@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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).