linux-kernel - Re: [rfc/patch 02/15] power: bq27200: this is an i2c device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 12 Jul 2009 22:49:33 +0300
From:	Felipe Balbi <felipe.balbi@...ia.com>
To:	ext Linus Walleij <linus.ml.walleij@...il.com>
Cc:	Felipe Balbi <me@...ipebalbi.com>,
	"dwmw2@...radead.org" <dwmw2@...radead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	ben-linux@...ff.org
Subject: Re: [rfc/patch 02/15] power: bq27200: this is an i2c device

On Sun, Jul 12, 2009 at 08:47:53PM +0200, ext Linus Walleij wrote:
> 2009/7/12 Felipe Balbi <me@...ipebalbi.com>:
> 
> > ... with hardcoded device address so i2c subsystem won't
> > talk to more than one of those.
> 
> So you remove support for multiple instances of this driver, OK.
> 
> But theoretically, what happens if you have two different I2C busses
> on your system with a battery driver on each?
> 
> Can you confirm that that will never happen?

If they are on different buses, there shouldn't be any problems.
Unfortunately I don't have a hw suitable for this kind of test.

Let's hear from Ben Dooks on this.

-- 
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/