From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Prashant Malani <pmalani@chromium.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
"open list:ULTRA-WIDEBAND (UWB) SUBSYSTEM:"
<linux-usb@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] acpi: Store the known device locations
Date: Mon, 20 Dec 2021 16:20:33 +0200 [thread overview]
Message-ID: <YcCRMUgpSSEhGeug@kuha.fi.intel.com> (raw)
In-Reply-To: <CAJZ5v0g9HjLr8n3OQwMY0EK5GdCc+8CJnO3mEUXom3g2sz9jXQ@mail.gmail.com>
On Fri, Dec 17, 2021 at 06:01:48PM +0100, Rafael J. Wysocki wrote:
> And overall I'm wondering if this can be achieved by storing the
> pld_crc directly in struct acpi_device and doing a
> bus_for_each_dev(&acpi_bus_type, ...) walk every time a list of
> devices sharing a _PLD is needed?
>
> It looks like typec_link_ports() is the only user of this and it can
> easily afford doing a walk like the above if I'm not mistaken.
OK. I'll try that out.
thanks,
--
heikki
next prev parent reply other threads:[~2021-12-20 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 13:24 [PATCH v3 0/4] acpi: Store _PLD information and convert users Heikki Krogerus
2021-12-17 13:24 ` [PATCH v3 1/4] acpi: Store the known device locations Heikki Krogerus
2021-12-17 17:01 ` Rafael J. Wysocki
2021-12-20 14:20 ` Heikki Krogerus [this message]
2021-12-17 13:24 ` [PATCH v3 2/4] usb: Link the ports to the connectors they are attached to Heikki Krogerus
2021-12-17 13:24 ` [PATCH v3 3/4] usb: typec: port-mapper: Convert to the component framework Heikki Krogerus
2021-12-17 13:24 ` [PATCH v3 4/4] usb: Remove usb_for_each_port() Heikki Krogerus
2021-12-17 14:11 ` [PATCH v3 0/4] acpi: Store _PLD information and convert users 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=YcCRMUgpSSEhGeug@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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