From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: dts: omap: workarounds for Ethernet PHY strap on DRA71 and DRA72 EVMs
Date: Tue, 27 Jun 2017 20:36:09 +0530 [thread overview]
Message-ID: <cover.1498573382.git.nsekhar@ti.com> (raw)
Hi Tony,
Here are some patches to overcome incorrect Ethernet PHY strap settings
on DRA72x EVM Rev C and DRA71 EVM. Both of these boards use TI's DP83867
PHY.
The incorrect PHY strap settings cause a voilation of PHY specification
and need to be worked around in software as documented in the commit
messages. But there is no known issue that these patches fix.
I did verify that there are no regressions with NFS boot on these boards
after the patches are applied on v4.12-rc4.
The series itself has been rebased on your omap-for-v4.13/dt branch since
it has some conflicts with patches you have queued.
Sekhar Nori (3):
ARM: dts: dra71-evm: workaround incorrect DP83867 RX_CTRL pin strap
ARM: dts: dra72-evm-revc: workaround incorrect DP83867 RX_CTRL pin
strap
ARM: omap2plus_defconfig: enable DP83867 phy driver
arch/arm/boot/dts/dra71-evm.dts | 2 ++
arch/arm/boot/dts/dra72-evm-revc.dts | 2 ++
arch/arm/configs/omap2plus_defconfig | 1 +
3 files changed, 5 insertions(+)
--
2.9.0
next reply other threads:[~2017-06-27 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 15:06 Sekhar Nori [this message]
2017-06-27 15:06 ` [PATCH 1/3] ARM: dts: dra71-evm: workaround incorrect DP83867 RX_CTRL pin strap Sekhar Nori
2017-06-27 15:06 ` [PATCH 2/3] ARM: dts: dra72-evm-revc: " Sekhar Nori
2017-06-27 15:06 ` [PATCH 3/3] ARM: omap2plus_defconfig: enable DP83867 phy driver Sekhar Nori
2017-06-28 16:54 ` Grygorii Strashko
2017-06-28 5:09 ` [PATCH 0/3] ARM: dts: omap: workarounds for Ethernet PHY strap on DRA71 and DRA72 EVMs Sekhar Nori
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=cover.1498573382.git.nsekhar@ti.com \
--to=nsekhar@ti.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;
as well as URLs for NNTP newsgroup(s).