From: Darren Hart <dvhart@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Grant Likely <grant.likely@secretlab.ca>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Alexandre Courbot <acourbot@nvidia.com>,
Linus Walleij <linus.walleij@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI / GPIO: Pass index to acpi_get_gpiod_by_index() when using properties
Date: Tue, 04 Nov 2014 15:42:38 -0800 [thread overview]
Message-ID: <5459646E.9000707@linux.intel.com> (raw)
In-Reply-To: <3196606.Sy6xFg88zg@vostro.rjw.lan>
On 11/4/14 14:54, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Subject: ACPI / property: Drop size_prop from acpi_dev_get_property_reference()
>
> The size_prop argument of the recently added function
> acpi_dev_get_property_reference() is not used by the only current
> caller of that function and is very unlikely to be used at any time
> going forward.
>
> Namely, for a property whose value is a list of items each containing
> a references to a device object possibly accompanied by some integers,
> the number of items in the list can always be computed as the number
> of elements of type ACPI_TYPE_LOCAL_REFERENCE in the property package.
> Thus it should never be necessary to provide an additional "cells"
> property with a value equal to the number of items in that list.
In this case, do we never expect a property to contain more than one
ACPI_TYPE_LOCAL_REFERENCE?
Package () { "foobar",
Package () {
"PCI0.FOO", "PCI0.BAR", 0, 1, 0,
"PCI0.FOO", "PCI0.BAR2", 0, 1, 1
}
}
This seems like it could be useful for connecting various types of
devices together, but I confess not to have a specific exmaple in mind.
It does concern me to limit the data format in this way.
I suppose should such a case become necessary, we can deal with the
issue then - and still avoid having a potential abuse point in the API
from the start.
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2014-11-04 23:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 11:15 [PATCH] ACPI / GPIO: Pass index to acpi_get_gpiod_by_index() when using properties Mika Westerberg
2014-10-28 15:57 ` Darren Hart
2014-10-28 21:59 ` Rafael J. Wysocki
2014-10-29 7:41 ` Alexandre Courbot
2014-10-29 7:41 ` Alexandre Courbot
2014-10-29 8:54 ` Mika Westerberg
2014-10-29 14:42 ` Rafael J. Wysocki
2014-10-29 14:51 ` Rafael J. Wysocki
2014-10-29 14:44 ` Mika Westerberg
2014-11-01 11:11 ` Grant Likely
2014-11-03 4:49 ` Darren Hart
2014-11-03 15:25 ` Rafael J. Wysocki
2014-11-03 21:52 ` Rafael J. Wysocki
2014-11-04 14:48 ` Grant Likely
2014-11-04 16:06 ` Rafael J. Wysocki
2014-11-04 22:54 ` Rafael J. Wysocki
2014-11-04 22:58 ` Grant Likely
2014-11-04 23:42 ` Darren Hart [this message]
2014-11-05 20:59 ` Rafael J. Wysocki
2014-11-05 20:53 ` Darren Hart
2014-11-05 9:16 ` Mika Westerberg
2014-11-05 21:00 ` Rafael J. Wysocki
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=5459646E.9000707@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=acourbot@nvidia.com \
--cc=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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.