nvidia-tegra-modules.git/include/media/csi.h, branch rtss22-ae NVIDIA's kernel modules to support tegra chips (used in Jetson boards) media:platform:tegra: Use lp_bypass_mode from DT 2019-03-21T14:58:40+00:00 snchen snchen@nvidia.com 2019-02-19T08:05:11+00:00 979ee246cff38308f1d3738568d0600e931c590f Apply the lp_bypass_mode from device tree instead of hard code as 1 bug 2506207 Change-Id: I5402fd7ac047ed369e69be9b726a2a2fd1dd1318 Signed-off-by: snchen <snchen@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/2022704 Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> Reviewed-by: Frank Chen <frankc@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Apply the lp_bypass_mode from device tree instead of hard code as 1

bug 2506207

Change-Id: I5402fd7ac047ed369e69be9b726a2a2fd1dd1318
Signed-off-by: snchen <snchen@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/2022704
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
Reviewed-by: Frank Chen <frankc@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
media: camera: csi: distinguish port and stream 2018-10-23T08:30:29+00:00 Vincent Chung vincentc@nvidia.com 2018-10-07T20:51:52+00:00 8f91d4798354c0da3ad6a2ff8ba0d9d37ed73549 Interpret the device tree nvcsi port-index as the csi_port, as opposed to the stream_id, since t19x nvcsi no longer has 1:1 mapping. Adds port g/h for t19x. Also rename variables and remove tegra_csi_port_num enum to avoid confusion; the enum label is meaningless, it is used for indexing the gang-mode port, not the csi_port. Bug 2412116 Bug 1996720 Change-Id: I2540d536c419d4199106da1ff6c3e461311adff2 Signed-off-by: Vincent Chung <vincentc@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1921139 (cherry picked from commit 0f9314e2658ecf2bfc31b302d90fb57f6246a946) Reviewed-on: https://git-master.nvidia.com/r/1932854 Reviewed-by: David Bang <dbang@nvidia.com> Reviewed-by: Bhanu Murthy V <bmurthyv@nvidia.com> Reviewed-by: Automatic_Commit_Validation_User GVS: Gerrit_Virtual_Submit Reviewed-by: Frank Chen <frankc@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Interpret the device tree nvcsi port-index as the csi_port, as opposed
to the stream_id, since t19x nvcsi no longer has 1:1 mapping. Adds
port g/h for t19x.

Also rename variables and remove tegra_csi_port_num enum to avoid
confusion; the enum label is meaningless, it is used for indexing the
gang-mode port, not the csi_port.

Bug 2412116
Bug 1996720

Change-Id: I2540d536c419d4199106da1ff6c3e461311adff2
Signed-off-by: Vincent Chung <vincentc@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1921139
(cherry picked from commit 0f9314e2658ecf2bfc31b302d90fb57f6246a946)
Reviewed-on: https://git-master.nvidia.com/r/1932854
Reviewed-by: David Bang <dbang@nvidia.com>
Reviewed-by: Bhanu Murthy V <bmurthyv@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Frank Chen <frankc@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
media: tegra: camera: add VC support 2018-05-13T03:00:17+00:00 Ruicheng Dai rdai@nvidia.com 2017-12-11T10:51:11+00:00 aaa65f73dc90b76db346288d5237a83af5b0246b add virtual channel support to t19x Bug 1947553 Change-Id: I59286411ecd49cb2882c56f58e7cf8f4765cd8ab Signed-off-by: Ruicheng Dai <rdai@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1656669 Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Vincent Chung <vincentc@nvidia.com> Reviewed-by: Jon Mayo <jmayo@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
add virtual channel support to t19x

Bug 1947553

Change-Id: I59286411ecd49cb2882c56f58e7cf8f4765cd8ab
Signed-off-by: Ruicheng Dai <rdai@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1656669
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Vincent Chung <vincentc@nvidia.com>
Reviewed-by: Jon Mayo <jmayo@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
drivers: csi5_fops fix mipi_clock_rate val 2018-04-27T00:56:08+00:00 David Bang dbang@nvidia.com 2018-02-07T00:18:52+00:00 75f08ce54cfcfb9ab4bd41023617241e401b3f7a Use the sensor clk rate instead of hardcoded value for mipi_clock_rate Jira CRTC-1558 Change-Id: I61df85fb17722dfc5e1061ce28b4cbb041d85b09 Signed-off-by: David Bang <dbang@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1653068 Reviewed-by: Vincent Chung <vincentc@nvidia.com> Reviewed-by: Bhushan Rayrikar <brayrikar@nvidia.com> Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Frank Chen <frankc@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Use the sensor clk rate instead of hardcoded value
for mipi_clock_rate

Jira CRTC-1558

Change-Id: I61df85fb17722dfc5e1061ce28b4cbb041d85b09
Signed-off-by: David Bang <dbang@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1653068
Reviewed-by: Vincent Chung <vincentc@nvidia.com>
Reviewed-by: Bhushan Rayrikar <brayrikar@nvidia.com>
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Frank Chen <frankc@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
drivers: camera: CPHY calibration support 2018-01-27T07:46:19+00:00 Bhanu Murthy V bmurthyv@nvidia.com 2018-01-12T02:41:39+00:00 033935acd9b1be2f71b2dd980e38d00e13ad29b2 Add proper phy mode read support from device tree to distinguish CPHY and DPHY sensor modes. Fix CPHY calibration flow to write CPHY mode and complete calibration. Bug 1946718 Change-Id: I801965207a6777aa71cc5fc24fcb0a7e0c487093 Signed-off-by: Bhanu Murthy V <bmurthyv@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1639635 Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
Add proper phy mode read support from device tree
to distinguish CPHY and DPHY sensor modes.
Fix CPHY calibration flow to write CPHY mode
and complete calibration.

Bug 1946718

Change-Id: I801965207a6777aa71cc5fc24fcb0a7e0c487093
Signed-off-by: Bhanu Murthy V <bmurthyv@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1639635
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
drivers: camera: Fix calibration for CSI2 2017-10-10T23:26:51+00:00 Bhanu Murthy V bmurthyv@nvidia.com 2017-09-21T18:56:53+00:00 1920764d68eac39cbd7304ec208b085a9930137a CSI2 mipi lanes calibration is driven by sensor state. As soon as the mipi pad is powered on the sensor is also powered/streamed to reach the standby state for performing the calibration during the initialization sequence of CSI2 HW. Address issues with loadable sensor modules, calibration will be performed only when the sensor is bound. Bug 200324656 Change-Id: Ia9b2ec15c48bfe39cb78bd9651c2574705b743a3 Signed-off-by: Bhanu Murthy V <bmurthyv@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1565678 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> Reviewed-by: svccoveritychecker <svccoveritychecker@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Frank Chen <frankc@nvidia.com> Reviewed-by: Josh Kergan <jkergan@nvidia.com> Reviewed-by: Jihoon Bang <jbang@nvidia.com> 
CSI2 mipi lanes calibration is driven by sensor
state. As soon as the mipi pad is powered on the
sensor is also powered/streamed to reach the standby
state for performing the calibration during the
initialization sequence of CSI2 HW.
Address issues with loadable sensor modules, calibration
will be performed only when the sensor is bound.

Bug 200324656

Change-Id: Ia9b2ec15c48bfe39cb78bd9651c2574705b743a3
Signed-off-by: Bhanu Murthy V <bmurthyv@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1565678
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
Reviewed-by: svccoveritychecker <svccoveritychecker@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Frank Chen <frankc@nvidia.com>
Reviewed-by: Josh Kergan <jkergan@nvidia.com>
Reviewed-by: Jihoon Bang <jbang@nvidia.com>
media:platform:tegra: Use cil_settletime from DT 2017-09-25T18:31:57+00:00 Josh Kergan jkergan@nvidia.com 2017-09-08T22:16:20+00:00 e34aa2bb41a47c82266feefed207f317c63cf32e At the V4L2 level, we were ignoring the sensor device tree node's cil_settletime property, and using some default (DEFAULT_THS_SETTLE) which does not work for all sensors. The cil_settletime sensor property is parsed from the sensor's device tree node and stored in a struct camera_common_data. Weirdly, struct tegra_csi_channel has a pointer to struct camera_common_data (s_data) that's completely unused. This patch assumes that the intent of this pointer is for the tegra_csi_channel to be able to get at the sensor properties. After parsing the sensor properties, we traverse the device tree to get at the csi node on which this sensor is attached, and connect the two via tegra_csi_channel's s_data pointer. Also, if cil_settletime is 0, autocalculate the value rather than using a hardcoded default. Bug 1982959 Bug 1885366 Bug 1981695 Change-Id: I824f42995862512d3fea7d7aeeb42816fe33cd73 Signed-off-by: Josh Kergan <jkergan@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1565592 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: Bhanu Murthy V <bmurthyv@nvidia.com> Reviewed-by: svccoveritychecker <svccoveritychecker@nvidia.com> Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Jihoon Bang <jbang@nvidia.com> 
At the V4L2 level, we were ignoring the sensor device tree node's
cil_settletime property, and using some default (DEFAULT_THS_SETTLE) which
does not work for all sensors.

The cil_settletime sensor property is parsed from the sensor's device tree
node and stored in a struct camera_common_data.

Weirdly, struct tegra_csi_channel has a pointer to struct
camera_common_data (s_data) that's completely unused.  This patch assumes
that the intent of this pointer is for the tegra_csi_channel to be able to
get at the sensor properties.  After parsing the sensor properties, we
traverse the device tree to get at the csi node on which this sensor is
attached, and connect the two via tegra_csi_channel's s_data pointer.

Also, if cil_settletime is 0, autocalculate the value rather than using a
hardcoded default.

Bug 1982959
Bug 1885366
Bug 1981695

Change-Id: I824f42995862512d3fea7d7aeeb42816fe33cd73
Signed-off-by: Josh Kergan <jkergan@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1565592
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Bhanu Murthy V <bmurthyv@nvidia.com>
Reviewed-by: svccoveritychecker <svccoveritychecker@nvidia.com>
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Jihoon Bang <jbang@nvidia.com>
Revert "media:platform:tegra: Use cil_settletime from DT" 2017-09-19T14:49:45+00:00 Konsta Holtta kholtta@nvidia.com 2017-09-19T10:16:54+00:00 f613f7f0865822df5a2d75b674570e90e7dd792f This reverts commit 2f6f384827c28101d2b854296797cdb9d5ac0e5b. Bug 1982959 Bug 1885366 Bug 1981695 Bug 1992830 Change-Id: I3372067ff778f7ea5d947fbcc69e6d08fe29c2a1 Signed-off-by: Konsta Holtta <kholtta@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1563322 
This reverts commit 2f6f384827c28101d2b854296797cdb9d5ac0e5b.

Bug 1982959
Bug 1885366
Bug 1981695
Bug 1992830

Change-Id: I3372067ff778f7ea5d947fbcc69e6d08fe29c2a1
Signed-off-by: Konsta Holtta <kholtta@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1563322
media:platform:tegra: Use cil_settletime from DT 2017-09-18T21:12:16+00:00 Josh Kergan jkergan@nvidia.com 2017-09-08T22:16:20+00:00 2f6f384827c28101d2b854296797cdb9d5ac0e5b At the V4L2 level, we were ignoring the sensor device tree node's cil_settletime property, and using some default (DEFAULT_THS_SETTLE) which does not work for all sensors. The cil_settletime sensor property is parsed from the sensor's device tree node and stored in a struct camera_common_data. Weirdly, struct tegra_csi_channel has a pointer to struct camera_common_data (s_data) that's completely unused. This patch assumes that the intent of this pointer is for the tegra_csi_channel to be able to get at the sensor properties. After parsing the sensor properties, we traverse the device tree to get at the csi node on which this sensor is attached, and connect the two via tegra_csi_channel's s_data pointer. Also, if cil_settletime is 0, autocalculate the value rather than using a hardcoded default. Bug 1982959 Bug 1885366 Bug 1981695 Change-Id: Ic340e984b20ac3c81d76ad5771c4df077c00f286 Signed-off-by: Josh Kergan <jkergan@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1554934 Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> 
At the V4L2 level, we were ignoring the sensor device tree node's
cil_settletime property, and using some default (DEFAULT_THS_SETTLE) which
does not work for all sensors.

The cil_settletime sensor property is parsed from the sensor's device tree
node and stored in a struct camera_common_data.

Weirdly, struct tegra_csi_channel has a pointer to struct
camera_common_data (s_data) that's completely unused.  This patch assumes
that the intent of this pointer is for the tegra_csi_channel to be able to
get at the sensor properties.  After parsing the sensor properties, we
traverse the device tree to get at the csi node on which this sensor is
attached, and connect the two via tegra_csi_channel's s_data pointer.

Also, if cil_settletime is 0, autocalculate the value rather than using a
hardcoded default.

Bug 1982959
Bug 1885366
Bug 1981695

Change-Id: Ic340e984b20ac3c81d76ad5771c4df077c00f286
Signed-off-by: Josh Kergan <jkergan@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1554934
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
drivers: camera: Fix Mipi Calibration sequence 2017-09-15T23:19:57+00:00 Bhanu Murthy V bmurthyv@nvidia.com 2017-09-15T00:18:34+00:00 12fe36d44b197e9ce0248cefc4d86dff8aa3ae1a MIPI calibration can happen irrespective of sensor state by keeping CSI CIL in reset state. This change adds calibration to complete when the CSI is powered ON and based on the sensor settings. By this approach the mipi lanes are calibrated and are ready as soon as sensor is turned ON. Bug 200324656 Change-Id: Ib2372b4fabeb7d7d3464e5b17ca2effaffac6eb8 Signed-off-by: Bhanu Murthy V <bmurthyv@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/1560331 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com> GVS: Gerrit_Virtual_Submit Reviewed-by: Jihoon Bang <jbang@nvidia.com> 
MIPI calibration can happen irrespective of
sensor state by keeping CSI CIL in reset
state. This change adds calibration to complete
when the CSI is powered ON and based on the sensor
settings. By this approach the mipi lanes are
calibrated and are ready as soon as sensor is
turned ON.

Bug 200324656

Change-Id: Ib2372b4fabeb7d7d3464e5b17ca2effaffac6eb8
Signed-off-by: Bhanu Murthy V <bmurthyv@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1560331
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Jihoon Bang <jbang@nvidia.com>