From: Andrew Lunn <andrew@lunn.ch>
To: Marcin Wojtas <mw@semihalf.com>
Cc: "David Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
netdev <netdev@vger.kernel.org>,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Antoine Ténart" <antoine.tenart@free-electrons.com>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Gregory Clément" <gregory.clement@free-electrons.com>,
"Ezequiel Garcia" <ezequiel.garcia@free-electrons.com>,
nadavh@marvell.com, "Neta Zur Hershkovits" <neta@marvell.com>,
"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
"Grzegorz Jaszczyk" <jaz@semihalf.com>,
"Tomasz Nowicki" <tn@semihalf.com>
Subject: Re: [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support
Date: Tue, 19 Dec 2017 21:46:14 +0100 [thread overview]
Message-ID: <20171219204614.GA24156@lunn.ch> (raw)
In-Reply-To: <CAPv3WKddg82waiapD8JzH0pCsWVTE2iT0LFz7PCYrrDDpXqmbw@mail.gmail.com>
> 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
next prev parent reply other threads:[~2017-12-19 20:46 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 9:17 [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support Marcin Wojtas
2017-12-18 9:17 ` [net-next: PATCH 1/8] device property: Introduce fwnode_get_mac_address() Marcin Wojtas
2017-12-18 9:17 ` [net-next: PATCH 2/8] device property: Introduce fwnode_get_phy_mode() Marcin Wojtas
2017-12-18 9:17 ` [net-next: PATCH 3/8] mdio_bus: Introduce fwnode MDIO helpers Marcin Wojtas
2017-12-18 9:18 ` [net-next: PATCH 4/8] net: mvmdio: add ACPI support Marcin Wojtas
2017-12-18 9:18 ` [net-next: PATCH 5/8] net: mvpp2: simplify maintaining enabled ports' list Marcin Wojtas
2017-12-18 9:18 ` [net-next: PATCH 6/8] net: mvpp2: use device_*/fwnode_* APIs instead of of_* Marcin Wojtas
2017-12-18 9:18 ` [net-next: PATCH 7/8] net: mvpp2: handle PHY with its fwnode Marcin Wojtas
2017-12-18 9:18 ` [net-next: PATCH 8/8] net: mvpp2: enable ACPI support in the driver Marcin Wojtas
2017-12-18 9:40 ` [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support Ard Biesheuvel
2017-12-18 15:49 ` Marcin Wojtas
2018-01-03 11:00 ` Graeme Gregory
2018-01-03 11:12 ` Marcin Wojtas
2018-01-03 12:47 ` Andrew Lunn
2018-01-03 13:13 ` Marcin Wojtas
2018-01-03 13:33 ` Andrew Lunn
2018-01-03 13:36 ` Marcin Wojtas
2018-01-04 16:09 ` Graeme Gregory
2018-01-04 16:20 ` Andrew Lunn
2018-01-08 14:45 ` Graeme Gregory
2018-01-08 14:53 ` Andrew Lunn
2018-01-08 15:14 ` Graeme Gregory
2018-01-08 15:42 ` Andrew Lunn
2018-01-08 17:17 ` Marcin Wojtas
2018-01-09 10:19 ` Graeme Gregory
2018-01-09 10:22 ` Marcin Wojtas
2018-01-09 13:00 ` Andrew Lunn
2018-01-18 12:31 ` Lorenzo Pieralisi
2018-01-18 13:00 ` Andrew Lunn
2018-01-19 18:07 ` Marcin Wojtas
2018-01-19 18:53 ` Andrew Lunn
2018-01-20 19:52 ` Mika Westerberg
2018-01-21 1:08 ` Andrew Lunn
2018-01-21 10:27 ` Mika Westerberg
2018-01-21 16:13 ` Andrew Lunn
2018-01-21 17:13 ` Ard Biesheuvel
2018-01-21 18:55 ` Andrew Lunn
2017-12-18 14:09 ` Rafael J. Wysocki
2017-12-19 18:48 ` David Miller
2017-12-19 18:59 ` Marcin Wojtas
2017-12-19 20:46 ` Andrew Lunn [this message]
2017-12-19 23:13 ` Marcin Wojtas
2017-12-21 19:21 ` Antoine Tenart
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=20171219204614.GA24156@lunn.ch \
--to=andrew@lunn.ch \
--cc=antoine.tenart@free-electrons.com \
--cc=ard.biesheuvel@linaro.org \
--cc=davem@davemloft.net \
--cc=ezequiel.garcia@free-electrons.com \
--cc=f.fainelli@gmail.com \
--cc=gregory.clement@free-electrons.com \
--cc=jaz@semihalf.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=neta@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tn@semihalf.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).