[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180122144342.GB16923@lunn.ch>
Date: Mon, 22 Jan 2018 15:43:42 +0100
From: Andrew Lunn <andrew@...n.ch>
To: David Miller <davem@...emloft.net>
Cc: mw@...ihalf.com, linux-kernel@...r.kernel.org,
antoine.tenart@...e-electrons.com,
linux-arm-kernel@...ts.infradead.org, netdev@...r.kernel.org,
linux-acpi@...r.kernel.org, graeme.gregory@...aro.org,
linux@...linux.org.uk, rafael.j.wysocki@...el.com,
f.fainelli@...il.com, thomas.petazzoni@...e-electrons.com,
gregory.clement@...e-electrons.com, stefanc@...vell.com,
nadavh@...vell.com, neta@...vell.com, ard.biesheuvel@...aro.org,
jaz@...ihalf.com, tn@...ihalf.com
Subject: Re: [net-next: PATCH v4 0/7] Armada 7k/8k PP2 ACPI support
On Mon, Jan 22, 2018 at 09:35:25AM -0500, David Miller wrote:
> From: Marcin Wojtas <mw@...ihalf.com>
> Date: Mon, 22 Jan 2018 14:00:37 +0100
>
> > There's a discussion about the ACPI vs generic MDIO/PHY change under
> > initial version of the patchset, however the patches in question were
> > for now abandoned from further re-sends.
>
> But doesn't the results of that discussion determine whether the way ACPI
> is being used in this patch series is what we want to do or not?
Hi David
The patches submitted here don't involve any ACPI for MDIO or PHY. It
is all MAC. And it is using standard ACPI primitives for devices,
nothing new.
It is not setting any precedence for MDIO and PHY. That is totally out
of scope for these patches. Whatever is decided for MDIO and PHY can
be added later.
Andrew
Powered by blists - more mailing lists