dt-bindings: tas2770: Convert tas2770 binding to yaml
PATCH v3 1/2 dt-bindings: tas2770: Convert tas2770 binding to yaml
Convert the tas2770 binding to yaml format.
Add in the reset-gpio to the binding as it is in the code but not documented in the binding.
--- .../devicetree/bindings/sound/tas2770.txt | 37 --------- .../devicetree/bindings/sound/tas2770.yaml | 76 +++++++++++++++++++ 2 files changed, 76 insertions(+), 37 deletions(-) delete mode 100644 Documentation/devicetree/bindings/sound/tas2770.txt create mode 100644 Documentation/devicetree/bindings/sound/tas2770.yaml
Documentation/devicetree/bindings/sound/tas2770.txt deleted +0 -37
@@ -1,37 +0,0 @@ -Texas Instruments TAS2770 Smart PA - -The TAS2770 is a mono, digital input Class-D audio amplifier optimized for -efficiently driving high peak power into small loudspeakers. -Integrated speaker voltage and current sense provides for -real time monitoring of loudspeaker behavior. - -Required properties: - - - compatible: - Should contain "ti,tas2770". - - reg: - The i2c address. Should contain <0x4c>, <0x4d>,<0x4e>, or <0x4f>. - - #address-cells - Should be <1>. - - #size-cells - Should be <0>. - - ti,asi-format: - Sets TDM RX capture edge. 0->Rising; 1->Falling. - - ti,imon-slot-no:- TDM TX current sense time slot. - - ti,vmon-slot-no:- TDM TX voltage sense time slot. - -Optional properties: - -- interrupt-parent: the phandle to the interrupt controller which provides - the interrupt. -- interrupts: interrupt specification for data-ready. - -Examples: - - tas2770@4c { - compatible = "ti,tas2770"; - reg = <0x4c>; - #address-cells = <1>; - #size-cells = <0>; - interrupt-parent = <&msm_gpio>; - interrupts = <97 0>; - ti,asi-format = <0>; - ti,imon-slot-no = <0>; - ti,vmon-slot-no = <2>; - }; -
Documentation/devicetree/bindings/sound/tas2770.yaml new file +76 -0
76 lines not on this page · raw message
Signature · 1 line
2.27.0
PATCH v3 2/2 ASoC: tas2770: Fix reset gpio property name
Fix the reset property name when allocating the GPIO descriptor. The gpiod_get_optional appends either the -gpio or -gpios suffix to the name.
--- sound/soc/codecs/tas2770.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
sound/soc/codecs/tas2770.c +1 -2
@@ -759,8 +759,7 @@ static int tas2770_i2c_probe(struct i2c_client *client, } } - tas2770->reset_gpio =devm_gpiod_get_optional (tas2770->dev, -"reset-gpio" , + tas2770->reset_gpio =devm_gpiod_get_optional (tas2770->dev,"reset" ,GPIOD_OUT_HIGH );if (IS_ERR (tas2770->reset_gpio)) {if (PTR_ERR (tas2770->reset_gpio) == -EPROBE_DEFER ) {
Signature · 1 line
2.27.0
Mark Brown
maintainerQuoted 3 lines · Dan Murphy
Convert the tas2770 binding to yaml format.
Add in the reset-gpio to the binding as it is in the code but not documented in the binding.
What's new about this version?
Mark
Quoted 5 lines · Mark Brown
Quoted 3 lines · Dan Murphy
Convert the tas2770 binding to yaml format.
Add in the reset-gpio to the binding as it is in the code but not documented in the binding.What's new about this version?
The licensing was updated and added reviewed-by from Rob from v1 of the patchset.
Mark Brown
maintainerQuoted 3 lines · Dan Murphy
Convert the tas2770 binding to yaml format.
Add in the reset-gpio to the binding as it is in the code but not documented in the binding.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: tas2770: Convert tas2770 binding to yaml
commit: ad0ddbb9ba3d5216bf3035db6684c1507c90b93b
[2/2] ASoC: tas2770: Fix reset gpio property name
commit: 58b868f51d6e38146e44cb09fcd92b5fc35d83bcAll 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