From: Simon Horman <horms@verge.net.au>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-mmc@vger.kernel.org,
Dirk Behme <dirk.behme@gmail.com>,
Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH 0/2] gen3: dts: enable on-board eMMC
Date: Fri, 16 Sep 2016 11:38:27 +0200 [thread overview]
Message-ID: <20160916093827.GB14562@verge.net.au> (raw)
In-Reply-To: <20160914170943.1663-1-wsa+renesas@sang-engineering.com>
On Wed, Sep 14, 2016 at 07:09:41PM +0200, Wolfram Sang wrote:
> From: Wolfram Sang <wsa@the-dreams.de>
>
> Here are the DTS changes to enable the on-board eMMC memory at 8 bit bus
> widths on R-Car Gen3 Salvator-X boards.
>
> Note that 'non-removable' is not supported yet because of Runtime PM issues. It
> seems we need to overhaul Runtime PM handling for other reasons as well, so I
> suggest the basic support goes in like this and DTS do not use 'non-removable'
> for now.
>
> Note also that I decided to use the pattern that pinctrl-0 is 3.3v and
> pinctrl-1 is 1.8v, although the eMMC is fixed at 1.8v. I tried a few ways to
> only use pinctrl-0 being 1.8v here, but they all ended up to be confusing for
> users IMO, so I sticked to the most consistent solution after all.
>
> These patches are based on top of Simon's sdr104-v7 patches and the accompanied
> driver patches sent a minute ago. A branch can be found here:
Please ping me / repost once these patches are ready to be merged.
prev parent reply other threads:[~2016-09-16 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 17:09 [PATCH 0/2] gen3: dts: enable on-board eMMC Wolfram Sang
2016-09-14 17:09 ` [PATCH 1/2] arm64: dts: r8a7795: salvator: " Wolfram Sang
2016-09-14 17:09 ` [PATCH 2/2] arm64: dts: r8a7796: salvator: enable on board eMMC Wolfram Sang
2016-09-16 9:38 ` Simon Horman [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=20160916093827.GB14562@verge.net.au \
--to=horms@verge.net.au \
--cc=dirk.behme@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@the-dreams.de \
/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