From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-acpi@vger.kernel.org, "Wysocki,
Rafael J" <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH 1/1] ACPI: property: Fix REF STR... reference parsing
Date: Mon, 31 Mar 2025 16:10:32 +0000 [thread overview]
Message-ID: <Z-q-ePJeM4XzeffL@kekkonen.localdomain> (raw)
In-Reply-To: <CAJZ5v0i=h1AQm5LVDj4m6X+oEh=3AQ=jMAMr+p6=K13AP73C9w@mail.gmail.com>
Hi Rafael,
On Mon, Mar 31, 2025 at 05:35:50PM +0200, Rafael J. Wysocki wrote:
> Hi Sakari,
>
> On Mon, Mar 31, 2025 at 5:10 PM Sakari Ailus
> <sakari.ailus@linux.intel.com> wrote:
> >
> > Hi Rafael,
> >
> > On Mon, Mar 31, 2025 at 05:00:52PM +0200, Rafael J. Wysocki wrote:
> > > Hi Sakari,
> > >
> > > On Mon, Mar 31, 2025 at 3:35 PM Sakari Ailus
> > > <sakari.ailus@linux.intel.com> wrote:
> > > >
> > > > Hi Rafael,
> > > >
> > > > On Mon, Mar 31, 2025 at 03:19:07PM +0200, Rafael J. Wysocki wrote:
> > > > > On Mon, Mar 31, 2025 at 2:18 PM Sakari Ailus
> > > > > <sakari.ailus@linux.intel.com> wrote:
> > > > > >
> > > > > > Restore parsing of ACPI data node references consisting of a device node
> > > > > > reference followed by one or more child data node names.
> > > > > >
> > > > > > Fixes: 9880702d123f ("ACPI: property: Support using strings in reference properties")
> > > > > > Cc: stable@vger.kernel.org # for 6.8 and later
> > > > > > Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > > > > > ---
> > > > > > Hi Rafael,
> > > > > >
> > > > > > It seems that support for REF STR... references got accidentally removed
> > > > > > when pure STR reference were added. The former are documented in
> > > > > > Documentation/firmware-guide/acpi/dsd/graph.rst .
> > > > >
> > > > > It would be good to provide an ASL example that is not parsed as
> > > > > expected before the change and will be parsed correctly after it.
> > > > >
> > > > > Admittedly, I can't quite recall the history leading to the above
> > > > > commit, but this paragraphs is present in its changelog:
> > > > >
> > > > > "Also remove the mechanism allowing data nodes to be referenced
> > > > > indirectly, with the help of an object reference pointing to the
> > > > > "ancestor" device and a path relative to it (this mechanism is not
> > > > > expected to be in use in any production platform firmware in the field)."
> > > > >
> > > > > so the change in question appears to be intentional rather than accidental.
> > > >
> > > > Right. This still continues to be documented in
> > > > Documentation/firmware-guide/acpi/dsd/graph.rst as noted in my previous
> > > > e-mail. A sample ASL snippet is can also be found in the same file. I only
> > > > noticed this when I tried to use such references.
> > > >
> > > > The other option indeed is to change the documentation and hope no-one
> > > > depends on it.
> > >
> > > I thought that this was the original plan.
> >
> > I wasn't aware of the plan. But given that no-one has complained yet,
> > there's a fair chance no-one will. I can post patches to switch to
> > string-only references.
>
> I think that it should be sufficient to update the documentation so it
> does not describe the indirect mechanism mentioned in the changelog of
> commit 9880702d123f, shouldn't it?
I'd think so.
The REF+STR data node references actually go back to
Documentation/firmware-guide/acpi/dsd/data-node-references.rst merged in
2018 and their documented use includes LEDs (besides graphs) as well. Just
FYI though.
--
Sakari Ailus
next prev parent reply other threads:[~2025-03-31 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 12:18 [PATCH 1/1] ACPI: property: Fix REF STR... reference parsing Sakari Ailus
2025-03-31 13:19 ` Rafael J. Wysocki
2025-03-31 13:35 ` Sakari Ailus
2025-03-31 15:00 ` Rafael J. Wysocki
2025-03-31 15:09 ` Sakari Ailus
2025-03-31 15:35 ` Rafael J. Wysocki
2025-03-31 16:10 ` Sakari Ailus [this message]
2025-06-16 5:41 ` Sakari Ailus
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=Z-q-ePJeM4XzeffL@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
/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