All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Linux MMC List <linux-mmc@vger.kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Simon Horman <horms@verge.net.au>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] mmc: renesas_sdhi_internal_dmac: Add r8a774b1 support
Date: Wed, 2 Oct 2019 10:20:33 +0200	[thread overview]
Message-ID: <20191002082032.GC1388@ninjato> (raw)
In-Reply-To: <OSBPR01MB210339B59E1B57FFDB00038AB8810@OSBPR01MB2103.jpnprd01.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 466 bytes --]


> > Exactly. Is RZ/G2N affected?
> 
> No. RZ/G2N is not affected.  I have enabled HS400 mode on RZ/G2N board and without this patch it works fine.
> 
> Note:-
>  I also tested with quirk entry added in sdhi_quirks_match.  That is also works fine.

You can't really test if this is needed or not. You need confirmation
from the HW team. This is also why the patch is not upstream yet because
there is still more on-going investigation for the HW teams.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-10-02  8:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24  6:49 [PATCH] mmc: renesas_sdhi_internal_dmac: Add r8a774b1 support Biju Das
2019-09-26 14:21 ` Geert Uytterhoeven
2019-09-26 15:11   ` Biju Das
2019-09-26 15:45     ` Geert Uytterhoeven
2019-09-27  9:28       ` Biju Das
2019-10-02  8:20         ` Wolfram Sang [this message]
2019-10-04  6:25         ` Biju Das
2019-10-22  7:30           ` Biju Das
2019-10-23 15:16 ` Wolfram Sang
2019-10-24  6:39   ` Biju Das
2019-10-28 12:37   ` Biju Das
2019-10-30 15:56 ` Ulf Hansson

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=20191002082032.GC1388@ninjato \
    --to=wsa@the-dreams.de \
    --cc=Chris.Paterson2@renesas.com \
    --cc=biju.das@bp.renesas.com \
    --cc=fabrizio.castro@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=ulf.hansson@linaro.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 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.