linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: "Simon Horman" <horms@verge.net.au>,
	"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>
Subject: [PATCH 0/2] arm64: dts: renesas: add missing strobe pin to SDHI
Date: Fri, 25 May 2018 17:05:16 +0200	[thread overview]
Message-ID: <20180525150518.26894-1-wsa+renesas@sang-engineering.com> (raw)

The strobe pin (SD2_DS) was forgotten to be configured when switching to 1.8V
on H3/M3-W/M3-N boards. Fix it with this series.

While this is a bug, I am not sure if it needs to be backported. This pin is
only needed for HS400 operation which we don't support yet but soon.

So, we surely want to have it in 4.17 before we hopefully merge HS400 support
for 4.18. But it could also be argued that this is a bug in the HW description,
so it needs to be backported. I am open for both options here.

But we really want this patch whenever we test HS400.

Thanks,

   Wolfram


Masaharu Hayakawa (1):
  arm64: dts: salvator-common: Add sdhi2_ds pin group to SDHI2 pinctrl
    groups

Wolfram Sang (1):
  arm64: dts: ulcb: Add sdhi2_ds pin group to SDHI2 pinctrl groups

 arch/arm64/boot/dts/renesas/salvator-common.dtsi | 4 ++--
 arch/arm64/boot/dts/renesas/ulcb.dtsi            | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

-- 
2.11.0

             reply	other threads:[~2018-05-25 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 15:05 Wolfram Sang [this message]
2018-05-25 15:05 ` [PATCH 1/2] arm64: dts: salvator-common: Add sdhi2_ds pin group to SDHI2 pinctrl groups Wolfram Sang
2018-05-25 15:05 ` [PATCH 2/2] arm64: dts: ulcb: " Wolfram Sang
2018-05-28  9:31   ` Simon Horman

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=20180525150518.26894-1-wsa+renesas@sang-engineering.com \
    --to=wsa+renesas@sang-engineering.com \
    --cc=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=niklas.soderlund@ragnatech.se \
    /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).