From: Nishanth Menon <nm@ti.com>
To: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
netdev@vger.kernel.org
Cc: "Nishanth Menon" <nm@ti.com>,
linux-doc@vger.kernel.org, "Tony Lindgren" <tony@atomide.com>,
linux-kernel@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: omap2430-sdp: add flags for ethernet functionality
Date: Wed, 11 Dec 2013 04:21:45 -0600 [thread overview]
Message-ID: <1386757305-12545-3-git-send-email-nm@ti.com> (raw)
In-Reply-To: <1386757305-12545-1-git-send-email-nm@ti.com>
Ethernet transition from board file to dts missed the required pdata
conversion. So fix the same.
Signed-off-by: Nishanth Menon <nm@ti.com>
---
arch/arm/boot/dts/omap2430-sdp.dts | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/omap2430-sdp.dts b/arch/arm/boot/dts/omap2430-sdp.dts
index 2c90d29..ec9263a 100644
--- a/arch/arm/boot/dts/omap2430-sdp.dts
+++ b/arch/arm/boot/dts/omap2430-sdp.dts
@@ -39,6 +39,11 @@
ranges = <5 0 0x08000000 0x01000000>;
ethernet@gpmc {
compatible = "smsc,lan91c94";
+ reg-io-width = <2>;
+ smsc,nowait;
+ smsc,leda = "100_10";
+ smsc,ledb = "TX_RX";
+
interrupt-parent = <&gpio5>;
interrupts = <21 IRQ_TYPE_LEVEL_LOW>; /* gpio149 */
reg = <5 0x300 0xf>;
--
1.7.9.5
prev parent reply other threads:[~2013-12-11 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 10:21 [PATCH 0/2] net: smc91x: add DT flags for legacy platforms Nishanth Menon
2013-12-11 10:21 ` [PATCH 1/2] net: smc91x: Read hardware behavior flags from device tree Nishanth Menon
2013-12-11 16:04 ` Tony Lindgren
[not found] ` <20131211160440.GA13171-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2013-12-11 18:27 ` Nishanth Menon
2013-12-11 10:21 ` Nishanth Menon [this message]
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=1386757305-12545-3-git-send-email-nm@ti.com \
--to=nm@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@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 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).