From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755562AbdDMSas (ORCPT ); Thu, 13 Apr 2017 14:30:48 -0400 Received: from ec2-52-27-115-49.us-west-2.compute.amazonaws.com ([52.27.115.49]:41319 "EHLO osg.samsung.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755472AbdDMSap (ORCPT ); Thu, 13 Apr 2017 14:30:45 -0400 From: Javier Martinez Canillas To: linux-kernel@vger.kernel.org Cc: Wolfram Sang , Javier Martinez Canillas , devicetree@vger.kernel.org, Gregory Clement , Sebastian Hesselbarth , Jason Cooper , Andrew Lunn , Rob Herring , Mark Rutland , Russell King , linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 04/22] ARM: dts: turris-omnia: Add generic compatible string for I2C EEPROM Date: Thu, 13 Apr 2017 15:28:21 -0300 Message-Id: <20170413182839.25381-5-javier@osg.samsung.com> X-Mailer: git-send-email 2.9.3 In-Reply-To: <20170413182839.25381-1-javier@osg.samsung.com> References: <20170413182839.25381-1-javier@osg.samsung.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Signed-off-by: Javier Martinez Canillas --- Changes in v2: None arch/arm/boot/dts/armada-385-turris-omnia.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/armada-385-turris-omnia.dts b/arch/arm/boot/dts/armada-385-turris-omnia.dts index 28eede180e4f..4185f6b1ba44 100644 --- a/arch/arm/boot/dts/armada-385-turris-omnia.dts +++ b/arch/arm/boot/dts/armada-385-turris-omnia.dts @@ -171,7 +171,7 @@ /* leds device (in STM32F0) at address 0x2b */ eeprom@54 { - compatible = "at,24c64"; + compatible = "at,24c64","atmel,24c64"; reg = <0x54>; /* The EEPROM contains data for bootloader. -- 2.9.3 From mboxrd@z Thu Jan 1 00:00:00 1970 From: javier@osg.samsung.com (Javier Martinez Canillas) Date: Thu, 13 Apr 2017 15:28:21 -0300 Subject: [PATCH v2 04/22] ARM: dts: turris-omnia: Add generic compatible string for I2C EEPROM In-Reply-To: <20170413182839.25381-1-javier@osg.samsung.com> References: <20170413182839.25381-1-javier@osg.samsung.com> Message-ID: <20170413182839.25381-5-javier@osg.samsung.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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. Signed-off-by: Javier Martinez Canillas --- Changes in v2: None arch/arm/boot/dts/armada-385-turris-omnia.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/armada-385-turris-omnia.dts b/arch/arm/boot/dts/armada-385-turris-omnia.dts index 28eede180e4f..4185f6b1ba44 100644 --- a/arch/arm/boot/dts/armada-385-turris-omnia.dts +++ b/arch/arm/boot/dts/armada-385-turris-omnia.dts @@ -171,7 +171,7 @@ /* leds device (in STM32F0) at address 0x2b */ eeprom at 54 { - compatible = "at,24c64"; + compatible = "at,24c64","atmel,24c64"; reg = <0x54>; /* The EEPROM contains data for bootloader. -- 2.9.3