Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752861AbdLSUqb (ORCPT ); Tue, 19 Dec 2017 15:46:31 -0500 Received: from vps0.lunn.ch ([185.16.172.187]:39094 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750918AbdLSUq2 (ORCPT ); Tue, 19 Dec 2017 15:46:28 -0500 Date: Tue, 19 Dec 2017 21:46:14 +0100 From: Andrew Lunn To: Marcin Wojtas Cc: David Miller , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, netdev , Russell King - ARM Linux , "Rafael J. Wysocki" , Florian Fainelli , Antoine =?iso-8859-1?Q?T=E9nart?= , Thomas Petazzoni , Gregory =?iso-8859-1?Q?Cl=E9ment?= , Ezequiel Garcia , nadavh@marvell.com, Neta Zur Hershkovits , Ard Biesheuvel , Grzegorz Jaszczyk , Tomasz Nowicki Subject: Re: [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support Message-ID: <20171219204614.GA24156@lunn.ch> References: <1513588684-15647-1-git-send-email-mw@semihalf.com> <20171219.134810.48027351795338458.davem@davemloft.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 609 Lines: 16 > 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