From: "Rafał Miłecki" <zajec5@gmail.com>
To: "David S . Miller" <davem@davemloft.net>
Cc: "Jon Mason" <jon.mason@broadcom.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Felix Fietkau" <nbd@openwrt.org>,
netdev@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH 0/3] net-next: use one struct bgmac & add PHY support
Date: Fri, 27 Jan 2017 10:20:40 +0100 [thread overview]
Message-ID: <20170127092043.17413-1-zajec5@gmail.com> (raw)
From: Rafał Miłecki <rafal@milecki.pl>
This patchset adds support for initializing PHY using PHY subsystem.
It's required e.g. for wireless access point devices that use bgmac
supported Ethernet device connected to some external PHY.
Implementing this required accessing phydev in bcma specific code which
wasn't possible with core code allocating struct bgmac on its own. This
is why I needed to modify alloc_etherdev usage first.
Rafał Miłecki (3):
net: bgmac: allocate struct bgmac just once & don't copy it
net: bgmac: drop struct bcma_mdio we don't need anymore
net: bgmac: use PHY subsystem for initializing PHY
drivers/net/ethernet/broadcom/bgmac-bcma-mdio.c | 108 +++++++++++-------------
drivers/net/ethernet/broadcom/bgmac-bcma.c | 2 +-
drivers/net/ethernet/broadcom/bgmac-platform.c | 2 +-
drivers/net/ethernet/broadcom/bgmac.c | 24 +++---
drivers/net/ethernet/broadcom/bgmac.h | 2 +-
5 files changed, 64 insertions(+), 74 deletions(-)
--
2.11.0
next reply other threads:[~2017-01-27 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 9:20 Rafał Miłecki [this message]
2017-01-27 9:20 ` [PATCH 1/3] net: bgmac: allocate struct bgmac just once & don't copy it Rafał Miłecki
2017-01-27 16:02 ` Felix Fietkau
2017-01-27 16:14 ` David Miller
2017-01-27 16:24 ` Rafał Miłecki
2017-01-27 9:20 ` [PATCH 2/3] net: bgmac: drop struct bcma_mdio we don't need anymore Rafał Miłecki
2017-01-27 9:20 ` [PATCH 3/3] net: bgmac: use PHY subsystem for initializing PHY Rafał Miłecki
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=20170127092043.17413-1-zajec5@gmail.com \
--to=zajec5@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jon.mason@broadcom.com \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=rafal@milecki.pl \
/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).