[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPv3WKccT+NPDqHoYGvaJSYawkViNiAJqEFZrykav=4o79Q2VA@mail.gmail.com>
Date: Wed, 17 Jan 2018 20:03:47 +0100
From: Marcin Wojtas <mw@...ihalf.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
netdev <netdev@...r.kernel.org>, linux-acpi@...r.kernel.org,
Graeme Gregory <graeme.gregory@...aro.org>,
"David S. Miller" <davem@...emloft.net>,
Russell King - ARM Linux <linux@...linux.org.uk>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Florian Fainelli <f.fainelli@...il.com>,
Antoine Ténart <antoine.tenart@...e-electrons.com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Gregory Clément
<gregory.clement@...e-electrons.com>,
Stefan Chulski <stefanc@...vell.com>, nadavh@...vell.com,
Neta Zur Hershkovits <neta@...vell.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Grzegorz Jaszczyk <jaz@...ihalf.com>,
Tomasz Nowicki <tn@...ihalf.com>
Subject: Re: [net-next: PATCH v3 0/7] Armada 7k/8k PP2 ACPI support
Hi Andrew,
2018-01-17 19:11 GMT+01:00 Andrew Lunn <andrew@...n.ch>:
> On Wed, Jan 17, 2018 at 05:55:39PM +0100, Marcin Wojtas wrote:
>> Hi,
>>
>> This is a third version of the patchset introducing mvpp2 driver ability
>> to operate with ACPI. Until follow-up generic MDIO is introduced
>> it can using the link interrupt capability (a.k.a. in-band management)
>> on all ports, 1000BaseT RGMII included.
>> Driver operation was tested on top of the net-next branch
>> with both DT and ACPI on MacchiatoBin and Armada 7040 DB boards.
>>
>> The main changes were requested during v2 review, which was
>> adding generic helper routines for:
>> * interating over available fwnodes (new patch 4/7)
>> * getting IRQ directly from fwnode (new patch 3/7)
>
> Hi Marcin
>
> Thanks for adding these helpers. It makes the changes for ACPI much
> less invasive and more natural.
>
> Does the IRQ helper solve the issue of getting an interrupt from a
> child node? I don't see this explicitly mentioned in the commit. It
> seems to be getting it from a device. Is the child a device?
>
I didn't use word 'child', but this is what exactly what the new
helper is capable of. Hence this should easily fit PHY IRQs,
regardless shape of their final ACPI representation. It's now enough
to have an ACPI handle with IRQ defined in its own _CRS method - it
does not have to be a parent / platform_device.
For the reference, please check the IRQs defined under ETHx subnodes
of the PP2 controllers nodes on MacchiatoBin:
https://github.com/MarvellEmbeddedProcessors/edk2-open-platform/blob/71ae395da1661374b0f07d1602afb1eee56e9794/Platforms/Marvell/Armada/AcpiTables/Armada80x0McBin/Dsdt.asl#L201
Best regards,
Marcin
Powered by blists - more mailing lists