Skip to contentSkip to conversation

Enable E5010 JPEG encoder

PATCH In review Devarsh Thakkar 2 participants 4 messages Aug 26, 2024 – Aug 28, 2024

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

cover Enable E5010 JPEG encoder

This series adds support for E5010 JPEG encoder device-tree node for TI's AM62A SoC and enables it in defconfig.

Devarsh Thakkar (2):
arm64: dts: ti: k3-am62a : Add E5010 JPEG Encoder
arm64: defconfig: Enable E5010 JPEG Encoder

 arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 10 ++++++++++
 arch/arm64/boot/dts/ti/k3-am62a.dtsi      |  2 ++
 arch/arm64/configs/defconfig              |  1 +
 3 files changed, 13 insertions(+)
Signature · 1 line
2.39.1
#1 lore raw

PATCH 1/2 arm64: dts: ti: k3-am62a : Add E5010 JPEG Encoder

This adds node for E5010 JPEG Encoder which is a stateful JPEG Encoder present in AM62A SoC [1], supporting baseline encoding of semiplanar based YUV420 and YUV422 raw video formats to JPEG encoding, with resolutions supported from 64x64 to 8kx8k.

E5010 JPEG Encoder IP is present in main domain, so this also adds address range for core and mmu regions of E5010 IP in cbass_main node.

---
 arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 10 ++++++++++
 arch/arm64/boot/dts/ti/k3-am62a.dtsi      |  2 ++
 2 files changed, 12 insertions(+)
arch/arm64/boot/dts/ti/k3-am62a-main.dtsi +10 -0
index 916fcf3cc57d..63fd4030df79 100644
@@ -1088,4 +1088,14 @@ vpu: video-codec@30210000 {
 		clocks = <&k3_clks 204 2>;
 		power-domains = <&k3_pds 204 TI_SCI_PD_EXCLUSIVE>;
 	};
+
+	e5010: jpeg-encoder@fd20000 {
+		compatible = "ti,am62a-jpeg-enc", "img,e5010-jpeg-enc";
+		reg = <0x00 0xfd20000 0x00 0x100>,
+		      <0x00 0xfd20200 0x00 0x200>;
+		reg-names = "core", "mmu";
+		clocks = <&k3_clks 201 0>;
+		power-domains = <&k3_pds 201 TI_SCI_PD_EXCLUSIVE>;
+		interrupts = <GIC_SPI 98 IRQ_TYPE_LEVEL_HIGH>;
+	};
 };
arch/arm64/boot/dts/ti/k3-am62a.dtsi +2 -0
index b1b884600293..4d79b3e9486a 100644
@@ -61,6 +61,8 @@ cbass_main: bus@f0000 {
 			 <0x00 0x08000000 0x00 0x08000000 0x00 0x00200000>, /* Main CPSW */
 			 <0x00 0x0e000000 0x00 0x0e000000 0x00 0x01d20000>, /* Second peripheral window */
 			 <0x00 0x0fd00000 0x00 0x0fd00000 0x00 0x00020000>, /* GPU */
+			 <0x00 0x0fd20000 0x00 0x0fd20000 0x00 0x00000100>, /* JPEGENC0_CORE */
+			 <0x00 0x0fd20200 0x00 0x0fd20200 0x00 0x00000200>, /* JPEGENC0_CORE_MMU */
 			 <0x00 0x20000000 0x00 0x20000000 0x00 0x0a008000>, /* Third peripheral window */
 			 <0x00 0x30040000 0x00 0x30040000 0x00 0x00080000>, /* PRUSS-M */
 			 <0x00 0x30101000 0x00 0x30101000 0x00 0x00010100>, /* CSI window */
Signature · 1 line
2.39.1
#2 lore raw

PATCH 2/2 arm64: defconfig: Enable E5010 JPEG Encoder

In reply to Devarsh Thakkar

This enables E5010 JPEG Encoder which is a stateful JPEG Encoder present in TI's AM62A SoC [1] and supporting baseline encoding of semiplanar based YUV420 and YUV422 raw video formats to JPEG encoding, with resolutions supported from 64x64 to 8kx8k resolution.

---
 arch/arm64/configs/defconfig | 1 +
 1 file changed, 1 insertion(+)
arch/arm64/configs/defconfig +1 -0
index b9928342418f..067ba9d9406d 100644
@@ -823,6 +823,7 @@ CONFIG_VIDEO_CADENCE_CSI2RX=m
 CONFIG_VIDEO_MEDIATEK_JPEG=m
 CONFIG_VIDEO_MEDIATEK_VCODEC=m
 CONFIG_VIDEO_WAVE_VPU=m
+CONFIG_VIDEO_E5010_JPEG_ENC=m
 CONFIG_VIDEO_IMX7_CSI=m
 CONFIG_VIDEO_IMX_MIPI_CSIS=m
 CONFIG_VIDEO_IMX8_ISI=m
Signature · 1 line
2.39.1
maintainer
#3 lore raw
In reply to Devarsh Thakkar

Hi Devarsh Thakkar,

Quoted 8 lines · Devarsh Thakkar

This series adds support for E5010 JPEG encoder device-tree node for TI's AM62A SoC and enables it in defconfig.

Devarsh Thakkar (2):
arm64: dts: ti: k3-am62a : Add E5010 JPEG Encoder
arm64: defconfig: Enable E5010 JPEG Encoder

[...]

I have applied

Following to branch ti-k3-dts-next on [1].

[1/2] arm64: dts: ti: k3-am62a : Add E5010 JPEG Encoder

      commit: 540fcd5fbdb5f3bbd6f6a88d85b9993a9318d474

Following to branch ti-k3-config-next on [1]:

[2/2] arm64: defconfig: Enable E5010 JPEG Encoder

      commit: e8c643daeaa9040e18f8349993b9bc504e9d2117

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

Signature · 3 lines
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D