From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 06/10] phy: rcar-gen2: add fallback binding
Date: Wed, 14 Mar 2018 22:26:23 +0000 [thread overview]
Message-ID: <1521066383.23626.109.camel@codethink.co.uk> (raw)
In-Reply-To: <1520249954-29357-7-git-send-email-fabrizio.castro@bp.renesas.com>
On Mon, 2018-03-05 at 11:39 +0000, Fabrizio Castro wrote:
> From: Simon Horman <horms+renesas@verge.net.au>
>
> 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>
> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Acked-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
[...]
This is missing a reference to the upstream commit
(7777cb8ba08dabcab8dc0e91ac0a26dde675edb6).
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
next prev parent reply other threads:[~2018-03-14 22:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 11:39 [cip-dev] [PATCH 00/10] Add PCI and USB PHY support to iwg20d Fabrizio Castro
2018-03-05 11:39 ` [cip-dev] [PATCH 01/10] PCI: rcar: Add gen2 fallback compatibility string for pci-rcar-gen2 Fabrizio Castro
2018-03-05 11:39 ` [cip-dev] [PATCH 02/10] PCI: rcar-gen2: Use gen2 fallback compatibility last Fabrizio Castro
2018-03-05 11:39 ` [cip-dev] [PATCH 03/10] PCI: rcar: Add device tree support for r8a7743/5 Fabrizio Castro
2018-03-05 11:39 ` [cip-dev] [PATCH 04/10] ARM: dts: r8a7743: Add internal PCI bridge nodes Fabrizio Castro
2018-03-05 11:39 ` [cip-dev] [PATCH 05/10] phy: rcar-gen2: Add r8a7743/5 support Fabrizio Castro
2018-03-05 11:39 ` [cip-dev] [PATCH 06/10] phy: rcar-gen2: add fallback binding Fabrizio Castro
2018-03-14 22:26 ` Ben Hutchings [this message]
2018-03-15 15:47 ` Fabrizio Castro
2018-03-05 11:39 ` [cip-dev] [PATCH 07/10] ARM: dts: r8a7743: Add USB PHY DT support Fabrizio Castro
2018-03-05 11:39 ` [cip-dev] [PATCH 08/10] ARM: dts: r8a7743: Link PCI USB devices to USB PHY Fabrizio Castro
2018-03-05 11:39 ` [cip-dev] [PATCH 09/10] ARM: dts: iwg20d-q7: Enable internal PCI Fabrizio Castro
2018-03-05 11:39 ` [cip-dev] [PATCH 10/10] ARM: dts: iwg20d-q7: Enable USB PHY Fabrizio Castro
2018-04-10 17:14 ` [cip-dev] [PATCH 00/10] Add PCI and USB PHY support to iwg20d Ben Hutchings
2018-04-10 17:44 ` Fabrizio Castro
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=1521066383.23626.109.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/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