Driver-Support of I2C_M_RECV_LEN
Hello,
in the documentation i found at
http://ww2.cs.fsu.edu/~rosentha/linux/2.6.26.5/docs/DocBook/kernel-api/re1222.html
the following sentence:
"Note that using this function requires that the client's adapter support the I2C_FUNC_SMBUS_READ_BLOCK_DATA functionality. Not all adapter drivers support this; its emulation through I2C messaging relies on a specific mechanism (I2C_M_RECV_LEN) which may not be implemented."
The second sentence says that the mechanism I2C_M_RECV_LEN is not all over implemented.
How i can figure out whether this mechanism will be provided of my driver? What is the alternative of using the function i2c_smbus_read_block_data?
Thanks a lot for your support,
Michael Post
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hello together,
Am 20.06.14 14:03, schrieb Michael Post:
Quoted 6 lines
Hello,
in the documentation i found at
http://ww2.cs.fsu.edu/~rosentha/linux/2.6.26.5/docs/DocBook/kernel-api/re1222.html
the following sentence:
Quoted 7 lines
"Note that using this function requires that the client's adapter support the
I2C_FUNC_SMBUS_READ_BLOCK_DATAfunctionality. Not all adapter drivers support this; its emulation through I2C messaging relies on a specific mechanism (I2C_M_RECV_LEN) which may not be implemented."
Quoted 7 lines
The second sentence says that the mechanism
I2C_M_RECV_LENis not all over implemented.How i can figure out whether this mechanism will be provided of my driver? What is the alternative of using the function
i2c_smbus_read_block_data?
does nobody has any clue or hints for me? Maybe there is an other mailinglist i can ask?
Thanks a lot,
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBCgAGBQJTtln2AAoJEFF6fE6T32A87NkH/3f2pslue7/oYiIiZ8PlKway C9hOI02EEX0Z+sxB31ZTMyis2VxGFmZ3VGp4sSpiPv2iK9huMYmeVV0a2a+J0MLg wmObCFRUZVN85lLqau+nEuqNMHSVYpYedHovC3Ui3rTHZNDM3pWJSDBy5dFG57d2 TE6Jae6Q31/hRn8gq106XmRdtYgKmzCfmfjRwYyBt0tYH2vQ43xhJQ3zGZCuKJ5O xjY4em5jLWv+oiWi/HAkXFqfC4GskklBcn77K9TDEuw+oXkeF8Re4JPmvOBKxrQA O+a246FVyyrKHs7VKXXAORX+Ty/q2QtP+dbFk9M0Uo0M0Xi17QhJ8TsUwQViFV4= =gIOJ
-----END PGP SIGNATURE-----
Hello together,
Am 20.06.14 14:03, schrieb Michael Post:
Quoted 11 lines
Hello,
in the documentation i found at
http://ww2.cs.fsu.edu/~rosentha/linux/2.6.26.5/docs/DocBook/kernel-api/re1222.html
the following sentence:"Note that using this function requires that the client's adapter support the
I2C_FUNC_SMBUS_READ_BLOCK_DATAfunctionality. Not all adapter drivers support this; its emulation through I2C messaging relies on a specific mechanism (I2C_M_RECV_LEN) which may not be implemented."
Quoted 5 lines
The second sentence says that the mechanism
I2C_M_RECV_LENis not all over implemented.How i can figure out whether this mechanism will be provided of my driver? What is the alternative of using the function
i2c_smbus_read_block_data?
does nobody has any clue or hints for me?
Maybe there is an other mailinglist i can ask?
Thanks a lot,
Michael
Hi,
Quoted 1 line
How i can figure out whether this mechanism will be provided of my driver?
Use i2c_get_functionality() and check for I2C_FUNC_SMBUS_READ_BLOCK_DATA (or look at the source code).
Quoted 1 line
What is the alternative of using the function
i2c_smbus_read_block_data?
That depends solely on your slave device. Check the documentation what transfer types it supports and what alternatives are possible.
Regards,
Wolfram