From: Marcin Wojtas <mw@semihalf.com>
To: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
netdev@vger.kernel.org
Cc: rafael@kernel.org, andriy.shevchenko@linux.intel.com,
sean.wang@mediatek.com, Landen.Chao@mediatek.com,
linus.walleij@linaro.org, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux@armlinux.org.uk,
hkallweit1@gmail.com, gjb@semihalf.com, mw@semihalf.com,
jaz@semihalf.com, tn@semihalf.com, Samer.El-Haj-Mahmoud@arm.com,
upstream@semihalf.com
Subject: [net-next: PATCH v2 0/8] DSA: switch to fwnode_/device_
Date: Fri, 15 Jul 2022 10:50:04 +0200 [thread overview]
Message-ID: <20220715085012.2630214-1-mw@semihalf.com> (raw)
Hi,
This is a re-spin of the DSA migration to fwnode_/device_ API.
As agreed, the ACPI-specific patches were kept aside for now,
until the MDIOSerialBus is submitted and accepted in the ACPI
Specification.
The patchset addresses all comments from the first version,
mostly related to usage of proper device_ helpers. Also,
as it was suggested, fwnode_dev_node_match() routine
was taken out of the network code and introduced as a generic
one in drivers/base/property.c
The details can be found in the changelog below. Any comments or
remarks will be appreciated.
Each patch was tested on:
* On EspressoBIN
* On SolidRun CN913x CEx7 Eval Board
IMPORTANT NOTE:
This patchset is rebased on top of the one from Russell
(https://lore.kernel.org/all/Ys7RdzGgHbYiPyB1@shell.armlinux.org.uk/),
so a care should be taken, when merging to the net-next tree.
Best regards,
Marcin
Changelog v1->v2:
1/8
* Drop unnecessary check in fixed_phy_get_gpiod()
* Improve line breaking
* Use device_set_node & dev_fwnode
2/8
* Switch to fwnode_property_count_u32 and fix comparison
in if statement.
3/8
* Drop dn usage entirely and use dp->fwnode only. Update
all dependent drivers to use to_of_node.
* Use device_set_node, dev_fwnode & device_get_named_child_node
* Replace '_of' routines suffix with '_fw'
4/8
* Use device_set_node
5/8
* New patch
6/8
* Use device_match_fwnode
* Restore EXPORT_SYMBOL()
7/8
* Get rid of of_mdiobus_register_device
8/8
* Use dev_fwnode in mv88e6xxx_probe
* Simplify condition checks in mv88e6xxx_probe as suggested by Andy
Marcin Wojtas (8):
net: phy: fixed_phy: switch to fwnode_ API
net: mdio: switch fixed-link PHYs API to fwnode_
net: dsa: switch to device_/fwnode_ APIs
net: mvpp2: initialize port fwnode pointer
device property: introduce fwnode_dev_node_match
net: core: switch to fwnode_find_net_device_by_node()
net: mdio: introduce fwnode_mdiobus_register_device()
net: dsa: mv88e6xxx: switch to device_/fwnode_ APIs
include/linux/etherdevice.h | 1 +
include/linux/fwnode_mdio.h | 22 ++++
include/linux/of_net.h | 6 -
include/linux/phy_fixed.h | 4 +-
include/linux/property.h | 2 +
include/net/dsa.h | 2 +-
net/dsa/dsa_priv.h | 4 +-
drivers/base/property.c | 22 ++++
drivers/net/dsa/mt7530.c | 2 +-
drivers/net/dsa/mv88e6xxx/chip.c | 57 ++++-----
drivers/net/dsa/qca8k.c | 2 +-
drivers/net/dsa/realtek/rtl8365mb.c | 2 +-
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c | 2 +-
drivers/net/mdio/fwnode_mdio.c | 129 ++++++++++++++++++++
drivers/net/mdio/of_mdio.c | 111 +----------------
drivers/net/phy/fixed_phy.c | 39 +++---
net/core/net-sysfs.c | 25 ++--
net/dsa/dsa2.c | 101 ++++++++-------
net/dsa/port.c | 70 ++++++-----
net/dsa/slave.c | 7 +-
20 files changed, 328 insertions(+), 282 deletions(-)
--
2.29.0
next reply other threads:[~2022-07-15 8:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 8:50 Marcin Wojtas [this message]
2022-07-15 8:50 ` [net-next: PATCH v2 1/8] net: phy: fixed_phy: switch to fwnode_ API Marcin Wojtas
2022-07-15 17:20 ` Florian Fainelli
2022-07-15 19:10 ` Marcin Wojtas
2022-07-15 8:50 ` [net-next: PATCH v2 2/8] net: mdio: switch fixed-link PHYs API to fwnode_ Marcin Wojtas
2022-07-15 8:50 ` [net-next: PATCH v2 3/8] net: dsa: switch to device_/fwnode_ APIs Marcin Wojtas
2022-07-15 19:25 ` Andy Shevchenko
2022-07-15 19:36 ` Marcin Wojtas
2022-07-15 8:50 ` [net-next: PATCH v2 4/8] net: mvpp2: initialize port fwnode pointer Marcin Wojtas
2022-07-15 8:50 ` [net-next: PATCH v2 5/8] device property: introduce fwnode_dev_node_match Marcin Wojtas
2022-07-15 19:36 ` Andy Shevchenko
2022-07-15 19:42 ` Andy Shevchenko
2022-07-15 23:15 ` Marcin Wojtas
2022-07-18 12:26 ` Andy Shevchenko
2022-07-15 8:50 ` [net-next: PATCH v2 6/8] net: core: switch to fwnode_find_net_device_by_node() Marcin Wojtas
2022-07-15 8:50 ` [net-next: PATCH v2 7/8] net: mdio: introduce fwnode_mdiobus_register_device() Marcin Wojtas
2022-07-15 8:50 ` [net-next: PATCH v2 8/8] net: dsa: mv88e6xxx: switch to device_/fwnode_ APIs Marcin Wojtas
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=20220715085012.2630214-1-mw@semihalf.com \
--to=mw@semihalf.com \
--cc=Landen.Chao@mediatek.com \
--cc=Samer.El-Haj-Mahmoud@arm.com \
--cc=andrew@lunn.ch \
--cc=andriy.shevchenko@linux.intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gjb@semihalf.com \
--cc=hkallweit1@gmail.com \
--cc=jaz@semihalf.com \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=rafael@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=tn@semihalf.com \
--cc=upstream@semihalf.com \
--cc=vivien.didelot@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).