ASoC: dt-bindings: keembay-i2s: Fix reg descriptions

intel,keembay-i2s has two register regions:
- I2S registers
- I2S gen configuration

Describe these regions accordingly to fix the following warning seen with 'make dt_binding_check':

Documentation/devicetree/bindings/sound/intel,keembay-i2s.example.dt.yaml: example-0: i2s@20140000:reg:0: [538181632, 512, 539623588, 4] is too long

---
 .../devicetree/bindings/sound/intel,keembay-i2s.yaml        | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

index 175e4fb0c315..2e0bbc1c868a 100644
@@ -23,7 +23,8 @@ properties:
 
   reg:
     items:
-      - description: I2S configuration
+      - description: I2S registers
+      - description: I2S gen configuration
 
   reg-names:
     items:

@@ -60,7 +61,8 @@ examples:
      i2s3: i2s@20140000 {
          compatible = "intel,keembay-i2s";
          #sound-dai-cells = <0>;
-         reg = <0x20140000 0x200 0x202a00a4 0x4>;
+         reg = <0x20140000 0x200>, /* I2S registers */
+               <0x202a00a4 0x4>; /* I2S gen configuration */
          reg-names = "i2s-regs", "i2s_gen_cfg";
          interrupts = <GIC_SPI 120 IRQ_TYPE_LEVEL_HIGH>;
          clock-names = "osc", "apb_clk";

2.17.1

Applied to

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

Thanks!

[1/1] ASoC: dt-bindings: keembay-i2s: Fix reg descriptions

      commit: 9308a3c92642cddb9ef89cc4014282cf14f2e2d2

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