From: Ulf Hansson <ulf.hansson@linaro.org>
To: Chris Brandt <chris.brandt@renesas.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Simon Horman <horms+renesas@verge.net.au>,
linux-mmc <linux-mmc@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] mmc: sh_mobile_sdhi: add ocr_mask option
Date: Tue, 13 Sep 2016 14:57:42 +0200 [thread overview]
Message-ID: <CAPDyKFqdznJ4xr5=L862uOfvqjsRpR3d+yRWtN1-8H5ZvP9GeQ@mail.gmail.com> (raw)
In-Reply-To: <20160912141507.6837-2-chris.brandt@renesas.com>
On 12 September 2016 at 16:15, Chris Brandt <chris.brandt@renesas.com> wrote:
> In moving platforms from board files to DT, there still needs to be a way
> to set the ocr_mask setting for the tmio driver during probe. Without this
> setting, the probe will fail because the supported voltages are not known.
Regarding the ocr_mask; How do these SoCs provides the power to the mmc/sd card?
Do note, I am *not* talking about the I/O voltage but the core power
to the card.
The reason for raising the question is that we have infrastructures in
the mmc core which can create the ocr_mask, by parsing a regulator's
voltage range. This is the recommended method to use, instead of using
hard coded ocr mask values.
Kind regards
Uffe
>
> This patch will also traditional platform registration platforms to
> migrate to DT.
>
> Signed-off-by: Chris Brandt <chris.brandt@renesas.com>
> ---
> drivers/mmc/host/sh_mobile_sdhi.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/mmc/host/sh_mobile_sdhi.c b/drivers/mmc/host/sh_mobile_sdhi.c
> index 5334f24..b033500 100644
> --- a/drivers/mmc/host/sh_mobile_sdhi.c
> +++ b/drivers/mmc/host/sh_mobile_sdhi.c
> @@ -59,6 +59,7 @@ enum tmio_mmc_dmac_type {
>
> struct sh_mobile_sdhi_of_data {
> unsigned long tmio_flags;
> + u32 tmio_ocr_mask;
> unsigned long capabilities;
> unsigned long capabilities2;
> enum dma_slave_buswidth dma_buswidth;
> @@ -630,6 +631,7 @@ static int sh_mobile_sdhi_probe(struct platform_device *pdev)
> const struct sh_mobile_sdhi_of_data *of_data = of_id->data;
>
> mmc_data->flags |= of_data->tmio_flags;
> + mmc_data->ocr_mask = of_data->tmio_ocr_mask;
> mmc_data->capabilities |= of_data->capabilities;
> mmc_data->capabilities2 |= of_data->capabilities2;
> mmc_data->dma_rx_offset = of_data->dma_rx_offset;
> --
> 2.9.2
>
>
next prev parent reply other threads:[~2016-09-13 12:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 14:15 [PATCH v3 0/3] mmc: sh_mobile_sdhi: Add r7s72100 support Chris Brandt
2016-09-12 14:15 ` [PATCH v3 1/3] mmc: sh_mobile_sdhi: add ocr_mask option Chris Brandt
2016-09-13 12:57 ` Ulf Hansson [this message]
2016-09-13 13:26 ` Geert Uytterhoeven
2016-09-13 13:50 ` Chris Brandt
2016-09-13 15:10 ` Ulf Hansson
2016-09-13 15:59 ` Chris Brandt
2016-09-17 9:12 ` Ulf Hansson
2016-09-17 13:38 ` Chris Brandt
2016-09-13 13:28 ` Chris Brandt
2016-10-20 13:05 ` Wolfram Sang
2016-09-12 14:15 ` [PATCH v3 2/3] mmc: tmio-mmc: add support for 32bit data port Chris Brandt
2016-09-22 8:13 ` Ulf Hansson
2016-10-14 13:18 ` Chris Brandt
2016-10-17 13:36 ` Ulf Hansson
2016-10-17 15:15 ` Wolfram Sang
2016-10-20 13:28 ` Wolfram Sang
2016-10-20 14:35 ` Chris Brandt
2016-10-20 23:12 ` Wolfram Sang
2016-10-21 13:43 ` Chris Brandt
2016-10-21 21:56 ` Wolfram Sang
2016-10-24 11:06 ` Geert Uytterhoeven
2016-10-24 11:11 ` Wolfram Sang
2016-10-24 12:37 ` Chris Brandt
2016-10-20 19:46 ` Chris Brandt
2016-10-20 23:04 ` Wolfram Sang
2016-11-01 8:49 ` Wolfram Sang
2016-11-01 13:40 ` Chris Brandt
2016-11-01 15:07 ` Wolfram Sang
2016-11-01 15:13 ` Chris Brandt
2016-09-12 14:15 ` [PATCH v3 3/3] mmc: sh_mobile_sdhi: Add r7s72100 support Chris Brandt
2016-11-01 8:49 ` Wolfram Sang
2016-10-14 13:14 ` [PATCH v3 0/3] " Chris Brandt
2016-11-07 18:38 ` 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='CAPDyKFqdznJ4xr5=L862uOfvqjsRpR3d+yRWtN1-8H5ZvP9GeQ@mail.gmail.com' \
--to=ulf.hansson@linaro.org \
--cc=chris.brandt@renesas.com \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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 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).