- Original Message -
> From: "Wolfram Sang"
> Sent: Friday, December 11, 2015 7:19:40 AM
>
> On Mon, Nov 16, 2015 at 06:02:19PM -0600, Aaron Sierra wrote:
> > Previously, the at24 driver would bail out in the case of a 16-bit
> > addressable EEPROM att
th 32-byte* access
*limited to 32-bytes by I2C_SMBUS_BLOCK_MAX.
Write performance:
248 B/s with 1-byte page (default)
3.9 KB/s with 128-byte* page (via platform data)
*limited to 31-bytes by I2C_SMBUS_BLOCK_MAX - 1.
Signed-off-by: Nate Case
Signed-off-by: Aaron Sierra
Review
th 32-byte* access
*limited to 32-bytes by I2C_SMBUS_BLOCK_MAX.
Write performance:
248 B/s with 1-byte page (default)
3.9 KB/s with 128-byte* page (via platform data)
*limited to 31-bytes by I2C_SMBUS_BLOCK_MAX - 1.
Signed-off-by: Nate Case
Signed-off-by: Aaron Sierra
Review
- 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
> >
th 32-byte* access
*limited to 32-bytes by I2C_SMBUS_BLOCK_MAX.
Write performance:
248 B/s with 1-byte page (default)
3.9 KB/s with 128-byte* page (via platform data)
*limited to 31-bytes by I2C_SMBUS_BLOCK_MAX - 1.
Signed-off-by: Nate Case
Signed-off-by: Aaron Sierra
--
th 32-byte* access
*limited to 32-bytes by I2C_SMBUS_BLOCK_MAX.
Write performance:
248 B/s with 1-byte page (default)
3.9 KB/s with 128-byte* page (via platform data)
*limited to 31-bytes by I2C_SMBUS_BLOCK_MAX - 1.
Signed-off-by: Nate Case
Signed-off-by: Aaron Sierra
--
- Original Message -
> From: "Jean Delvare"
> Sent: Tuesday, November 3, 2015 4:33:53 AM
>
> Hi Aaron,
>
> On Thu, 3 Sep 2015 14:53:30 -0500 (CDT), Aaron Sierra wrote:
> > Previously, the at24 driver would bail out in the case of a 16-bit
> >
- Original Message -
> From: "Jean Delvare"
> Sent: Monday, November 2, 2015 7:42:09 AM
>
> Hi Aaron,
>
> Sorry for the late reply.
>
> On Thu, 3 Sep 2015 14:52:35 -0500 (CDT), Aaron Sierra wrote:
> > Introduce at24_smbus_write_i2c_block_data() t
ff-by: Nate Case
Signed-off-by: Aaron Sierra
---
v2 - Account for changes related to introduction of
i2c_smbus_read_i2c_block_data_or_emulated()
drivers/misc/eeprom/Kconfig | 4 +++-
drivers/misc/eeprom/at24.c | 32 +++-
2 files changed, 30 insertions(
I2C_SMBUS_BLOCK_MAX / 2.
Signed-off-by: Aaron Sierra
---
v2 - Unchanged from v1
drivers/misc/eeprom/at24.c | 35 ---
1 file changed, 32 insertions(+), 3 deletions(-)
diff --git a/drivers/misc/eeprom/at24.c b/drivers/misc/eeprom/at24.c
index c6cb7f8..c3d3add 100644
Introduce at24_smbus_write_byte_data() to allow very slow (e.g.
248 B/s) write access to 16-bit EEPROM devices attached to SMBus
controllers like the Intel SCH.
Signed-off-by: Nate Case
Signed-off-by: Aaron Sierra
---
v2 - Unchanged from v1
drivers/misc/eeprom/at24.c | 35
- Original Message -
> From: "Aaron Sierra"
> Sent: Thursday, September 3, 2015 2:53:30 PM
>
> 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 w
vices:
AT24CM01 attached to Intel ISCH SMBus (1.8 KB/s)
AT24C512 attached to Intel I801 SMBus (1.4 KB/s)
Signed-off-by: Nate Case
Signed-off-by: Aaron Sierra
---
drivers/misc/eeprom/Kconfig | 4 +++-
drivers/misc/eeprom/at24.c | 40 +++-
2 files ch
I2C_SMBUS_BLOCK_MAX / 2.
Signed-off-by: Aaron Sierra
---
drivers/misc/eeprom/at24.c | 35 ---
1 file changed, 32 insertions(+), 3 deletions(-)
diff --git a/drivers/misc/eeprom/at24.c b/drivers/misc/eeprom/at24.c
index 2d3db81..4cf53a0 100644
--- a/drivers/misc/eeprom
Introduce at24_smbus_write_byte_data() to allow very slow (e.g.
248 B/s) write access to 16-bit EEPROM devices attached to SMBus
controllers like the Intel SCH.
Signed-off-by: Nate Case
Signed-off-by: Aaron Sierra
---
drivers/misc/eeprom/at24.c | 35 ---
1 file
> From: "Martin Mokrejs"
> Jason Baron wrote:
> > Hi,
> >
> > I've also hit the i2c_i801 driver conflicts with ACPI region:
> >
> > kernel: [73904.044722] i801_smbus :00:1f.3: PCI INT C -> GSI 18
> > (level, low) -> IRQ 18
> > kernel: [73904.045573] ACPI: resource :00:1f.3 [io
> > 0xf00
will occur.
This corrects behavior seen on some hardware where an ACPI resource
conflict is detected, but the ASL methods defined in ACPI are
incompatible with the i2c-scmi driver. This results in no driver being
bound to the hardware, when both could safely be bound.
Signed-off-by: Aaron Sierra
v2: ran through checkpatch.pl:
- fixed a line of spaces at the beginning of the line (Thanks Eudean)
- replaced msleep(1) with usleep_range(1000, 3000)
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majord...@vger.kernel.org
More majordomo in
will occur.
This corrects behavior seen on some hardware where an ACPI resource
conflict is detected, but the ASL methods defined in ACPI are
incompatible with the i2c-scmi driver. This results in no driver being
bound to the hardware, when both could safely be bound.
Signed-off-by: Aaron Sierra
will occur.
This corrects behavior seen on some hardware where an ACPI resource
conflict is detected, but the ASL methods defined in ACPI are
incompatible with the i2c-scmi driver. This results in no driver being
bound to the hardware, when both could safely be bound.
Signed-off-by: Aaron Sierra
20 matches
Mail list logo
