Skip to contentSkip to conversation

ASoC: dt-bindings: realtek,rt5640: Make interrupts optional

PATCH In review Fabio Estevam 2 participants 2 messages Jul 27 – Jul 29

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ASoC: dt-bindings: realtek,rt5640: Make interrupts optional

The RT5640 GPIO1/IRQ pin can be configured either as GPIO1 or as the codec interrupt output.

Some boards, such as the Firefly-RK3399, do not connect the codec interrupt output. This causes the following binding validation warning:

'interrupts' is a required property

Make the interrupts property optional to support such hardware configurations.

---
 Documentation/devicetree/bindings/sound/realtek,rt5640.yaml | 1 -
 1 file changed, 1 deletion(-)
Documentation/devicetree/bindings/sound/realtek,rt5640.yaml +0 -1
index 2eb631950963..922fe161f4d7 100644
@@ -135,7 +135,6 @@ properties:
 required:
   - compatible
   - reg
-  - interrupts
 
 unevaluatedProperties: false
 
Signature · 1 line
2.43.0
maintainer
#1 lore raw
Quoted 1 line · Fabio Estevam

ASoC: dt-bindings: realtek,rt5640: Make interrupts optional

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.2

Thanks!

[1/1] ASoC: dt-bindings: realtek,rt5640: Make interrupts optional

      https://git.kernel.org/broonie/sound/c/537601771adb

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

Thanks,
Mark