Date: Sun, 31 Dec 2017 20:23:54 +0100
From: Andrew Lunn <andrew@lunn.ch>
To: Marcin Wojtas <mw@semihalf.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        netdev@vger.kernel.org, linux-acpi@vger.kernel.org,
        graeme.gregory@linaro.org, davem@davemloft.net, linux@armlinux.org.uk,
        rafael.j.wysocki@intel.com, f.fainelli@gmail.com,
        antoine.tenart@free-electrons.com, thomas.petazzoni@free-electrons.com,
        gregory.clement@free-electrons.com, ezequiel.garcia@free-electrons.com,
        nadavh@marvell.com, neta@marvell.com, ard.biesheuvel@linaro.org,
        jaz@semihalf.com, tn@semihalf.com
Subject: Re: [net-next: PATCH v2 5/5] net: mvpp2: enable ACPI support in the
 driver
Message-ID: <20171231192354.GB20455@lunn.ch>
References: <1514721520-18964-1-git-send-email-mw@semihalf.com>
 <1514721520-18964-6-git-send-email-mw@semihalf.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1514721520-18964-6-git-send-email-mw@semihalf.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 691
Lines: 18

> * 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