From: Andrew Lunn <andrew@lunn.ch>
To: Marcin Wojtas <mw@semihalf.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Graeme Gregory <graeme.gregory@linaro.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"<netdev@vger.kernel.org>" <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Russell King - ARM Linux <linux@arm.linux.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 CLEMENT <gregory.clement@free-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@free-ele>
Subject: Re: [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support
Date: Fri, 19 Jan 2018 19:53:53 +0100 [thread overview]
Message-ID: <20180119185353.GF13094@lunn.ch> (raw)
In-Reply-To: <CAPv3WKcYrbfKjsnwZ39Tyq3HN0aneUQZdbeUzLbFgLUbMc3w8Q@mail.gmail.com>
> Since I have a code that can be tested and easily modified to use
> different ACPI approaches with real platform MDIO controller
> (mvmdio.c) and NIC (mvpp2.c), in coming weeks I may be able to find
> some time to prepare a proof of concept based on GenericSerialBus.
> Please expect some RFC patches hopefully right after the coming merge
> window is closed.
It would also be interesting to know how the standardisation process
works.
I'm sure these is a FAQs, so maybe somebody could point us towards it.
Do we need to submit a proposed extension to the ACPI standard at the
same time as the patch? Should we not accept the code into Linux until
the proposal has been accepted? Or can we accept the code
provisionally, with the understanding that if the ACPI committee
rejects the extension, or suggest alternations, we can take the code
out of Linux without having to worry about backwards compatibility?
Thanks
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support
Date: Fri, 19 Jan 2018 19:53:53 +0100 [thread overview]
Message-ID: <20180119185353.GF13094@lunn.ch> (raw)
In-Reply-To: <CAPv3WKcYrbfKjsnwZ39Tyq3HN0aneUQZdbeUzLbFgLUbMc3w8Q@mail.gmail.com>
> Since I have a code that can be tested and easily modified to use
> different ACPI approaches with real platform MDIO controller
> (mvmdio.c) and NIC (mvpp2.c), in coming weeks I may be able to find
> some time to prepare a proof of concept based on GenericSerialBus.
> Please expect some RFC patches hopefully right after the coming merge
> window is closed.
It would also be interesting to know how the standardisation process
works.
I'm sure these is a FAQs, so maybe somebody could point us towards it.
Do we need to submit a proposed extension to the ACPI standard at the
same time as the patch? Should we not accept the code into Linux until
the proposal has been accepted? Or can we accept the code
provisionally, with the understanding that if the ACPI committee
rejects the extension, or suggest alternations, we can take the code
out of Linux without having to worry about backwards compatibility?
Thanks
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Marcin Wojtas <mw@semihalf.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Graeme Gregory <graeme.gregory@linaro.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"<netdev@vger.kernel.org>" <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Russell King - ARM Linux <linux@arm.linux.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 CLEMENT <gregory.clement@free-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Nadav Haklai <nadavh@marvell.com>,
Neta Zur Hershkovits <neta@marvell.com>,
Grzegorz Jaszczyk <jaz@semihalf.com>,
Tomasz Nowicki <tn@semihalf.com>,
Hanjun Guo <hanjun.guo@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>,
mika.westerberg@linux.intel.com
Subject: Re: [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support
Date: Fri, 19 Jan 2018 19:53:53 +0100 [thread overview]
Message-ID: <20180119185353.GF13094@lunn.ch> (raw)
In-Reply-To: <CAPv3WKcYrbfKjsnwZ39Tyq3HN0aneUQZdbeUzLbFgLUbMc3w8Q@mail.gmail.com>
> Since I have a code that can be tested and easily modified to use
> different ACPI approaches with real platform MDIO controller
> (mvmdio.c) and NIC (mvpp2.c), in coming weeks I may be able to find
> some time to prepare a proof of concept based on GenericSerialBus.
> Please expect some RFC patches hopefully right after the coming merge
> window is closed.
It would also be interesting to know how the standardisation process
works.
I'm sure these is a FAQs, so maybe somebody could point us towards it.
Do we need to submit a proposed extension to the ACPI standard at the
same time as the patch? Should we not accept the code into Linux until
the proposal has been accepted? Or can we accept the code
provisionally, with the understanding that if the ACPI committee
rejects the extension, or suggest alternations, we can take the code
out of Linux without having to worry about backwards compatibility?
Thanks
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Marcin Wojtas <mw@semihalf.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Graeme Gregory <graeme.gregory@linaro.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"<netdev@vger.kernel.org>" <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Russell King - ARM Linux <linux@arm.linux.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 CLEMENT <gregory.clement@free-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@free-ele
Subject: Re: [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support
Date: Fri, 19 Jan 2018 19:53:53 +0100 [thread overview]
Message-ID: <20180119185353.GF13094@lunn.ch> (raw)
In-Reply-To: <CAPv3WKcYrbfKjsnwZ39Tyq3HN0aneUQZdbeUzLbFgLUbMc3w8Q@mail.gmail.com>
> Since I have a code that can be tested and easily modified to use
> different ACPI approaches with real platform MDIO controller
> (mvmdio.c) and NIC (mvpp2.c), in coming weeks I may be able to find
> some time to prepare a proof of concept based on GenericSerialBus.
> Please expect some RFC patches hopefully right after the coming merge
> window is closed.
It would also be interesting to know how the standardisation process
works.
I'm sure these is a FAQs, so maybe somebody could point us towards it.
Do we need to submit a proposed extension to the ACPI standard at the
same time as the patch? Should we not accept the code into Linux until
the proposal has been accepted? Or can we accept the code
provisionally, with the understanding that if the ACPI committee
rejects the extension, or suggest alternations, we can take the code
out of Linux without having to worry about backwards compatibility?
Thanks
Andrew
next prev parent reply other threads:[~2018-01-19 18:53 UTC|newest]
Thread overview: 126+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 9:17 [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support Marcin Wojtas
2017-12-18 9:17 ` Marcin Wojtas
2017-12-18 9:17 ` Marcin Wojtas
2017-12-18 9:17 ` [net-next: PATCH 1/8] device property: Introduce fwnode_get_mac_address() Marcin Wojtas
2017-12-18 9:17 ` Marcin Wojtas
2017-12-18 9:17 ` Marcin Wojtas
2017-12-18 9:17 ` [net-next: PATCH 2/8] device property: Introduce fwnode_get_phy_mode() Marcin Wojtas
2017-12-18 9:17 ` Marcin Wojtas
2017-12-18 9:17 ` [net-next: PATCH 3/8] mdio_bus: Introduce fwnode MDIO helpers Marcin Wojtas
2017-12-18 9:17 ` Marcin Wojtas
2017-12-18 9:17 ` Marcin Wojtas
2017-12-18 9:18 ` [net-next: PATCH 4/8] net: mvmdio: add ACPI support Marcin Wojtas
2017-12-18 9:18 ` Marcin Wojtas
2017-12-18 9:18 ` [net-next: PATCH 5/8] net: mvpp2: simplify maintaining enabled ports' list Marcin Wojtas
2017-12-18 9:18 ` Marcin Wojtas
2017-12-18 9:18 ` Marcin Wojtas
2017-12-18 9:18 ` [net-next: PATCH 6/8] net: mvpp2: use device_*/fwnode_* APIs instead of of_* Marcin Wojtas
2017-12-18 9:18 ` Marcin Wojtas
2017-12-18 9:18 ` [net-next: PATCH 7/8] net: mvpp2: handle PHY with its fwnode Marcin Wojtas
2017-12-18 9:18 ` Marcin Wojtas
2017-12-18 9:18 ` [net-next: PATCH 8/8] net: mvpp2: enable ACPI support in the driver Marcin Wojtas
2017-12-18 9:18 ` Marcin Wojtas
2017-12-18 9:40 ` [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support Ard Biesheuvel
2017-12-18 9:40 ` Ard Biesheuvel
2017-12-18 15:49 ` Marcin Wojtas
2017-12-18 15:49 ` Marcin Wojtas
2017-12-18 15:49 ` Marcin Wojtas
2018-01-03 11:00 ` Graeme Gregory
2018-01-03 11:00 ` Graeme Gregory
2018-01-03 11:00 ` Graeme Gregory
2018-01-03 11:12 ` Marcin Wojtas
2018-01-03 11:12 ` Marcin Wojtas
2018-01-03 11:12 ` Marcin Wojtas
2018-01-03 12:47 ` Andrew Lunn
2018-01-03 12:47 ` Andrew Lunn
2018-01-03 12:47 ` Andrew Lunn
2018-01-03 13:13 ` Marcin Wojtas
2018-01-03 13:13 ` Marcin Wojtas
2018-01-03 13:13 ` Marcin Wojtas
2018-01-03 13:33 ` Andrew Lunn
2018-01-03 13:33 ` Andrew Lunn
2018-01-03 13:33 ` Andrew Lunn
2018-01-03 13:36 ` Marcin Wojtas
2018-01-03 13:36 ` Marcin Wojtas
2018-01-03 13:36 ` Marcin Wojtas
2018-01-04 16:09 ` Graeme Gregory
2018-01-04 16:09 ` Graeme Gregory
2018-01-04 16:09 ` Graeme Gregory
2018-01-04 16:20 ` Andrew Lunn
2018-01-04 16:20 ` Andrew Lunn
2018-01-04 16:20 ` Andrew Lunn
2018-01-08 14:45 ` Graeme Gregory
2018-01-08 14:45 ` Graeme Gregory
2018-01-08 14:45 ` Graeme Gregory
2018-01-08 14:53 ` Andrew Lunn
2018-01-08 14:53 ` Andrew Lunn
2018-01-08 14:53 ` Andrew Lunn
2018-01-08 15:14 ` Graeme Gregory
2018-01-08 15:14 ` Graeme Gregory
2018-01-08 15:14 ` Graeme Gregory
2018-01-08 15:42 ` Andrew Lunn
2018-01-08 15:42 ` Andrew Lunn
2018-01-08 15:42 ` Andrew Lunn
2018-01-08 17:17 ` Marcin Wojtas
2018-01-08 17:17 ` Marcin Wojtas
2018-01-08 17:17 ` Marcin Wojtas
2018-01-09 10:19 ` Graeme Gregory
2018-01-09 10:19 ` Graeme Gregory
2018-01-09 10:19 ` Graeme Gregory
2018-01-09 10:22 ` Marcin Wojtas
2018-01-09 10:22 ` Marcin Wojtas
2018-01-09 10:22 ` Marcin Wojtas
2018-01-09 13:00 ` Andrew Lunn
2018-01-09 13:00 ` Andrew Lunn
2018-01-09 13:00 ` Andrew Lunn
2018-01-18 12:31 ` Lorenzo Pieralisi
2018-01-18 12:31 ` Lorenzo Pieralisi
2018-01-18 12:31 ` Lorenzo Pieralisi
2018-01-18 12:31 ` Lorenzo Pieralisi
2018-01-18 13:00 ` Andrew Lunn
2018-01-18 13:00 ` Andrew Lunn
2018-01-18 13:00 ` Andrew Lunn
2018-01-18 13:00 ` Andrew Lunn
2018-01-19 18:07 ` Marcin Wojtas
2018-01-19 18:07 ` Marcin Wojtas
2018-01-19 18:07 ` Marcin Wojtas
2018-01-19 18:07 ` Marcin Wojtas
2018-01-19 18:53 ` Andrew Lunn [this message]
2018-01-19 18:53 ` Andrew Lunn
2018-01-19 18:53 ` Andrew Lunn
2018-01-19 18:53 ` Andrew Lunn
2018-01-20 19:52 ` Mika Westerberg
2018-01-20 19:52 ` Mika Westerberg
2018-01-20 19:52 ` Mika Westerberg
2018-01-21 1:08 ` Andrew Lunn
2018-01-21 1:08 ` Andrew Lunn
2018-01-21 1:08 ` Andrew Lunn
2018-01-21 1:08 ` Andrew Lunn
2018-01-21 10:27 ` Mika Westerberg
2018-01-21 10:27 ` Mika Westerberg
2018-01-21 10:27 ` Mika Westerberg
2018-01-21 10:27 ` Mika Westerberg
2018-01-21 16:13 ` Andrew Lunn
2018-01-21 16:13 ` Andrew Lunn
2018-01-21 16:13 ` Andrew Lunn
2018-01-21 16:13 ` Andrew Lunn
2018-01-21 17:13 ` Ard Biesheuvel
2018-01-21 17:13 ` Ard Biesheuvel
2018-01-21 17:13 ` Ard Biesheuvel
2018-01-21 17:13 ` Ard Biesheuvel
2018-01-21 18:55 ` Andrew Lunn
2018-01-21 18:55 ` Andrew Lunn
2018-01-21 18:55 ` Andrew Lunn
2018-01-21 18:55 ` Andrew Lunn
2017-12-18 14:09 ` Rafael J. Wysocki
2017-12-18 14:09 ` Rafael J. Wysocki
2017-12-19 18:48 ` David Miller
2017-12-19 18:48 ` David Miller
2017-12-19 18:59 ` Marcin Wojtas
2017-12-19 18:59 ` Marcin Wojtas
2017-12-19 20:46 ` Andrew Lunn
2017-12-19 20:46 ` Andrew Lunn
2017-12-19 23:13 ` Marcin Wojtas
2017-12-19 23:13 ` Marcin Wojtas
2017-12-21 19:21 ` Antoine Tenart
2017-12-21 19:21 ` Antoine Tenart
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=20180119185353.GF13094@lunn.ch \
--to=andrew@lunn.ch \
--cc=antoine.tenart@free-electrons.com \
--cc=ard.biesheuvel@linaro.org \
--cc=davem@davemloft.net \
--cc=ezequiel.garcia@free-ele \
--cc=f.fainelli@gmail.com \
--cc=graeme.gregory@linaro.org \
--cc=gregory.clement@free-electrons.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=mw@semihalf.com \
--cc=netdev@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.