From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/4] sh-pfc: sh73a0: Add VCCQ MC0 regulator
Date: Wed, 24 Apr 2013 21:20:42 +0000 [thread overview]
Message-ID: <1590111.1UoTytYiZa@avalon> (raw)
In-Reply-To: <1366672585-9098-3-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Linus,
Thanks for the review.
On Wednesday 24 April 2013 14:36:10 Linus Walleij wrote:
> On Tue, Apr 23, 2013 at 1:16 AM, Laurent Pinchart wrote:
> > The sh73a0 has an internal power gate on the VCCQ power supply for the
> > SDHI0 device that is controlled (for some strange reason) by a bit in a
> > PFC register.
> >
> > Export a regulator to control the SDHI0 VCCQ power supply.
> >
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
>
> I need Mark Browns consent+ACK on this but I'm OK with it under the special
> circumstances.
I'm not very fond of this either, but given the circumstances there's few
other options. The best one would be to fix the hardware design(ers) :-)
> However pls update the commit message with some info that the register
> bits are used by pin control too and thus there is no way to achieve
> an atomic writel/readl sequence unless this is under the pinctrl umbrella
> so you can take &pfc->lock.
Done.
> > +static void __sh73a0_vccq_mc0_enable(struct regulator_dev *reg, bool
> > enable)
>
> Skip the __ and the confusing name "_enable" for a function that
> does both enable and disable.
>
> Call it sh73a0_vccq_mc0_endisable is my suggestion.
That's a weird name, but I can live with that.
I'll submit a v2 with the two changes.
> Apart from that I'm happy with it if Mark is.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-04-24 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 23:16 [PATCH 2/4] sh-pfc: sh73a0: Add VCCQ MC0 regulator Laurent Pinchart
2013-04-24 12:36 ` Linus Walleij
2013-04-24 21:20 ` Laurent Pinchart [this message]
2013-04-24 22:25 ` Sergei Shtylyov
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=1590111.1UoTytYiZa@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 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).