linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	DTML <devicetree@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: mmc: renesas_sdhi: Document r8a77961 support
Date: Tue, 10 Dec 2019 14:09:54 +0100	[thread overview]
Message-ID: <CAPDyKFrccGjrVJhL3Hwu0Adg7e-rRs2hdkMe1mS6G2RbHF6WJw@mail.gmail.com> (raw)
In-Reply-To: <20191205134349.6410-2-geert+renesas@glider.be>

On Thu, 5 Dec 2019 at 14:43, Geert Uytterhoeven <geert+renesas@glider.be> wrote:
>
> Document support for the SDHI controller in the Renesas R-Car M3-W+
> (R8A77961) SoC.
>
> Update all references to R-Car M3-W from "r8a7796" to "r8a77960", to
> avoid confusion between R-Car M3-W (R8A77960) and M3-W+.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

Applied for next, thanks!

Kind regards
Uffe


> ---
> No driver update is needed if "[PATCH] mmc: renesas_sdhi: remove
> whitelist for internal DMAC"[1] makes it in first.
>
> [1] https://lore.kernel.org/linux-mmc/20191203194859.917-1-wsa@the-dreams.de/
> ---
>  Documentation/devicetree/bindings/mmc/renesas,sdhi.txt | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/mmc/renesas,sdhi.txt b/Documentation/devicetree/bindings/mmc/renesas,sdhi.txt
> index bc08fc43a9be466b..e6cc47844207049b 100644
> --- a/Documentation/devicetree/bindings/mmc/renesas,sdhi.txt
> +++ b/Documentation/devicetree/bindings/mmc/renesas,sdhi.txt
> @@ -23,7 +23,8 @@ Required properties:
>                 "renesas,sdhi-r8a7793" - SDHI IP on R8A7793 SoC
>                 "renesas,sdhi-r8a7794" - SDHI IP on R8A7794 SoC
>                 "renesas,sdhi-r8a7795" - SDHI IP on R8A7795 SoC
> -               "renesas,sdhi-r8a7796" - SDHI IP on R8A7796 SoC
> +               "renesas,sdhi-r8a7796" - SDHI IP on R8A77960 SoC
> +               "renesas,sdhi-r8a77961" - SDHI IP on R8A77961 SoC
>                 "renesas,sdhi-r8a77965" - SDHI IP on R8A77965 SoC
>                 "renesas,sdhi-r8a77970" - SDHI IP on R8A77970 SoC
>                 "renesas,sdhi-r8a77980" - SDHI IP on R8A77980 SoC
> --
> 2.17.1
>

  reply	other threads:[~2019-12-10 13:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 13:43 [PATCH 0/2] mmc: renesas_sdhi: Add r8a77961 support Geert Uytterhoeven
2019-12-05 13:43 ` [PATCH 1/2] dt-bindings: mmc: renesas_sdhi: Document " Geert Uytterhoeven
2019-12-10 13:09   ` Ulf Hansson [this message]
2019-12-05 13:43 ` [PATCH 2/2] mmc: renesas_sdhi_internal_dmac: Add " Geert Uytterhoeven
2019-12-05 17:54 ` [PATCH 0/2] mmc: renesas_sdhi: " Niklas Söderlund

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=CAPDyKFrccGjrVJhL3Hwu0Adg7e-rRs2hdkMe1mS6G2RbHF6WJw@mail.gmail.com \
    --to=ulf.hansson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --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 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).