[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YNObfrJN0Qk5RO+x@lunn.ch>
Date: Wed, 23 Jun 2021 22:37:18 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Marcin Wojtas <mw@...ihalf.com>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
davem@...emloft.net, kuba@...nel.org, linux@...linux.org.uk,
jaz@...ihalf.com, gjb@...ihalf.com, upstream@...ihalf.com,
Samer.El-Haj-Mahmoud@....com, jon@...id-run.com, tn@...ihalf.com,
rjw@...ysocki.net, lenb@...nel.org
Subject: Re: [net-next: PATCH v3 5/6] net: mvpp2: enable using phylink with
ACPI
> +static bool mvpp2_use_acpi_compat_mode(struct fwnode_handle *port_fwnode)
> +{
> + if (!is_acpi_node(port_fwnode))
> + return false;
> +
> + return (!fwnode_property_present(port_fwnode, "phy-handle") &&
> + !fwnode_property_present(port_fwnode, "managed") &&
> + !fwnode_get_named_child_node(port_fwnode, "fixed-link"));
I'm not too sure about this last one. You only use fixed-link when
connecting to an Ethernet switch. I doubt anybody will try ACPI and a
switch. It has been agreed, ACPI is for simple hardware, and you need
to use DT for advanced hardware configurations.
What is your use case for fixed-link?
Andrew
Powered by blists - more mailing lists