[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20200731153119.GJ1712415@lunn.ch>
Date: Fri, 31 Jul 2020 17:31:19 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Vikas Singh <vikas.singh@...esoftware.com>
Cc: f.fainelli@...il.com, hkallweit1@...il.com, linux@...linux.org.uk,
netdev@...r.kernel.org,
"Calvin Johnson (OSS)" <calvin.johnson@....nxp.com>,
Kuldip Dwivedi <kuldip.dwivedi@...esoftware.com>,
"Madalin Bucur (OSS)" <madalin.bucur@....nxp.com>,
Vikas Singh <vikas.singh@....com>
Subject: Re: [PATCH 2/2] net: phy: Associate device node with fixed PHY
On Wed, Jul 29, 2020 at 07:34:19PM +0530, Vikas Singh wrote:
> Hi Andrew,
>
> I understand your concern But my use case is pretty simple and straightforward.
> As you are already aware of the fact that operating systems running on standard
> server hardware requires standard firmware interfaces to be present in order to
> boot
> and function correctly.
> Here SBBR describes these firmware requirements which covers UEFI & ACPI.
> Therefore I would like to provide dual boot support to such systems which means
> supporting ACPI along with existing DT.
> Now kernels "__fixed_phy_registe() " being a wonderful implementation catters
> almost every thing required for both ACPI & DT
> But fails to register fixed PHYs in case of ACPI because it has no clue of the
> fwnode (of_node in case of DT) to attach with a PHY device.
You failed to answer my question. Why do you need a fixed PHY? Please
could you point me at your DT files so i can at least understand your
hardware.
Andrew
Powered by blists - more mailing lists