linux-kernel - Re: [PATCH v2 0/2] arm64: dts: ti: k3-j721s2/j784s4: Add CSI BCDMA nodes

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: <169764101786.299606.12584643376472033357.b4-ty@ti.com>
Date:   Wed, 18 Oct 2023 20:28:43 +0530
From:   Vignesh Raghavendra <vigneshr@...com>
To:     <nm@...com>, <kristo@...nel.org>, <robh+dt@...nel.org>,
        <krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        Vaishnav Achath <vaishnav.a@...com>
CC:     Vignesh Raghavendra <vigneshr@...com>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <u-kumar1@...com>, <j-choudhary@...com>
Subject: Re: [PATCH v2 0/2] arm64: dts: ti: k3-j721s2/j784s4: Add CSI BCDMA nodes

Hi Vaishnav Achath,

On Tue, 10 Oct 2023 16:47:21 +0530, Vaishnav Achath wrote:
> J721S2 and J784S4 have a dedicated BCDMA controller for
> Camera Serial Interface. Add the node for the DMA controllers
> and keep it disabled by default.
> 
> The BCDMA instances were enabled/disabled and tested:
> J721S2 : https://gist.github.com/vaishnavachath/4b9d7ec2ee1aad59a57d44cf28ed7eb0
> J784S4 : https://gist.github.com/vaishnavachath/f928e4566aa80c7f47e7ac3c1491d62e
> 
> [...]

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

[1/2] arm64: dts: ti: k3-j721s2-main: Add BCDMA instance for CSI2RX
      commit: 10c6c4db6283053e8ec20eef19eb77d4aeffed1a
[2/2] arm64: dts: ti: k3-j784s4-main: Add BCDMA instance for CSI2RX
      commit: 8b2e41833bd649086e32ac4c3a412d7ec80e8202

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