From: Rob Herring <robh@kernel.org>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] phy: rcar-gen3-usb2: add fallback binding
Date: Fri, 4 Mar 2016 22:28:03 -0600 [thread overview]
Message-ID: <20160305042803.GQ13525@rob-hp-laptop> (raw)
In-Reply-To: <1456965518-13615-3-git-send-email-horms+renesas@verge.net.au>
On Thu, Mar 03, 2016 at 09:38:38AM +0900, Simon Horman wrote:
> In the case of Renesas R-Car hardware we know that there are generations of
> SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the
> relationship between IP blocks might be. For example, I believe that
> r8a7790 is older than r8a7791 but that doesn't imply that the latter is a
> descendant of the former or vice versa.
>
> We can, however, by examining the documentation and behaviour of the
> hardware at run-time observe that the current driver implementation appears
> to be compatible with the IP blocks on SoCs within a given generation.
>
> For the above reasons and convenience when enabling new SoCs a
> per-generation fallback compatibility string scheme being adopted for
> drivers for Renesas SoCs.
>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> ---
> v2
> * Use renesas,rcar-gen3-usb-phy rather than renesas,usb-phy-gen3 as
> the new compatibility string to fit in with the preferred scheme
> for new compatibility string names.
> ---
> Documentation/devicetree/bindings/phy/rcar-gen3-phy-usb2.txt | 10 ++++++++--
> drivers/phy/phy-rcar-gen3-usb2.c | 1 +
> 2 files changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/phy/rcar-gen3-phy-usb2.txt b/Documentation/devicetree/bindings/phy/rcar-gen3-phy-usb2.txt
> index eaf7e9b7ce6b..86826ca2fdef 100644
> --- a/Documentation/devicetree/bindings/phy/rcar-gen3-phy-usb2.txt
> +++ b/Documentation/devicetree/bindings/phy/rcar-gen3-phy-usb2.txt
> @@ -6,6 +6,12 @@ This file provides information on what the device node for the R-Car generation
> Required properties:
> - compatible: "renesas,usb2-phy-r8a7795" if the device is a part of an R8A7795
> SoC.
> + "renesas,rcar-gen3-usb2-phy" for a generic R-Car Gen3 compatible device.
> +
> + When compatible with the generic version, nodes must list the
> + SoC-specific version corresponding to the platform first
> + followed by the generic version.
> +
> - reg: offset and length of the partial USB 2.0 Host register block.
> - clocks: clock phandle and specifier pair(s).
> - #phy-cells: see phy-bindings.txt in the same directory, must be <0>.
> @@ -19,14 +25,14 @@ channel as USB OTG:
> Example (R-Car H3):
>
> usb-phy@ee080200 {
> - compatible = "renesas,usb2-phy-r8a7795";
> + compatible = "renesas,usb2-phy-r8a7795","renesas,rcar-gen3-usb2-phy";
space...
> reg = <0 0xee080200 0 0x700>;
> interrupts = <GIC_SPI 108 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&mstp7_clks R8A7795_CLK_EHCI0>;
> };
>
> usb-phy@ee0a0200 {
> - compatible = "renesas,usb2-phy-r8a7795";
> + compatible = "renesas,usb2-phy-r8a7795","renesas,rcar-gen3-usb2-phy";
space...
Otherwise,
Acked-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2016-03-05 4:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 0:38 [PATCH v2 0/2] phy: rcar-gen2, rcar-gen3-usb2: add fallback binding Simon Horman
[not found] ` <1456965518-13615-1-git-send-email-horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2016-03-03 0:38 ` [PATCH v2 1/2] phy: rcar-gen2: " Simon Horman
2016-03-03 8:12 ` Geert Uytterhoeven
[not found] ` <1456965518-13615-2-git-send-email-horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2016-03-05 4:27 ` Rob Herring
2016-03-03 0:38 ` [PATCH v2 2/2] phy: rcar-gen3-usb2: " Simon Horman
2016-03-03 8:13 ` Geert Uytterhoeven
[not found] ` <CAMuHMdW24p_nx19232LADRMHY8-976YX-S41zEGQhmoe+3_AxQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-03 9:23 ` Yoshihiro Shimoda
2016-03-05 4:28 ` Rob Herring [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=20160305042803.GQ13525@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=yoshihiro.shimoda.uh@renesas.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