From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 1/4] spi: sh-msiof: Add R-Car Gen 2 and 3 fallback bindings
Date: Tue, 10 Apr 2018 18:33:40 +0100 [thread overview]
Message-ID: <1523381620.2654.194.camel@codethink.co.uk> (raw)
In-Reply-To: <1520530089-4988-2-git-send-email-fabrizio.castro@bp.renesas.com>
On Thu, 2018-03-08 at 17:28 +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 it's 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 is being adopted for
> drivers for Renesas SoCs.
>
> Also:
> * Deprecate renesas,sh-msiof. It seems poorly named as it is only
> ? compatible with SH-Mobile. It also appears unused in mainline.
>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> (cherry picked from commit 4286db8456f4fa0c6af2b6b9abc5991a7e7da69c)
> Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> (cherry picked from commit 77f252646eb0ec1e78847fe5725c98ee9e70b39e)
I deleted this second commit reference, which I assume refers to some
private branch.
Ben.
> (removed "renesas,rcar-gen3-msiof")
> Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
[...]
--
Ben Hutchings
Software Developer, Codethink Ltd.
next prev parent reply other threads:[~2018-04-10 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 17:28 [cip-dev] [PATCH 0/4] Add MSIOF support to r8a7743 Fabrizio Castro
2018-03-08 17:28 ` [cip-dev] [PATCH 1/4] spi: sh-msiof: Add R-Car Gen 2 and 3 fallback bindings Fabrizio Castro
2018-04-10 17:33 ` Ben Hutchings [this message]
2018-04-10 17:49 ` Fabrizio Castro
2018-03-08 17:28 ` [cip-dev] [PATCH 2/4] spi: sh-msiof: Add compatible strings for r8a774[35] Fabrizio Castro
2018-03-08 17:28 ` [cip-dev] [PATCH 3/4] spi: sh-msiof: Add r8a774[35] to the compatible list Fabrizio Castro
2018-03-08 17:28 ` [cip-dev] [PATCH 4/4] ARM: dts: r8a7743: Add MSIOF[012] support Fabrizio Castro
2018-04-10 17:40 ` [cip-dev] [PATCH 0/4] Add MSIOF support to r8a7743 Ben Hutchings
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=1523381620.2654.194.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