From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/7] mfd: add mc34708 driver
Date: Tue, 21 Feb 2012 21:45:01 +0100 [thread overview]
Message-ID: <20120221204501.GF3852@pengutronix.de> (raw)
In-Reply-To: <20120221153856.GL9343@game.jcrosoft.org>
On Tue, Feb 21, 2012 at 04:38:56PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 16:35 Tue 21 Feb , Eric Bénard wrote:
> > Le Tue, 21 Feb 2012 15:10:11 +0100,
> > Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> a écrit :
> > > I still don't like the idea to export it
> > >
> > > You need a proper API to manage the PMIC
> > >
> > > so for today no need of this and I doubt the API will need it
> > >
> > for today we have what is inside barebox and this patche is coherent
> > with what is actually inside barebox (please check other drivers in mfd
> > and mx35-3stack for example).
> > For the future we may no more need this if we have a proper PMIC API
> > but as this API actually is not written, this patchset makes sense.
> today you do not need it
>
> today you just need to known it the chip is here
>
> so just check if the devfs is present
>
Don't know where your problem is with exporting it. Yes, it supports
only a single pmic, but that's all we have on the boards I know. And
this function can be used to modify registers on the pmic, some boards
need this. The day might come when we need some regulator API, but we
are not there and often enough getting a board to run properly is just
'modify this damn bit in the pmic'
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-02-21 20:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 0:27 [PATCH 1/7] add i2c clock support Eric Bénard
2012-02-21 0:27 ` [PATCH 2/7] mfd: add mc34708 driver Eric Bénard
2012-02-21 3:48 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-21 7:03 ` Eric Bénard
2012-02-21 13:03 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-21 13:22 ` Eric Bénard
2012-02-21 14:10 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-21 15:35 ` Eric Bénard
2012-02-21 15:38 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-21 20:45 ` Sascha Hauer [this message]
2012-02-21 21:09 ` Marc Reilly
2012-02-21 0:27 ` [PATCH 3/7] i.MX53: add silicn revision functions Eric Bénard
2012-02-22 7:33 ` Sascha Hauer
2012-02-27 8:20 ` [PATCH v2 1/7] add i2c clock support Eric Bénard
2012-02-27 8:20 ` [PATCH v2 2/7] mfd: add mc34708 driver Eric Bénard
2012-02-27 8:20 ` [PATCH v2 3/7] i.MX53: add silicon revision functions Eric Bénard
2012-02-27 8:20 ` [PATCH v2 4/7] i.MX53: enable pull up on I2C0 pins Eric Bénard
2012-02-27 8:20 ` [PATCH v2 5/7] mx53-loco: add i2c support Eric Bénard
2012-02-27 8:20 ` [PATCH v2 6/7] mx53-loco: add board revision support Eric Bénard
2012-02-27 15:40 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-27 18:58 ` Sascha Hauer
2012-02-27 8:20 ` [PATCH v2 7/7] mx53-loco: update defconfig Eric Bénard
2012-02-27 18:59 ` [PATCH v2 1/7] add i2c clock support Sascha Hauer
2012-02-21 0:27 ` [PATCH 4/7] i.MX53: enable pull up on I2C0 pins Eric Bénard
2012-02-21 0:27 ` [PATCH 5/7] mx53-loco: add i2c support Eric Bénard
2012-02-21 0:27 ` [PATCH 6/7] mx53-loco: add board revision support Eric Bénard
2012-02-21 3:50 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-21 0:27 ` [PATCH 7/7] mx53-loco: update defconfig Eric Bénard
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=20120221204501.GF3852@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
/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