| 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
| ||
|
Message-ID: <541DDA9B.40904@metafoo.de> Date: Sat, 20 Sep 2014 21:50:51 +0200 From: Lars-Peter Clausen <lars@...afoo.de> To: Wolfram Sang <wsa@...-dreams.de>, Jean-Michel Hautbois <jean-michel.hautbois@...alys.com> CC: linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org, mark.rutland@....com Subject: Re: [PATCH] i2c: Add generic support passing secondary devices addresses On 09/20/2014 06:49 PM, Wolfram Sang wrote: > On Fri, Sep 05, 2014 at 04:02:19PM +0200, Jean-Michel Hautbois wrote: >> Some I2C devices have multiple addresses assigned, for example each address >> corresponding to a different internal register map page of the device. >> So far drivers which need support for this have handled this with a driver >> specific and non-generic implementation, e.g. passing the additional address >> via platform data. > > This raises the first question for me: Are the additional addresses > configurable? Sadly, I can't find good documentation for the adv7604. > Otherwise, if I know I have a adv7604 and know its addresses, this > information should go into the driver and not the DT. > They are. The current driver hard codes the other addresses, but that's not working when you have multiple adv7604s on the same I2C bus. - Lars -- 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/
Powered by blists - more mailing lists