[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7ce75234f8b2dd8bcc747f296f626487.squirrel@twosheds.infradead.org>
Date: Wed, 15 Oct 2014 15:11:18 -0000
From: "David Woodhouse" <dwmw2@...radead.org>
To: "Darren Hart" <dvhart@...ux.intel.com>
Cc: "David Woodhouse" <dwmw2@...radead.org>,
"Mark Rutland" <mark.rutland@....com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
"Mika Westerberg" <mika.westerberg@...ux.intel.com>,
"ACPI Devel Maling List" <linux-acpi@...r.kernel.org>,
"Aaron Lu" <aaron.lu@...el.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"Linus Walleij" <linus.walleij@...aro.org>,
"Alexandre Courbot" <gnurou@...il.com>,
"Dmitry Torokhov" <dmitry.torokhov@...il.com>,
"Bryan Wu" <cooloney@...il.com>,
"grant.likely@...aro.org" <grant.likely@...aro.org>,
"Arnd Bergmann" <arnd@...db.de>, dvhart@...radead.org
Subject: Re: [PATCH v4 00/13] Add ACPI _DSD and unified device properties
support
> My comment was going to be along the same lines. It is an optional
> parameter, which is what I would expect for a firmware-specific type of
> property.
Right. Fundamentally, device properties (in DT or ACPI) exist to describe
the hardware in a generic and abstract fashion. It's a slippery slope from
saying "you don't need this property because you know you whether you are
on the *foo* architecture", to saying "you don't this property because you
know whether you're on a Assabet or not." I think it's wrong to go down
that path.
--
dwmw2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists