linux-kernel - Re: [PATCH] ASoC: ti: j721e-evm: Fix clock configuration for ti,j7200-cpb-audio compatible

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 for Android: free password hash cracker in your pocket

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

Message-Id: <174231911337.192994.1707640060973057001.b4-ty@kernel.org>
Date: Tue, 18 Mar 2025 17:31:53 +0000
From: Mark Brown <broonie@...nel.org>
To: peter.ujfalusi@...il.com, lgirdwood@...il.com, 
 linux-kernel@...r.kernel.org, Jayesh Choudhary <j-choudhary@...com>
Cc: perex@...ex.cz, tiwai@...e.com, linux-sound@...r.kernel.org
Subject: Re: [PATCH] ASoC: ti: j721e-evm: Fix clock configuration for
 ti,j7200-cpb-audio compatible

On Tue, 18 Mar 2025 17:05:24 +0530, Jayesh Choudhary wrote:
> For 'ti,j7200-cpb-audio' compatible, there is support for only one PLL for
> 48k. For 11025, 22050, 44100 and 88200 sampling rates, due to absence of
> J721E_CLK_PARENT_44100, we get EINVAL while running any audio application.
> Add support for these rates by using the 48k parent clock and adjusting
> the clock for these rates later in j721e_configure_refclk.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: ti: j721e-evm: Fix clock configuration for ti,j7200-cpb-audio compatible
      commit: 45ff65e30deb919604e68faed156ad96ce7474d9

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