You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Removing the direct references to AM62A and replacing them with common
macros.
Also updating differences between AEN and 62a. There are not many since it
is the same IP and same clock configuration for both platforms. All latency
numbers and performance metrics are common between the two.
Signed-off-by: Brandon Brnich <[email protected]>
Copy file name to clipboardExpand all lines: source/linux/Foundational_Components/Kernel/Kernel_Drivers/E5010_JPEG_Encoder.rst
+43-19Lines changed: 43 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,5 @@
1
+
.. include:: /_replacevars.rst
2
+
1
3
******************
2
4
E5010 JPEG Encoder
3
5
******************
@@ -102,8 +104,8 @@ of video encoding based use-cases utilizing this driver as demonstrated in below
102
104
103
105
Building the driver
104
106
===================
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:
107
109
108
110
.. code-block:: kconfig
109
111
@@ -172,22 +174,44 @@ Due to runtime power management feature, when JPEG encoder
172
174
is not being used by any of the applications, it stays in suspended
173
175
state and same can be verified using k3conf utility as shown below :
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
379
403
with this clocking is as below :
380
404
381
405
+-------------------+--------------------+
@@ -389,7 +413,7 @@ with this clocking is as below :
389
413
With these numbers theoretically E5010 core can handle 3840x2160@60fps equivalent load
390
414
for 4:2:2 video formats and 3840x2160@75fps equivalent load for 4:2:0 video formats.
391
415
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 :
0 commit comments