From: Mark Brown <broonie-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
To: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
Anton Vorontsov
<avorontsov-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>,
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH 2/2] i2c: MPC8349E-mITX Power Management and GPIO expander driver
Date: Tue, 23 Sep 2008 13:07:15 +0100 [thread overview]
Message-ID: <20080923120713.GC32245@sirena.org.uk> (raw)
In-Reply-To: <20080922224540.GM2716-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
On Mon, Sep 22, 2008 at 11:45:40PM +0100, Ben Dooks wrote:
> I've also a driver for a similar PMU fitted to a number
> of our boards that provides basic gpio (wakeup sources) and some
> minimalist power management (so isn't really fit for regulator
> framwork) and isn't really a gpio chip (so drivers/gpio isn't
> really the place for it either.)
FWIW the regulator framework does have support for representing things
as limited as completely non-controllable regulators so it may still be
worth considering that. It at least provides a degree of abstraction
for the clients in case they are used with more complex regulators and
would allow integration of your PMU with more complex secondary
regulators. May not be worth the bother, though.
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-09-23 12:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 18:03 [PATCH 2/2] i2c: MPC8349E-mITX Power Management and GPIO expander driver Anton Vorontsov
[not found] ` <20080919180354.GB13899-wnGakbxT3iijyJ0x5qLZdcN33GVbZNy3@public.gmane.org>
2008-09-22 22:45 ` Ben Dooks
[not found] ` <20080922224540.GM2716-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2008-09-23 12:07 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-23 14:13 Anton Vorontsov
2008-10-10 14:22 ` Kumar Gala
2008-10-10 14:45 ` Anton Vorontsov
[not found] ` <20081010144545.GA956-wnGakbxT3iijyJ0x5qLZdcN33GVbZNy3@public.gmane.org>
2008-10-10 14:58 ` Kumar Gala
2008-10-10 15:16 ` Anton Vorontsov
[not found] ` <20080923141300.GB31262-wnGakbxT3iijyJ0x5qLZdcN33GVbZNy3@public.gmane.org>
2008-10-10 18:46 ` Kumar Gala
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=20080923120713.GC32245@sirena.org.uk \
--to=broonie-gfdadszt00ze9xe1eozjha@public.gmane.org \
--cc=avorontsov-hkdhdckH98+B+jHODAdFcQ@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.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