[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181026131301.GC30093@lunn.ch>
Date: Fri, 26 Oct 2018 15:13:01 +0200
From: Andrew Lunn <andrew@...n.ch>
To: "Wang, Dongsheng" <dongsheng.wang@...-semitech.com>
Cc: Timur Tabi <timur@...nel.org>,
"Zheng, Joey" <yu.zheng@...-semitech.com>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"robert.moore@...el.com" <robert.moore@...el.com>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Subject: Re: [PATCH v3 2/2] net: qcom/emac: add phy-handle support for ACPI
On Fri, Oct 26, 2018 at 03:04:25AM +0000, Wang, Dongsheng wrote:
> On 2018/10/26 10:37, Timur Tabi wrote:
> > On 10/25/18 9:18 PM, Wang, Dongsheng wrote:
> >> But when I was reading Documentation/acpi/DSD-properties-rules.txt, my
> >> understanding is we should try to conform to DT bindings. So maybe ACPI
> >> doesn't have such a document, just DT bindings.
> > There was an attempt to document DSDs, but it was abandoned after a while.
> >
> > https://github.com/ahs3/dsd
> >
>
> Yes, here's a database concept, and I asked some Intel guys, the answer
> I got was there is no such database or document. :(
Hi Dongsheng
If there is no clear documentation for ACPI, it becomes even more
important that the xgene code is refactored into a central location,
and you make use of it. We really need to avoid every ACPI ethernet
driver doing its own thing.
Thanks
Andrew
Powered by blists - more mailing lists