ARM: dts: efm32: Add generic compatible string for I2C EEPROM
PATCH RESEND 1/4 ARM: dts: efm32: Add generic compatible string for I2C EEPROM
The at24 driver allows to register I2C EEPROM chips using different vendor and devices, but the I2C subsystem does not take the vendor into account when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be taken into account so the driver defines only a set of compatible strings using the "atmel" vendor as a generic fallback for compatible I2C devices.
So add this generic fallback to the device node compatible string to make the device to match the driver using the OF device ID table.
---
arch/arm/boot/dts/efm32gg-dk3750.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/boot/dts/efm32gg-dk3750.dts +1 -1
@@ -37,7 +37,7 @@ }; eeprom at 50 { - compatible = "microchip,24c02"; + compatible = "microchip,24c02", "atmel,24c02"; reg = <0x50>; pagesize = <16>; };
Signature · 1 line
2.14.3
PATCH RESEND 2/4 ARM: dts: keystone: Add generic compatible string for I2C EEPROM
The at24 driver allows to register I2C EEPROM chips using different vendor and devices, but the I2C subsystem does not take the vendor into account when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be taken into account so the driver defines only a set of compatible strings using the "atmel" vendor as a generic fallback for compatible I2C devices.
So add this generic fallback to the device node compatible string to make the device to match the driver using the OF device ID table.
---
arch/arm/boot/dts/keystone-k2e-evm.dts | 2 +- arch/arm/boot/dts/keystone-k2hk-evm.dts | 2 +- arch/arm/boot/dts/keystone-k2l-evm.dts | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
arch/arm/boot/dts/keystone-k2e-evm.dts +1 -1
@@ -82,7 +82,7 @@ &i2c0 { dtt at 50 { - compatible = "at,24c1024"; + compatible = "atmel,24c1024"; reg = <0x50>; }; };
arch/arm/boot/dts/keystone-k2hk-evm.dts +1 -1
@@ -158,7 +158,7 @@ &i2c0 { dtt at 50 { - compatible = "at,24c1024"; + compatible = "atmel,24c1024"; reg = <0x50>; }; };
arch/arm/boot/dts/keystone-k2l-evm.dts +1 -1
@@ -55,7 +55,7 @@ &i2c0 { dtt at 50 { - compatible = "at,24c1024"; + compatible = "atmel,24c1024"; reg = <0x50>; }; };
Signature · 1 line
2.14.3
[email protected]
AppliedRe: [RESEND PATCH 2/4] ARM: dts: keystone: Add generic compatible string for I2C EEPROM
Quoted 8 lines · Javier Martinez Canillas
The at24 driver allows to register I2C EEPROM chips using different vendor and devices, but the I2C subsystem does not take the vendor into account when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be taken into account so the driver defines only a set of compatible strings using the "atmel" vendor as a generic fallback for compatible I2C devices.
Quoted 6 lines
So add this generic fallback to the device node compatible string to make the device to match the driver using the OF device ID table.
Signed-off-by Javier Martinez Canillas <[email protected]>---
Applied
PATCH RESEND 3/4 ARM: dts: lpc18xx: Add generic compatible string for I2C EEPROM
In reply to Javier Martinez CanillasThe at24 driver allows to register I2C EEPROM chips using different vendor and devices, but the I2C subsystem does not take the vendor into account when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be taken into account so the driver defines only a set of compatible strings using the "atmel" vendor as a generic fallback for compatible I2C devices.
So add this generic fallback to the device node compatible string to make the device to match the driver using the OF device ID table.
---
arch/arm/boot/dts/lpc4337-ciaa.dts | 6 +++--- arch/arm/boot/dts/lpc4350-hitex-eval.dts | 2 +- arch/arm/boot/dts/lpc4357-ea4357-devkit.dts | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-)
arch/arm/boot/dts/lpc4337-ciaa.dts +3 -3
@@ -174,17 +174,17 @@ clock-frequency = <400000>; eeprom at 50 { - compatible = "microchip,24c512"; + compatible = "microchip,24c512", "atmel,24c512"; reg = <0x50>; }; eeprom at 51 { - compatible = "microchip,24c02"; + compatible = "microchip,24c02", "atmel,24c02"; reg = <0x51>; }; eeprom at 54 { - compatible = "microchip,24c512"; + compatible = "microchip,24c512", "atmel,24c512"; reg = <0x54>; }; };
arch/arm/boot/dts/lpc4350-hitex-eval.dts +1 -1
@@ -429,7 +429,7 @@ }; eeprom at 50 { - compatible = "nxp,24c02"; + compatible = "nxp,24c02", "atmel,24c02"; reg = <0x50>; };
arch/arm/boot/dts/lpc4357-ea4357-devkit.dts +1 -1
@@ -490,7 +490,7 @@ }; eeprom at 57 { - compatible = "microchip,24c64"; + compatible = "microchip,24c64", "atmel,24c64"; reg = <0x57>; }; };
Signature · 1 line
2.14.3
Arnd Bergmann
AppliedRe: [RESEND PATCH 3/4] ARM: dts: lpc18xx: Add generic compatible string for I2C EEPROM
Quoted 4 lines · Javier Martinez Canillas
The at24 driver allows to register I2C EEPROM chips using different vendor and devices, but the I2C subsystem does not take the vendor into account when matching using the I2C table since it only has device entries.
Quoted 8 lines
But when matching using an OF table, both the vendor and device has to be taken into account so the driver defines only a set of compatible strings using the "atmel" vendor as a generic fallback for compatible I2C devices.
So add this generic fallback to the device node compatible string to make the device to match the driver using the OF device ID table.
Signed-off-by Javier Martinez Canillas <[email protected]>
Applied, thanks
Arnd
PATCH RESEND 4/4 ARM: dts: socfpga: Add generic compatible string for I2C EEPROM
In reply to Javier Martinez CanillasThe at24 driver allows to register I2C EEPROM chips using different vendor and devices, but the I2C subsystem does not take the vendor into account when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be taken into account so the driver defines only a set of compatible strings using the "atmel" vendor as a generic fallback for compatible I2C devices.
So add this generic fallback to the device node compatible string to make the device to match the driver using the OF device ID table.
---
arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dts +1 -1
@@ -237,7 +237,7 @@ clock-frequency = <100000>; at24 at 50 { - compatible = "at24,24c02"; + compatible = "atmel,24c02"; pagesize = <8>; reg = <0x50>; };
Signature · 1 line
2.14.3
Arnd Bergmann
AppliedRe: [RESEND PATCH 4/4] ARM: dts: socfpga: Add generic compatible string for I2C EEPROM
Quoted 4 lines · Javier Martinez Canillas
The at24 driver allows to register I2C EEPROM chips using different vendor and devices, but the I2C subsystem does not take the vendor into account when matching using the I2C table since it only has device entries.
Quoted 8 lines
But when matching using an OF table, both the vendor and device has to be taken into account so the driver defines only a set of compatible strings using the "atmel" vendor as a generic fallback for compatible I2C devices.
So add this generic fallback to the device node compatible string to make the device to match the driver using the OF device ID table.
Signed-off-by Javier Martinez Canillas <[email protected]>
Applied, thanks!
Arnd
Arnd Bergmann
AppliedQuoted 4 lines · Javier Martinez Canillas
The at24 driver allows to register I2C EEPROM chips using different vendor and devices, but the I2C subsystem does not take the vendor into account when matching using the I2C table since it only has device entries.
Quoted 8 lines
But when matching using an OF table, both the vendor and device has to be taken into account so the driver defines only a set of compatible strings using the "atmel" vendor as a generic fallback for compatible I2C devices.
So add this generic fallback to the device node compatible string to make the device to match the driver using the OF device ID table.
Signed-off-by Javier Martinez Canillas <[email protected]>
Applied to next/dt, thanks
Arnd