- Sep 23, 2021
-
-
Robert Nelson authored
5.10.59-ti-arm64-r9 bb.org_defconfig 5.10 TI Delta: https://github.com/RobertCNelson/ti-linux-kernel/compare/18d726513306c676055b634d1e6bfea6a2ac3699...8128da9522b896b4908546f5e0b69967381d3d41 BBDTBS: https://github.com/beagleboard/BeagleBoard-DeviceTrees/commit/a6c2cffd56515e65f2068491ae520f52302ed5d8 WIRELESS_REGDB: https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/commit/?id=47007d0169c4c6c855a3fc5333c142489a43e89e Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
-
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Reference: v5.14.7 Signed-off-by: -
Robert Nelson authored
This reverts commit 956b200a . Signed-off-by:
-
Robert Nelson authored
Signed-off-by: -
-
-
LCPD Auto Merger authored
TI-Feature: connectivity TI-Branch: connectivity-ti-linux-5.10.y * 'connectivity-ti-linux-5.10.y' of ssh://bitbucket.itg.ti.com/lcpdpublicdom/connectivity : (41 commits) arm64: dts: ti: k3-j721e: Update compatible for DPHY phy: cdns-dphy: Add common module reset to DPHY RX phy: dt-bindings: cdns-dphy: Add j721e-dphy compatible media: i2c: ov5647: use pm_runtime_resume_and_get() media: ov5647: Remove 640x480 SBGGR8 mode media: ov5647: Support VIDIOC_SUBSCRIBE_EVENT media: ov5647: Constify oe_enable/disable reglist media: ov5647: Apply controls only when powered media: ov5647: Rework s_stream() operation media: ov5647: Use pm_runtime infrastructure media: ov5647: Advertise the correct exposure range media: ov5647: Support V4L2_CID_VBLANK control media: ov5647: Support V4L2_CID_HBLANK control media: ov5647: Support V4L2_CID_PIXEL_RATE media: ov5647: Set V4L2_SUBDEV_FL_HAS_EVENTS flag media: ov5647: Implement set_fmt pad operation media: ov5647: Use SBGGR10_1X10 640x480 as default media: ov5647: Add SGGBR10_1X10 modes media: ov5647: Rename SBGGR8 VGA mode media: ov5647: Add support for get_selection() ... Signed-off-by:
LCPD Auto Merger <lcpd_integration@list.ti.com>
-
Add the j721e specific compatible to DPHY node. Signed-off-by:
Sinthu Raja <sinthu.raja@ti.com> Signed-off-by:
Vignesh Raghavendra <vigneshr@ti.com> Reviewed-by:
Pratyush Yadav <p.yadav@ti.com>
-
DPHY RX module has a common module reset (RSTB_CMN) among four different other resets. The module expects all four resets to be released in a specific order. In TI J721E SR1.0 the RSTB_CMN is internally tied to CSI_RX_RST which is hardware controlled, so no explicit control from software is required to reset the DPHY RX module. With J721E SR2.0 the RSTB_CMN is separated out of the hardware controlled and tied to a MMR bit of the DPHY RX module. An explicit write to control the common module reset from software is required. Update DPHY_RX configure function to release the common module reset. Currently this feature is specific to TI J721E SR2.0 therefore add a compatible string and introduce a driver quirk to release the reset and set it for J721E SR2.0. Signed-off-by:
-
Document the j721e compatible for cdns-dphy. Signed-off-by:
-
commit 5187df40 upstream. Commit dd8088d5 ("PM: runtime: Add pm_runtime_resume_and_get to deal with usage counter") added pm_runtime_resume_and_get() in order to automatically handle dev->power.usage_count decrement on errors. Use the new API, in order to cleanup the error check logic. (cherry picked from commit 5187df40 ) Signed-off-by:
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Signed-off-by:
Nishanth Menon <nm@ti.com> Signed-off-by:
Jacopo Mondi <jacopo@jmondi.org> Acked-by:
-
commit 38c22308 upstream. Capturing in 640x480 SBGGR8_1X8 hangs the system when capturing with the unicam driver on RaspberryPi 4 platform. Remove it and remove the support for multiple media bus codes in the driver. (cherry picked from commit 38c22308 ) Signed-off-by:
Sakari Ailus <sakari.ailus@linux.intel.com> Signed-off-by:
-
commit dc337308 upstream. The driver reports the V4L2_SUBDEV_FL_HAS_EVENTS flag but does not support subscribing and unsubscribing to events. (cherry picked from commit dc337308 ) Signed-off-by:
-
commit d0744070 upstream. Make the two register-value lists const. (cherry picked from commit d0744070 ) Signed-off-by:
-
commit 4eec1919 upstream. Use pm_runtime_get_if_in_use() in s_ctrl to apply controls only when the device is powered on. Rework the control set function to balance the pm_runtime_get_if_in_use() call with pm_runtime_put() at the end of the function. (cherry picked from commit 4eec1919 ) Signed-off-by:
-
commit 2f038c97 upstream. Rework the s_stream() operation to turn the sensor on and off at stream enable/disable time using the pm_runtime infrastructure. Protect the stream on/off from being called multiple times in sequence with a 'streaming' flag. (cherry picked from commit 2f038c97 ) Signed-off-by:
-
commit 089b7c70 upstream. Use the pm_runtime framework to replace the legacy s_power() operation. (cherry picked from commit 089b7c70 ) Signed-off-by:
-
commit 646a0249 upstream. Exposure is clipped by the VTS of the mode, so it needs to be updated when this is changed. (cherry picked from commit 646a0249 ) Signed-off-by:
Dave Stevenson <dave.stevenson@raspberrypi.com> Signed-off-by:
-
commit 2512c064 upstream. Adds vblank control to allow for frame rate control. (cherry picked from commit 2512c064 ) Signed-off-by:
-
commit c6da1ae4 upstream. Add support for the V4L2_CID_HBLANK read-only control. The implementation has been upported from RaspberryPi BSP commit: commit d82f202156605 ("media: i2c: ov5647: Set V4L2_SUBDEV_FL_HAS_EVENTS flag") (cherry picked from commit c6da1ae4 ) Signed-off-by:
-
commit 911f4516 upstream. Clients need to know the pixel rate in order to compute exposure and frame rate values. Advertise it. (cherry picked from commit 911f4516 ) [nm@ti.com: Fixups] Signed-off-by:
-
commit 7ef761a0 upstream. The ov5647 subdev can generate control events, therefore set the V4L2_SUBDEV_FL_HAS_EVENTS flag. (cherry picked from commit 7ef761a0 ) Signed-off-by:
-
commit 6869e971 upstream. Now that the driver supports more than a single mode, implement the .set_fmt pad operation and adjust the existing .get_fmt one to report the currently applied format. (cherry picked from commit 6869e971 ) [nm@ti.com: fixup reorder] Signed-off-by:
-
commit 87576ac6 upstream. The SBGGR10_1X10 formats support more resolutions than SBGGR8_1X8. Make it the default sensor format and set 2x2 binned 640x480 resolution as default sensor size as it maximizes the FOV and framerate. (cherry picked from commit 87576ac6 ) Signed-off-by:
-
commit a8df5af6 upstream. Add 4 additional sensor modes in SBGGR10_1X10 format. Add the following resolutions: - 2592x1944 full resolution - 1920x1080 1080p cropped - 1296x972 2x2 binned - 640x480 2x2 binned, 2x2 subsampled The register lists and modes definition have been upported from the RaspberryPi BSP at revision: commit 581dfda6d0a62 ("media: i2c: ov5647: Advertise the correct exposure range") (cherry picked from commit a8df5af6 ) Signed-off-by:
-
commit e907bd66 upstream. Before adding new modes, rename the only existing one to report the bit depth to distinguish it from future additions. While at it, briefly describe the mode. (cherry picked from commit e907bd66 ) Signed-off-by:
-
commit 14f70a32 upstream. Support the get_selection() pad operation to report the device full pixel array size, the currently applied analogue crop rectangle and the active pixel array dimensions. (cherry picked from commit 14f70a32 ) [nm@ti.com: fixup re-ordering] Signed-off-by:
-
commit d7d6074e upstream. Break format handling out from the main driver structure. This commit prepares for the introduction of more sensor formats and resolutions by instrumenting the existing operation to work on multiple modes instead of assuming a single supported one. (cherry picked from commit d7d6074e ) Signed-off-by:
-
commit 5bc5ca71 upstream. The driver structure name is referred to with different names ('ov5647', 'state', 'sensor') in different functions in the driver. Polish this up by using 'struct ov5647 *sensor' everywhere. (cherry picked from commit 5bc5ca71 ) Signed-off-by:
-
commit 4974c2f1 upstream. Add controls to support AWB, AEC and AGC. Also add control support to set exposure (in lines) and analogue gain (as a register code). (cherry picked from commit 4974c2f1 ) Signed-off-by:
David Plowman <david.plowman@raspberrypi.com> Signed-off-by:
Naushir Patuck <naush@raspberrypi.com> Signed-off-by:
-
commit ab614f27 upstream. Use the driver mutex to protect s_stream() operations. This will become more relevant once the sensor will support more formats and set_format() could be issue concurrently to s_stream(). (cherry picked from commit ab614f27 ) Signed-off-by:
-
commit 464090c0 upstream. Implement the .enum_frame_size subdev pad operation. As the driver only supports one format and one resolution at the moment the implementation is trivial. (cherry picked from commit 464090c0 ) Signed-off-by:
-
commit f7a70f9a upstream. Rename __sensor_init() function to ov5647_set_mode() as the function is a regular one and the double underscores prefix shall be removed, and then move it to program the mode at s_stream(1) time, not at sensor power up. Break out from __sensor_init() the stream_off() operation call at sensor power up to coax the lanes in LP-11 state. (cherry picked from commit f7a70f9a ) Signed-off-by:
-
commit 2b18cbcf upstream. The ov5647_read()/ov5647_write() return in case of success the number of bytes read or written respectively. This requires callers to check if the return value is less than zero to detect an error. Unfortunately, in several places, callers directly return the result of a read/write call, causing issues when the returned valued is checked to be different from zero to detect an error. Fix this by returning zero if i2c_master_send() and i2c_master_read() return a positive value (the number of bytes written or read). (cherry picked from commit 2b18cbcf ) Signed-off-by:
-
commit 24169a5a upstream. Replace the boilerplate license text with the SPDX identifier. (cherry picked from commit 24169a5a ) Signed-off-by:
-
commit c9a05cec upstream. The driver has some obvious style issues which are worth fixing before expanding the driver capabilities. Fix: - Variable declaration order - Function parameters alignment - Multi-line comments and spurious line breaks - Use lowercase for hexadecimal values - > 80 cols lines Cosmetic change, no functional changes intended. (cherry picked from commit c9a05cec ) [nm@ti.com: fixups] Signed-off-by:
-
commit 7a482630 upstream. The driver currently support a single format. Fix its initialization to use the only supported resolution. (cherry picked from commit 7a482630 ) Signed-off-by:
-
