On Mon, Jun 17, 2024 at 02:53:38PM +0100, Simon Trimmer wrote: > IRQ lookup functions such as those in ACPI can return error values when > an IRQ is not defined. The i2c core driver converts the error codes to a > value of 0 and the SPI bus driver passes them unaltered to client device > drivers. > > The cs35l56 driver should only accept positive non-zero values as IRQ > numbers. Have all architectures removed 0 as a valid IRQ?
Attachment:
signature.asc
Description: PGP signature
- Follow-Ups:
- Re: [PATCH] ASoC: cs35l56: Accept values greater than 0 as IRQ numbers
- From: Richard Fitzgerald
- Re: [PATCH] ASoC: cs35l56: Accept values greater than 0 as IRQ numbers
- References:
- [PATCH] ASoC: cs35l56: Accept values greater than 0 as IRQ numbers
- From: Simon Trimmer
- [PATCH] ASoC: cs35l56: Accept values greater than 0 as IRQ numbers
- Prev by Date: [PATCH] ASoC: cs35l56: Accept values greater than 0 as IRQ numbers
- Next by Date: Re: [PATCH v3 1/4] ASoC: dt-bindings: lpc32xx: Add lpc32xx i2s DT binding
- Previous by thread: [PATCH] ASoC: cs35l56: Accept values greater than 0 as IRQ numbers
- Next by thread: Re: [PATCH] ASoC: cs35l56: Accept values greater than 0 as IRQ numbers
- Index(es):