From: Marcin Wojtas <mw@semihalf.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
netdev <netdev@vger.kernel.org>,
linux-acpi@vger.kernel.org,
"Graeme Gregory" <graeme.gregory@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
"Russell King - ARM Linux" <linux@armlinux.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>,
"Stefan Chulski" <stefanc@marvell.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 v3 0/7] Armada 7k/8k PP2 ACPI support
Date: Wed, 17 Jan 2018 20:03:47 +0100 [thread overview]
Message-ID: <CAPv3WKccT+NPDqHoYGvaJSYawkViNiAJqEFZrykav=4o79Q2VA@mail.gmail.com> (raw)
In-Reply-To: <20180117181148.GA5894@lunn.ch>
Hi Andrew,
2018-01-17 19:11 GMT+01:00 Andrew Lunn <andrew@lunn.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
next prev parent reply other threads:[~2018-01-17 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 16:55 [net-next: PATCH v3 0/7] Armada 7k/8k PP2 ACPI support Marcin Wojtas
2018-01-17 16:55 ` [net-next: PATCH v3 1/7] device property: Introduce fwnode_get_mac_address() Marcin Wojtas
2018-01-17 16:55 ` [net-next: PATCH v3 2/7] device property: Introduce fwnode_get_phy_mode() Marcin Wojtas
2018-01-17 16:55 ` [net-next: PATCH v3 3/7] device property: Introduce fwnode_irq_get() Marcin Wojtas
2018-01-17 16:55 ` [net-next: PATCH v3 4/7] device property: Allow iterating over available child fwnodes Marcin Wojtas
2018-01-17 16:55 ` [net-next: PATCH v3 5/7] net: mvpp2: simplify maintaining enabled ports' list Marcin Wojtas
2018-01-17 16:55 ` [net-next: PATCH v3 6/7] net: mvpp2: use device_*/fwnode_* APIs instead of of_* Marcin Wojtas
2018-01-17 16:55 ` [net-next: PATCH v3 7/7] net: mvpp2: enable ACPI support in the driver Marcin Wojtas
2018-01-17 18:11 ` [net-next: PATCH v3 0/7] Armada 7k/8k PP2 ACPI support Andrew Lunn
2018-01-17 19:03 ` Marcin Wojtas [this message]
2018-01-17 20:20 ` Andrew Lunn
2018-01-18 15:53 ` graeme.gregory
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='CAPv3WKccT+NPDqHoYGvaJSYawkViNiAJqEFZrykav=4o79Q2VA@mail.gmail.com' \
--to=mw@semihalf.com \
--cc=andrew@lunn.ch \
--cc=antoine.tenart@free-electrons.com \
--cc=ard.biesheuvel@linaro.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=graeme.gregory@linaro.org \
--cc=gregory.clement@free-electrons.com \
--cc=jaz@semihalf.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nadavh@marvell.com \
--cc=neta@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=stefanc@marvell.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).