From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Sverdlin Subject: [PATCH v2] dts: keystone: Use new "ti,keystone-i2c" compatible Date: Mon, 14 Sep 2015 11:07:02 +0200 Message-ID: <55F68E36.2030609@nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Grygorii Strashko , Wolfram Sang , "linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" Cc: Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.orgMark Rutland List-Id: devicetree@vger.kernel.org Now as "i2c-davinci" driver has special handling for Keystone it's time to switch the device tree to use new "compatible" property. Old one is left for backwards- compatibility. Signed-off-by: Alexander Sverdlin --- Changes in v2: - As suggested by Mark Rutland, kept the old "compatible" for backwards- compatibility arch/arm/boot/dts/keystone.dtsi | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/arm/boot/dts/keystone.dtsi b/arch/arm/boot/dts/keystone.dtsi index 72816d6..abd7455 100644 --- a/arch/arm/boot/dts/keystone.dtsi +++ b/arch/arm/boot/dts/keystone.dtsi @@ -106,7 +106,7 @@ }; i2c0: i2c@2530000 { - compatible = "ti,davinci-i2c"; + compatible = "ti,keystone-i2c", "ti,davinci-i2c"; reg = <0x02530000 0x400>; clock-frequency = <100000>; clocks = <&clki2c>; @@ -116,7 +116,7 @@ }; i2c1: i2c@2530400 { - compatible = "ti,davinci-i2c"; + compatible = "ti,keystone-i2c", "ti,davinci-i2c"; reg = <0x02530400 0x400>; clock-frequency = <100000>; clocks = <&clki2c>; @@ -126,7 +126,7 @@ }; i2c2: i2c@2530800 { - compatible = "ti,davinci-i2c"; + compatible = "ti,keystone-i2c", "ti,davinci-i2c"; reg = <0x02530800 0x400>; clock-frequency = <100000>; clocks = <&clki2c>;