From: o.schinagl@ultimaker.com (Olliver Schinagl)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/5] dts: sunxi: correct vendor prefix on OLinuXino a10s micro
Date: Thu, 10 Sep 2015 10:31:18 +0200 [thread overview]
Message-ID: <1441873881-3665-3-git-send-email-o.schinagl@ultimaker.com> (raw)
In-Reply-To: <1441873881-3665-1-git-send-email-o.schinagl@ultimaker.com>
From: Olliver Schinagl <oliver@schinagl.nl>
The OLinuXino A10S micro features an eeprom. According to the eeprom.txt
binding document, we should use the manufacturer and 'at' is not the
proper manufacturer id according to the vendor-prefixes.
This patch takes the proper vendor-prefix and uses it for the eeprom
node.
Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
---
arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dts b/arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dts
index a7e19e4..49a1be6 100644
--- a/arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dts
+++ b/arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dts
@@ -104,7 +104,7 @@
status = "okay";
at24 at 50 {
- compatible = "at,24c16";
+ compatible = "atmel,24c16";
pagesize = <16>;
reg = <0x50>;
read-only;
--
2.1.4
next prev parent reply other threads:[~2015-09-10 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 8:31 [PATCH v2 0/5] Add eeprom to the Olimex series of boards Olliver Schinagl
2015-09-10 8:31 ` [PATCH v2 1/5] dts: sunxi: add eeprom to A10 OLinuXino Lime board Olliver Schinagl
2015-09-10 8:31 ` Olliver Schinagl [this message]
2015-09-10 8:31 ` [PATCH v2 3/5] dts: sunxi: add eeprom to A20 " Olliver Schinagl
2015-09-10 8:31 ` [PATCH v2 4/5] dts: sunxi: add eeprom to A20 OLinuXino Lime2 board Olliver Schinagl
2015-09-10 8:31 ` [PATCH v2 5/5] dts: sunxi: add eeprom to A20 OLinuXino micro board Olliver Schinagl
2015-09-10 18:31 ` [PATCH v2 0/5] Add eeprom to the Olimex series of boards Maxime Ripard
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=1441873881-3665-3-git-send-email-o.schinagl@ultimaker.com \
--to=o.schinagl@ultimaker.com \
--cc=linux-arm-kernel@lists.infradead.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