Linux ACPI
 help / color / mirror / Atom feed
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 13:35:53 +0000	[thread overview]
Message-ID: <Z-qaOXTRS7z_He62@kekkonen.localdomain> (raw)
In-Reply-To: <CAJZ5v0jGCaJLTka57nB6mx4VDxZJUBVBbGV=7HdKKpf+7jCvjw@mail.gmail.com>

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.

> 
> >  drivers/acpi/property.c | 23 ++++++++++++++++++++---
> >  1 file changed, 20 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/acpi/property.c b/drivers/acpi/property.c
> > index 436019d96027..4e3202a0b305 100644
> > --- a/drivers/acpi/property.c
> > +++ b/drivers/acpi/property.c
> > @@ -807,10 +807,27 @@ acpi_fwnode_get_named_child_node(const struct fwnode_handle *fwnode,
> >  static int acpi_get_ref_args(struct fwnode_reference_args *args,
> >                              struct fwnode_handle *ref_fwnode,
> >                              const union acpi_object **element,
> > -                            const union acpi_object *end, size_t num_args)
> > +                            const union acpi_object *end, size_t num_args,
> > +                            bool follow_strings)
> >  {
> >         u32 nargs = 0, i;
> >
> > +       /*
> > +        * Parse REF STR... references by following named child nodes below the
> > +        * device node pointed by REF.
> > +        */
> > +       if (follow_strings) {
> > +               for (; (*element) < end && (*element)->type == ACPI_TYPE_STRING;
> > +                    (*element)++) {
> > +                       const char *child_name = (*element)->string.pointer;
> > +
> > +                       ref_fwnode = acpi_fwnode_get_named_child_node(ref_fwnode,
> > +                                                                     child_name);
> > +                       if (!ref_fwnode)
> > +                               return -EINVAL;
> > +               }
> > +       }
> > +
> >         /*
> >          * Assume the following integer elements are all args. Stop counting on
> >          * the first reference (possibly represented as a string) or end of the
> > @@ -999,7 +1016,7 @@ int __acpi_node_get_property_reference(const struct fwnode_handle *fwnode,
> >
> >                         ret = acpi_get_ref_args(idx == index ? args : NULL,
> >                                                 acpi_fwnode_handle(device),
> > -                                               &element, end, num_args);
> > +                                               &element, end, num_args, true);
> >                         if (ret < 0)
> >                                 return ret;
> >
> > @@ -1017,7 +1034,7 @@ int __acpi_node_get_property_reference(const struct fwnode_handle *fwnode,
> >
> >                         ret = acpi_get_ref_args(idx == index ? args : NULL,
> >                                                 ref_fwnode, &element, end,
> > -                                               num_args);
> > +                                               num_args, false);
> >                         if (ret < 0)
> >                                 return ret;
> >

-- 
Regards,

Sakari Ailus

  reply	other threads:[~2025-03-31 13:35 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 [this message]
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
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-qaOXTRS7z_He62@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