From: Andrew Lunn <andrew@lunn.ch>
To: David Miller <davem@davemloft.net>, shawnguo@kernel.org
Cc: netdev <netdev@vger.kernel.org>,
linux ARM <linux-arm-kernel@lists.infradead.org>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
Andrew Lunn <andrew@lunn.ch>
Subject: [PATCH 2/2] ARM: VF610: ZII devel b: Add switch eeprom-length properties
Date: Fri, 26 May 2017 01:44:44 +0200 [thread overview]
Message-ID: <1495755884-31341-3-git-send-email-andrew@lunn.ch> (raw)
In-Reply-To: <1495755884-31341-1-git-send-email-andrew@lunn.ch>
Two of the Ethernet switches on this board have EEPROMs connected.
Add the eeprom-length property to the device tree, making it possible
to access the EEPROM using ethtool -e.
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
---
arch/arm/boot/dts/vf610-zii-dev-rev-b.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-zii-dev-rev-b.dts b/arch/arm/boot/dts/vf610-zii-dev-rev-b.dts
index 37f95427616f..acdf12ad0622 100644
--- a/arch/arm/boot/dts/vf610-zii-dev-rev-b.dts
+++ b/arch/arm/boot/dts/vf610-zii-dev-rev-b.dts
@@ -78,6 +78,7 @@
interrupts = <27 IRQ_TYPE_LEVEL_LOW>;
interrupt-controller;
#interrupt-cells = <2>;
+ eeprom-length = <512>;
ports {
#address-cells = <1>;
@@ -163,6 +164,7 @@
interrupts = <26 IRQ_TYPE_LEVEL_LOW>;
interrupt-controller;
#interrupt-cells = <2>;
+ eeprom-length = <512>;
ports {
#address-cells = <1>;
--
2.11.0
next prev parent reply other threads:[~2017-05-25 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 23:44 [PATCH 0/2] Document and use eeprom-length property Andrew Lunn
2017-05-25 23:44 ` [PATCH 1/2] net: dsa: mv88e6xxx: Add eeprom-length to binding Andrew Lunn
2017-05-25 23:44 ` Andrew Lunn [this message]
2017-05-27 8:10 ` [PATCH 2/2] ARM: VF610: ZII devel b: Add switch eeprom-length properties Shawn Guo
2017-05-26 19:02 ` [PATCH 0/2] Document and use eeprom-length property David Miller
2017-05-27 8:13 ` Shawn Guo
2017-05-27 22:42 ` David Miller
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=1495755884-31341-3-git-send-email-andrew@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=shawnguo@kernel.org \
--cc=vivien.didelot@savoirfairelinux.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 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).