- Original Message -
> From: "Jean Delvare"
> Sent: Tuesday, November 10, 2015 3:39:20 AM
>
> Hi Aaron,
>
> On Mon, 9 Nov 2015 18:25:11 -0600 (CST), Aaron Sierra wrote:
> > Previously, the at24 driver would bail out in the case of a 16-bit
> > addressable EEPROM
On 09.11.2015 23:15, Wolfram Sang wrote:
Hi guys,
while handling the merge conflict for the designware-platdrv, I noticed
an asymmetry in the runtime PM handling. Currently, code looks like
this:
if (dev->pm_runtime_disabled) {
pm_runtime_forbid(>dev);
} else {
Hi Aaron,
On Mon, 9 Nov 2015 18:25:11 -0600 (CST), Aaron Sierra wrote:
> Previously, the at24 driver would bail out in the case of a 16-bit
> addressable EEPROM attached to an SMBus controller. This is because
> SMBus block reads and writes don't map to I2C multi-byte reads and
> writes when the
Hi Michael,
> Do I understand it right, I can set the Master in slave mode and the
> new slave get his own i2c-adresse?
Yes, you can have your own address then. Note that I recently gave a
talk about the slave framework. You can find the slides here:
http://elinux.org/ELCE_2015_Presentations
I am currently working with a I.mx6 quad-core-processor on Linux 3.19.
I would like to implement the "I2C slave support", by Wolfram Sang, In
this processor.
For this purpose, I would have some comprehension questions.
Do I understand it right, I can set the Master in slave mode and the
new