From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH] ACPI: glue: Use acpi_device_adr() in acpi_find_child_device()
Date: Wed, 27 Oct 2021 20:17:02 +0300 [thread overview]
Message-ID: <YXmJjlY6+oFy4siX@smile.fi.intel.com> (raw)
In-Reply-To: <11862679.O9o76ZdvQC@kreacher>
On Wed, Oct 27, 2021 at 06:59:06PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Instead of evaluating _ADR in acpi_find_child_device(), use the
> observation that it has already been evaluated and the value returned
> by it has been stored in the pnp.type.bus_address field of the ACPI
> device object at hand.
...
> + acpi_bus_address addr = acpi_device_adr(adev);
> int score;
>
> - status = acpi_evaluate_integer(adev->handle, METHOD_NAME__ADR,
> - NULL, &addr);
> - if (ACPI_FAILURE(status) || addr != address)
> + if (!adev->pnp.type.bus_address || addr != address)
> continue;
I'm not sure I understand the new check, i.e. !adev->pnp.type.bus_address.
IIUC _ADR == 0 is a valid value and children may have it like this.
I believe this change will break the working things (first comes to my mind
is drivers/mfd/intel_quark_i2c_gpio.c).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-10-27 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 16:59 Rafael J. Wysocki
2021-10-27 17:17 ` Andy Shevchenko [this message]
2021-10-27 17:23 ` Rafael J. Wysocki
2021-10-27 17:35 ` 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=YXmJjlY6+oFy4siX@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--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
all inboxes | Powered by JetHome®