[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ee74146068b04503a89c4a05d4e19792@HXTBJIDCEMVIW02.hxtcorp.net>
Date: Mon, 12 Nov 2018 02:52:46 +0000
From: "Wang, Dongsheng" <dongsheng.wang@...-semitech.com>
To: Andrew Lunn <andrew@...n.ch>
CC: "timur@...nel.org" <timur@...nel.org>,
"Zheng, Joey" <yu.zheng@...-semitech.com>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [RFC PATCH 0/3] acpi: Add acpi mdio support code
On 2018/11/9 7:23, Andrew Lunn wrote:
> I'm just trying to ensure whatever is defined is flexible enough that
> we really can later support everything which DT does. We have PHYs on
> MDIO busses, inside switches, which are on MDIO busses, which are
> inside Ethernet interfaces, etc.
>
> An MDIO bus is very similar to an i2c bus. How is that described in
> ACPI? Anything we can learn from that?
All the documents I've seen are from UEFII/ACPICA and I have not seen any
independent description of MDIO in the ACPI documents. Maybe I missed a
document, too.
I think not all devices need to be described in ACPI. The ACPI defines what
should be included in a device, as well as some special definitions. Our
MDIO
doesn't need a special definition, because it's enough to use a generic ACPI
description. I think that's why MDIO doesn't have a separate description.
Cheers,
Dongsheng
Powered by blists - more mailing lists