From: Andrew Lunn <andrew@lunn.ch>
To: Wang Dongsheng <dongsheng.wang@hxt-semitech.com>
Cc: timur@kernel.org, yu.zheng@hxt-semitech.com,
f.fainelli@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v3 2/2] net: qcom/emac: add phy-handle support for ACPI
Date: Thu, 25 Oct 2018 21:24:30 +0200 [thread overview]
Message-ID: <20181025192430.GA16785@lunn.ch> (raw)
In-Reply-To: <7935985e49270ad2948b2a52d26510bdf55572e6.1540459999.git.dongsheng.wang@hxt-semitech.com>
On Thu, Oct 25, 2018 at 06:09:15PM +0800, Wang Dongsheng wrote:
> Use "phy-handle" to porint an internal MDIO device port.
Hi Dongsheng
You are basically defining how all future ACPI based MAC drivers get
access to their PHY. This needs to become part of the ACPI standard,
etc.
This code should not be hidden away in the emac driver. It needs to be
placed somewhere public so other drivers can use it. And it needs good
documentation, including an example of what needs to go into the ACPI
tables, etc.
Thanks
Andrew
next prev parent reply other threads:[~2018-10-26 3:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 8:53 [PATCH v2 0/4] net: qcom/emac: add shared mdio bus support Wang Dongsheng
2018-09-17 8:53 ` [PATCH v2 1/4] net: qcom/emac: split phy_config to mdio bus create and get phy device Wang Dongsheng
2018-09-17 8:53 ` [PATCH v2 2/4] dt-bindings: net: qcom: Add binding for shared mdio bus Wang Dongsheng
2018-09-17 14:50 ` Andrew Lunn
2018-09-17 16:47 ` Wang, Dongsheng
2018-09-17 16:54 ` Florian Fainelli
2018-09-18 8:47 ` Wang, Dongsheng
2018-09-18 12:35 ` Andrew Lunn
2018-09-19 9:19 ` Wang, Dongsheng
2018-09-19 12:25 ` Andrew Lunn
2018-09-19 14:05 ` Timur Tabi
2018-09-19 15:20 ` Andrew Lunn
2018-09-20 13:42 ` Timur Tabi
2018-10-25 10:08 ` [PATCH v3 0/2] net: qcom/emac: add shared mdio bus support Wang Dongsheng
2018-10-25 10:08 ` [PATCH v3 1/2] net: qcom/emac: split phy_config to mdio bus create and get phy device Wang Dongsheng
2018-10-25 10:09 ` [PATCH v3 2/2] net: qcom/emac: add phy-handle support for ACPI Wang Dongsheng
2018-10-25 19:24 ` Andrew Lunn [this message]
2018-10-26 2:18 ` Wang, Dongsheng
2018-10-26 2:37 ` Timur Tabi
2018-10-26 3:04 ` Wang, Dongsheng
2018-10-26 13:13 ` Andrew Lunn
2018-10-29 2:39 ` Wang, Dongsheng
2018-10-29 12:40 ` Andrew Lunn
2018-10-30 5:15 ` Wang, Dongsheng
2018-11-08 7:21 ` [RFC PATCH 0/3] acpi: Add acpi mdio support code Wang Dongsheng
2018-11-08 7:22 ` [RFC PATCH 1/3] " Wang Dongsheng
2018-11-08 7:45 ` Rafael J. Wysocki
2018-11-08 7:55 ` Wang, Dongsheng
2018-11-08 8:01 ` Rafael J. Wysocki
2018-11-12 17:25 ` Andrew Lunn
2018-11-08 7:22 ` [RFC PATCH 2/3] net: qcom/emac: split phy_config to mdio bus create and get phy device Wang Dongsheng
2018-11-08 7:22 ` [RFC PATCH 3/3] net: qcom/emac: add phy-handle support for ACPI Wang Dongsheng
2018-11-08 23:23 ` [RFC PATCH 0/3] acpi: Add acpi mdio support code Andrew Lunn
2018-11-09 0:37 ` Timur Tabi
2018-11-10 9:10 ` Wang, Dongsheng
2018-11-12 17:20 ` Andrew Lunn
2018-11-13 7:36 ` Wang, Dongsheng
2018-11-12 2:52 ` Wang, Dongsheng
2018-09-20 1:33 ` [PATCH v2 2/4] dt-bindings: net: qcom: Add binding for shared mdio bus Wang, Dongsheng
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=20181025192430.GA16785@lunn.ch \
--to=andrew@lunn.ch \
--cc=dongsheng.wang@hxt-semitech.com \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=timur@kernel.org \
--cc=yu.zheng@hxt-semitech.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).