From: Guenter Roeck <linux@roeck-us.net>
To: Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Joachim Eastwood <manabian@gmail.com>,
Jean Delvare <jdelvare@suse.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-hwmon@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Ariel D'Alessandro <ariel@vanguardiasur.com.ar>
Subject: [PATCH 3/3] ARM: dts: lpc4350-hitex-eval: Fix binding for SE97
Date: Tue, 5 Jul 2016 09:44:33 -0700 [thread overview]
Message-ID: <1467737073-7949-3-git-send-email-linux@roeck-us.net> (raw)
In-Reply-To: <1467737073-7949-1-git-send-email-linux@roeck-us.net>
The 'compatible = "nxp,jc42"' binding only happened to work because
the Linux driver is named jc42. The driver now supports generic
bindings for JC-42 compatible chips, so use the generic binding instead.
Cc: Ariel D'Alessandro <ariel@vanguardiasur.com.ar>
Cc: Joachim Eastwood <manabian@gmail.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
arch/arm/boot/dts/lpc4350-hitex-eval.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/lpc4350-hitex-eval.dts b/arch/arm/boot/dts/lpc4350-hitex-eval.dts
index 6c9048d4d03c..c97cba1d26a8 100644
--- a/arch/arm/boot/dts/lpc4350-hitex-eval.dts
+++ b/arch/arm/boot/dts/lpc4350-hitex-eval.dts
@@ -424,7 +424,7 @@
/* NXP SE97BTP with temperature sensor + eeprom */
sensor@18 {
- compatible = "nxp,jc42";
+ compatible = "nxp,se97", "jedec,jc-42.4-temp";
reg = <0x18>;
};
--
2.5.0
next prev parent reply other threads:[~2016-07-05 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 16:44 [PATCH 1/3] dt/bindings: Add bindings for JC-42.4 compatible temperature sensors Guenter Roeck
2016-07-05 16:44 ` [PATCH 2/3] hwmon: (jc42) Add support for generic JC-42.4 devicetree binding Guenter Roeck
2016-07-05 16:44 ` Guenter Roeck [this message]
2016-07-11 14:30 ` [PATCH 1/3] dt/bindings: Add bindings for JC-42.4 compatible temperature sensors Rob Herring
2016-07-11 14:48 ` Guenter Roeck
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=1467737073-7949-3-git-send-email-linux@roeck-us.net \
--to=linux@roeck-us.net \
--cc=ariel@vanguardiasur.com.ar \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manabian@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).