[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2470178.4zbWKgRd7I@vostro.rjw.lan>
Date: Wed, 05 Nov 2014 22:04:38 +0100
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Timur Tabi <timur@...eaurora.org>
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Linus Walleij <linus.walleij@...aro.org>,
Alexandre Courbot <gnurou@...il.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
Ning Li <ning.li@...el.com>, Alan Cox <alan@...ux.intel.com>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support
On Tuesday, November 04, 2014 05:18:47 PM Timur Tabi wrote:
> On 11/04/2014 04:56 PM, Timur Tabi wrote:
> >
> > > I'm
> >> not sure how much of that code can be shared between DT and ACPI ATM, but
> >> it looks like at least some of it can be shared.
> >
> > So ACPI does not support the concept if variable length properties?
>
> Ah, I see that it does:
>
> int acpi_dev_prop_read_array(struct acpi_device *adev, const char *propname,
> enum dev_prop_type proptype, void *val,
> size_t nval)
> {
> ...
> if (!val)
> return obj->package.count;
>
>
> If I pass NULL for 'val', it returns the number of items.
Yes, it does that.
If you pass NULL for val to device_property_read_*_array(), it will also
return the number of items in the property. Including the string one.
We're missing a couple of calls that you'd need for pinctrl, but I'd rather
add those along with some users.
Rafael
--
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