From: atull <atull@opensource.altera.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Mark Brown <broonie@kernel.org>, Jean Delvare <jdelvare@suse.de>,
<lm-sensors@lm-sensors.org>, <linux-kernel@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: power supply gating with ltc2978
Date: Tue, 19 Aug 2014 09:21:36 -0500 [thread overview]
Message-ID: <alpine.DEB.2.02.1408190914310.22837@atx-linux-37> (raw)
In-Reply-To: <20140818030717.GA5131@roeck-us.net>
On Mon, 18 Aug 2014, Guenter Roeck wrote:
> On Sat, Aug 16, 2014 at 02:20:50PM +0100, Mark Brown wrote:
> > On Fri, Aug 15, 2014 at 04:34:49PM -0500, atull wrote:
> >
> > > I am interested in adding functionality to be able to gate power supplies
> > > going through a ltc2978. I see that there is a hwmon driver already
> > > existing (hwmon/pmbus/ltc2978.c). I see some of the other hwmon drivers
> > > have MFD's. It looks like this ltc driver would need a MFD and a
> > > regulator driver added. However I don't see other pmbus hwmon drivers
> > > using MFD.
> >
> > > So I am asking for recommendations and reservations on how to proceed here
> > > before I get too far with this.
> >
> > Without knowing anything at all about pmbus or this particular hardware
> > it's hard to comment but what you're saying here sounds sensible (though
> > I do see that apparently splitting the drivers may not actually be
> > sensible from Guenter's followup).
>
> I had originally thought about converting the pmbus drivers to mfd with client
> drivers, but I concluded that it would add a lot of complexity with little gain.
> It makes sense to separate a driver into mfd and a number of client drivers
> if a device has clear functional blocks for the different devices it supports.
> With PMBus, this is not the case. Separating a PMBus driver would be a purely
> artificial costruct, and there would be overlapping functionality. Separating
> just a single driver out of the group of PMBus drivers, as seems to be suggested
> above, makes even less sense as one simply can not separate the core PMBus
> driver code from its front-end drivers.
>
> On the other side, adding regulator support into the PMBus driver code would
> make a lot of sense. It should also be quite straightforward.
>
> Or anyway that is my opinion. If someone wants to spend the time and separate
> the PMBus drivers into an MfD part and hwmon and regulator client drivers, I'll
> be happy to look at the resulting patch set.
>
> Guenter
>
Hi Guenter,
I'd really rather just add regulator support to the PMBus driver code and
avoid all the mess of creating a MFD. It seems more straigtforward. I'll
let you know when I have something working to look at.
Alan
prev parent reply other threads:[~2014-08-19 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 21:34 atull
2014-08-15 21:58 ` Guenter Roeck
2014-08-16 13:20 ` Mark Brown
2014-08-18 3:07 ` Guenter Roeck
2014-08-19 14:21 ` atull [this message]
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=alpine.DEB.2.02.1408190914310.22837@atx-linux-37 \
--to=atull@opensource.altera.com \
--cc=broonie@kernel.org \
--cc=jdelvare@suse.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.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
all inboxes | Powered by JetHome®