netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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.nxp.com, kuldip.dwivedi@puresoftware.com,
	madalin.bucur@oss.nxp.com, vikas.singh@nxp.com
Subject: Re: [PATCH 2/2] net: phy: Associate device node with fixed PHY
Date: Tue, 28 Jul 2020 15:00:01 +0200	[thread overview]
Message-ID: <20200728130001.GB1712415@lunn.ch> (raw)
In-Reply-To: <1595938400-13279-3-git-send-email-vikas.singh@puresoftware.com>

On Tue, Jul 28, 2020 at 05:43:20PM +0530, Vikas Singh wrote:
> This patch will extend "struct fixed_phy_status" by adding new
> "struct device *dev" member entry in it.
> This change will help to handle the fixed phy registration in
> ACPI probe case for fwnodes.

Hi Vikas

Please could you tell us more about your use cases. It seems that
using ACPI on ARM is limited to SBSA/SBSA system. It is not clear to
me why you would need a fixed-link PHY on such a system.

   Andrew

  reply	other threads:[~2020-07-28 13:00 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 [this message]
     [not found]     ` <CADvVLtXVVfU3-U8DYPtDnvGoEK2TOXhpuE=1vz6nnXaFBA8pNA@mail.gmail.com>
2020-07-31 15:31       ` Andrew Lunn
     [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=20200728130001.GB1712415@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).