dt-bindings: tas2562: Add TAS2564 to binding

Add the TAS2564 compatible and data sheet link to the binding.

---
 Documentation/devicetree/bindings/sound/tas2562.yaml | 2 ++
 1 file changed, 2 insertions(+)

index c3b7e19a0d44..d3ceda356aaa 100644
@@ -19,12 +19,14 @@ description: |
   Specifications about the audio amplifier can be found at:
     https://www.ti.com/lit/gpn/tas2562
     https://www.ti.com/lit/gpn/tas2563
+    https://www.ti.com/lit/gpn/tas2564
 
 properties:
   compatible:
     enum:
       - ti,tas2562
       - ti,tas2563
+      - ti,tas2564
 
   reg:
     maxItems: 1

2.28.0

Add the TAS2564 as a supported amplifier. This amplifier is register, bitmap and feature compatible to the TAS2562.

---
 sound/soc/codecs/tas2562.c | 3 +++
 1 file changed, 3 insertions(+)

index 99920c691d28..56d410141ee0 100644
@@ -58,6 +58,7 @@ struct tas2562_data {
 enum tas256x_model {
 	TAS2562,
 	TAS2563,
+	TAS2564,
 };
 
 static int tas2562_set_bias_level(struct snd_soc_component *component,

@@ -761,6 +762,7 @@ static int tas2562_probe(struct i2c_client *client,
 static const struct i2c_device_id tas2562_id[] = {
 	{ "tas2562", TAS2562 },
 	{ "tas2563", TAS2563 },
+	{ "tas2564", TAS2564 },
 	{ }
 };
 MODULE_DEVICE_TABLE(i2c, tas2562_id);

@@ -768,6 +770,7 @@ MODULE_DEVICE_TABLE(i2c, tas2562_id);
 static const struct of_device_id tas2562_of_match[] = {
 	{ .compatible = "ti,tas2562", },
 	{ .compatible = "ti,tas2563", },
+	{ .compatible = "ti,tas2564", },
 	{ },
 };
 MODULE_DEVICE_TABLE(of, tas2562_of_match);

2.28.0

Applied to

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

Thanks!

[1/2] dt-bindings: tas2562: Add TAS2564 to binding

      commit: 7a477213923fe07c17db7c3104cce6b316f75f60
[2/2] ASoC: tas2562: Add the TAS2564 compatible
      commit: 534c0f4391a497d10c2b5eb3df2016221b6ec4f6

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