[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150811201237.GW4914@rric.localhost>
Date: Tue, 11 Aug 2015 22:12:37 +0200
From: Robert Richter <robert.richter@...iumnetworks.com>
To: David Daney <ddaney@...iumnetworks.com>
CC: David Miller <davem@...emloft.net>, <ddaney.cavm@...il.com>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-mips@...ux-mips.org>, <tomasz.nowicki@...aro.org>,
<sgoutham@...ium.com>, <linux-arm-kernel@...ts.infradead.org>,
<linux-acpi@...r.kernel.org>, <mark.rutland@....com>,
<rafael@...nel.org>, <david.daney@...ium.com>
Subject: Re: [PATCH v2 0/2] net: thunder: Add ACPI support.
On 11.08.15 13:04:55, David Daney wrote:
> >In the future it might be better structured to try and get the OF
> >node, and if that fails then try and use the ACPI method to obtain
> >these values.
>
> Our current approach, as you can see in the patch, is the opposite. If ACPI
> is being used, prefer that over the OF device tree.
>
> You seem to be recommending precedence for OF. It should be consistent
> across all drivers/sub-systems, so do you really think that OF before ACPI
> is the way to go?
If ACPI is enabled then no OF function may be called at all.
With !ACPI or acpi=no kernel parameter, then acpi_disabled is set and
no ACPI function should be called. It always falls back to and only
uses OF/devicetree in this case.
So there is now way to try devicetree first and then use acpi or vice
versa. There is no mixup using acpi or devicetree with the same boot,
either one or the other.
-Robert
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists