From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-i2c <linux-i2c@vger.kernel.org>,
Wolfram Sang <wsa@the-dreams.de>,
"Rafael J. Wysocki" <rafael@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Mani, Rajmohan" <rajmohan.mani@intel.com>,
Tomasz Figa <tfiga@chromium.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Bingbu Cao <bingbu.cao@intel.com>,
Chiranjeevi Rapolu <chiranjeevi.rapolu@intel.com>,
Hyungwoo Yang <hyungwoo.yang@intel.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v7 6/6] Documentation: ACPI: Document allow-low-power-probe _DSD property
Date: Wed, 2 Sep 2020 17:57:01 +0200 [thread overview]
Message-ID: <CAJZ5v0jFceTFRTD55cz3ZHRZpuNRK_z9=_DxWexc8ArsGU3cog@mail.gmail.com> (raw)
In-Reply-To: <20200901210333.8462-7-sakari.ailus@linux.intel.com>
On Tue, Sep 1, 2020 at 11:03 PM Sakari Ailus
<sakari.ailus@linux.intel.com> wrote:
>
> Document the probe-low-power _DSD property and how it is used with I²C
> drivers.
I would reorder the series to make this go right after the [1/6] or
maybe even fold it into that patch.
The point is that the changes in [1/6] clearly depend on the property
defined here.
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
> .../acpi/dsd/allow-low-power-probe.rst | 28 +++++++++++++++++++
> Documentation/firmware-guide/acpi/index.rst | 1 +
> 2 files changed, 29 insertions(+)
> create mode 100644 Documentation/firmware-guide/acpi/dsd/allow-low-power-probe.rst
>
> diff --git a/Documentation/firmware-guide/acpi/dsd/allow-low-power-probe.rst b/Documentation/firmware-guide/acpi/dsd/allow-low-power-probe.rst
> new file mode 100644
> index 0000000000000..6fcc89162b898
> --- /dev/null
> +++ b/Documentation/firmware-guide/acpi/dsd/allow-low-power-probe.rst
> @@ -0,0 +1,28 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +======================================
> +Probing I²C devices in low power state
> +======================================
> +
> +Introduction
> +============
> +
> +In some cases it may be preferred to leave certain devices powered off for the
> +entire system bootup if powering on these devices has adverse side effects,
> +beyond just powering on the said device. Linux recognizes the _DSD property
> +"allow-low-power-probe" that can be used for this purpose.
It would be good to refer to the document defining the generic _DSD
properties mechanism and the GUID used for that from here.
The meaning of "_DSD property" may not be entirely clear to the
reader as it stands.
And maybe call the property "i2c-allow-low-power-probe" or similar, to
indicate that it is specific to i2c.
> +
> +How it works
> +============
> +
> +The property "allow-low-power-probe" boolean property may be used to tell Linux
"boolean device property" ?
> +that the I²C framework should instruct the kernel ACPI framework to leave the
> +device in the low power state. If the driver indicates its support for this by
> +setting the I2C_DRV_FL_ALLOW_LOW_POWER_PROBE flag in struct i2c_driver.flags
> +field and the "allow-low-power-probe" property is present, the device will not
> +be powered on for probe.
> +
> +The downside is that as the device is not powered on, even if there's a problem
> +with the device, the driver likely probes just fine but the first user will
> +find out the device doesn't work, instead of a failure at probe time. This
> +feature should thus be used sparingly.
It would be good to give an ASL example with this property provided.
> diff --git a/Documentation/firmware-guide/acpi/index.rst b/Documentation/firmware-guide/acpi/index.rst
> index ad3b5afdae77e..0070fcde9e669 100644
> --- a/Documentation/firmware-guide/acpi/index.rst
> +++ b/Documentation/firmware-guide/acpi/index.rst
> @@ -11,6 +11,7 @@ ACPI Support
> dsd/graph
> dsd/data-node-references
> dsd/leds
> + dsd/allow-low-power-probe
> enumeration
> osi
> method-customizing
> --
next prev parent reply other threads:[~2020-09-02 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 21:03 [PATCH v7 0/6] Support running driver's probe for a device powered off Sakari Ailus
2020-09-01 21:03 ` [PATCH v7 1/6] i2c: Allow an ACPI driver to manage the device's power state during probe Sakari Ailus
2020-09-01 21:03 ` [PATCH v7 2/6] ACPI: Add a convenience function to tell a device is in low power state Sakari Ailus
2020-09-01 21:03 ` [PATCH v7 3/6] ov5670: Support probe whilst the device is in a " Sakari Ailus
2020-09-01 21:03 ` [PATCH v7 4/6] media: i2c: imx319: Support probe while the device is off Sakari Ailus
2020-09-01 21:03 ` [PATCH v7 5/6] at24: Support probing while off Sakari Ailus
2020-09-01 21:03 ` [PATCH v7 6/6] Documentation: ACPI: Document allow-low-power-probe _DSD property Sakari Ailus
2020-09-02 15:57 ` Rafael J. Wysocki [this message]
2020-09-02 16:31 ` Sakari Ailus
2020-09-02 16:34 ` Rafael J. Wysocki
2020-09-02 19:59 ` 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='CAJZ5v0jFceTFRTD55cz3ZHRZpuNRK_z9=_DxWexc8ArsGU3cog@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=bingbu.cao@intel.com \
--cc=chiranjeevi.rapolu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hyungwoo.yang@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rajmohan.mani@intel.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@chromium.org \
--cc=wsa@the-dreams.de \
/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).