From: Sekhar Nori <nsekhar@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] ARM: dts: omap: workarounds for Ethernet PHY strap on DRA71 and DRA72 EVMs
Date: Wed, 9 Aug 2017 19:32:46 +0530 [thread overview]
Message-ID: <cover.1502284400.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.
Changes from v1:
- Add Grygorii's reviewed-by to 3/3
- Rebase on latest mainline master
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 | 3 +++
arch/arm/configs/omap2plus_defconfig | 1 +
3 files changed, 6 insertions(+)
--
2.9.0
next reply other threads:[~2017-08-09 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 14:02 Sekhar Nori [this message]
2017-08-09 14:02 ` [PATCH v2 1/3] ARM: dts: dra71-evm: workaround incorrect DP83867 RX_CTRL pin strap Sekhar Nori
[not found] ` <cover.1502284400.git.nsekhar-l0cyMroinI0@public.gmane.org>
2017-08-09 14:02 ` [PATCH v2 2/3] ARM: dts: dra72-evm-revc: " Sekhar Nori
2017-08-09 14:02 ` [PATCH v2 3/3] ARM: omap2plus_defconfig: enable DP83867 phy driver Sekhar Nori
2017-08-09 22:26 ` [PATCH v2 0/3] ARM: dts: omap: workarounds for Ethernet PHY strap on DRA71 and DRA72 EVMs Grygorii Strashko
[not found] ` <ca0d0615-d813-d00b-e853-25df9a5c49b6-l0cyMroinI0@public.gmane.org>
2017-08-10 17:37 ` Tony Lindgren
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.1502284400.git.nsekhar@ti.com \
--to=nsekhar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).