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  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, 21 Sep 2014 21:23:25 +0200
From:	Lars-Peter Clausen <>
To:	Wolfram Sang <>
CC:	Jean-Michel Hautbois <>,,,
Subject: Re: [PATCH] i2c: Add generic support passing secondary devices addresses

On 09/21/2014 07:49 PM, Wolfram Sang wrote:
>>> 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.
> How is this configured? I can't imagine every address has its own
> setting, but rather some 1-3 pins which select a certain block of
> addresses?

Every secondary address has its own register and can be set to any valid I2C 

- Lars
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists