From: "Rafał Miłecki" <zajec5@gmail.com>
To: "David S . Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: "Xo Wang" <xow@google.com>, "Joel Stanley" <joel@jms.id.au>,
"Jon Mason" <jon.mason@broadcom.com>,
"Jaedon Shin" <jaedon.shin@gmail.com>,
netdev@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH V2 0/3] net-next: Broadcom PHY driver cleanup
Date: Wed, 25 Jan 2017 21:00:24 +0100 [thread overview]
Message-ID: <20170125200027.14387-1-zajec5@gmail.com> (raw)
From: Rafał Miłecki <rafal@milecki.pl>
I will probably need to use broadcom.ko for PHY connected to interface
of bgmac supported device so I started looking at it willing to
understand it better.
I found AUXCTL part of the driver / lib a bit confusing and hard to read
so I'm trying to clean it up a bit. I hope this patchset makes following
AUXCTL operations much easier making it clear which defines are for
registers and which for values.
There is no functional change in this pachset.
Rafał Miłecki (3):
net: phy: broadcom: use auxctl reading helper in BCM54612E code
net: phy: broadcom: drop duplicated define for RGMII SKEW delay
net: phy: bcm-phy-lib: clean up remaining AUXCTL register defines
drivers/net/phy/broadcom.c | 8 +++-----
include/linux/brcmphy.h | 16 +++++++---------
2 files changed, 10 insertions(+), 14 deletions(-)
--
2.11.0
next reply other threads:[~2017-01-25 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 20:00 Rafał Miłecki [this message]
2017-01-25 20:00 ` [PATCH V2 1/3] net: phy: broadcom: use auxctl reading helper in BCM54612E code Rafał Miłecki
2017-01-25 20:00 ` [PATCH V2 2/3] net: phy: broadcom: drop duplicated define for RGMII SKEW delay Rafał Miłecki
2017-01-25 20:34 ` Florian Fainelli
2017-01-25 20:00 ` [PATCH V2 3/3] net: phy: bcm-phy-lib: clean up remaining AUXCTL register defines Rafał Miłecki
2017-01-25 20:35 ` Florian Fainelli
2017-01-26 4:14 ` [PATCH V2 0/3] net-next: Broadcom PHY driver cleanup David Miller
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=20170125200027.14387-1-zajec5@gmail.com \
--to=zajec5@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jaedon.shin@gmail.com \
--cc=joel@jms.id.au \
--cc=jon.mason@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=xow@google.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).