Re: [PATCH 2/4] ASoC: tas2781-i2c: Drop weird GPIO code

From: Mark Brown
Date: Wed Jul 03 2024 - 16:25:28 EST

Next message: Kees Cook: "Re: [PATCH] dm-verity: fix dm_is_verity_target() when dm-verity is builtin"
Previous message: Kees Cook: "Re: [PATCH 01/53] workqueue: Introduce the create*_workqueue2() macros"
In reply to: Linus Walleij: "[PATCH 2/4] ASoC: tas2781-i2c: Drop weird GPIO code"
Next in thread: Linus Walleij: "[PATCH 3/4] ASoC: tas2781-i2c: Get the right GPIO line"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mon, Jul 01, 2024 at 09:02:13AM +0200, Linus Walleij wrote:
> The tas2781-i2c driver gets an IRQ from either ACPI or device tree,
> then proceeds to check if the IRQ has a corresponding GPIO and in
> case it does enforce the GPIO as input and set a label on it.

This doesn't apply against current code, please check and resend.

Attachment: signature.asc
Description: PGP signature

Next message: Kees Cook: "Re: [PATCH] dm-verity: fix dm_is_verity_target() when dm-verity is builtin"
Previous message: Kees Cook: "Re: [PATCH 01/53] workqueue: Introduce the create*_workqueue2() macros"
In reply to: Linus Walleij: "[PATCH 2/4] ASoC: tas2781-i2c: Drop weird GPIO code"
Next in thread: Linus Walleij: "[PATCH 3/4] ASoC: tas2781-i2c: Get the right GPIO line"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]