From: Andrew Lunn <andrew@lunn.ch>
To: Vikas Singh <vikas.singh@puresoftware.com>
Cc: f.fainelli@gmail.com, hkallweit1@gmail.com,
linux@armlinux.org.uk, netdev@vger.kernel.org,
"Calvin Johnson (OSS)" <calvin.johnson@oss.nxp.com>,
Kuldip Dwivedi <kuldip.dwivedi@puresoftware.com>,
"Madalin Bucur (OSS)" <madalin.bucur@oss.nxp.com>,
Vikas Singh <vikas.singh@nxp.com>
Subject: Re: [PATCH 2/2] net: phy: Associate device node with fixed PHY
Date: Fri, 31 Jul 2020 17:31:19 +0200 [thread overview]
Message-ID: <20200731153119.GJ1712415@lunn.ch> (raw)
In-Reply-To: <CADvVLtXVVfU3-U8DYPtDnvGoEK2TOXhpuE=1vz6nnXaFBA8pNA@mail.gmail.com>
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
next prev parent reply other threads:[~2020-07-31 15:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 12:13 [PATCH 0/2] Add fwnode helper functions to MDIO bus driver Vikas Singh
2020-07-28 12:13 ` [PATCH 1/2] net: phy: Add fwnode helper functions Vikas Singh
2020-08-01 8:10 ` kernel test robot
2020-07-28 12:13 ` [PATCH 2/2] net: phy: Associate device node with fixed PHY Vikas Singh
2020-07-28 13:00 ` Andrew Lunn
[not found] ` <CADvVLtXVVfU3-U8DYPtDnvGoEK2TOXhpuE=1vz6nnXaFBA8pNA@mail.gmail.com>
2020-07-31 15:31 ` Andrew Lunn [this message]
[not found] ` <CADvVLtUrZDGqwEPO_ApCWK1dELkUEjrH47s1CbYEYOH9XgZMRg@mail.gmail.com>
2020-08-01 9:41 ` Russell King - ARM Linux admin
2020-08-01 15:11 ` Andrew Lunn
2020-08-03 8:33 ` Madalin Bucur (OSS)
2020-08-03 9:07 ` Russell King - ARM Linux admin
2020-08-03 11:45 ` Madalin Bucur (OSS)
2020-08-03 12:57 ` Andrew Lunn
2020-08-03 14:33 ` Madalin Bucur (OSS)
2020-08-03 15:00 ` Andrew Lunn
2020-08-03 16:59 ` Russell King - ARM Linux admin
2020-08-03 14:10 ` Russell King - ARM Linux admin
2020-08-03 14:47 ` Madalin Bucur (OSS)
2020-08-03 16:53 ` Russell King - ARM Linux admin
2020-08-04 5:36 ` Madalin Bucur (OSS)
-- strict thread matches above, loose matches on Subject: below --
2020-07-22 11:32 [PATCH 0/2] Add fwnode helper functions to MDIO bus driver Vikas Singh
2020-07-22 11:32 ` [PATCH 2/2] net: phy: Associate device node with fixed PHY Vikas Singh
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=20200731153119.GJ1712415@lunn.ch \
--to=andrew@lunn.ch \
--cc=calvin.johnson@oss.nxp.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuldip.dwivedi@puresoftware.com \
--cc=linux@armlinux.org.uk \
--cc=madalin.bucur@oss.nxp.com \
--cc=netdev@vger.kernel.org \
--cc=vikas.singh@nxp.com \
--cc=vikas.singh@puresoftware.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).