From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] pinctrl: sh-pfc: fix SDHI0 VccQ regulator on sh73a0 with DT
Date: Wed, 10 Jul 2013 09:20:05 +0000 [thread overview]
Message-ID: <3882330.n7B3srRuA4@avalon> (raw)
In-Reply-To: <Pine.LNX.4.64.1307091625490.28812@axis700.grange>
Hi Guennadi,
Thank you for the patch.
On Tuesday 09 July 2013 16:27:24 Guennadi Liakhovetski wrote:
> The PFC pinctrl driver on sh73a0 is also regiatering a VccQ regulator for
> SDHI0. However, its consumers list only included the platform-data based
> SDHI device name. When booted with DT SDHI0 couldn't enable VccQ and
> therefore was unusable. Fix this by adding a consumer with DT-based name.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
>
> Is this the correct fix or is there a better option? Observed and tested
> on kzm9g-reference.
The fix looks good to me.
> drivers/pinctrl/sh-pfc/pfc-sh73a0.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/pinctrl/sh-pfc/pfc-sh73a0.c
> b/drivers/pinctrl/sh-pfc/pfc-sh73a0.c index 7956df5..31f7d0e 100644
> --- a/drivers/pinctrl/sh-pfc/pfc-sh73a0.c
> +++ b/drivers/pinctrl/sh-pfc/pfc-sh73a0.c
> @@ -3785,6 +3785,7 @@ static const struct regulator_desc
> sh73a0_vccq_mc0_desc = {
>
> static struct regulator_consumer_supply sh73a0_vccq_mc0_consumers[] = {
> REGULATOR_SUPPLY("vqmmc", "sh_mobile_sdhi.0"),
> + REGULATOR_SUPPLY("vqmmc", "ee100000.sdhi"),
> };
>
> static const struct regulator_init_data sh73a0_vccq_mc0_init_data = {
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-07-10 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 14:27 [PATCH] pinctrl: sh-pfc: fix SDHI0 VccQ regulator on sh73a0 with DT Guennadi Liakhovetski
2013-07-10 1:15 ` Simon Horman
2013-07-10 9:20 ` Laurent Pinchart [this message]
2013-07-22 19:09 ` Linus Walleij
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=3882330.n7B3srRuA4@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.org \
/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.