From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] regulator: mc13783: consider Power Gates as digital regulators.
Date: Mon, 18 Jan 2010 17:37:23 +0000 [thread overview]
Message-ID: <20100118173722.GA12689@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1263835570.3632.33.camel@realization>
As I just wrote...
On Mon, Jan 18, 2010 at 06:07:53PM +0100, Alberto Panizzo wrote:
> Something like this?
> if (mask & MC13783_REG_POWERMISC_PWGTSPI_M) {
> u32 new_state = (val & MC13783_REG_POWERMISC_PWGTSPI_M) ^ mask;
>
> mc13783_state_powermisc_pwgt =
> (mc13783_state_powermisc_pwgt & ~mask) | new_state;
> }
Yes, that's clearer.
> > > + if (ret)
> > > + return ret;
> > > +
> > > + valread = (valread & ~mask) | val;
> > > +
> > > + /* Re propose the stored state for Power Gates */
> > > + valread = (valread & ~MC13783_REG_POWERMISC_PWGTSPI_M) |
> > > + mc13783_state_powermisc_pwgt;
> >
> > ...and this further mainpulation.
> What is obscure in this? it is the same operation as the previous
> MC13783_REG_POWERMISC_PWGTSPI_M is the mask for PWGT1 and 2 bits and in
> mc13783_state_powermisc_pwgt there is the stored state for those two bits.
Part of it is the fact that the first bit was almost completely opaque
but even so it would be less surprising if you first worked out the
value you wanted to set, then did whatever manipulation was required to
translate into the format that actually gets written.
next prev parent reply other threads:[~2010-01-18 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 16:02 [PATCH] regulator: mc13783: consider Power Gates as digital regulators Alberto Panizzo
2010-01-18 16:32 ` Mark Brown
2010-01-18 17:26 ` Alberto Panizzo
2010-01-18 17:37 ` Mark Brown [this message]
[not found] ` <1263834473.3632.31.camel@realization>
[not found] ` <20100118172002.GB6889@rakim.wolfsonmicro.main>
2010-01-18 17:50 ` Alberto Panizzo
2010-01-18 17:56 ` Mark Brown
2010-01-18 19:04 ` Uwe Kleine-König
2010-01-18 21:01 ` Alberto Panizzo
2010-01-19 10:26 ` Liam Girdwood
2010-01-19 11:12 ` Alberto Panizzo
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=20100118173722.GA12689@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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).