From: "Rafał Miłecki" <zajec5@gmail.com>
To: "David S . Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Jon Mason" <jon.mason@broadcom.com>,
"Steve Lin" <steven.lin1@broadcom.com>,
"Tobias Klauser" <tklauser@distanz.ch>,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH 0/2] net: support bgmac with B50212E B1 PHY
Date: Thu, 12 Oct 2017 10:21:24 +0200 [thread overview]
Message-ID: <20171012082126.30660-1-zajec5@gmail.com> (raw)
From: Rafał Miłecki <rafal@milecki.pl>
I got a report that a board with BCM47189 SoC and B50212E B1 PHY doesn't
work well some devices as there is massive ping loss. After analyzing
PHY state it has appeared that is runs in slave mode and doesn't auto
switch to master properly when needed.
This patchset fixes this by:
1) Adding new flag support to the PHY driver for setting master mode
2) Modifying bgmac to request master mode for reported hardware
Rafał Miłecki (2):
net: phy: broadcom: support new device flag for setting master mode
net: bgmac: enable master mode for BCM54210E and B50212E PHYs
drivers/net/ethernet/broadcom/bgmac-bcma.c | 8 +++++++-
drivers/net/phy/broadcom.c | 6 ++++++
include/linux/brcmphy.h | 1 +
3 files changed, 14 insertions(+), 1 deletion(-)
--
2.11.0
next reply other threads:[~2017-10-12 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 8:21 Rafał Miłecki [this message]
2017-10-12 8:21 ` [PATCH 1/2] net: phy: broadcom: support new device flag for setting master mode Rafał Miłecki
2017-10-12 8:21 ` [PATCH 2/2] net: bgmac: enable master mode for BCM54210E and B50212E PHYs Rafał Miłecki
2017-10-13 5:59 ` [PATCH 0/2] net: support bgmac with B50212E B1 PHY David Miller
2017-10-13 19:14 ` Florian Fainelli
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=20171012082126.30660-1-zajec5@gmail.com \
--to=zajec5@gmail.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=jon.mason@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=steven.lin1@broadcom.com \
--cc=tklauser@distanz.ch \
/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).