mbox series

[v3,0/6] ASoC: Add NTP8918 and NTP8835 codecs support

Message ID 20240925-ntp-amps-8918-8835-v3-0-e2459a8191a6@salutedevices.com (mailing list archive)
Headers show
Series ASoC: Add NTP8918 and NTP8835 codecs support | expand

Message

Igor Prusov Sept. 25, 2024, 2:52 p.m. UTC
This series adds support for two NeoFidelity amplifiers. For both
amplifiers vendor provides software for equalizer and filters
configuration, which generates firmware files with registers values.
Since in both cases those files have same encoding, a common helper
module is added to get firmware via request_firmware() API and set
registers values.

Changes in V3:
- Added clocks to bindings and drivers
- removed unused includes
- ntp8835_reset_gpio() now only implements reset sequence and does not
  leave device in reset state
- make data const where possible
- Link to V2: https://lore.kernel.org/lkml/20240709221203.92167-5-ivprusov@salutedevices.com/

Changes in V2:
- Fix dt_binding_check errors
- Link to V1: https://lore.kernel.org/all/20240709172834.9785-1-ivprusov@salutedevices.com/

---
Igor Prusov (6):
      dt-bindings: vendor-prefixes: Add NeoFidelity, Inc
      ASoC: codecs: Add NeoFidelity Firmware helpers
      ASoC: dt-bindings: Add NeoFidelity NTP8918
      ASoC: codecs: Add NeoFidelity NTP8918 codec
      ASoC: dt-bindings: Add NeoFidelity NTP8835
      ASoC: codecs: Add NeoFidelity NTP8835 codec

 .../bindings/sound/neofidelity,ntp8835.yaml        |  73 ++++
 .../bindings/sound/neofidelity,ntp8918.yaml        |  70 +++
 .../devicetree/bindings/vendor-prefixes.yaml       |   2 +
 sound/soc/codecs/Kconfig                           |  13 +
 sound/soc/codecs/Makefile                          |   6 +
 sound/soc/codecs/ntp8835.c                         | 480 +++++++++++++++++++++
 sound/soc/codecs/ntp8918.c                         | 397 +++++++++++++++++
 sound/soc/codecs/ntpfw.c                           | 137 ++++++
 sound/soc/codecs/ntpfw.h                           |  23 +
 9 files changed, 1201 insertions(+)
---
base-commit: c7fbbb45ef78ff349d16923b516bc8667367d1a6
change-id: 20240924-ntp-amps-8918-8835-1fb126809fa3

Best regards,

Comments

Mark Brown Oct. 1, 2024, 5:53 p.m. UTC | #1
On Wed, 25 Sep 2024 17:52:38 +0300, Igor Prusov wrote:
> This series adds support for two NeoFidelity amplifiers. For both
> amplifiers vendor provides software for equalizer and filters
> configuration, which generates firmware files with registers values.
> Since in both cases those files have same encoding, a common helper
> module is added to get firmware via request_firmware() API and set
> registers values.
> 
> [...]

Applied to

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

Thanks!

[1/6] dt-bindings: vendor-prefixes: Add NeoFidelity, Inc
      commit: 5d9e6d6fc1b98c8c22d110ee931b3b233d43cd13
[2/6] ASoC: codecs: Add NeoFidelity Firmware helpers
      commit: ba1850dc0f2b5638a4a6aa16905c1856dc17587b
[3/6] ASoC: dt-bindings: Add NeoFidelity NTP8918
      commit: 64fbb6bdd45b8953fcad5c4ec648f74c96aec5f3
[4/6] ASoC: codecs: Add NeoFidelity NTP8918 codec
      commit: 2bd61fff3e93b93a20f618028433bcbe8329a6db
[5/6] ASoC: dt-bindings: Add NeoFidelity NTP8835
      commit: 3e2aba5f0b0cafad44c2f635dc19d7bf3f54b978
[6/6] ASoC: codecs: Add NeoFidelity NTP8835 codec
      commit: dc9004ea273a9141c16b90a687da70b77f5a640a

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