nvidia-tegra-modules.git/include/media/mc_common.h, branch rtss22-ae NVIDIA's kernel modules to support tegra chips (used in Jetson boards) capture-vi: use separate ringbuffer to pass iova to rtcpu 2021-06-21T08:55:03+00:00 Kirill Artamonov kartamonov@nvidia.com 2021-06-15T00:11:28+00:00 6e262c637e5116e3057b73788c02358bafe2b725 Passing iova pointers using capture descriptor is not safe since usermode application can access them. Use additional ringbuffer shared between kernel and rtcpu to pass iova pointers securely. Related changes and bugfixes: Use permanent vmap mapping for VI capture descriptors. This should also improve performance and reduce fragmentation of kernel address space. Don't use relocs. Access descriptor like normal C structure. Remove unused parameter capture_data from tegra_channel to avoid confusing null pointer investigation when accidentally using it. Check for zero pin count at submit to avoid potential memory mapping leak which will happen if usermode submits same capture descriptor without waiting for completion. Reboot rtcpu if fail to communicate with rtcpu during channel release IVC call. Allocate fixed size unpin buffer at setup time istead of relying on kzalloc/kfree during each request. This is to simplify critical runtime codepath and remove flexible array struct member which is prohibited by MISRA C conventions. CAMASIL-7466 bug 2768992 bug 3231670 bug 200688288 bug 200690078 CAMASIL-7460 CAMASIL-7477 CAMASIL-4619 CAMASIL-7465 Change-Id: Ia39de887093bbc158c72008ae387287ce30ebd82 Signed-off-by: Kirill Artamonov <kartamonov@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2475799 (cherry picked from commit 71ad1f9d54a45e54767d5fa9411a4aee83374398) Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2545006 Reviewed-by: Igor Mitsyanko <imitsyanko@nvidia.com> Reviewed-by: Semi Malinen <smalinen@nvidia.com> Reviewed-by: Pekka Pessi <ppessi@nvidia.com> Reviewed-by: Mika Liljeberg <mliljeberg@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: Igor Mitsyanko <imitsyanko@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit 
Passing iova pointers using capture descriptor is not safe since
usermode application can access them.

Use additional ringbuffer shared between kernel and rtcpu to
pass iova pointers securely.

Related changes and bugfixes:

Use permanent vmap mapping for VI capture descriptors.
This should also improve performance and reduce fragmentation
of kernel address space.

Don't use relocs. Access descriptor like normal C structure.

Remove unused parameter capture_data from tegra_channel to
avoid confusing null pointer investigation when accidentally
using it.

Check for zero pin count at submit to avoid potential memory
mapping leak which will happen if usermode submits same capture
descriptor without waiting for completion.

Reboot rtcpu if fail to communicate with rtcpu during
channel release IVC call.

Allocate fixed size unpin buffer at setup time istead of
relying on kzalloc/kfree during each request. This is to simplify
critical runtime codepath and remove flexible array struct
member which is prohibited by MISRA C conventions.

CAMASIL-7466

bug 2768992
bug 3231670
bug 200688288
bug 200690078
CAMASIL-7460
CAMASIL-7477
CAMASIL-4619
CAMASIL-7465

Change-Id: Ia39de887093bbc158c72008ae387287ce30ebd82
Signed-off-by: Kirill Artamonov <kartamonov@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2475799
(cherry picked from commit 71ad1f9d54a45e54767d5fa9411a4aee83374398)
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2545006
Reviewed-by: Igor Mitsyanko <imitsyanko@nvidia.com>
Reviewed-by: Semi Malinen <smalinen@nvidia.com>
Reviewed-by: Pekka Pessi <ppessi@nvidia.com>
Reviewed-by: Mika Liljeberg <mliljeberg@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: Igor Mitsyanko <imitsyanko@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
drivers:media:vi5_fops add gang mode support 2021-01-22T15:38:58+00:00 arai arai@nvidia.com 2020-06-04T18:10:10+00:00 72c57f0e21570a90a2ccf9bc244ca0d62c5626dc add support for gang mode captures involving 8 CSI lanes Bug 2834674 Change-Id: I8f542312bb176be274ef0b6d447dd489086e62d1 Signed-off-by: arai <arai@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2355825 Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> Reviewed-by: Frank Chen <frankc@nvidia.com> Reviewed-by: Sudhir Vyas <svyas@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit 
add support for gang mode captures involving
8 CSI lanes

Bug 2834674

Change-Id: I8f542312bb176be274ef0b6d447dd489086e62d1
Signed-off-by: arai <arai@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2355825
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Reviewed-by: Frank Chen <frankc@nvidia.com>
Reviewed-by: Sudhir Vyas <svyas@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
media: tegra: camera: vi2: locking for vi recover 2020-03-13T16:15:22+00:00 Ken Chang kenc@nvidia.com 2019-04-02T07:05:18+00:00 e64de31e5d0be79486f3a6bbfd11965347037fe7 Introduce rwsem for the locking between vi/csi recover call and the capture thread to avoid vi/csi register accesses during vi reset. Bug 200486098 Change-Id: I9a6b643708bec9db739ecd1e0607fe56713b00fb Signed-off-by: Ken Chang <kenc@nvidia.com> (cherry picked from commit 04765fae230bc8f7c4ae6908c7f934a4056000ae) Reviewed-on: https://git-master.nvidia.com/r/2097524 (cherry picked from commit 8e4c60d8b7ff81b817226cad1a6fd82ffaeba623) (cherry picked from commit 0313cd0998849973041daa78f57917504cf669b6) Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2309291 Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: automaticguardword <automaticguardword@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Introduce rwsem for the locking between vi/csi recover call and
the capture thread to avoid vi/csi register accesses during vi
reset.

Bug 200486098

Change-Id: I9a6b643708bec9db739ecd1e0607fe56713b00fb
Signed-off-by: Ken Chang <kenc@nvidia.com>
(cherry picked from commit 04765fae230bc8f7c4ae6908c7f934a4056000ae)
Reviewed-on: https://git-master.nvidia.com/r/2097524
(cherry picked from commit 8e4c60d8b7ff81b817226cad1a6fd82ffaeba623)
(cherry picked from commit 0313cd0998849973041daa78f57917504cf669b6)
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2309291
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: automaticguardword <automaticguardword@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
tegra: camera: vi2: allow only two outstanding capture 2020-03-13T16:15:12+00:00 Ken Chang kenc@nvidia.com 2019-04-01T08:43:42+00:00 f3c2b98214e13813e1c872359a32f64678e21834 The syncpt fifo depth of VI_MW_ACK_DONE and VI_CSI_PP_FRAME_START is 2. So block the capture thread to wait until the programmed syncpt events are handled by the release thread. Bug 200486098 Change-Id: Iabf0b3a0a1a29e3736d7e8c3d10c6eea5b758681 Signed-off-by: Ken Chang <kenc@nvidia.com> (cherry picked from commit f622d4ee6ae33cdd85f4be9151e86a38dd97b10c) Reviewed-on: https://git-master.nvidia.com/r/2097523 (cherry picked from commit 2e4f1f721af37156cf6824d3604bc5eac698c24d) (cherry picked from commit dc212c8a26506731088495e3eb8d8b38b494a734) Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2309290 Reviewed-by: Bibek Basu <bbasu@nvidia.com> Reviewed-by: automaticguardword <automaticguardword@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
The syncpt fifo depth of VI_MW_ACK_DONE and VI_CSI_PP_FRAME_START
is 2. So block the capture thread to wait until the programmed syncpt
events are handled by the release thread.

Bug 200486098

Change-Id: Iabf0b3a0a1a29e3736d7e8c3d10c6eea5b758681
Signed-off-by: Ken Chang <kenc@nvidia.com>
(cherry picked from commit f622d4ee6ae33cdd85f4be9151e86a38dd97b10c)
Reviewed-on: https://git-master.nvidia.com/r/2097523
(cherry picked from commit 2e4f1f721af37156cf6824d3604bc5eac698c24d)
(cherry picked from commit dc212c8a26506731088495e3eb8d8b38b494a734)
Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2309290
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: automaticguardword <automaticguardword@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
GVS: Gerrit_Virtual_Submit
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
tegra: camera: add preferred stride controls 2019-12-09T12:54:43+00:00 Jerry Chang jerchang@nvidia.com 2019-11-25T09:16:41+00:00 66a98fe674c58418d80921d04ddc962cb5bddd8b add preferred stride cid control for stride adjustment Bug 2722149 Change-Id: Ifef54fc2e9410abd71fcf3e575c2fdfb68ff7ee8 Signed-off-by: Jerry Chang <jerchang@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/2246839 Reviewed-by: Automatic_Commit_Validation_User GVS: Gerrit_Virtual_Submit Reviewed-by: Frank Chen <frankc@nvidia.com> Reviewed-by: Joshua Widen <jwiden@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
add preferred stride cid control for stride adjustment

Bug 2722149

Change-Id: Ifef54fc2e9410abd71fcf3e575c2fdfb68ff7ee8
Signed-off-by: Jerry Chang <jerchang@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/2246839
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Frank Chen <frankc@nvidia.com>
Reviewed-by: Joshua Widen <jwiden@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
media: tegra: allocate video_device dynamically 2019-10-17T23:24:39+00:00 Ahung Cheng ahcheng@nvidia.com 2018-01-16T08:41:17+00:00 b0c4680557b92bef6a7c338b4f995ecf0483362c Using initialized static video_device for video_register_device during sensor re-bind will cause panic with following log. ----------- kobject (ffffffc0794d70c0): tried to init an initialized object, something is seriously wrong. ----------- Hence, modify vi driver to use dynamic video_device bug 2015230 bug 2719996 Change-Id: Ia7bfb5621e34b54a079c45b3f9aafeaa06407515 Reviewed-on: https://git-master.nvidia.com/r/1639229 Signed-off-by: Frank Chen <frankc@nvidia.com> (cherry picked from commit 39b1a64a8ee9e40cd4f1a99c2d936e3310e5e8b9) Reviewed-on: https://git-master.nvidia.com/r/2208308 GVS: Gerrit_Virtual_Submit Reviewed-by: Shan Neng Chen <snchen@nvidia.com> Reviewed-by: Sudhir Vyas <svyas@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Using initialized static video_device for video_register_device
during sensor re-bind will cause panic with following log.
-----------
kobject (ffffffc0794d70c0): tried to init an initialized object,
something is seriously wrong.
-----------
Hence, modify vi driver to use dynamic video_device

bug 2015230
bug 2719996

Change-Id: Ia7bfb5621e34b54a079c45b3f9aafeaa06407515
Reviewed-on: https://git-master.nvidia.com/r/1639229
Signed-off-by: Frank Chen <frankc@nvidia.com>
(cherry picked from commit 39b1a64a8ee9e40cd4f1a99c2d936e3310e5e8b9)
Reviewed-on: https://git-master.nvidia.com/r/2208308
GVS: Gerrit_Virtual_Submit
Reviewed-by: Shan Neng Chen <snchen@nvidia.com>
Reviewed-by: Sudhir Vyas <svyas@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
media: tegra: add notifier unbind 2019-10-17T23:24:30+00:00 Ahung Cheng ahcheng@nvidia.com 2018-01-12T07:29:45+00:00 b7dd1e66dcf16d88eefe59cbd680118d465fa884 Add notifier unbind to support sensor module removal and clean up subdev and video node. bug 2015230 bug 2719996 Change-Id: I701e06aa5f7e231368100dcde7198a3fdca09c8d Reviewed-on: https://git-master.nvidia.com/r/1637189 Signed-off-by: Frank Chen <frankc@nvidia.com> (cherry picked from commit f0103c38c3dc2c069c39b2d25cd7e5706eae927b) Reviewed-on: https://git-master.nvidia.com/r/2207584 Reviewed-by: Automatic_Commit_Validation_User GVS: Gerrit_Virtual_Submit Reviewed-by: Shan Neng Chen <snchen@nvidia.com> Reviewed-by: Jerry Chang <jerchang@nvidia.com> Reviewed-by: Sudhir Vyas <svyas@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Add notifier unbind to support sensor module removal
and clean up subdev and video node.

bug 2015230
bug 2719996

Change-Id: I701e06aa5f7e231368100dcde7198a3fdca09c8d
Reviewed-on: https://git-master.nvidia.com/r/1637189
Signed-off-by: Frank Chen <frankc@nvidia.com>
(cherry picked from commit f0103c38c3dc2c069c39b2d25cd7e5706eae927b)
Reviewed-on: https://git-master.nvidia.com/r/2207584
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Shan Neng Chen <snchen@nvidia.com>
Reviewed-by: Jerry Chang <jerchang@nvidia.com>
Reviewed-by: Sudhir Vyas <svyas@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
vi4: add interlace support 2019-09-25T22:40:37+00:00 Anubhav Rai arai@nvidia.com 2019-09-16T09:27:39+00:00 6a1120b750c7aee3ea09c488c9d6b2b9def11e06 Add interlaced yuv support for v4l2 framework in vi. It will support two interlaced modes top_bottom and interleaved. bug 200548055 bug 2672044 Change-Id: Ie9c435ac38ba2f2e534f7f4f3d1f21220a49c682 Signed-off-by: Anubhav Rai <arai@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/2198656 Reviewed-by: Automatic_Commit_Validation_User GVS: Gerrit_Virtual_Submit Reviewed-by: Sudhir Vyas <svyas@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Add interlaced yuv support for v4l2 framework
in vi. It will support two interlaced modes
top_bottom and interleaved.

bug 200548055
bug 2672044

Change-Id: Ie9c435ac38ba2f2e534f7f4f3d1f21220a49c682
Signed-off-by: Anubhav Rai <arai@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/2198656
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Sudhir Vyas <svyas@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
drivers: media: Align stride length 2019-05-07T18:48:11+00:00 Anubhav Rai arai@nvidia.com 2019-03-25T13:18:25+00:00 0e2c026217cc62b041ee8c7dc32e63a6cfac17f1 Add a memory alignment logic for strides/bytesperline as per vi2 registers description. bug 200490095 Change-Id: I72ab74f29c19dbb7eb470549357126cca6f52e5b Signed-off-by: Anubhav Rai <arai@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/2080909 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: Frank Chen <frankc@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Sudhir Vyas <svyas@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Add a memory alignment logic for strides/bytesperline
as per vi2 registers description.

bug 200490095

Change-Id: I72ab74f29c19dbb7eb470549357126cca6f52e5b
Signed-off-by: Anubhav Rai <arai@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/2080909
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Frank Chen <frankc@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Sudhir Vyas <svyas@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
drivers: camera: Add sensor blob arch in VI driver 2019-02-01T07:28:24+00:00 Bhanu Murthy V bmurthyv@nvidia.com 2018-11-01T20:38:11+00:00 29cd2401366040b4dc925f07fc02b7df2fc86fcf Support writing blobs in the V4L2 VI media controller driver when streaming starts only if the sensor driver version matches and support blob packaging. Support blob writing for all the socs. VI2 and VI4 will write blobs in CCPLEX and VI5 will move to writing blobs in firmware in follow up modifications. This is to ensure the common sensor driver across socs will not get overloaded with multiple feature support. Expose sensor configuration and blob contorls only from VI5 as this path will not be needed for past VI versions. Bug 2433156 Change-Id: I3a41ed6393b33e1f33622c1d38fa967031578179 Signed-off-by: Bhanu Murthy V <bmurthyv@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1941464 (cherry picked from commit f3bf3d77cea9d7b533dfea8c203f7dc715f94cf9) Reviewed-on: https://git-master.nvidia.com/r/2006766 Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Support writing blobs in the V4L2 VI media controller
driver when streaming starts only if the sensor driver
version matches and support blob packaging.
Support blob writing for all the socs. VI2 and VI4 will
write blobs in CCPLEX and VI5 will move to writing blobs
in firmware in follow up modifications.
This is to ensure the common sensor driver across socs
will not get overloaded with multiple feature support.
Expose sensor configuration and blob contorls only from
VI5 as this path will not be needed for past VI versions.

Bug 2433156

Change-Id: I3a41ed6393b33e1f33622c1d38fa967031578179
Signed-off-by: Bhanu Murthy V <bmurthyv@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1941464
(cherry picked from commit f3bf3d77cea9d7b533dfea8c203f7dc715f94cf9)
Reviewed-on: https://git-master.nvidia.com/r/2006766
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>