[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171231192354.GB20455@lunn.ch>
Date: Sun, 31 Dec 2017 20:23:54 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Marcin Wojtas <mw@...ihalf.com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
netdev@...r.kernel.org, linux-acpi@...r.kernel.org,
graeme.gregory@...aro.org, davem@...emloft.net,
linux@...linux.org.uk, rafael.j.wysocki@...el.com,
f.fainelli@...il.com, antoine.tenart@...e-electrons.com,
thomas.petazzoni@...e-electrons.com,
gregory.clement@...e-electrons.com,
ezequiel.garcia@...e-electrons.com, nadavh@...vell.com,
neta@...vell.com, ard.biesheuvel@...aro.org, jaz@...ihalf.com,
tn@...ihalf.com
Subject: Re: [net-next: PATCH v2 5/5] net: mvpp2: enable ACPI support in the
driver
> * Modify way of obtaining interrupts - with ACPI they are resources
> bound to struct platform_device and it's not possible to obtain
> them directly from the child node. Hence a formula is used, depending
> on the port_id and number of possible CPUs.
Hi Marcin
I know nothing about ACPI. Is this limitation with respect to
interrupts fundamental to ACPI, or just that nobody has implemented
flexible interrupt support yet?
> * Until proper MDIO bus and PHY handling with ACPI is established in the
> kernel, use only link interrupts feature in the driver.
I think interrupts might be interesting with PHY devices, since they
are child nodes of the MDIO device....
Andrew
Powered by blists - more mailing lists