Re: I2C_M_RECV_LEN for i2c-mxs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Uwe,

> The reason I used wolfram@... is probably:

Looking up MAINTAINERS would have done it :)

> Ah, ok. But then there is a different problem: Even though "my" driver
> only advertises I2C_FUNC_I2C | I2C_FUNC_SMBUS_EMUL calling
> i2c_smbus_read_block_data in userspace results in .master_xfer being
> called with I2C_M_RECV_LEN set.

>From Documentation/i2c/functionality:

Because not every I2C or SMBus adapter implements everything in the 
I2C specifications, a client can not trust that everything it needs
is implemented when it is given the option to attach to an adapter:
the client needs some way to check whether an adapter has the needed
functionality...

Regards,

   Wolfram
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux GPIO]     [Linux SPI]     [Linux Hardward Monitoring]     [LM Sensors]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux