From: graeme.gregory@linaro.org
To: Andrew Lunn <andrew@lunn.ch>
Cc: Marcin Wojtas <mw@semihalf.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
linux-acpi@vger.kernel.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
Date: Wed, 3 Jan 2018 11:16:11 +0000 [thread overview]
Message-ID: <20180103111611.GB21230@xora-haswell> (raw)
In-Reply-To: <20171231192354.GB20455@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
On Sun, Dec 31, 2017 at 08:23:54PM +0100, Andrew Lunn wrote:
> > * 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?
>
The infrastructure is there to traverse trees of children, but I don't
think there any helper functions.
Graeme
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-03 11:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 11:58 [net-next: PATCH v2 0/5] Armada 7k/8k PP2 ACPI support Marcin Wojtas
2017-12-31 11:58 ` [net-next: PATCH v2 1/5] device property: Introduce fwnode_get_mac_address() Marcin Wojtas
2018-01-03 11:27 ` Rafael J. Wysocki
2017-12-31 11:58 ` [net-next: PATCH v2 2/5] device property: Introduce fwnode_get_phy_mode() Marcin Wojtas
2018-01-03 11:27 ` Rafael J. Wysocki
2017-12-31 11:58 ` [net-next: PATCH v2 3/5] net: mvpp2: simplify maintaining enabled ports' list Marcin Wojtas
2017-12-31 11:58 ` [net-next: PATCH v2 4/5] net: mvpp2: use device_*/fwnode_* APIs instead of of_* Marcin Wojtas
2017-12-31 19:18 ` Andrew Lunn
2018-01-01 10:04 ` Marcin Wojtas
2017-12-31 11:58 ` [net-next: PATCH v2 5/5] net: mvpp2: enable ACPI support in the driver Marcin Wojtas
2017-12-31 19:23 ` Andrew Lunn
2018-01-01 10:10 ` Marcin Wojtas
2018-01-02 13:33 ` Andrew Lunn
2018-01-02 13:55 ` Marcin Wojtas
2018-01-02 14:08 ` Andrew Lunn
2018-01-02 15:05 ` Marcin Wojtas
2018-01-02 17:22 ` Florian Fainelli
2018-01-03 11:16 ` graeme.gregory [this message]
2018-01-03 11:19 ` Marcin Wojtas
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=20180103111611.GB21230@xora-haswell \
--to=graeme.gregory@linaro.org \
--cc=andrew@lunn.ch \
--cc=antoine.tenart@free-electrons.com \
--cc=ard.biesheuvel@linaro.org \
--cc=davem@davemloft.net \
--cc=ezequiel.garcia@free-electrons.com \
--cc=f.fainelli@gmail.com \
--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=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=neta@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=rafael.j.wysocki@intel.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).