From: Simon Horman <horms+renesas@verge.net.au>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Simon Horman <horms+renesas@verge.net.au>
Subject: [PATCH v3 0/2] phy: rcar-gen2, rcar-gen3-usb2: add fallback binding
Date: Mon, 7 Mar 2016 10:58:39 +0900 [thread overview]
Message-ID: <1457315921-30217-1-git-send-email-horms+renesas@verge.net.au> (raw)
Add fallback compatibility strings for rcar phy drivers.
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.
Changes in v3:
* Added Acks
* Corrected whitespace in examples
Changes in v2:
* Update new compatibility strings to match the preferred scheme for
ordering elements
* Rebase
Simon Horman (2):
phy: rcar-gen2: add fallback binding
phy: rcar-gen3-usb2: add fallback binding
Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt | 8 +++++++-
Documentation/devicetree/bindings/phy/rcar-gen3-phy-usb2.txt | 10 ++++++++--
drivers/phy/phy-rcar-gen2.c | 1 +
drivers/phy/phy-rcar-gen3-usb2.c | 1 +
4 files changed, 17 insertions(+), 3 deletions(-)
--
2.1.4
next reply other threads:[~2016-03-07 1:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 1:58 Simon Horman [this message]
2016-03-07 1:58 ` [PATCH v3 1/2] phy: rcar-gen2: add fallback binding Simon Horman
2016-03-07 1:58 ` [PATCH v3 2/2] phy: rcar-gen3-usb2: " Simon Horman
2016-03-25 2:09 ` [PATCH v3 0/2] phy: rcar-gen2, " Simon Horman
2016-04-07 9:47 ` Kishon Vijay Abraham I
2016-04-29 8:28 ` Kishon Vijay Abraham I
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=1457315921-30217-1-git-send-email-horms+renesas@verge.net.au \
--to=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;
as well as URLs for NNTP newsgroup(s).