netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Marcin Wojtas <mw@semihalf.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	netdev@vger.kernel.org, rafael@kernel.org,
	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, jaz@semihalf.com,
	tn@semihalf.com, Samer.El-Haj-Mahmoud@arm.com,
	upstream@semihalf.com
Subject: Re: [net-next: PATCH v2 3/8] net: dsa: switch to device_/fwnode_ APIs
Date: Fri, 15 Jul 2022 22:25:40 +0300	[thread overview]
Message-ID: <YtG/NFKC6a0oPTcd@smile.fi.intel.com> (raw)
In-Reply-To: <20220715085012.2630214-4-mw@semihalf.com>

On Fri, Jul 15, 2022 at 10:50:07AM +0200, Marcin Wojtas wrote:
> In order to support both ACPI and DT, modify the generic
> DSA code to use device_/fwnode_ equivalent routines.
> Drop using port's dn field and use only fwnode - update
> all dependent drivers.
> Because support for more generic fwnode is added,
> replace '_of' suffix with '_fw' in related routines.
> No functional change is introduced by this patch.

It's a bit too narrow text in the commit message, can you use more width?

...

> -		ret = of_get_phy_mode(dsa_to_port(ds, 5)->dn, &interface);
> +		ret = of_get_phy_mode(to_of_node(dsa_to_port(ds, 5)->fwnode), &interface);

So, I believe this is expected to be a temporary change and something like
fwnode_get_phy_mode() is on its way, correct?

...

> -			phy_handle = of_parse_phandle(dp->dn, "phy-handle", 0);
> +			phy_handle = of_parse_phandle(to_of_node(dp->fwnode), "phy-handle", 0);

This can be translated to fwnode_find_reference(), but it might require more
changes.

Actually you may start from converting drivers one-by-one to fwnode
APIs (as much as it's possible), and then do with a library call. Up to you.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2022-07-15 19:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15  8:50 [net-next: PATCH v2 0/8] DSA: switch to fwnode_/device_ Marcin Wojtas
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 [this message]
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=YtG/NFKC6a0oPTcd@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=Landen.Chao@mediatek.com \
    --cc=Samer.El-Haj-Mahmoud@arm.com \
    --cc=andrew@lunn.ch \
    --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=mw@semihalf.com \
    --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).