linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v11 0/6] Support running driver's probe for a device powered off
@ 2021-10-18 12:17 Sakari Ailus
  2021-10-18 12:17 ` [PATCH 1/6] ACPI: scan: Obtain device's desired enumeration power state Sakari Ailus
                   ` (6 more replies)
  0 siblings, 7 replies; 10+ messages in thread
From: Sakari Ailus @ 2021-10-18 12:17 UTC (permalink / raw)
  To: linux-i2c
  Cc: Wolfram Sang, Rafael J. Wysocki, linux-acpi, linux-kernel,
	Greg Kroah-Hartman, rajmohan.mani, Tomasz Figa,
	Bartosz Golaszewski, Bingbu Cao, Chiranjeevi Rapolu,
	Hyungwoo Yang, linux-media

Hello everyone,

These patches enable calling (and finishing) a driver's probe function
without powering on the respective device on busses where the practice is
to power on the device for probe. While it generally is a driver's job to
check the that the device is there, there are cases where it might be
undesirable. (In this case it stems from a combination of hardware design
and user expectations; see below.) The downside with this change is that
if there is something wrong with the device, it will only be found at the
time the device is used. In this case (the camera sensors + EEPROM in a
sensor) I don't see any tangible harm from that though.

An indication both from the driver and the firmware is required to allow
the device's power state to remain off during probe (see the second patch).


The use case is such that there is a privacy LED next to an integrated
user-facing laptop camera, and this LED is there to signal the user that
the camera is recording a video or capturing images. That LED also happens
to be wired to one of the power supplies of the camera, so whenever you
power on the camera, the LED will be lit, whether images are captured from
the camera --- or not. There's no way to implement this differently
without additional software control (allowing of which is itself a
hardware design decision) on most CSI-2-connected camera sensors as they
simply have no pin to signal the camera streaming state.

This is also what happens during driver probe: the camera will be powered
on by the I²C subsystem calling dev_pm_domain_attach() and the device is
already powered on when the driver's own probe function is called. To the
user this visible during the boot process as a blink of the privacy LED,
suggesting that the camera is recording without the user having used an
application to do that. From the end user's point of view the behaviour is
not expected and for someone unfamiliar with internal workings of a
computer surely seems quite suspicious --- even if images are not being
actually captured.

I've tested these on linux-next master.

since v11 <URL:https://lore.kernel.org/lkml/20210210230800.30291-1-sakari.ailus@linux.intel.com/>:

- Rebase on linux-next.

- Call device object that designates the intended power state for probe
  "_DSC" instead of "_DSE".

- Remove the ov5670 driver patch from the set due to conflict (will merge
  through media tree later on).

since v10 <URL:https://lore.kernel.org/linux-acpi/20210205132505.20173-1-sakari.ailus@linux.intel.com/>:

- Instead of "low power state" refer to ACPI D states and "full power", of
  which latter is used in individual drivers.

- Fix remaining references to _DSD properties.

- Rework commit messages to reflect recent changes.

- Rework the documentation to separate _DSE from I²C as it's not really
  specific to that.

- Rename the I2C_DRV_FL_ALLOW_LOW_POWER_PROBE flag as
  I2C_DRV_ACPI_WAIVE_D0_PROBE.

since v9 <URL:https://lore.kernel.org/linux-acpi/CAJZ5v0jjgy2KXOw5pyshvaEVzLctu4jsgYK1+YDA+8sZfp-6mw@mail.gmail.com/T/#m003f56b33350772364b1f5c832e9025677107933>:

- Use _DSE object designed for the very purpose of designating intended
  device probe power state instead of _PRE.

- Rework documentation to reflect the property to _DSE changes (missed in
  v9).

- Put maximum device enumeration power state in struct acpi_device_power,
  instead of a flag in struct acpi_device_power_flags. The default is
  ACPI_STATE_D0.

- i2c_acpi_allow_low_power_probe() now returns true if the desired power
  state is greater or equal to the current device power state.

- Rename local variable low_power as off_during_probe.

since v8 <URL:https://lore.kernel.org/patchwork/cover/1300068/>:

- Make use of ACPI _PRE object instead of a _DSD property (new patch,
  1st), align documentation with that.

- Added a blank line.

- Rebased on current linux-next master.

since v7 <URL:https://lore.kernel.org/linux-acpi/20200901210333.8462-1-sakari.ailus@linux.intel.com/>:

- Reorder documentation patch right after the implemenation in the I²C
  framework.

- Rename allow-low-power-probe property as i2c-allow-low-power-probe.

- Remove extra "property" from the description of the
  i2c-allow-low-power-probe property and mention it's a device property.

- Add an example to the documentation and refer to the _DSD property spec.

since v6 <URL:https://lore.kernel.org/linux-acpi/20200826115432.6103-1-sakari.ailus@linux.intel.com/>:

- Use u32 for the flags field in struct i2c_driver.

- Use acpi_dev_get_property to read the allow-low-power-probe property.

since v5 <URL:https://lore.kernel.org/linux-acpi/20200810142747.12400-1-sakari.ailus@linux.intel.com/>:

- Identify sensors when they're first powered on. In previous versions, if
  this wasn't in probe, it was not done at all.

- Return allow_low_power_probe() only for ACPI devices, i.e. OF systems
  are not affected by these changes.

- Document that I2C_DRV_FL_ALLOW_LOW_POWER_PROBE flag only applies to ACPI
  drivers.

- Fix extra regulator_disable in at24 driver's remove function when the
  device was already in low power state.

since v4 <URL:https://lore.kernel.org/linux-acpi/20200121134157.20396-1-sakari.ailus@linux.intel.com/>:

- Rename "probe-low-power" property as "allow-low-power-probe". This is
  taken into account in function and file naming, too.

- Turn probe_low_power field in struct i2c_driver into flags field.

- Rebase on Wolfram's i2c/for-next branch that contains the removal of the
  support for disabling I²C core IRQ mappings (commit
  0c2a34937f7e4c4776bb261114c475392da2355c).

- Change wording for "allow-low-power-probe" property in ACPI
  documentation.

since v3 <URL:https://lore.kernel.org/linux-acpi/20200109154529.19484-1-sakari.ailus@linux.intel.com/T/#t>:

- Rework the 2nd patch based on Rafael's comments

	- Rework description of the ACPI low power state helper function,
	  according to Rafael's text.

	- Rename and rework the same function as
	  acpi_dev_state_low_power().

	- Reflect the changes in commit message as well.

- Added a patch to document the probe-low-power _DSD property.

since v2 <URL:https://patchwork.kernel.org/cover/11114255/>:

- Remove extra CONFIG_PM ifdefs; these are not needed.

- Move the checks for power state hints from drivers/base/dd.c to
  drivers/i2c/i2c-base-core.c; these are I²C devices anyway.

- Move the probe_low_power field from struct device_driver to struct
  i2c_driver.

since v1:

- Rename probe_powered_off struct device field as probe_low_power and
  reflect the similar naming to the patches overall.

- Work with CONFIG_PM disabled, too.

Rajmohan Mani (1):
  media: i2c: imx319: Support device probe in non-zero ACPI D state

Sakari Ailus (5):
  ACPI: scan: Obtain device's desired enumeration power state
  i2c: Allow an ACPI driver to manage the device's power state during
    probe
  Documentation: ACPI: Document _DSC object usage for enum power state
  ACPI: Add a convenience function to tell a device is in D0 state
  at24: Support probing while in non-zero ACPI D state

 Documentation/firmware-guide/acpi/index.rst   |  1 +
 .../firmware-guide/acpi/non-d0-probe.rst      | 78 +++++++++++++++++++
 drivers/acpi/device_pm.c                      | 26 +++++++
 drivers/acpi/scan.c                           |  4 +
 drivers/i2c/i2c-core-acpi.c                   | 10 +++
 drivers/i2c/i2c-core-base.c                   |  7 +-
 drivers/media/i2c/imx319.c                    | 74 +++++++++++-------
 drivers/misc/eeprom/at24.c                    | 45 ++++++-----
 include/acpi/acpi_bus.h                       |  1 +
 include/linux/acpi.h                          |  5 ++
 include/linux/i2c.h                           | 18 +++++
 11 files changed, 218 insertions(+), 51 deletions(-)
 create mode 100644 Documentation/firmware-guide/acpi/non-d0-probe.rst

-- 
2.30.2


^ permalink raw reply	[flat|nested] 10+ messages in thread

* [PATCH 1/6] ACPI: scan: Obtain device's desired enumeration power state
  2021-10-18 12:17 [PATCH v11 0/6] Support running driver's probe for a device powered off Sakari Ailus
@ 2021-10-18 12:17 ` Sakari Ailus
  2021-10-18 12:17 ` [PATCH 2/6] i2c: Allow an ACPI driver to manage the device's power state during probe Sakari Ailus
                   ` (5 subsequent siblings)
  6 siblings, 0 replies; 10+ messages in thread
From: Sakari Ailus @ 2021-10-18 12:17 UTC (permalink / raw)
  To: linux-i2c
  Cc: Wolfram Sang, Rafael J. Wysocki, linux-acpi, linux-kernel,
	Greg Kroah-Hartman, rajmohan.mani, Tomasz Figa,
	Bartosz Golaszewski, Bingbu Cao, Chiranjeevi Rapolu,
	Hyungwoo Yang, linux-media

Store a device's desired enumeration power state in struct
acpi_device_power during acpi_device object's initialisation.

Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
 drivers/acpi/scan.c     | 4 ++++
 include/acpi/acpi_bus.h | 1 +
 2 files changed, 5 insertions(+)

diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
index dce2c291b982b..a50f1967c73dc 100644
--- a/drivers/acpi/scan.c
+++ b/drivers/acpi/scan.c
@@ -1017,6 +1017,7 @@ static void acpi_bus_init_power_state(struct acpi_device *device, int state)
 
 static void acpi_bus_get_power_flags(struct acpi_device *device)
 {
+	unsigned long long dsc = ACPI_STATE_D0;
 	u32 i;
 
 	/* Presence of _PS0|_PR0 indicates 'power manageable' */
@@ -1038,6 +1039,9 @@ static void acpi_bus_get_power_flags(struct acpi_device *device)
 	if (acpi_has_method(device->handle, "_DSW"))
 		device->power.flags.dsw_present = 1;
 
+	acpi_evaluate_integer(device->handle, "_DSC", NULL, &dsc);
+	device->power.state_for_enumeration = dsc;
+
 	/*
 	 * Enumerate supported power management states
 	 */
diff --git a/include/acpi/acpi_bus.h b/include/acpi/acpi_bus.h
index 53b6e9f9de7b4..6b4eb5742869a 100644
--- a/include/acpi/acpi_bus.h
+++ b/include/acpi/acpi_bus.h
@@ -278,6 +278,7 @@ struct acpi_device_power {
 	int state;		/* Current state */
 	struct acpi_device_power_flags flags;
 	struct acpi_device_power_state states[ACPI_D_STATE_COUNT];	/* Power states (D0-D3Cold) */
+	u8 state_for_enumeration; /* Maximum power state for enumeration */
 };
 
 struct acpi_dep_data {
-- 
2.30.2


^ permalink raw reply related	[flat|nested] 10+ messages in thread

* [PATCH 2/6] i2c: Allow an ACPI driver to manage the device's power state during probe
  2021-10-18 12:17 [PATCH v11 0/6] Support running driver's probe for a device powered off Sakari Ailus
  2021-10-18 12:17 ` [PATCH 1/6] ACPI: scan: Obtain device's desired enumeration power state Sakari Ailus
@ 2021-10-18 12:17 ` Sakari Ailus
  2021-10-18 12:17 ` [PATCH 3/6] Documentation: ACPI: Document _DSC object usage for enum power state Sakari Ailus
                   ` (4 subsequent siblings)
  6 siblings, 0 replies; 10+ messages in thread
From: Sakari Ailus @ 2021-10-18 12:17 UTC (permalink / raw)
  To: linux-i2c
  Cc: Wolfram Sang, Rafael J. Wysocki, linux-acpi, linux-kernel,
	Greg Kroah-Hartman, rajmohan.mani, Tomasz Figa,
	Bartosz Golaszewski, Bingbu Cao, Chiranjeevi Rapolu,
	Hyungwoo Yang, linux-media

Enable drivers to tell ACPI that there's no need to power on a device for
probe. Drivers should still perform this by themselves if there's a need
to. In some cases powering on the device during probe is undesirable, and
this change enables a driver to choose what fits best for it.

Add a field called "flags" into struct i2c_driver for driver flags, and a
flag I2C_DRV_ACPI_WAIVE_D0_PROBE to tell a driver supports probe in ACPI D
states other than 0.

Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Acked-by: Wolfram Sang <wsa@kernel.org>
---
 drivers/i2c/i2c-core-acpi.c | 10 ++++++++++
 drivers/i2c/i2c-core-base.c |  7 ++++---
 include/linux/i2c.h         | 18 ++++++++++++++++++
 3 files changed, 32 insertions(+), 3 deletions(-)

diff --git a/drivers/i2c/i2c-core-acpi.c b/drivers/i2c/i2c-core-acpi.c
index 546cc935e035a..c025919cdaaee 100644
--- a/drivers/i2c/i2c-core-acpi.c
+++ b/drivers/i2c/i2c-core-acpi.c
@@ -526,6 +526,16 @@ struct i2c_client *i2c_acpi_new_device(struct device *dev, int index,
 }
 EXPORT_SYMBOL_GPL(i2c_acpi_new_device);
 
+bool i2c_acpi_waive_d0_probe(struct device *dev)
+{
+	struct i2c_driver *driver = to_i2c_driver(dev->driver);
+	struct acpi_device *adev = ACPI_COMPANION(dev);
+
+	return driver->flags & I2C_DRV_ACPI_WAIVE_D0_PROBE &&
+		adev && adev->power.state_for_enumeration >= adev->power.state;
+}
+EXPORT_SYMBOL_GPL(i2c_acpi_waive_d0_probe);
+
 #ifdef CONFIG_ACPI_I2C_OPREGION
 static int acpi_gsb_i2c_read_bytes(struct i2c_client *client,
 		u8 cmd, u8 *data, u8 data_len)
diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c
index 54964fbe3f033..f193f90585841 100644
--- a/drivers/i2c/i2c-core-base.c
+++ b/drivers/i2c/i2c-core-base.c
@@ -551,7 +551,8 @@ static int i2c_device_probe(struct device *dev)
 	if (status < 0)
 		goto err_clear_wakeup_irq;
 
-	status = dev_pm_domain_attach(&client->dev, true);
+	status = dev_pm_domain_attach(&client->dev,
+				      !i2c_acpi_waive_d0_probe(dev));
 	if (status)
 		goto err_clear_wakeup_irq;
 
@@ -590,7 +591,7 @@ static int i2c_device_probe(struct device *dev)
 err_release_driver_resources:
 	devres_release_group(&client->dev, client->devres_group_id);
 err_detach_pm_domain:
-	dev_pm_domain_detach(&client->dev, true);
+	dev_pm_domain_detach(&client->dev, !i2c_acpi_waive_d0_probe(dev));
 err_clear_wakeup_irq:
 	dev_pm_clear_wake_irq(&client->dev);
 	device_init_wakeup(&client->dev, false);
@@ -621,7 +622,7 @@ static void i2c_device_remove(struct device *dev)
 
 	devres_release_group(&client->dev, client->devres_group_id);
 
-	dev_pm_domain_detach(&client->dev, true);
+	dev_pm_domain_detach(&client->dev, !i2c_acpi_waive_d0_probe(dev));
 	if (!pm_runtime_status_suspended(&client->dev) && adap->bus_regulator)
 		regulator_disable(adap->bus_regulator);
 
diff --git a/include/linux/i2c.h b/include/linux/i2c.h
index 2ce3efbe9198a..16119ac1aa97e 100644
--- a/include/linux/i2c.h
+++ b/include/linux/i2c.h
@@ -11,6 +11,7 @@
 #define _LINUX_I2C_H
 
 #include <linux/acpi.h>		/* for acpi_handle */
+#include <linux/bits.h>
 #include <linux/mod_devicetable.h>
 #include <linux/device.h>	/* for struct device */
 #include <linux/sched.h>	/* for completion */
@@ -222,6 +223,15 @@ enum i2c_alert_protocol {
 	I2C_PROTOCOL_SMBUS_HOST_NOTIFY,
 };
 
+/**
+ * enum i2c_driver_flags - Flags for an I2C device driver
+ *
+ * @I2C_DRV_ACPI_WAIVE_D0_PROBE: Don't put the device in D0 state for probe
+ */
+enum i2c_driver_flags {
+	I2C_DRV_ACPI_WAIVE_D0_PROBE = BIT(0),
+};
+
 /**
  * struct i2c_driver - represent an I2C device driver
  * @class: What kind of i2c device we instantiate (for detect)
@@ -236,6 +246,7 @@ enum i2c_alert_protocol {
  * @detect: Callback for device detection
  * @address_list: The I2C addresses to probe (for detect)
  * @clients: List of detected clients we created (for i2c-core use only)
+ * @flags: A bitmask of flags defined in &enum i2c_driver_flags
  *
  * The driver.owner field should be set to the module owner of this driver.
  * The driver.name field should be set to the name of this driver.
@@ -294,6 +305,8 @@ struct i2c_driver {
 	int (*detect)(struct i2c_client *client, struct i2c_board_info *info);
 	const unsigned short *address_list;
 	struct list_head clients;
+
+	u32 flags;
 };
 #define to_i2c_driver(d) container_of(d, struct i2c_driver, driver)
 
@@ -1015,6 +1028,7 @@ u32 i2c_acpi_find_bus_speed(struct device *dev);
 struct i2c_client *i2c_acpi_new_device(struct device *dev, int index,
 				       struct i2c_board_info *info);
 struct i2c_adapter *i2c_acpi_find_adapter_by_handle(acpi_handle handle);
+bool i2c_acpi_waive_d0_probe(struct device *dev);
 #else
 static inline bool i2c_acpi_get_i2c_resource(struct acpi_resource *ares,
 					     struct acpi_resource_i2c_serialbus **i2c)
@@ -1038,6 +1052,10 @@ static inline struct i2c_adapter *i2c_acpi_find_adapter_by_handle(acpi_handle ha
 {
 	return NULL;
 }
+static inline bool i2c_acpi_waive_d0_probe(struct device *dev)
+{
+	return false;
+}
 #endif /* CONFIG_ACPI */
 
 #endif /* _LINUX_I2C_H */
-- 
2.30.2


^ permalink raw reply related	[flat|nested] 10+ messages in thread

* [PATCH 3/6] Documentation: ACPI: Document _DSC object usage for enum power state
  2021-10-18 12:17 [PATCH v11 0/6] Support running driver's probe for a device powered off Sakari Ailus
  2021-10-18 12:17 ` [PATCH 1/6] ACPI: scan: Obtain device's desired enumeration power state Sakari Ailus
  2021-10-18 12:17 ` [PATCH 2/6] i2c: Allow an ACPI driver to manage the device's power state during probe Sakari Ailus
@ 2021-10-18 12:17 ` Sakari Ailus
  2021-10-25 11:01   ` Bingbu Cao
  2021-10-18 12:17 ` [PATCH 4/6] ACPI: Add a convenience function to tell a device is in D0 state Sakari Ailus
                   ` (3 subsequent siblings)
  6 siblings, 1 reply; 10+ messages in thread
From: Sakari Ailus @ 2021-10-18 12:17 UTC (permalink / raw)
  To: linux-i2c
  Cc: Wolfram Sang, Rafael J. Wysocki, linux-acpi, linux-kernel,
	Greg Kroah-Hartman, rajmohan.mani, Tomasz Figa,
	Bartosz Golaszewski, Bingbu Cao, Chiranjeevi Rapolu,
	Hyungwoo Yang, linux-media

Document the use of the _DSC object for setting desirable power state
during probe.

Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
---
 Documentation/firmware-guide/acpi/index.rst   |  1 +
 .../firmware-guide/acpi/non-d0-probe.rst      | 78 +++++++++++++++++++
 2 files changed, 79 insertions(+)
 create mode 100644 Documentation/firmware-guide/acpi/non-d0-probe.rst

diff --git a/Documentation/firmware-guide/acpi/index.rst b/Documentation/firmware-guide/acpi/index.rst
index a99ee402b212b..b053b0c3d6969 100644
--- a/Documentation/firmware-guide/acpi/index.rst
+++ b/Documentation/firmware-guide/acpi/index.rst
@@ -26,5 +26,6 @@ ACPI Support
    acpi-lid
    lpit
    video_extension
+   non-d0-probe
    extcon-intel-int3496
    intel-pmc-mux
diff --git a/Documentation/firmware-guide/acpi/non-d0-probe.rst b/Documentation/firmware-guide/acpi/non-d0-probe.rst
new file mode 100644
index 0000000000000..78781e1ab6a3d
--- /dev/null
+++ b/Documentation/firmware-guide/acpi/non-d0-probe.rst
@@ -0,0 +1,78 @@
+.. SPDX-License-Identifier: GPL-2.0
+
+========================================
+Probing devices in other D states than 0
+========================================
+
+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.
+
+How it works
+============
+
+The _DSC (Device State for Configuration) object that evaluates to an integer
+may be used to tell Linux the highest allowed D state for a device during
+probe. The support for _DSC requires support from the kernel bus type if the
+bus driver normally sets the device in D0 state for probe.
+
+The downside of using _DSC 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.
+
+I²C
+---
+
+If an I²C driver indicates its support for this by setting the
+I2C_DRV_ACPI_WAIVE_D0_PROBE flag in struct i2c_driver.flags field and the
+_DSC object evaluates to integer higher than the D state of the device,
+the device will not be powered on (put in D0 state) for probe.
+
+D states
+--------
+
+The D states and thus also the allowed values for _DSC are listed below. Refer
+to [1] for more information on device power states.
+
+.. code-block:: text
+
+	Number	State	Description
+	0	D0	Device fully powered on
+	1	D1
+	2	D2
+	3	D3hot
+	4	D3cold	Off
+
+References
+==========
+
+[1] https://uefi.org/specifications/ACPI/6.4/02_Definition_of_Terms/Definition_of_Terms.html#device-power-state-definitions
+
+Example
+=======
+
+An ASL example describing an ACPI device using _DSC object to tell Operating
+System the device should remain powered off during probe looks like this. Some
+objects not relevant from the example point of view have been omitted.
+
+.. code-block:: text
+
+	Device (CAM0)
+        {
+		Name (_HID, "SONY319A")
+		Name (_UID, Zero)
+		Name (_CRS, ResourceTemplate ()
+		{
+			I2cSerialBus(0x0020, ControllerInitiated, 0x00061A80,
+				     AddressingMode7Bit, "\\_SB.PCI0.I2C0",
+				     0x00, ResourceConsumer)
+		})
+		Name (_DSC, 0, NotSerialized)
+		{
+			Return (0x4)
+                }
+	}
-- 
2.30.2


^ permalink raw reply related	[flat|nested] 10+ messages in thread

* [PATCH 4/6] ACPI: Add a convenience function to tell a device is in D0 state
  2021-10-18 12:17 [PATCH v11 0/6] Support running driver's probe for a device powered off Sakari Ailus
                   ` (2 preceding siblings ...)
  2021-10-18 12:17 ` [PATCH 3/6] Documentation: ACPI: Document _DSC object usage for enum power state Sakari Ailus
@ 2021-10-18 12:17 ` Sakari Ailus
  2021-10-18 12:17 ` [PATCH 5/6] media: i2c: imx319: Support device probe in non-zero ACPI D state Sakari Ailus
                   ` (2 subsequent siblings)
  6 siblings, 0 replies; 10+ messages in thread
From: Sakari Ailus @ 2021-10-18 12:17 UTC (permalink / raw)
  To: linux-i2c
  Cc: Wolfram Sang, Rafael J. Wysocki, linux-acpi, linux-kernel,
	Greg Kroah-Hartman, rajmohan.mani, Tomasz Figa,
	Bartosz Golaszewski, Bingbu Cao, Chiranjeevi Rapolu,
	Hyungwoo Yang, linux-media

Add a convenience function to tell whether a device is in D0 state,
primarily for use in drivers' probe or remove functions on busses where
the custom is to power on the device for the duration of both.

Returns false on non-ACPI systems.

Suggested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
---
 drivers/acpi/device_pm.c | 26 ++++++++++++++++++++++++++
 include/linux/acpi.h     |  5 +++++
 2 files changed, 31 insertions(+)

diff --git a/drivers/acpi/device_pm.c b/drivers/acpi/device_pm.c
index 0028b6b51c877..19b33c028f356 100644
--- a/drivers/acpi/device_pm.c
+++ b/drivers/acpi/device_pm.c
@@ -1400,4 +1400,30 @@ bool acpi_storage_d3(struct device *dev)
 }
 EXPORT_SYMBOL_GPL(acpi_storage_d3);
 
+/**
+ * acpi_dev_state_d0 - Tell if the device is in D0 power state
+ * @dev: Physical device the ACPI power state of which to check
+ *
+ * On a system without ACPI, return true. On a system with ACPI, return true if
+ * the current ACPI power state of the device is D0, or false otherwise.
+ *
+ * Note that the power state of a device is not well-defined after it has been
+ * passed to acpi_device_set_power() and before that function returns, so it is
+ * not valid to ask for the ACPI power state of the device in that time frame.
+ *
+ * This function is intended to be used in a driver's probe or remove
+ * function. See Documentation/firmware-guide/acpi/low-power-probe.rst for
+ * more information.
+ */
+bool acpi_dev_state_d0(struct device *dev)
+{
+	struct acpi_device *adev = ACPI_COMPANION(dev);
+
+	if (!adev)
+		return true;
+
+	return adev->power.state == ACPI_STATE_D0;
+}
+EXPORT_SYMBOL_GPL(acpi_dev_state_d0);
+
 #endif /* CONFIG_PM */
diff --git a/include/linux/acpi.h b/include/linux/acpi.h
index 375715b0535fb..143ce7e0bee13 100644
--- a/include/linux/acpi.h
+++ b/include/linux/acpi.h
@@ -1014,6 +1014,7 @@ int acpi_subsys_runtime_suspend(struct device *dev);
 int acpi_subsys_runtime_resume(struct device *dev);
 int acpi_dev_pm_attach(struct device *dev, bool power_on);
 bool acpi_storage_d3(struct device *dev);
+bool acpi_dev_state_d0(struct device *dev);
 #else
 static inline int acpi_subsys_runtime_suspend(struct device *dev) { return 0; }
 static inline int acpi_subsys_runtime_resume(struct device *dev) { return 0; }
@@ -1025,6 +1026,10 @@ static inline bool acpi_storage_d3(struct device *dev)
 {
 	return false;
 }
+static inline bool acpi_dev_state_d0(struct device *dev)
+{
+	return true;
+}
 #endif
 
 #if defined(CONFIG_ACPI) && defined(CONFIG_PM_SLEEP)
-- 
2.30.2


^ permalink raw reply related	[flat|nested] 10+ messages in thread

* [PATCH 5/6] media: i2c: imx319: Support device probe in non-zero ACPI D state
  2021-10-18 12:17 [PATCH v11 0/6] Support running driver's probe for a device powered off Sakari Ailus
                   ` (3 preceding siblings ...)
  2021-10-18 12:17 ` [PATCH 4/6] ACPI: Add a convenience function to tell a device is in D0 state Sakari Ailus
@ 2021-10-18 12:17 ` Sakari Ailus
  2021-10-18 12:17 ` [PATCH 6/6] at24: Support probing while " Sakari Ailus
  2021-11-03 18:10 ` [PATCH v11 0/6] Support running driver's probe for a device powered off Rafael J. Wysocki
  6 siblings, 0 replies; 10+ messages in thread
From: Sakari Ailus @ 2021-10-18 12:17 UTC (permalink / raw)
  To: linux-i2c
  Cc: Wolfram Sang, Rafael J. Wysocki, linux-acpi, linux-kernel,
	Greg Kroah-Hartman, rajmohan.mani, Tomasz Figa,
	Bartosz Golaszewski, Bingbu Cao, Chiranjeevi Rapolu,
	Hyungwoo Yang, linux-media

From: Rajmohan Mani <rajmohan.mani@intel.com>

Tell ACPI device PM code that the driver supports the device being in
non-zero ACPI D state when the driver's probe function is entered.

Signed-off-by: Rajmohan Mani <rajmohan.mani@intel.com>
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Reviewed-by: Bingbu Cao <bingbu.cao@intel.com>
---
 drivers/media/i2c/imx319.c | 74 ++++++++++++++++++++++----------------
 1 file changed, 44 insertions(+), 30 deletions(-)

diff --git a/drivers/media/i2c/imx319.c b/drivers/media/i2c/imx319.c
index dba0854ab5aad..daa976858e296 100644
--- a/drivers/media/i2c/imx319.c
+++ b/drivers/media/i2c/imx319.c
@@ -140,6 +140,8 @@ struct imx319 {
 
 	/* Streaming on/off */
 	bool streaming;
+	/* True if the device has been identified */
+	bool identified;
 };
 
 static const struct imx319_reg imx319_global_regs[] = {
@@ -2084,6 +2086,31 @@ imx319_set_pad_format(struct v4l2_subdev *sd,
 	return 0;
 }
 
+/* Verify chip ID */
+static int imx319_identify_module(struct imx319 *imx319)
+{
+	struct i2c_client *client = v4l2_get_subdevdata(&imx319->sd);
+	int ret;
+	u32 val;
+
+	if (imx319->identified)
+		return 0;
+
+	ret = imx319_read_reg(imx319, IMX319_REG_CHIP_ID, 2, &val);
+	if (ret)
+		return ret;
+
+	if (val != IMX319_CHIP_ID) {
+		dev_err(&client->dev, "chip id mismatch: %x!=%x",
+			IMX319_CHIP_ID, val);
+		return -EIO;
+	}
+
+	imx319->identified = true;
+
+	return 0;
+}
+
 /* Start streaming */
 static int imx319_start_streaming(struct imx319 *imx319)
 {
@@ -2091,6 +2118,10 @@ static int imx319_start_streaming(struct imx319 *imx319)
 	const struct imx319_reg_list *reg_list;
 	int ret;
 
+	ret = imx319_identify_module(imx319);
+	if (ret)
+		return ret;
+
 	/* Global Setting */
 	reg_list = &imx319_global_setting;
 	ret = imx319_write_regs(imx319, reg_list->regs, reg_list->num_of_regs);
@@ -2206,26 +2237,6 @@ static int __maybe_unused imx319_resume(struct device *dev)
 	return ret;
 }
 
-/* Verify chip ID */
-static int imx319_identify_module(struct imx319 *imx319)
-{
-	struct i2c_client *client = v4l2_get_subdevdata(&imx319->sd);
-	int ret;
-	u32 val;
-
-	ret = imx319_read_reg(imx319, IMX319_REG_CHIP_ID, 2, &val);
-	if (ret)
-		return ret;
-
-	if (val != IMX319_CHIP_ID) {
-		dev_err(&client->dev, "chip id mismatch: %x!=%x",
-			IMX319_CHIP_ID, val);
-		return -EIO;
-	}
-
-	return 0;
-}
-
 static const struct v4l2_subdev_core_ops imx319_subdev_core_ops = {
 	.subscribe_event = v4l2_ctrl_subdev_subscribe_event,
 	.unsubscribe_event = v4l2_event_subdev_unsubscribe,
@@ -2420,6 +2431,7 @@ static struct imx319_hwcfg *imx319_get_hwcfg(struct device *dev)
 static int imx319_probe(struct i2c_client *client)
 {
 	struct imx319 *imx319;
+	bool full_power;
 	int ret;
 	u32 i;
 
@@ -2432,11 +2444,14 @@ static int imx319_probe(struct i2c_client *client)
 	/* Initialize subdev */
 	v4l2_i2c_subdev_init(&imx319->sd, client, &imx319_subdev_ops);
 
-	/* Check module identity */
-	ret = imx319_identify_module(imx319);
-	if (ret) {
-		dev_err(&client->dev, "failed to find sensor: %d", ret);
-		goto error_probe;
+	full_power = acpi_dev_state_d0(&client->dev);
+	if (full_power) {
+		/* Check module identity */
+		ret = imx319_identify_module(imx319);
+		if (ret) {
+			dev_err(&client->dev, "failed to find sensor: %d", ret);
+			goto error_probe;
+		}
 	}
 
 	imx319->hwcfg = imx319_get_hwcfg(&client->dev);
@@ -2488,11 +2503,9 @@ static int imx319_probe(struct i2c_client *client)
 	if (ret < 0)
 		goto error_media_entity;
 
-	/*
-	 * Device is already turned on by i2c-core with ACPI domain PM.
-	 * Enable runtime PM and turn off the device.
-	 */
-	pm_runtime_set_active(&client->dev);
+	/* Set the device's state to active if it's in D0 state. */
+	if (full_power)
+		pm_runtime_set_active(&client->dev);
 	pm_runtime_enable(&client->dev);
 	pm_runtime_idle(&client->dev);
 
@@ -2545,6 +2558,7 @@ static struct i2c_driver imx319_i2c_driver = {
 	},
 	.probe_new = imx319_probe,
 	.remove = imx319_remove,
+	.flags = I2C_DRV_ACPI_WAIVE_D0_PROBE,
 };
 module_i2c_driver(imx319_i2c_driver);
 
-- 
2.30.2


^ permalink raw reply related	[flat|nested] 10+ messages in thread

* [PATCH 6/6] at24: Support probing while in non-zero ACPI D state
  2021-10-18 12:17 [PATCH v11 0/6] Support running driver's probe for a device powered off Sakari Ailus
                   ` (4 preceding siblings ...)
  2021-10-18 12:17 ` [PATCH 5/6] media: i2c: imx319: Support device probe in non-zero ACPI D state Sakari Ailus
@ 2021-10-18 12:17 ` Sakari Ailus
  2021-11-03 18:10 ` [PATCH v11 0/6] Support running driver's probe for a device powered off Rafael J. Wysocki
  6 siblings, 0 replies; 10+ messages in thread
From: Sakari Ailus @ 2021-10-18 12:17 UTC (permalink / raw)
  To: linux-i2c
  Cc: Wolfram Sang, Rafael J. Wysocki, linux-acpi, linux-kernel,
	Greg Kroah-Hartman, rajmohan.mani, Tomasz Figa,
	Bartosz Golaszewski, Bingbu Cao, Chiranjeevi Rapolu,
	Hyungwoo Yang, linux-media

In certain use cases (where the chip is part of a camera module, and the
camera module is wired together with a camera privacy LED), powering on
the device during probe is undesirable. Add support for the at24 to
execute probe while being in ACPI D state other than 0 (which means fully
powered on).

Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Acked-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
---
 drivers/misc/eeprom/at24.c | 45 +++++++++++++++++++++++---------------
 1 file changed, 27 insertions(+), 18 deletions(-)

diff --git a/drivers/misc/eeprom/at24.c b/drivers/misc/eeprom/at24.c
index 305ffad131a29..49ab656e8a96e 100644
--- a/drivers/misc/eeprom/at24.c
+++ b/drivers/misc/eeprom/at24.c
@@ -595,6 +595,7 @@ static int at24_probe(struct i2c_client *client)
 	bool i2c_fn_i2c, i2c_fn_block;
 	unsigned int i, num_addresses;
 	struct at24_data *at24;
+	bool full_power;
 	struct regmap *regmap;
 	bool writable;
 	u8 test_byte;
@@ -747,14 +748,16 @@ static int at24_probe(struct i2c_client *client)
 
 	i2c_set_clientdata(client, at24);
 
-	err = regulator_enable(at24->vcc_reg);
-	if (err) {
-		dev_err(dev, "Failed to enable vcc regulator\n");
-		return err;
-	}
+	full_power = acpi_dev_state_d0(&client->dev);
+	if (full_power) {
+		err = regulator_enable(at24->vcc_reg);
+		if (err) {
+			dev_err(dev, "Failed to enable vcc regulator\n");
+			return err;
+		}
 
-	/* enable runtime pm */
-	pm_runtime_set_active(dev);
+		pm_runtime_set_active(dev);
+	}
 	pm_runtime_enable(dev);
 
 	at24->nvmem = devm_nvmem_register(dev, &nvmem_config);
@@ -766,15 +769,18 @@ static int at24_probe(struct i2c_client *client)
 	}
 
 	/*
-	 * Perform a one-byte test read to verify that the
-	 * chip is functional.
+	 * Perform a one-byte test read to verify that the chip is functional,
+	 * unless powering on the device is to be avoided during probe (i.e.
+	 * it's powered off right now).
 	 */
-	err = at24_read(at24, 0, &test_byte, 1);
-	if (err) {
-		pm_runtime_disable(dev);
-		if (!pm_runtime_status_suspended(dev))
-			regulator_disable(at24->vcc_reg);
-		return -ENODEV;
+	if (full_power) {
+		err = at24_read(at24, 0, &test_byte, 1);
+		if (err) {
+			pm_runtime_disable(dev);
+			if (!pm_runtime_status_suspended(dev))
+				regulator_disable(at24->vcc_reg);
+			return -ENODEV;
+		}
 	}
 
 	pm_runtime_idle(dev);
@@ -794,9 +800,11 @@ static int at24_remove(struct i2c_client *client)
 	struct at24_data *at24 = i2c_get_clientdata(client);
 
 	pm_runtime_disable(&client->dev);
-	if (!pm_runtime_status_suspended(&client->dev))
-		regulator_disable(at24->vcc_reg);
-	pm_runtime_set_suspended(&client->dev);
+	if (acpi_dev_state_d0(&client->dev)) {
+		if (!pm_runtime_status_suspended(&client->dev))
+			regulator_disable(at24->vcc_reg);
+		pm_runtime_set_suspended(&client->dev);
+	}
 
 	return 0;
 }
@@ -833,6 +841,7 @@ static struct i2c_driver at24_driver = {
 	.probe_new = at24_probe,
 	.remove = at24_remove,
 	.id_table = at24_ids,
+	.flags = I2C_DRV_ACPI_WAIVE_D0_PROBE,
 };
 
 static int __init at24_init(void)
-- 
2.30.2


^ permalink raw reply related	[flat|nested] 10+ messages in thread

* Re: [PATCH 3/6] Documentation: ACPI: Document _DSC object usage for enum power state
  2021-10-18 12:17 ` [PATCH 3/6] Documentation: ACPI: Document _DSC object usage for enum power state Sakari Ailus
@ 2021-10-25 11:01   ` Bingbu Cao
  2021-10-25 11:25     ` Sakari Ailus
  0 siblings, 1 reply; 10+ messages in thread
From: Bingbu Cao @ 2021-10-25 11:01 UTC (permalink / raw)
  To: Sakari Ailus, linux-i2c
  Cc: Wolfram Sang, Rafael J. Wysocki, linux-acpi, linux-kernel,
	Greg Kroah-Hartman, rajmohan.mani, Tomasz Figa,
	Bartosz Golaszewski, Bingbu Cao, Chiranjeevi Rapolu,
	Hyungwoo Yang, linux-media

Sakari,

On 10/18/21 8:17 PM, Sakari Ailus wrote:
> Document the use of the _DSC object for setting desirable power state
> during probe.
> 
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> Reviewed-by: Tomasz Figa <tfiga@chromium.org>
> ---
>  Documentation/firmware-guide/acpi/index.rst   |  1 +
>  .../firmware-guide/acpi/non-d0-probe.rst      | 78 +++++++++++++++++++
>  2 files changed, 79 insertions(+)
>  create mode 100644 Documentation/firmware-guide/acpi/non-d0-probe.rst
> 
> diff --git a/Documentation/firmware-guide/acpi/index.rst b/Documentation/firmware-guide/acpi/index.rst
> index a99ee402b212b..b053b0c3d6969 100644
> --- a/Documentation/firmware-guide/acpi/index.rst
> +++ b/Documentation/firmware-guide/acpi/index.rst
> @@ -26,5 +26,6 @@ ACPI Support
>     acpi-lid
>     lpit
>     video_extension
> +   non-d0-probe
>     extcon-intel-int3496
>     intel-pmc-mux
> diff --git a/Documentation/firmware-guide/acpi/non-d0-probe.rst b/Documentation/firmware-guide/acpi/non-d0-probe.rst
> new file mode 100644
> index 0000000000000..78781e1ab6a3d
> --- /dev/null
> +++ b/Documentation/firmware-guide/acpi/non-d0-probe.rst
> @@ -0,0 +1,78 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +========================================
> +Probing devices in other D states than 0
> +========================================
> +
> +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.
> +
> +How it works
> +============
> +
> +The _DSC (Device State for Configuration) object that evaluates to an integer
> +may be used to tell Linux the highest allowed D state for a device during
> +probe. The support for _DSC requires support from the kernel bus type if the
> +bus driver normally sets the device in D0 state for probe.
> +
> +The downside of using _DSC 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.
> +
> +I²C
> +---
> +
> +If an I²C driver indicates its support for this by setting the
> +I2C_DRV_ACPI_WAIVE_D0_PROBE flag in struct i2c_driver.flags field and the
> +_DSC object evaluates to integer higher than the D state of the device,
> +the device will not be powered on (put in D0 state) for probe.
> +
> +D states
> +--------
> +
> +The D states and thus also the allowed values for _DSC are listed below. Refer
> +to [1] for more information on device power states.
> +
> +.. code-block:: text
> +
> +	Number	State	Description
> +	0	D0	Device fully powered on
> +	1	D1
> +	2	D2
> +	3	D3hot
> +	4	D3cold	Off
> +
> +References
> +==========
> +
> +[1] https://uefi.org/specifications/ACPI/6.4/02_Definition_of_Terms/Definition_of_Terms.html#device-power-state-definitions
> +
> +Example
> +=======
> +
> +An ASL example describing an ACPI device using _DSC object to tell Operating
> +System the device should remain powered off during probe looks like this. Some
> +objects not relevant from the example point of view have been omitted.
> +
> +.. code-block:: text
> +
> +	Device (CAM0)
> +        {
> +		Name (_HID, "SONY319A")
> +		Name (_UID, Zero)
> +		Name (_CRS, ResourceTemplate ()
> +		{
> +			I2cSerialBus(0x0020, ControllerInitiated, 0x00061A80,
> +				     AddressingMode7Bit, "\\_SB.PCI0.I2C0",
> +				     0x00, ResourceConsumer)
> +		})
> +		Name (_DSC, 0, NotSerialized)
> +		{
> +			Return (0x4)
> +                }
One question here:
Is the value of _DSC object evaluated from 'Method' or 'Name' ?

> +	}
> 

-- 
Best regards,
Bingbu Cao

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH 3/6] Documentation: ACPI: Document _DSC object usage for enum power state
  2021-10-25 11:01   ` Bingbu Cao
@ 2021-10-25 11:25     ` Sakari Ailus
  0 siblings, 0 replies; 10+ messages in thread
From: Sakari Ailus @ 2021-10-25 11:25 UTC (permalink / raw)
  To: Rafael J. Wysocki, Bingbu Cao
  Cc: linux-i2c, Wolfram Sang, linux-acpi, linux-kernel,
	Greg Kroah-Hartman, rajmohan.mani, Tomasz Figa,
	Bartosz Golaszewski, Bingbu Cao, Chiranjeevi Rapolu,
	Hyungwoo Yang, linux-media

Hi Bingbu,

On Mon, Oct 25, 2021 at 07:01:41PM +0800, Bingbu Cao wrote:
> Sakari,
> 
> On 10/18/21 8:17 PM, Sakari Ailus wrote:
> > Document the use of the _DSC object for setting desirable power state
> > during probe.
> > 
> > Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > Reviewed-by: Tomasz Figa <tfiga@chromium.org>
> > ---
> >  Documentation/firmware-guide/acpi/index.rst   |  1 +
> >  .../firmware-guide/acpi/non-d0-probe.rst      | 78 +++++++++++++++++++
> >  2 files changed, 79 insertions(+)
> >  create mode 100644 Documentation/firmware-guide/acpi/non-d0-probe.rst
> > 
> > diff --git a/Documentation/firmware-guide/acpi/index.rst b/Documentation/firmware-guide/acpi/index.rst
> > index a99ee402b212b..b053b0c3d6969 100644
> > --- a/Documentation/firmware-guide/acpi/index.rst
> > +++ b/Documentation/firmware-guide/acpi/index.rst
> > @@ -26,5 +26,6 @@ ACPI Support
> >     acpi-lid
> >     lpit
> >     video_extension
> > +   non-d0-probe
> >     extcon-intel-int3496
> >     intel-pmc-mux
> > diff --git a/Documentation/firmware-guide/acpi/non-d0-probe.rst b/Documentation/firmware-guide/acpi/non-d0-probe.rst
> > new file mode 100644
> > index 0000000000000..78781e1ab6a3d
> > --- /dev/null
> > +++ b/Documentation/firmware-guide/acpi/non-d0-probe.rst
> > @@ -0,0 +1,78 @@
> > +.. SPDX-License-Identifier: GPL-2.0
> > +
> > +========================================
> > +Probing devices in other D states than 0
> > +========================================
> > +
> > +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.
> > +
> > +How it works
> > +============
> > +
> > +The _DSC (Device State for Configuration) object that evaluates to an integer
> > +may be used to tell Linux the highest allowed D state for a device during
> > +probe. The support for _DSC requires support from the kernel bus type if the
> > +bus driver normally sets the device in D0 state for probe.
> > +
> > +The downside of using _DSC 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.
> > +
> > +I²C
> > +---
> > +
> > +If an I²C driver indicates its support for this by setting the
> > +I2C_DRV_ACPI_WAIVE_D0_PROBE flag in struct i2c_driver.flags field and the
> > +_DSC object evaluates to integer higher than the D state of the device,
> > +the device will not be powered on (put in D0 state) for probe.
> > +
> > +D states
> > +--------
> > +
> > +The D states and thus also the allowed values for _DSC are listed below. Refer
> > +to [1] for more information on device power states.
> > +
> > +.. code-block:: text
> > +
> > +	Number	State	Description
> > +	0	D0	Device fully powered on
> > +	1	D1
> > +	2	D2
> > +	3	D3hot
> > +	4	D3cold	Off
> > +
> > +References
> > +==========
> > +
> > +[1] https://uefi.org/specifications/ACPI/6.4/02_Definition_of_Terms/Definition_of_Terms.html#device-power-state-definitions
> > +
> > +Example
> > +=======
> > +
> > +An ASL example describing an ACPI device using _DSC object to tell Operating
> > +System the device should remain powered off during probe looks like this. Some
> > +objects not relevant from the example point of view have been omitted.
> > +
> > +.. code-block:: text
> > +
> > +	Device (CAM0)
> > +        {
> > +		Name (_HID, "SONY319A")
> > +		Name (_UID, Zero)
> > +		Name (_CRS, ResourceTemplate ()
> > +		{
> > +			I2cSerialBus(0x0020, ControllerInitiated, 0x00061A80,
> > +				     AddressingMode7Bit, "\\_SB.PCI0.I2C0",
> > +				     0x00, ResourceConsumer)
> > +		})
> > +		Name (_DSC, 0, NotSerialized)
> > +		{
> > +			Return (0x4)
> > +                }
> One question here:
> Is the value of _DSC object evaluated from 'Method' or 'Name' ?

"Method". This is a bug in the documentation. Thanks!

Rafael: could you fix this while applying?

-- 
Sakari Ailus

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [PATCH v11 0/6] Support running driver's probe for a device powered off
  2021-10-18 12:17 [PATCH v11 0/6] Support running driver's probe for a device powered off Sakari Ailus
                   ` (5 preceding siblings ...)
  2021-10-18 12:17 ` [PATCH 6/6] at24: Support probing while " Sakari Ailus
@ 2021-11-03 18:10 ` Rafael J. Wysocki
  6 siblings, 0 replies; 10+ messages in thread
From: Rafael J. Wysocki @ 2021-11-03 18:10 UTC (permalink / raw)
  To: Sakari Ailus
  Cc: linux-i2c, Wolfram Sang, Rafael J. Wysocki,
	ACPI Devel Maling List, Linux Kernel Mailing List,
	Greg Kroah-Hartman, Mani, Rajmohan, Tomasz Figa,
	Bartosz Golaszewski, Bingbu Cao, Chiranjeevi Rapolu,
	Hyungwoo Yang, Linux Media Mailing List

On Mon, Oct 18, 2021 at 5:16 PM Sakari Ailus
<sakari.ailus@linux.intel.com> wrote:
>
> Hello everyone,
>
> These patches enable calling (and finishing) a driver's probe function
> without powering on the respective device on busses where the practice is
> to power on the device for probe. While it generally is a driver's job to
> check the that the device is there, there are cases where it might be
> undesirable. (In this case it stems from a combination of hardware design
> and user expectations; see below.) The downside with this change is that
> if there is something wrong with the device, it will only be found at the
> time the device is used. In this case (the camera sensors + EEPROM in a
> sensor) I don't see any tangible harm from that though.
>
> An indication both from the driver and the firmware is required to allow
> the device's power state to remain off during probe (see the second patch).
>
>
> The use case is such that there is a privacy LED next to an integrated
> user-facing laptop camera, and this LED is there to signal the user that
> the camera is recording a video or capturing images. That LED also happens
> to be wired to one of the power supplies of the camera, so whenever you
> power on the camera, the LED will be lit, whether images are captured from
> the camera --- or not. There's no way to implement this differently
> without additional software control (allowing of which is itself a
> hardware design decision) on most CSI-2-connected camera sensors as they
> simply have no pin to signal the camera streaming state.
>
> This is also what happens during driver probe: the camera will be powered
> on by the I²C subsystem calling dev_pm_domain_attach() and the device is
> already powered on when the driver's own probe function is called. To the
> user this visible during the boot process as a blink of the privacy LED,
> suggesting that the camera is recording without the user having used an
> application to do that. From the end user's point of view the behaviour is
> not expected and for someone unfamiliar with internal workings of a
> computer surely seems quite suspicious --- even if images are not being
> actually captured.
>
> I've tested these on linux-next master.
>
> since v11 <URL:https://lore.kernel.org/lkml/20210210230800.30291-1-sakari.ailus@linux.intel.com/>:
>
> - Rebase on linux-next.
>
> - Call device object that designates the intended power state for probe
>   "_DSC" instead of "_DSE".
>
> - Remove the ov5670 driver patch from the set due to conflict (will merge
>   through media tree later on).
>
> since v10 <URL:https://lore.kernel.org/linux-acpi/20210205132505.20173-1-sakari.ailus@linux.intel.com/>:
>
> - Instead of "low power state" refer to ACPI D states and "full power", of
>   which latter is used in individual drivers.
>
> - Fix remaining references to _DSD properties.
>
> - Rework commit messages to reflect recent changes.
>
> - Rework the documentation to separate _DSE from I²C as it's not really
>   specific to that.
>
> - Rename the I2C_DRV_FL_ALLOW_LOW_POWER_PROBE flag as
>   I2C_DRV_ACPI_WAIVE_D0_PROBE.
>
> since v9 <URL:https://lore.kernel.org/linux-acpi/CAJZ5v0jjgy2KXOw5pyshvaEVzLctu4jsgYK1+YDA+8sZfp-6mw@mail.gmail.com/T/#m003f56b33350772364b1f5c832e9025677107933>:
>
> - Use _DSE object designed for the very purpose of designating intended
>   device probe power state instead of _PRE.
>
> - Rework documentation to reflect the property to _DSE changes (missed in
>   v9).
>
> - Put maximum device enumeration power state in struct acpi_device_power,
>   instead of a flag in struct acpi_device_power_flags. The default is
>   ACPI_STATE_D0.
>
> - i2c_acpi_allow_low_power_probe() now returns true if the desired power
>   state is greater or equal to the current device power state.
>
> - Rename local variable low_power as off_during_probe.
>
> since v8 <URL:https://lore.kernel.org/patchwork/cover/1300068/>:
>
> - Make use of ACPI _PRE object instead of a _DSD property (new patch,
>   1st), align documentation with that.
>
> - Added a blank line.
>
> - Rebased on current linux-next master.
>
> since v7 <URL:https://lore.kernel.org/linux-acpi/20200901210333.8462-1-sakari.ailus@linux.intel.com/>:
>
> - Reorder documentation patch right after the implemenation in the I²C
>   framework.
>
> - Rename allow-low-power-probe property as i2c-allow-low-power-probe.
>
> - Remove extra "property" from the description of the
>   i2c-allow-low-power-probe property and mention it's a device property.
>
> - Add an example to the documentation and refer to the _DSD property spec.
>
> since v6 <URL:https://lore.kernel.org/linux-acpi/20200826115432.6103-1-sakari.ailus@linux.intel.com/>:
>
> - Use u32 for the flags field in struct i2c_driver.
>
> - Use acpi_dev_get_property to read the allow-low-power-probe property.
>
> since v5 <URL:https://lore.kernel.org/linux-acpi/20200810142747.12400-1-sakari.ailus@linux.intel.com/>:
>
> - Identify sensors when they're first powered on. In previous versions, if
>   this wasn't in probe, it was not done at all.
>
> - Return allow_low_power_probe() only for ACPI devices, i.e. OF systems
>   are not affected by these changes.
>
> - Document that I2C_DRV_FL_ALLOW_LOW_POWER_PROBE flag only applies to ACPI
>   drivers.
>
> - Fix extra regulator_disable in at24 driver's remove function when the
>   device was already in low power state.
>
> since v4 <URL:https://lore.kernel.org/linux-acpi/20200121134157.20396-1-sakari.ailus@linux.intel.com/>:
>
> - Rename "probe-low-power" property as "allow-low-power-probe". This is
>   taken into account in function and file naming, too.
>
> - Turn probe_low_power field in struct i2c_driver into flags field.
>
> - Rebase on Wolfram's i2c/for-next branch that contains the removal of the
>   support for disabling I²C core IRQ mappings (commit
>   0c2a34937f7e4c4776bb261114c475392da2355c).
>
> - Change wording for "allow-low-power-probe" property in ACPI
>   documentation.
>
> since v3 <URL:https://lore.kernel.org/linux-acpi/20200109154529.19484-1-sakari.ailus@linux.intel.com/T/#t>:
>
> - Rework the 2nd patch based on Rafael's comments
>
>         - Rework description of the ACPI low power state helper function,
>           according to Rafael's text.
>
>         - Rename and rework the same function as
>           acpi_dev_state_low_power().
>
>         - Reflect the changes in commit message as well.
>
> - Added a patch to document the probe-low-power _DSD property.
>
> since v2 <URL:https://patchwork.kernel.org/cover/11114255/>:
>
> - Remove extra CONFIG_PM ifdefs; these are not needed.
>
> - Move the checks for power state hints from drivers/base/dd.c to
>   drivers/i2c/i2c-base-core.c; these are I²C devices anyway.
>
> - Move the probe_low_power field from struct device_driver to struct
>   i2c_driver.
>
> since v1:
>
> - Rename probe_powered_off struct device field as probe_low_power and
>   reflect the similar naming to the patches overall.
>
> - Work with CONFIG_PM disabled, too.
>
> Rajmohan Mani (1):
>   media: i2c: imx319: Support device probe in non-zero ACPI D state
>
> Sakari Ailus (5):
>   ACPI: scan: Obtain device's desired enumeration power state
>   i2c: Allow an ACPI driver to manage the device's power state during
>     probe
>   Documentation: ACPI: Document _DSC object usage for enum power state
>   ACPI: Add a convenience function to tell a device is in D0 state
>   at24: Support probing while in non-zero ACPI D state
>
>  Documentation/firmware-guide/acpi/index.rst   |  1 +
>  .../firmware-guide/acpi/non-d0-probe.rst      | 78 +++++++++++++++++++
>  drivers/acpi/device_pm.c                      | 26 +++++++
>  drivers/acpi/scan.c                           |  4 +
>  drivers/i2c/i2c-core-acpi.c                   | 10 +++
>  drivers/i2c/i2c-core-base.c                   |  7 +-
>  drivers/media/i2c/imx319.c                    | 74 +++++++++++-------
>  drivers/misc/eeprom/at24.c                    | 45 ++++++-----
>  include/acpi/acpi_bus.h                       |  1 +
>  include/linux/acpi.h                          |  5 ++
>  include/linux/i2c.h                           | 18 +++++
>  11 files changed, 218 insertions(+), 51 deletions(-)
>  create mode 100644 Documentation/firmware-guide/acpi/non-d0-probe.rst
>
> --

I've queued up this series for 5.16-rc, thanks!

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2021-11-03 18:10 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-18 12:17 [PATCH v11 0/6] Support running driver's probe for a device powered off Sakari Ailus
2021-10-18 12:17 ` [PATCH 1/6] ACPI: scan: Obtain device's desired enumeration power state Sakari Ailus
2021-10-18 12:17 ` [PATCH 2/6] i2c: Allow an ACPI driver to manage the device's power state during probe Sakari Ailus
2021-10-18 12:17 ` [PATCH 3/6] Documentation: ACPI: Document _DSC object usage for enum power state Sakari Ailus
2021-10-25 11:01   ` Bingbu Cao
2021-10-25 11:25     ` Sakari Ailus
2021-10-18 12:17 ` [PATCH 4/6] ACPI: Add a convenience function to tell a device is in D0 state Sakari Ailus
2021-10-18 12:17 ` [PATCH 5/6] media: i2c: imx319: Support device probe in non-zero ACPI D state Sakari Ailus
2021-10-18 12:17 ` [PATCH 6/6] at24: Support probing while " Sakari Ailus
2021-11-03 18:10 ` [PATCH v11 0/6] Support running driver's probe for a device powered off Rafael J. Wysocki

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).