From: Timur Tabi <timur@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Wang, Dongsheng" <dongsheng.wang@hxt-semitech.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"Zheng, Joey" <yu.zheng@hxt-semitech.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 2/4] dt-bindings: net: qcom: Add binding for shared mdio bus
Date: Thu, 20 Sep 2018 08:42:04 -0500 [thread overview]
Message-ID: <78719753-77bd-596a-dfc7-ccd676850283@kernel.org> (raw)
In-Reply-To: <20180919152052.GD17466@lunn.ch>
On 9/19/18 10:20 AM, Andrew Lunn wrote:
> I suspect that is not going to be easy. Last time i looked, the ACPI
> standard had nothing about MDIO busses or PHYs. Marcin Wojtas did some
> work in this area a while back for the mvpp2, but if i remember
> correctly, he worked around this by simply not having a PHY when using
> ACPI, and making use of a MAC interrupt which indicated when there was
> link.
>
> Whoever implements this first needs to be an ACPI expert and probably
> needs to write it up and submit it as an amendment to the ACPI
> standard.
If that's what it takes, then so be it. But adding DT support for a
device that is only used on ACPI platforms is not a worthwhile endeavor.
After ACPI support is merged, Dongsheng can choose to add DT support to
maintain parity, if he wants. Maybe one day the MSM developers will use
the upstream driver on one of their SOCs.
next prev parent reply other threads:[~2018-09-20 13:42 UTC|newest]
Thread overview: 13+ 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 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 [this message]
2018-09-20 1:33 ` 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=78719753-77bd-596a-dfc7-ccd676850283@kernel.org \
--to=timur@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dongsheng.wang@hxt-semitech.com \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.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).