From: Florian Fainelli <f.fainelli@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"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: Re: [PATCH 0/2] net: support bgmac with B50212E B1 PHY
Date: Fri, 13 Oct 2017 12:14:39 -0700 [thread overview]
Message-ID: <cf1018f4-f2fb-c3fe-d76a-b968c50e9eca@gmail.com> (raw)
In-Reply-To: <20171012082126.30660-1-zajec5@gmail.com>
On 10/12/2017 01:21 AM, Rafał Miłecki wrote:
> 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
Sorry for the late reply, and it's been applied already, but this looks
good to me, thanks for implementing it this way!
--
Florian
prev parent reply other threads:[~2017-10-13 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 8:21 [PATCH 0/2] net: support bgmac with B50212E B1 PHY Rafał Miłecki
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 [this message]
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=cf1018f4-f2fb-c3fe-d76a-b968c50e9eca@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--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 \
--cc=zajec5@gmail.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).