From: Sekhar Nori <nsekhar@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/3] Fix for rare beaglebone ethernet failures
Date: Thu, 23 Aug 2018 17:11:28 +0530 [thread overview]
Message-ID: <20180823114131.8684-1-nsekhar@ti.com> (raw)
There have been reports of ethernet network failures on beagle
bone black. These have been root caused to ethernet PHY latching
to a different address on boot than what is programmed in DT.
See: https://groups.google.com/d/msg/beagleboard/9mctrG26Mc8/1FuI_i5KW10J
This patch series tries to workaround this suitaiton by patching
device-tree passed to kernel with the correct address. As well as
updating the PHY address U-Boot drivers themselves use.
Tested on beaglebone black rev A4 by simulating the error condition
I was also able to hit the actual hardware error once in a while.
Sekhar Nori (3):
drivers: net: cpsw: add support to update phy address
board: ti: am335x: add support to fixup phy address
configs: am335x_evm: enable OF_BOARD_SETUP
board/ti/am335x/board.c | 78 ++++++++++++++++++++++++++++++++++++++++++++
configs/am335x_evm_defconfig | 1 +
drivers/net/cpsw.c | 29 ++++++++++++++++
include/cpsw.h | 1 +
4 files changed, 109 insertions(+)
--
2.16.2
next reply other threads:[~2018-08-23 11:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 11:41 Sekhar Nori [this message]
2018-08-23 11:41 ` [U-Boot] [PATCH 1/3] drivers: net: cpsw: add support to update phy address Sekhar Nori
2018-08-24 14:13 ` Tom Rini
2018-09-26 12:48 ` [U-Boot] [U-Boot, " Tom Rini
2018-08-23 11:41 ` [U-Boot] [PATCH 2/3] board: ti: am335x: add support to fixup " Sekhar Nori
2018-08-24 14:13 ` Tom Rini
2018-09-26 12:48 ` [U-Boot] [U-Boot, " Tom Rini
2018-08-23 11:41 ` [U-Boot] [PATCH 3/3] configs: am335x_evm: enable OF_BOARD_SETUP Sekhar Nori
2018-08-24 14:13 ` Tom Rini
2018-09-26 12:48 ` [U-Boot] [U-Boot, " Tom Rini
2018-08-24 16:37 ` [U-Boot] [PATCH 0/3] Fix for rare beaglebone ethernet failures Grygorii Strashko
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=20180823114131.8684-1-nsekhar@ti.com \
--to=nsekhar@ti.com \
--cc=u-boot@lists.denx.de \
/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