From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: David Brownell <dbrownell@users.sourceforge.net>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>
Subject: Re: PMBus support in Linux
Date: Fri, 28 May 2010 21:42:39 -0700 [thread overview]
Message-ID: <20100529044239.GA19155@ericsson.com> (raw)
In-Reply-To: <20100529023401.GB12507@pengutronix.de>
On Fri, May 28, 2010 at 10:34:01PM -0400, Wolfram Sang wrote:
>
> CCing lm-sensors and David...
>
> On Fri, May 28, 2010 at 09:16:31AM -0700, Guenter Roeck wrote:
>
> > does anyone know if there is an effort to add infrastructure for PMBus
> > support (or support for specific PMBus devices) to Linux ?
>
> I found this:
>
> http://lists.lm-sensors.org/pipermail/lm-sensors/2008-April/022969.html
>
I found that as well, but that was about it. Not sure if I want to use it
as a starting point or even for reference since it is gplv3.
Probably useful for debugging, though.
> Hmm, sitting ontop of SMBus, it makes perfect sense to use i2c-dev (David knows
> what he is doing, of course ;)). But having no repo and all, it is hard to
> maintain this utility. Is there any chance to pick it up in the kernel-tree?
> tools/i2c/ or such? Hmm, it's GPL v3...
>
Maybe there is now more interest in kernel driver support - looks like there
are several PMBus chips available today.
If there is no activity yet, question is if I should write individual drivers or
if I should define a PMBus infrastructure on top of i2c/smbus first.
Any thoughts on which approach would be more likely to be accepted into the kernel ?
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2010-05-29 4:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 16:16 PMBus support in Linux Guenter Roeck
2010-05-29 2:34 ` Wolfram Sang
2010-05-29 4:42 ` Guenter Roeck [this message]
[not found] ` <20100529044239.GA19155-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>
2010-05-29 8:53 ` Wolfram Sang
[not found] ` <20100529085301.GA14982-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-05-29 15:33 ` Guenter Roeck
[not found] ` <20100529153312.GA20814-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>
2010-05-29 15:47 ` Wolfram Sang
[not found] ` <20100529154741.GB7572-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-05-29 17:12 ` Guenter Roeck
[not found] ` <20100529171229.GA21284-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>
2010-05-30 4:15 ` Wolfram Sang
[not found] ` <20100530041507.GA20222-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-05-30 15:08 ` Guenter Roeck
[not found] ` <20100529023401.GB12507-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-05-29 7:39 ` Jean Delvare
[not found] ` <20100529093929.38e03e06-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2010-05-29 8:16 ` Wolfram Sang
[not found] ` <20100529081633.GA7428-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-05-29 10:03 ` Jean Delvare
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=20100529044239.GA19155@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-i2c@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=w.sang@pengutronix.de \
/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).