[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171219204614.GA24156@lunn.ch>
Date: Tue, 19 Dec 2017 21:46:14 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Marcin Wojtas <mw@...ihalf.com>
Cc: David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
netdev <netdev@...r.kernel.org>,
Russell King - ARM Linux <linux@....linux.org.uk>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Florian Fainelli <f.fainelli@...il.com>,
Antoine Ténart
<antoine.tenart@...e-electrons.com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Gregory Clément
<gregory.clement@...e-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
nadavh@...vell.com, Neta Zur Hershkovits <neta@...vell.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Grzegorz Jaszczyk <jaz@...ihalf.com>,
Tomasz Nowicki <tn@...ihalf.com>
Subject: Re: [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support
> Of course! v2 will not have such problem, I've been waiting however
> for the feedback about the ACPI representation. Anyway, I'm strongly
> leaning towards using _ADR/_CID objects in PHY's nodes for ACPI, so
> maybe I'll just issue the v2 in order to push the discussion a bit
> forward.
Hi Marcin
I know ~0 about ACPI. But what seems to be missing for me is
documentation. You are defining a ABI here, which all future MDIO
busses, PHYs, and to some extent Ethernet switches need to follow. So
i would expect this to be documented somewhere.
How does documentation work in the ACPI world?
Andrew
Powered by blists - more mailing lists