From: Felipe Balbi <balbi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
devicetree@vger.kernel.org, Schuyler Patton <spatton@ti.com>,
Koen Kooi <koen@dominion.thruhere.net>, Tom Rini <trini@ti.com>,
Kevin Hilman <khilman@linaro.org>,
stable@vger.kernel.org, Felipe Balbi <balbi@ti.com>
Subject: [PATCH] arm: dts: am335x-bone-common: add collision and carrier sense pinmux
Date: Mon, 5 Jan 2015 15:44:14 -0600 [thread overview]
Message-ID: <1420494254-24314-1-git-send-email-balbi@ti.com> (raw)
From: Schuyler Patton <spatton@ti.com>
Added pin mux definitions for collision and carrier sense errors coming
from the ethernet phy. Without these two signals the MAC ends up ignoring
the errors detected by the PHY which end up causing a lower throughput
problem when the phy is in half duplex mode such as connected through a hub.
Fixes: 2ba3549 (ARM: dts: am335x-bone*: add DT for BeagleBone Black)
Cc: Koen Kooi <koen@dominion.thruhere.net>
Cc: Tom Rini <trini@ti.com>
Cc: Kevin Hilman <khilman@linaro.org>
Cc: <stable@vger.kernel.org> # v3.13+
Signed-off-by: Schuyler Patton <spatton@ti.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
---
arch/arm/boot/dts/am335x-bone-common.dtsi | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-bone-common.dtsi b/arch/arm/boot/dts/am335x-bone-common.dtsi
index 6cc25ed..4b29fad 100644
--- a/arch/arm/boot/dts/am335x-bone-common.dtsi
+++ b/arch/arm/boot/dts/am335x-bone-common.dtsi
@@ -97,6 +97,8 @@
cpsw_default: cpsw_default {
pinctrl-single,pins = <
/* Slave 1 */
+ 0x108 (PIN_INPUT | MUX_MODE0) /* mii1_col.mii1_col */
+ 0x10c (PIN_INPUT | MUX_MODE0) /* mii1_crs.mii1_crs */
0x110 (PIN_INPUT_PULLUP | MUX_MODE0) /* mii1_rxerr.mii1_rxerr */
0x114 (PIN_OUTPUT_PULLDOWN | MUX_MODE0) /* mii1_txen.mii1_txen */
0x118 (PIN_INPUT_PULLUP | MUX_MODE0) /* mii1_rxdv.mii1_rxdv */
@@ -116,6 +118,8 @@
cpsw_sleep: cpsw_sleep {
pinctrl-single,pins = <
/* Slave 1 reset value */
+ 0x108 (PIN_INPUT_PULLDOWN | MUX_MODE7)
+ 0x10c (PIN_INPUT_PULLDOWN | MUX_MODE7)
0x110 (PIN_INPUT_PULLDOWN | MUX_MODE7)
0x114 (PIN_INPUT_PULLDOWN | MUX_MODE7)
0x118 (PIN_INPUT_PULLDOWN | MUX_MODE7)
--
2.2.0
reply other threads:[~2015-01-05 21:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1420494254-24314-1-git-send-email-balbi@ti.com \
--to=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@linaro.org \
--cc=koen@dominion.thruhere.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=spatton@ti.com \
--cc=stable@vger.kernel.org \
--cc=tony@atomide.com \
--cc=trini@ti.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).