docs: correct i2cdetect usage and ignore archived notes
The engine exposes only SMBus BYTE_DATA/WORD_DATA, so i2cdetect (which needs SMBus QUICK or READ_BYTE) cannot scan the bus. Replace the misleading "i2cdetect -r/-y" scan instructions with a direct i2cget byte-data read in the README, the cover letter and the smoke test. Also gitignore the archived internal working documents (docs/archive-*.md). Signed-off-by: Simone Chifari <simone.chifari@gmail.com>
This commit is contained in:
@@ -89,8 +89,9 @@ on both read and write paths.
|
||||
|
||||
Since the hardware requires a register offset for every transaction,
|
||||
I2C_SMBUS_QUICK and I2C_SMBUS_BYTE (which have no offset) are not supported
|
||||
(returning -EOPNOTSUPP). Use `i2cdetect -r` (read byte data probe) to scan
|
||||
for devices. Standard kernel drivers such as ee1004 (for DDR4 SPD) load
|
||||
(returning -EOPNOTSUPP). For the same reason i2cdetect cannot scan the bus;
|
||||
access a device directly with a byte-data read, e.g. `i2cget -y <bus> 0x50 0x02`
|
||||
reads SPD byte 2. Standard kernel drivers such as ee1004 (for DDR4 SPD) load
|
||||
and bind successfully via BYTE_DATA reads.
|
||||
|
||||
udev autoloads the module on PCI add event (MODULE_DEVICE_TABLE present).
|
||||
|
||||
Reference in New Issue
Block a user