From: Astrid Rost <[email protected]>
PATCH 1 - convert ts3a227e bindings to yaml.
PATCH 2 - add ts3a227e bindings to support debounce times.
PATCH 3 - add ts3a227e driver to support debounce times.
v3 -> v4
Removed the comments on enums in Patch2.
Signed-off-by: Astrid Rost <[email protected]>
Astrid Rost (3):
dt-bindings: sound: ti,ts3a227e: convert to yaml
dt-bindings: sound: ti,ts3a227e: add control of debounce
ASoC: ts3a227e: add parameters to control debounce times
.../bindings/sound/ti,ts3a227e.yaml | 94 +++++++++++++++++++
.../devicetree/bindings/sound/ts3a227e.txt | 30 ------
sound/soc/codecs/ts3a227e.c | 61 ++++++++++--
3 files changed, 149 insertions(+), 36 deletions(-)
create mode 100644 Documentation/devicetree/bindings/sound/ti,ts3a227e.yaml
delete mode 100644 Documentation/devicetree/bindings/sound/ts3a227e.txt
--
2.20.1
On Wed, Sep 21, 2022 at 10:18:31AM +0200, Astrid Rost wrote:
> Astrid Rost (3):
> dt-bindings: sound: ti,ts3a227e: convert to yaml
> dt-bindings: sound: ti,ts3a227e: add control of debounce
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
On Wed, 21 Sep 2022 10:18:31 +0200, Astrid Rost wrote:
> From: Astrid Rost <[email protected]>
>
> PATCH 1 - convert ts3a227e bindings to yaml.
> PATCH 2 - add ts3a227e bindings to support debounce times.
> PATCH 3 - add ts3a227e driver to support debounce times.
>
> v3 -> v4
> Removed the comments on enums in Patch2.
>
> [...]
Applied to
broonie/sound.git for-next
Thanks!
[1/3] dt-bindings: sound: ti,ts3a227e: convert to yaml
commit: be541bd473618f64fa14138dc7f63b0643363f7b
[2/3] dt-bindings: sound: ti,ts3a227e: add control of debounce
commit: 6a47412d0798735b0715d224574d216dba9e630c
[3/3] ASoC: ts3a227e: add parameters to control debounce times
commit: d20fa87e80c363a1c9534afb31df2fa90087e51d
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