Messages in this thread Patch in this message | | | From | Raul E Rangel <> | Subject | [PATCH v6 13/13] Input: raydium_ts_i2c - Don't set wake_capable and wake_irq | Date | Thu, 29 Sep 2022 10:19:17 -0600 |
| |
The i2c-core will now handle setting the wake_irq and wake capability for DT and ACPI systems.
Signed-off-by: Raul E Rangel <rrangel@chromium.org> ---
(no changes since v1)
drivers/input/touchscreen/raydium_i2c_ts.c | 9 --------- 1 file changed, 9 deletions(-)
diff --git a/drivers/input/touchscreen/raydium_i2c_ts.c b/drivers/input/touchscreen/raydium_i2c_ts.c index 66c5b577b791d4f..88d187dc5d325f6 100644 --- a/drivers/input/touchscreen/raydium_i2c_ts.c +++ b/drivers/input/touchscreen/raydium_i2c_ts.c @@ -1185,15 +1185,6 @@ static int raydium_i2c_probe(struct i2c_client *client, return error; } - /* - * The wake IRQ should be declared via device tree instead of assuming - * the IRQ can wake the system. This is here for legacy reasons and - * will be removed once the i2c-core supports querying ACPI for wake - * capabilities. - */ - if (!client->dev.power.wakeirq) - dev_pm_set_wake_irq(&client->dev, client->irq); - error = devm_device_add_group(&client->dev, &raydium_i2c_attribute_group); if (error) { -- 2.37.3.998.g577e59143f-goog
| |