Hi Samuel,
> > On Sunday, April 01, 2012 04:41:35 PM Marc Reilly wrote:
> > > This series (against mfd-2.6/for-next) changes the mc13xxx driver to
> > > use regmap and adds I2C support.
> > > It has a compile dependency on regmap/for-next, as the spi driver uses
> > > the recently added pad_bits c
Hi Marc,
On Tue, Apr 17, 2012 at 09:21:41AM +1000, Marc Reilly wrote:
> Hi Samuel,
>
>
> On Sunday, April 01, 2012 04:41:35 PM Marc Reilly wrote:
> > This series (against mfd-2.6/for-next) changes the mc13xxx driver to use
> > regmap and adds I2C support.
> > It has a compile dependency on regma
Hi Samuel,
On Sunday, April 01, 2012 04:41:35 PM Marc Reilly wrote:
> This series (against mfd-2.6/for-next) changes the mc13xxx driver to use
> regmap and adds I2C support.
> It has a compile dependency on regmap/for-next, as the spi driver uses the
> recently added pad_bits config field.
(bump
Hello Marc,
On Sun, Apr 01, 2012 at 07:39:49PM +1000, Marc Reilly wrote:
> > On Sun, Apr 01, 2012 at 04:41:35PM +1000, Marc Reilly wrote:
> > > This series (against mfd-2.6/for-next) changes the mc13xxx driver to use
> > > regmap and adds I2C support.
> > > It has a compile dependency on regmap/fo
Hi Marc, thanks for V5.
> This series (against mfd-2.6/for-next) changes the mc13xxx driver to use
> regmap and adds I2C support.
> It has a compile dependency on regmap/for-next, as the spi driver uses the
> recently added pad_bits config field.
If included in your plans to relocate the current
Hi Marc,
On Sun, Apr 01, 2012 at 04:41:35PM +1000, Marc Reilly wrote:
> This series (against mfd-2.6/for-next) changes the mc13xxx driver to use
> regmap and adds I2C support.
> It has a compile dependency on regmap/for-next, as the spi driver uses the
> recently added pad_bits config field.
>
>
Hi,
This series (against mfd-2.6/for-next) changes the mc13xxx driver to use
regmap and adds I2C support.
It has a compile dependency on regmap/for-next, as the spi driver uses the
recently added pad_bits config field.
Patch 2/4 has:
Reviewed-by: Mark Brown
Patch 4/4 has:
Signed-off-by: Oskar S
Hi,
This series (against mfd-2.6/for-next) changes the mc13xxx driver to use
regmap and adds I2C support.
It has a compile dependency on regmap/for-next, as the spi driver uses the
recently added pad_bits config field.
Changes since V3:
- spi driver uses padded register format (reads should actu
Hi,
This series (against mfd-2.6/for-next) changes the mc13xxx driver to use
regmap and adds I2C support. It generally goes about this the same way as
the previous 2 versions, but now uses regmap.
I am unable to test SPI functionality, but the I2C stuff works. It would be
great if someone could
On Sun, Mar 11, 2012 at 12:50:18PM +0100, Wolfram Sang wrote:
> free, if this is desired. I think the regmap approach should have been tried
> before we go custom. sound/soc/codecs/ad193x.c might give an impression how
> regmap spi/i2c in one driver could look like.
There's a bunch of other examp
> The only issue from V1 [0] not addressed is the use of regmap - mainly, I
> don't
> have the time. I accept that this is a lame excuse but hope that use of
> regmap
> can come later if it is required.
I really appreciate the effort, yet I fear that this is a show stopper. It gets
open coded
Hi,
This series (based on Samuel's mfd-2.6/for-next) adds I2C support for the
mc13xxx family PMICs. Thanks to Oscar for adding dt support for the I2C driver.
Hi Marc,
On Fri, Jan 20, 2012 at 06:55:35PM +1100, Marc Reilly wrote:
> Hi,
>
> Thankyou all for your feedback and comments. I'll use them for a V2 but
> Samuel, I'd like to know if you'd like me to base them on a specific branch
> before I do.
Please rebase it against my for-next branch.
> S
On Fri, Jan 20, 2012 at 06:55:35PM +1100, Marc Reilly wrote:
> On Thursday, January 19, 2012 10:29:41 PM Mark Brown wrote:
> > On Thu, Jan 19, 2012 at 12:12:31PM +0100, Arnaud Patard wrote:
> > > I've never looked at regmap deeply but can't it be done with regmap or is
> > > it just a bad idea ?
Marc Reilly writes:
> Hi,
Hi,
>
> Thankyou all for your feedback and comments. I'll use them for a V2 but
> Samuel, I'd like to know if you'd like me to base them on a specific branch
> before I do.
>
> Shawn, thanks for testing!
>
> On Thursday, January 19, 2012 10:29:41 PM Mark Brown wrote:
On Thu, Jan 19, 2012 at 12:12:31PM +0100, Arnaud Patard wrote:
> I've never looked at regmap deeply but can't it be done with regmap or is it
> just a bad idea ?
Glancing quickly at the existing code it should map on reasonably well,
though a new format definition may be required for the 25 bit s
Marc Reilly writes:
> Hi,
Hi,
>
> This series (based on 3.2) adds I2C support for the mc13xxx family PMICs.
> The patches are similar, but not identical to my previous patches for this
> [1], the
> main difference being the way the config items are done in patch 2.
>
> I don't have the hardwar
Hi Marc,
On Thu, Jan 19, 2012 at 12:01:31PM +1100, Marc Reilly wrote:
> Hi,
>
> This series (based on 3.2) adds I2C support for the mc13xxx family PMICs.
> The patches are similar, but not identical to my previous patches for this
> [1], the
> main difference being the way the config items are d
Hi,
This series (based on 3.2) adds I2C support for the mc13xxx family PMICs.
The patches are similar, but not identical to my previous patches for this [1],
the
main difference being the way the config items are done in patch 2.
I don't have the hardware to retest on SPI hardware, I'd appreciat
19 matches
Mail list logo
