All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodolfo Giometti <giometti@enneenne.com>
To: Anton Vorontsov <cbouatmailru@gmail.com>
Cc: linux-kernel@vger.kernel.org, Anton Vorontsov <cbou@mail.ru>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] power: support for Texas Instruments BQ27x00 battery managers.
Date: Fri, 1 Aug 2008 11:26:43 +0200	[thread overview]
Message-ID: <20080801092643.GX8465@enneenne.com> (raw)
In-Reply-To: <20080801082853.GA19224@zarina>

On Fri, Aug 01, 2008 at 12:28:53PM +0400, Anton Vorontsov wrote:
> > On Mon, Jun 23, 2008 at 10:38:17AM +0400, Anton Vorontsov wrote:
> > 
> > > Here is the patch to show the idea. I only tested it to build, so no
> > > guaranties that it will work on the actual hardware. :-)
> > > 
> > > This patch should be separated: one patch is for I2C subsystem
> > > maintainer (drivers/i2c/* changes) and another (drivers/power/* +
> > > include/linux/bq27x00.h) is for me.
> > 
> > On my system I need to specify 2 battery chips into the platform
> > specific file as follow (file is arch/arm/mach-pxa/wr1100.c):
> > 
> > 	static struct i2c_board_info __initdata wr1100_i2c_mux_devices[] = {
> > 	        {
> > 	                I2C_BOARD_INFO("bq27200", 0x55),
> > 	        },
> > 	};
> > 		
> >         i2c_register_board_info(2, wr1100_i2c_mux_devices,
> >                                         ARRAY_SIZE(wr1100_i2c_mux_devices));
> >         i2c_register_board_info(3, wr1100_i2c_mux_devices,
> >                                         ARRAY_SIZE(wr1100_i2c_mux_devices));
> > 
> > By using your solution I cannot use this code, is that right?
> 
> Why not? I think there should be no problem.

The platform_driver_register() conflicts with i2c_add_driver(),
doesn't it? O_o

> [...]
> > if you agree, I prefere resend my
> > patch without the #ifdef and the w1 support (since I cannot test it at
> > all) but living the possibility to add that support later.
> 
> Yes, that would be also fine.

Ok, since I cannot test the w1 subsystem at all, is better I provide
only tested code. :)

Ciao,

Rodolfo

-- 

GNU/Linux Solutions                  e-mail: giometti@enneenne.com
Linux Device Driver                          giometti@linux.it
Embedded Systems                     phone:  +39 349 2432127
UNIX programming                     skype:  rodolfo.giometti

      reply	other threads:[~2008-08-01  9:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 13:08 [PATCH] power: support for Texas Instruments BQ27x00 battery managers Rodolfo Giometti
     [not found] ` <20080619233411.GA27198@zarina>
2008-06-20  6:13   ` Rodolfo Giometti
2008-06-23  6:38     ` Anton Vorontsov
     [not found]       ` <20080731210354.GW8465@enneenne.com>
2008-08-01  8:28         ` Anton Vorontsov
2008-08-01  9:26           ` Rodolfo Giometti [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=20080801092643.GX8465@enneenne.com \
    --to=giometti@enneenne.com \
    --cc=cbou@mail.ru \
    --cc=cbouatmailru@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.