mbox series

[v2,0/4] arm64: dts: ti: Enable camera for SK-AM62P

Message ID 20240220-am62p_csi-v2-0-3e71d9945571@ti.com
Headers
Series arm64: dts: ti: Enable camera for SK-AM62P |

Message

Jai Luthra Feb. 20, 2024, 6:18 a.m. UTC 
  This series enables support for camera sensors using CSI-RX ports on
AM62P family of SoCs.

Particularly, it enables OV5640 and IMX219 sensors via the 22-pin FFC
CSI-RX connector on SK-AM62P [1] using the existing common overlays for
SK-AM62* family of boards.

Capture test:
https://gist.github.com/jailuthra/11f3383ccc0902b9db90d806222597a3

[1]: https://www.ti.com/tool/SK-AM62P-LP

Signed-off-by: Jai Luthra <j-luthra@ti.com>
---
Changes in v2:
- Rebase on top of ti-k3-dts-next
- Fix commit description of PATCH 3/4 to specify we are keeping the nodes
  disabled
- Link to v1: https://lore.kernel.org/r/20240201-am62p_csi-v1-0-c83bb9eaeb49@ti.com

Range-diff from v1:

1:  646c0b26cee4 ! 1:  61c395edcfd3 arm64: dts: ti: k3-am62p: Fix memory ranges for DMSS
    @@ Commit message
         to enable programming the interrupts correctly.

         Fixes: 29075cc09f43 ("arm64: dts: ti: Introduce AM62P5 family of SoCs")
    +    Reviewed-by: Vaishnav Achath <vaishnav.a@ti.com>
         Signed-off-by: Jai Luthra <j-luthra@ti.com>

      ## arch/arm64/boot/dts/ti/k3-am62p.dtsi ##
2:  5d6c41db44e3 ! 2:  2720ce668bf9 arm64: dts: ti: k3-am62p: Add DMASS1 for CSI
    @@ Commit message
         On AM62P, CSI-RX uses a dedicated BCDMA instance (DMASS1) for
         transferring captured camera frames to DDR, so enable it.

    +    Reviewed-by: Vaishnav Achath <vaishnav.a@ti.com>
         Signed-off-by: Jai Luthra <j-luthra@ti.com>

      ## arch/arm64/boot/dts/ti/k3-am62p-main.dtsi ##
3:  2896237c1ad1 ! 3:  9853acf0bc6f arm64: dts: ti: k3-am62p: Add nodes for CSI-RX
    @@ Commit message

         AM62P supports image capture via the MIPI CSI-2 protocol, it uses three
         IPs to achieve this: Cadence DPHY, Cadence CSI-RX, and TI's pixelgrabber
    -    wrapper on top. Enable all of these IPs in the devicetree.
    +    wrapper on top. Add nodes for these IPs in the devicetree, and keep them
    +    disabled here, so these may be enabled by the sensor overlays.

    +    Reviewed-by: Vaishnav Achath <vaishnav.a@ti.com>
         Signed-off-by: Jai Luthra <j-luthra@ti.com>

      ## arch/arm64/boot/dts/ti/k3-am62p-main.dtsi ##
4:  7a82f73e345d < -:  ------------ arm64: dts: ti: Enable overlays for SK-AM62P
-:  ------------ > 4:  1a5e859dec12 arm64: dts: ti: Enable overlays for SK-AM62P

---
Jai Luthra (4):
      arm64: dts: ti: k3-am62p: Fix memory ranges for DMSS
      arm64: dts: ti: k3-am62p: Add DMASS1 for CSI
      arm64: dts: ti: k3-am62p: Add nodes for CSI-RX
      arm64: dts: ti: Enable overlays for SK-AM62P

 arch/arm64/boot/dts/ti/Makefile           | 10 ++++
 arch/arm64/boot/dts/ti/k3-am62p-main.dtsi | 98 +++++++++++++++++++++++++++++++
 arch/arm64/boot/dts/ti/k3-am62p.dtsi      |  2 +-
 3 files changed, 109 insertions(+), 1 deletion(-)
---
base-commit: 0f9eb43f009091501dd0c68232aa6530ba0e0185
change-id: 20240201-am62p_csi-b69d172406ca

Best regards,

Comments

Vignesh Raghavendra Feb. 22, 2024, 1:22 p.m. UTC | #1 
Hi Jai Luthra,

On Tue, 20 Feb 2024 11:48:01 +0530, Jai Luthra wrote:
> This series enables support for camera sensors using CSI-RX ports on
> AM62P family of SoCs.
> 
> Particularly, it enables OV5640 and IMX219 sensors via the 22-pin FFC
> CSI-RX connector on SK-AM62P [1] using the existing common overlays for
> SK-AM62* family of boards.
> 
> [...]

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

[1/4] arm64: dts: ti: k3-am62p: Fix memory ranges for DMSS
      commit: 90a67583171f213711de662fab9f8d24a2d291a9
[2/4] arm64: dts: ti: k3-am62p: Add DMASS1 for CSI
      commit: 091e2e05228fa3fd424b1d775b04fb4734d5275b
[3/4] arm64: dts: ti: k3-am62p: Add nodes for CSI-RX
      commit: a8787f4fd29a43c5351daf3059a6156ff089a441
[4/4] arm64: dts: ti: Enable overlays for SK-AM62P
      commit: 598139b8c7c56cc6fb30ef8b4cf34b53a7fa5d0f

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