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]

Message-ID: <63386a3d0907121147x5065be43tf9d19e9e33f0ffbd@mail.gmail.com>
Date:	Sun, 12 Jul 2009 20:47:53 +0200
From:	Linus Walleij <linus.ml.walleij@...il.com>
To:	Felipe Balbi <me@...ipebalbi.com>
Cc:	dwmw2@...radead.org, linux-kernel@...r.kernel.org
Subject: Re: [rfc/patch 02/15] power: bq27200: this is an i2c device

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?

Linus Walleij
--
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/