Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
From:   Mark Brown <broonie@kernel.org>
To:     robh+dt@kernel.org, Jayesh Choudhary <j-choudhary@ti.com>
Cc:     devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
        peter.ujfalusi@gmail.com, linux-kernel@vger.kernel.org,
        lgirdwood@gmail.com, krzysztof.kozlowski@canonical.com
In-Reply-To: <20220209063008.2928-1-j-choudhary@ti.com>
References: <20220209063008.2928-1-j-choudhary@ti.com>
Subject: Re: [PATCH v6] ASoC: dt-bindings: davinci-mcasp: convert McASP bindings to yaml schema
Message-Id: <164442301594.4135858.14145086977040876727.b4-ty@kernel.org>
Date:   Wed, 09 Feb 2022 16:10:15 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 9 Feb 2022 12:00:08 +0530, Jayesh Choudhary wrote:
> Convert the bindings for McASP controllers for TI SoCs from txt
> to YAML schema.
> 
> Adds additional properties 'clocks', 'clock-names', 'power-domains',
> '#sound-dai-cells' and 'port' which were missing from the txt file.
> Removes properties 'sram-size-playback' and 'sram-size-capture'
> since they are not used.
> Adds 'dmas' and 'dma-names' in the example which were missing from
> the txt file.
> Changes 'interrupts' and 'interrupt-names' from optional to
> required properties.
> Changes 'op-modes', 'serial-dir' to optional properties as they are
> not needed if the McASP is used only as GPIO.
> Changes 'tdm-slots' to required property only for I2S operation mode.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: dt-bindings: davinci-mcasp: convert McASP bindings to yaml schema
      commit: 8be90641a0bbd9a3606547aa6a0f70b020e74c8f

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