All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] mmc: renesas_sdhi: add R-Car Gen[123] fallback compatibility strings
Date: Fri, 20 Oct 2017 12:03:23 +0200	[thread overview]
Message-ID: <CAPDyKFoHBSj6j+ksfGtqyxiwWsS8CfNio-6TN4XyVGWji27qMQ@mail.gmail.com> (raw)
In-Reply-To: <20171018070023.3878-1-horms+renesas@verge.net.au>

On 18 October 2017 at 09:00, Simon Horman <horms+renesas@verge.net.au> wrote:
> Add fallback compatibility strings for R-Car Gen 1, 2 and 3 to the SDHI
> bindings and driver.
>
> In the case of Renesas R-Car hardware we know that there are generations of
> SoCs, f.e. Gen 1 and 2. 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 is being adopted for
> drivers for Renesas SoCs.
>
> Based on mmc/next
>
> Changes since v3:
> * Corrected typos in changelogs
> * Enhanced grammar in comatibility string usage text
>
> Changes since v2:
> * Update example to current upstream using newer CPG/MSSR bindings
>
> Changes since v1:
> * Describe example in patch one as being for the r8a7790 (R-Car H2) rather
>   than the r8a7779 (R-Car H1)
> * Accumulate review tags from Geert Uytterhoeven
>
> Simon Horman (3):
>   dt-bindings: mmc: renesas_sdhi: provide example in bindings
>     documentation
>   dt-bindings: mmc: renesas_sdhi: add R-Car Gen[123] fallback
>     compatibility strings
>   mmc: renesas_sdhi: implement R-Car Gen[123] fallback compatibility
>     strings
>
>  Documentation/devicetree/bindings/mmc/tmio_mmc.txt | 70 +++++++++++++++++++++-
>  drivers/mmc/host/renesas_sdhi_internal_dmac.c      |  1 +
>  drivers/mmc/host/renesas_sdhi_sys_dmac.c           |  5 +-
>  3 files changed, 74 insertions(+), 2 deletions(-)
>
> --
> 2.11.0
>

Thanks, applied for next!

Kind regards
Uffe

      parent reply	other threads:[~2017-10-20 10:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18  7:00 [PATCH v4 0/3] mmc: renesas_sdhi: add R-Car Gen[123] fallback compatibility strings Simon Horman
2017-10-18  7:00 ` [PATCH v4 1/3] dt-bindings: mmc: renesas_sdhi: provide example in bindings documentation Simon Horman
2017-10-18  7:24   ` Wolfram Sang
2017-10-18  7:00 ` [PATCH v4 2/3] dt-bindings: mmc: renesas_sdhi: add R-Car Gen[123] fallback compatibility strings Simon Horman
2017-10-18  7:24   ` Wolfram Sang
2017-10-18  7:00 ` [PATCH v4 3/3] mmc: renesas_sdhi: implement " Simon Horman
2017-10-18  7:25   ` Wolfram Sang
2017-10-20 10:03 ` Ulf Hansson [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=CAPDyKFoHBSj6j+ksfGtqyxiwWsS8CfNio-6TN4XyVGWji27qMQ@mail.gmail.com \
    --to=ulf.hansson@linaro.org \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.