linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/4] ACPI / property: Allow holes in reference properties
Date: Tue, 11 Oct 2016 22:46:26 +0200	[thread overview]
Message-ID: <CAJZ5v0jGCrwB+mC6r-DVo-BYmLX-5WeKMEUnZ8NNmLsYCB2mfg@mail.gmail.com> (raw)
In-Reply-To: <20160929133944.158596-2-mika.westerberg@linux.intel.com>

On Thu, Sep 29, 2016 at 3:39 PM, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
> DT allows holes or empty phandles for references. This is used for example
> in SPI subsystem where some chip selects are native and others are regular
> GPIOs. In ACPI _DSD we currently do not support this but instead the
> preceding reference consumes all following integer arguments.
>
> For example we would like to support something like the below ASL fragment
> for SPI:
>
>   Package () {
>       "cs-gpios",
>       Package () {
>           ^GPIO, 19, 0, 0, // GPIO CS0
>           0,               // Native CS
>           ^GPIO, 20, 0, 0, // GPIO CS1
>       }
>   }
>
> The zero in the middle means "no entry" or NULL reference. To support this
> we change acpi_data_get_property_reference() to take firmware node and
> num_args as argument and rename it to __acpi_node_get_property_reference().
> The function returns -ENOENT if the given index resolves to "no entry"
> reference and -ENODATA when there are no more entries in the property.
>
> We then add static inline wrapper acpi_node_get_property_reference() that
> passes MAX_ACPI_REFERENCE_ARGS as num_args to support the existing
> behaviour which some drivers have been relying on.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>

The patch looks good to me and I don't see any reason to defer it, so
I'm queuing it up for the next ACPI pull request.

Thanks,
Rafael

  reply	other threads:[~2016-10-11 20:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 13:39 [PATCH v2 0/4] ACPI / gpio: Updates to properties Mika Westerberg
2016-09-29 13:39 ` [PATCH v2 1/4] ACPI / property: Allow holes in reference properties Mika Westerberg
2016-10-11 20:46   ` Rafael J. Wysocki [this message]
2016-10-20 12:00   ` Linus Walleij
2016-09-29 13:39 ` [PATCH v2 2/4] ACPI / gpio: Add support for naming GPIOs Mika Westerberg
2016-10-07 17:05   ` Andy Shevchenko
2016-10-09 15:01     ` Mika Westerberg
2016-10-09 17:08       ` Andy Shevchenko
2016-10-20 12:02   ` Linus Walleij
2016-10-20 12:08     ` Mika Westerberg
2016-10-20 12:06   ` Linus Walleij
2016-10-20 12:14     ` Mika Westerberg
2016-09-29 13:39 ` [PATCH v2 3/4] ACPI / gpio: Add hogging support Mika Westerberg
2016-10-20 12:09   ` Linus Walleij
2016-10-20 12:29     ` Mika Westerberg
2016-09-29 13:39 ` [PATCH v2 4/4] ACPI / gpio: Allow holes in list of GPIOs for a device Mika Westerberg
2016-10-20 12:10   ` Linus Walleij
2016-10-07 17:10 ` [PATCH v2 0/4] ACPI / gpio: Updates to properties Andy Shevchenko

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=CAJZ5v0jGCrwB+mC6r-DVo-BYmLX-5WeKMEUnZ8NNmLsYCB2mfg@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=gnurou@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).