All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 1/2] ARM: dts: dra7-evm: fix compatible name for pcf8575
Date: Thu, 16 Jul 2015 19:03:35 +0530	[thread overview]
Message-ID: <5b6c44c005b3628ce8c90f09ada673893129fb06.1437053417.git.nsekhar@ti.com> (raw)
In-Reply-To: <cover.1437053417.git.nsekhar@ti.com>

Compatible name "ti,pcf8575" used in dra7-evm.dts is not
documented in binding definitions nor is used by the
gpio-pcf857x driver.

The correct compatible to use is "nxp,pcf8575". Fix it.

The existing .dtb works in spite of this issue because
i2c_device_match() falls back to id table based matching
if compatible match fails.

Reported-by: Tero Kristo <t-kristo@ti.com>
Signed-off-by: Sekhar Nori <nsekhar@ti.com>
---
 arch/arm/boot/dts/dra7-evm.dts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/dra7-evm.dts b/arch/arm/boot/dts/dra7-evm.dts
index aa465904f6cc..5f33556175da 100644
--- a/arch/arm/boot/dts/dra7-evm.dts
+++ b/arch/arm/boot/dts/dra7-evm.dts
@@ -401,7 +401,7 @@
 	};
 
 	pcf_gpio_21: gpio@21 {
-		compatible = "ti,pcf8575";
+		compatible = "nxp,pcf8575";
 		reg = <0x21>;
 		lines-initial-states = <0x1408>;
 		gpio-controller;
-- 
2.4.4.408.g16da57c

WARNING: multiple messages have this Message-ID (diff)
From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: dra7-evm: fix compatible name for pcf8575
Date: Thu, 16 Jul 2015 19:03:35 +0530	[thread overview]
Message-ID: <5b6c44c005b3628ce8c90f09ada673893129fb06.1437053417.git.nsekhar@ti.com> (raw)
In-Reply-To: <cover.1437053417.git.nsekhar@ti.com>

Compatible name "ti,pcf8575" used in dra7-evm.dts is not
documented in binding definitions nor is used by the
gpio-pcf857x driver.

The correct compatible to use is "nxp,pcf8575". Fix it.

The existing .dtb works in spite of this issue because
i2c_device_match() falls back to id table based matching
if compatible match fails.

Reported-by: Tero Kristo <t-kristo@ti.com>
Signed-off-by: Sekhar Nori <nsekhar@ti.com>
---
 arch/arm/boot/dts/dra7-evm.dts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/dra7-evm.dts b/arch/arm/boot/dts/dra7-evm.dts
index aa465904f6cc..5f33556175da 100644
--- a/arch/arm/boot/dts/dra7-evm.dts
+++ b/arch/arm/boot/dts/dra7-evm.dts
@@ -401,7 +401,7 @@
 	};
 
 	pcf_gpio_21: gpio at 21 {
-		compatible = "ti,pcf8575";
+		compatible = "nxp,pcf8575";
 		reg = <0x21>;
 		lines-initial-states = <0x1408>;
 		gpio-controller;
-- 
2.4.4.408.g16da57c

  reply	other threads:[~2015-07-16 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 13:33 [PATCH 0/2] ARM: dts: dra7x-evm: fix incorrect compatibles Sekhar Nori
2015-07-16 13:33 ` Sekhar Nori
2015-07-16 13:33 ` Sekhar Nori [this message]
2015-07-16 13:33   ` [PATCH 1/2] ARM: dts: dra7-evm: fix compatible name for pcf8575 Sekhar Nori
2015-07-16 13:33 ` [PATCH 2/2] ARM: dts: dra72-evm: " Sekhar Nori
2015-07-16 13:33   ` Sekhar Nori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5b6c44c005b3628ce8c90f09ada673893129fb06.1437053417.git.nsekhar@ti.com \
    --to=nsekhar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.