linux-kernel - Re: [PATCH v2 1/4] arm64: dts: ti: k3-am62a: Enable AUDIO

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: <171984950182.3152309.13258458514527438759.b4-ty@ti.com>
Date: Wed, 3 Jul 2024 10:07:06 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <nm@...com>, <kristo@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
        <conor+dt@...nel.org>, <w.egorov@...tec.de>,
        Garrett Giordano
	<ggiordano@...tec.com>
CC: Vignesh Raghavendra <vigneshr@...com>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <upstream@...ts.phytec.de>
Subject: Re: [PATCH v2 1/4] arm64: dts: ti: k3-am62a: Enable AUDIO_REFCLKx

Hi Garrett Giordano,

On Wed, 26 Jun 2024 08:52:41 -0700, Garrett Giordano wrote:
> On AM62a SoCs the AUDIO_REFCLKx clocks can be used as an input to
> external peripherals when configured through CTRL_MMR, so add the
> clock nodes.
> 
> Based on: Link: https://lore.kernel.org/lkml/20230807202159.13095-2-francesco@dolcini.it/
> 
> 
> [...]

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

[1/4] arm64: dts: ti: k3-am62a: Enable AUDIO_REFCLKx
      commit: fe6a73eee30173695d3a56e30033d7bb1f4c79eb
[2/4] arm64: dts: ti: Add am62x-phyboard-lyra carrier board
      commit: f1b3adade0459a9a2d9fb0964f975e9541fb1ac9
[3/4] dt-bindings: arm: ti: Add bindings for PHYTEC AM62Ax based hardware
      commit: 567c373f441b29414157c00cfff09f1c60e83bf6
[4/4] arm64: dts: ti: Add basic support for phyBOARD-Lyra-AM62Ax
      commit: d69383885576954033b537c29c7d259f18e75293

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