Skip to content

Commit 97e06df

Browse files
authored
Merge pull request #29 from b-brnich/master
E5010 Documentation Update
2 parents 0330678 + be16ff7 commit 97e06df

File tree

3 files changed

+45
-19
lines changed

3 files changed

+45
-19
lines changed

configs/AM67/AM67_linux_toc.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,7 @@ linux/Foundational_Components/Kernel/Kernel_Drivers/Audio
4545
linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX
4646
linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto
4747
linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7
48+
linux/Foundational_Components/Kernel/Kernel_Drivers/E5010_JPEG_Encoder
4849
linux/Foundational_Components/Kernel/Kernel_Drivers/GPIO
4950
linux/Foundational_Components/Kernel/Kernel_Drivers/I2C
5051
linux/Foundational_Components/Kernel/Kernel_Drivers/MCAN

configs/J722S/J722S_linux_toc.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,7 @@ linux/Foundational_Components/Kernel/Kernel_Drivers/Audio
4646
linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX
4747
linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto
4848
linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7
49+
linux/Foundational_Components/Kernel/Kernel_Drivers/E5010_JPEG_Encoder
4950
linux/Foundational_Components/Kernel/Kernel_Drivers/GPIO
5051
linux/Foundational_Components/Kernel/Kernel_Drivers/I2C
5152
linux/Foundational_Components/Kernel/Kernel_Drivers/MCAN

source/linux/Foundational_Components/Kernel/Kernel_Drivers/E5010_JPEG_Encoder.rst

Lines changed: 43 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
1+
.. include:: /_replacevars.rst
2+
13
******************
24
E5010 JPEG Encoder
35
******************
@@ -102,8 +104,8 @@ of video encoding based use-cases utilizing this driver as demonstrated in below
102104
103105
Building the driver
104106
===================
105-
The E5010 JPEG driver is already enabled as a kernel module in processor SDK 9.0 for AM62A in the default defconfig being used for the board.
106-
If using a separate defconfig, It can be enabled explicitly for compilation by setting corresponding Kconfig as shown below:
107+
The E5010 JPEG driver is already enabled as a kernel module on |__PART_FAMILY_DEVICE_NAMES__| as part of the default defconfig being used for the board.
108+
If using a separate defconfig, it can be enabled explicitly for compilation by setting corresponding Kconfig as shown below:
107109

108110
.. code-block:: kconfig
109111
@@ -172,22 +174,44 @@ Due to runtime power management feature, when JPEG encoder
172174
is not being used by any of the applications, it stays in suspended
173175
state and same can be verified using k3conf utility as shown below :
174176

175-
.. code-block:: console
177+
.. ifconfig:: CONFIG_part_variant in ('AM62AX')
178+
179+
.. code-block:: console
180+
181+
root@am62axx-evm:~# k3conf dump device 201
182+
|------------------------------------------------------------------------------|
183+
| VERSION INFO |
184+
|------------------------------------------------------------------------------|
185+
| K3CONF | (version 0.3-nogit built Thu Jul 25 14:13:02 UTC 2024) |
186+
| SoC | AM62Ax SR1.0 |
187+
| SYSFW | ABI: 4.0 (firmware version 0x000a '10.0.8--v10.00.08 (Fiery Fox))') |
188+
|------------------------------------------------------------------------------|
189+
190+
|---------------------------------------------------|
191+
| Device ID | Device Name | Device Status |
192+
|---------------------------------------------------|
193+
| 201 | AM62AX_DEV_JPGENC0 | DEVICE_STATE_OFF |
194+
|---------------------------------------------------|
195+
196+
.. ifconfig:: CONFIG_part_variant in ('J722S', 'AM67')
197+
198+
.. code-block:: console
199+
200+
root@j722s-evm-evm:~# k3conf dump device 201
201+
|------------------------------------------------------------------------------|
202+
| VERSION INFO |
203+
|------------------------------------------------------------------------------|
204+
| K3CONF | (version 0.3-nogit built Thu Jul 25 14:13:02 UTC 2024) |
205+
| SoC | J722S SR1.0 |
206+
| SYSFW | ABI: 4.0 (firmware version 0x000a '10.0.8--v10.00.08 (Fiery Fox))') |
207+
|------------------------------------------------------------------------------|
208+
209+
|---------------------------------------------------|
210+
| Device ID | Device Name | Device Status |
211+
|---------------------------------------------------|
212+
| 201 | J722S_DEV_JPGENC0 | DEVICE_STATE_OFF |
213+
|---------------------------------------------------|
176214
177-
root@am62axx-evm:~# k3conf dump device 201
178-
|------------------------------------------------------------------------------|
179-
| VERSION INFO |
180-
|------------------------------------------------------------------------------|
181-
| K3CONF | (version 0.3-nogit built Thu Jul 25 14:13:02 UTC 2024) |
182-
| SoC | AM62Ax SR1.0 |
183-
| SYSFW | ABI: 4.0 (firmware version 0x000a '10.0.8--v10.00.08 (Fiery Fox))') |
184-
|------------------------------------------------------------------------------|
185-
186-
|---------------------------------------------------|
187-
| Device ID | Device Name | Device Status |
188-
|---------------------------------------------------|
189-
| 201 | AM62AX_DEV_JPGENC0 | DEVICE_STATE_OFF |
190-
|---------------------------------------------------|
191215
192216
.. ifconfig:: CONFIG_part_variant in ('AM62AX')
193217

@@ -375,7 +399,7 @@ Buffer alignment requirements
375399

376400
Performance and Latency Benchmarking
377401
====================================
378-
The E5010 core is clocked at 250Mhz in AM62A and theoretical performance expectation
402+
The E5010 core is clocked at 250Mhz on |__PART_FAMILY_DEVICE_NAMES__| and theoretical performance expectation
379403
with this clocking is as below :
380404

381405
+-------------------+--------------------+
@@ -389,7 +413,7 @@ with this clocking is as below :
389413
With these numbers theoretically E5010 core can handle 3840x2160@60fps equivalent load
390414
for 4:2:2 video formats and 3840x2160@75fps equivalent load for 4:2:0 video formats.
391415

392-
This however requires the upstream element (for e.g. camera) to support above rates. On AM62A board fastest locally available upstream element source is `wave5 VPU decoder <../../../Foundational_Components_Multimedia_wave5.html>`__ which provides maximum performance of 3840x2160@59 fps with low bitrate files and we were able to achieve same performance after passing this decoded data to E5010 JPEG Encoder as shown in below example :
416+
This however requires the upstream element (for e.g. camera) to support above rates. On |__PART_FAMILY_DEVICE_NAMES__| board fastest locally available upstream element source is :ref:`wave5 VPU decoder <foundational-components-multimedia>` which provides maximum performance of 3840x2160@59 fps with low bitrate files and we were able to achieve same performance after passing this decoded data to E5010 JPEG Encoder as shown in below example :
393417

394418
.. code-block:: console
395419

0 commit comments

Comments
 (0)