linux-kernel - Re: [PATCH v3 0/2] Enable audio support for J722S-EVM

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: <171984950181.3152309.14393845920250640127.b4-ty@ti.com>
Date: Thu, 4 Jul 2024 13:25:42 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <linux-kernel@...r.kernel.org>, <nm@...com>, <j-luthra@...com>,
        Jayesh
 Choudhary <j-choudhary@...com>
CC: Vignesh Raghavendra <vigneshr@...com>, <kristo@...nel.org>,
        <robh@...nel.org>, <krzk+dt@...nel.org>, <conor+dt@...nel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <u-kumar1@...com>
Subject: Re: [PATCH v3 0/2] Enable audio support for J722S-EVM

Hi Jayesh Choudhary,

On Tue, 25 Jun 2024 17:02:59 +0530, Jayesh Choudhary wrote:
> These 2 patches enable audio on J722S-EVM platform.
> 
> This patch depends upon the bcdma driver fix posted upstream:
> <https://lore.kernel.org/all/20240607-bcdma_chan_cnt-v2-1-bf1a55529d91@ti.com/>
> 
> Changelog v2->v3:
> - Move audio_refclk1 node to SOC level dtsi (k3-j722s-main.dtsi)
>   in a separate patch
> - Rename vcc_3v3_aud to vsys_io_3v3
> - Fix ball number for McASP pins in comments
> - Fix padding for audio_ext_refclk1_pins_default pinmux
> - Pick up R-by from Jai
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/2] arm64: dts: ti: k3-j722s-main: Add audio_refclk node
      commit: a5cd7067e45c33907afe20c0d1ab5e75b09a1ee2
[2/2] arm64: dts: ti: k3-j722s-evm: Enable analog audio support
      commit: 3a36c535dfd279ff093cc9271f474a99531bea21

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant 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.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh