linux-kernel - Re: (subset) [PATCH v1 0/3] db845c/rb3: add i2s playback support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <173444204405.31585.10764828283359007380.b4-ty@kernel.org>
Date: Tue, 17 Dec 2024 13:27:24 +0000
From: Mark Brown <broonie@...nel.org>
To: konradybcio@...nel.org, andersson@...nel.org, 
 srinivas.kandagatla@...aro.org, Alexey Klimov <alexey.klimov@...aro.org>
Cc: tiwai@...e.com, lgirdwood@...il.com, perex@...ex.cz, robh@...nel.org, 
 krzk+dt@...nel.org, conor+dt@...nel.org, dmitry.baryshkov@...aro.org, 
 linux-sound@...r.kernel.org, linux-arm-msm@...r.kernel.org, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v1 0/3] db845c/rb3: add i2s playback support

On Thu, 05 Dec 2024 02:33:41 +0000, Alexey Klimov wrote:
> There are i2s signals provided in low-speed connector on such boards
> as required by 96boards spec. Looks like it is possible to actually
> playback something via these pins after adding missing parts here
> and there.
> 
> I tested simple widely available cheap DACs like UDA1334 and PCM5102A
> and they works just fine without need for mclk. I guess any DAC that
> can handle 48 kHz and 16bit will do.
> 
> [...]

Applied to

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

Thanks!

[2/3] ASoC: qcom: sdm845: add handling of secondary MI2S clock
      commit: 8bfb66c75cdace542dabe87841152614fd5b8d91

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