- 19 Jul, 2023 7 commits
-
-
Yu Zhe authored
Pointer variables of void * type do not require type cast. Signed-off-by:
Yu Zhe <yuzhe@nfschina.com> Signed-off-by:
Hans Verkuil <hverkuil-cisco@xs4all.nl>
-
Yu Zhe authored
Pointer variables of void * type do not require type cast. Signed-off-by:
-
Yu Zhe authored
Pointer variables of void * type do not require type cast. Signed-off-by:
-
Dongliang Mu authored
The previous commit 4b208f8b ("[media] siano: register media controller earlier")moves siano_media_device_register before smscore_register_device, and adds corresponding error handling code if smscore_register_device fails. However, it misses the following error handling code of smsusb_init_device. Fix this by moving error handling code at the end of smsusb_init_device and adding a goto statement in the following error handling parts. Fixes: 4b208f8b ("[media] siano: register media controller earlier") Signed-off-by:
Dongliang Mu <dzm91@hust.edu.cn> Signed-off-by:
-
Dong Chuanjian authored
remove unnecessary void* type casting. Signed-off-by:
Dong Chuanjian <chuanjian@nfschina.com> Signed-off-by:
-
ye xingchen authored
Follow the advice of the Documentation/filesystems/sysfs.rst and show() should only use sysfs_emit() or sysfs_emit_at() when formatting the value to be returned to user space. Signed-off-by:
ye xingchen <ye.xingchen@zte.com.cn> Signed-off-by:
-
ye xingchen authored
Follow the advice of the Documentation/filesystems/sysfs.rst and show() should only use sysfs_emit() or sysfs_emit_at() when formatting the value to be returned to user space. Signed-off-by:
Tommaso Merciai <tommaso.merciai@amarulasolutions.com> Signed-off-by:
-
- 14 Jul, 2023 33 commits
-
-
Christophe JAILLET authored
If fwnode_graph_get_remote_endpoint() fails, 'fwnode' is known to be NULL, so fwnode_handle_put() is a no-op. Release the reference taken from a previous fwnode_graph_get_port_parent() call instead. Also handle fwnode_graph_get_port_parent() failures. In order to fix these issues, add an error handling path to the function and the needed gotos. Fixes: ca50c197 ("[media] v4l: fwnode: Support generic fwnode for parsing standardised properties") Signed-off-by:
Christophe JAILLET <christophe.jaillet@wanadoo.fr> Signed-off-by:
Sakari Ailus <sakari.ailus@linux.intel.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@kernel.org>
-
Tomi Valkeinen authored
Add driver for TI DS90UB953 FPD-Link III Serializer. Signed-off-by:
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> Reviewed-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Reviewed-by:
Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by:
-
Tomi Valkeinen authored
Add driver for TI DS90UB913 FPD-Link III Serializer. Signed-off-by:
-
Tomi Valkeinen authored
Add driver for TI DS90UB960 FPD-Link III Deserializer. Signed-off-by:
-
Tomi Valkeinen authored
Add DT bindings for TI DS90UB960 FPD-Link III Deserializer. Signed-off-by:
Rob Herring <robh@kernel.org> Reviewed-by:
-
Tomi Valkeinen authored
Add DT bindings for TI DS90UB953 FPD-Link III Serializer. Signed-off-by:
-
Tomi Valkeinen authored
Add DT bindings for TI DS90UB913 FPD-Link III Serializer. Signed-off-by:
-
Luca Ceresoli authored
An ATR is a device that looks similar to an i2c-mux: it has an I2C slave "upstream" port and N master "downstream" ports, and forwards transactions from upstream to the appropriate downstream port. But it is different in that the forwarded transaction has a different slave address. The address used on the upstream bus is called the "alias" and is (potentially) different from the physical slave address of the downstream chip. Add a helper file (just like i2c-mux.c for a mux or switch) to allow implementing ATR features in a device driver. The helper takes care of adapter creation/destruction and translates addresses at each transaction. Signed-off-by:
Luca Ceresoli <luca@lucaceresoli.net> Signed-off-by:
Wolfram Sang <wsa@kernel.org> Signed-off-by:
-
Tomi Valkeinen authored
Add bindings for I2C Address Translator. Only one property is added, 'i2c-alias-pool', which can be used in the bindings for the device that supports ATR. Signed-off-by:
-
Claudiu Beznea authored
devm_kasprintf() returns a pointer to dynamically allocated memory. Pointer could be NULL in case allocation fails. Check pointer validity. Identified with coccinelle (kmerr.cocci script). Fixes: 0556f1d5 ("media: tvp5150: add input source selection of_graph support") Signed-off-by:
Claudiu Beznea <claudiu.beznea@microchip.com> Reviewed-by:
Marco Felsch <m.felsch@pengutronix.de> Signed-off-by:
-
Bingbu Cao authored
On ACPI based platforms, the ov13b10 camera sensor need to be powered up by acquire the PM resource from INT3472. INT3472 will register one regulator 'avdd', one reset gpio and clock source for ov13b10. Add 2 power interfaces that are registered as runtime PM callbacks. Signed-off-by:
Bingbu Cao <bingbu.cao@intel.com> Signed-off-by:
Hao Yao <hao.yao@intel.com> Suggested-by:
Hans de Goede <hdegoede@redhat.com> Reviewed-by:
-
Hans de Goede authored
The supported ad5820 and ad5821 VCMs both use a single 16 bit register which is written by sending 2 bytes with the data directly after sending the i2c-client address. The ad5823 OTOH has a more typical i2c / smbus device setup with multiple 8 bit registers where the first byte send after the i2c-client address is the register address and the actual data only starts from the second byte after the i2c-client address. The ad5823 i2c_ and of_device_id-s was added at the same time as the ad5821 ids with as rationale: """ Some camera modules also refer that AD5823 is a replacement of AD5820: https://download.kamami.com/p564094-OV8865_DS.pdf """ The AD5823 may be an electrical and functional replacement of the AD5820, but from a software pov it is not compatible at all and it is going to need its own driver, drop its id from the ad5820 driver. Fixes: b8bf7313 ("media: ad5820: Add support for ad5821 and ad5823") Cc: Pavel Machek <pavel@ucw.cz> Cc: Ricardo Ribalda Delgado <ribalda@kernel.org> Signed-off-by:
Ricardo Ribalda <ribalda@chromium.org> Signed-off-by:
-
Tommaso Merciai authored
The format param actually is not used in imx290_ctrl_update function, let's drop this Fixes: bc35f9a2 ("media: i2c: imx290: Fix the pixel rate at 148.5Mpix/s") Signed-off-by:
Tommaso Merciai <tomm.merciai@gmail.com> Reviewed-by:
Dave Stevenson <dave.stevenson@raspberrypi.com> Signed-off-by:
-
Bingbu Cao authored
On ACPI systems, the HID of ov13b10 is 'OVTI13B1', add this new HID in acpi IDs table to make driver support it. Signed-off-by:
-
Nicolas Ferre authored
Wenyou's email is bouncing, remove him from this camera driver's entry and mark it as orphan. Signed-off-by:
Nicolas Ferre <nicolas.ferre@microchip.com> Signed-off-by:
-
Bingbu Cao authored
The ov13b10 need be connected to a CIO2 or IPU device by bridge, sometimes the bridge driver was not probed before ov13b10 driver, then the absence of the fwnode endpoint for this device is expected, so driver return -EPROBE_DEFER in this case to let the probe occur after bridge driver. Signed-off-by:
-
Guoniu.zhou authored
OV5640 will output abnormal image data when work at low resolution (320x240, 176x144 and 160x120) after switching from high resolution, such as 1080P, the time interval between high and low switching must be less than 1000ms in order to OV5640 don't enter suspend state during the time. The reason is by 0x3824 value don't restore to initialize value when do resolution switching. In high resolution setting array, 0x3824 is set to 0x04, but low resolution setting array remove 0x3824 in commit db15c195 ("media: ov5640: Remove duplicated mode settings"). So when do resolution switching from high to low, such as 1080P to 320x240, and the time interval is less than auto suspend delay time which means global initialize setting array will not be loaded, the output image data are abnormal. Hence move 0x3824 from ov5640_init_setting[] table to ov5640_setting_low_res[] table and also move 0x4407 0x460b, 0x460c to avoid same issue. Fixes: db15c195 ("media: ov5640: Remove duplicated mode settings") Signed-off-by:
Guoniu.zhou <guoniu.zhou@nxp.com> Reviewed-by:
Jacopo Mondi <jacopo.mondi@ideasonboard.com> Signed-off-by:
-
Jason Chen authored
The HTS value cannot be directly compared to the sensor's output size. It needs to be converted to an absolute time unit. Additionally, the hblank value need to be modified as it was previous invalid. Signed-off-by:
Jason Chen <jason.z.chen@intel.com> Signed-off-by:
-
Sakari Ailus authored
Remove Shawn Tu's and Chiranjeevi Rapolu's e-mail addresses as they are no longer function. Signed-off-by:
-
Sakari Ailus authored
Chiranjeevi's e-mail is bouncing: chiranjeevi.rapolu@intel.com DM3NAM02FT041.mail.protection.outlook.com Remote Server returned '550 5.4.1 Recipient address rejected: Access denied. AS(201806281)' Assign the driver to myself. Signed-off-by:
-
Sakari Ailus authored
Dongchun's e-mail is no longer active and he hasn't given a new one: The following message to <dongchun.zhu@mediatek.com> was undeliverable. The reason for the problem: 5.1.0 - Unknown address error 550-'Relaying mail to dongchun.zhu@mediatek.com is not allowed' Mark the drivers as orphaned. Signed-off-by:
-
Sakari Ailus authored
I maintain V4L2 sensor and lens drivers but there hasn't been a specific MAINTAINERS entry for them. Add it now. Signed-off-by:
-
Sakari Ailus authored
Shawn Tu's e-mail address is bouncing: shawnx.tu@intel.com Remote Server returned '550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup' Assign the sensor drivers Shawn maintained to myself. Reported-by:
Conor Dooley <conor.dooley@microchip.com> Signed-off-by:
-
Bingbu Cao authored
cio2 bridge driver is moved out of ipu3, current ipu3 cio2 driver only has 1 source file, then we can rename the source file back to ipu3-cio2.c. Signed-off-by:
Daniel Scally <dan.scally@ideasonboard.com> Signed-off-by:
-
Bingbu Cao authored
Before bridge driver use CIO2_NUM_PORTS as the maximum supported CSI2 port number. Current bridge driver is moved out of ipu3, so define a new macro in ipu bridge for all IPUs instead of including CIO2 definition. This patch also removes the ipu3-cio2.h inclusion in ipu-bridge.h. Signed-off-by:
-
Bingbu Cao authored
cio2 bridge was involved along with IPU3. However, in fact all Intel IPUs besides IPU3 CIO2 need this bridge driver. This patch move bridge driver out of ipu3 directory and rename as ipu-bridge. Then it can be worked with IPU3 and other Intel IPUs. Signed-off-by:
-
Jack Zhu authored
Add support for Starfive JH7110 SoC which has the cadence csi2 receiver. Reviewed-by:
Jack Zhu <jack.zhu@starfivetech.com> Signed-off-by:
-
Jack Zhu authored
Add support for external MIPI D-PHY. Reviewed-by:
-
Jack Zhu authored
Add operation on reset for Cadence MIPI-CSI2 RX Controller. Reviewed-by:
-
Jack Zhu authored
Add resets property for Cadence MIPI-CSI2 RX controller Reviewed-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Reviewed-by:
-
Jack Zhu authored
Convert DT bindings document for Cadence MIPI-CSI2 RX controller to DT schema format. For compatible, new compatibles should not be messed with conversion, but the original binding did not specify any SoC-specific compatible string, so add the StarFive compatible string. Reviewed-by:
-
Krzysztof Kozlowski authored
The driver can match only via the DT table so the table should be always used and the of_match_ptr does not have any sense (this also allows ACPI matching via PRP0001, even though it might not be relevant here). This also fixes !CONFIG_OF error: drivers/media/i2c/max9286.c:1707:34: error: ‘max9286_dt_ids’ defined but not used [-Werror=unused-const-variable=] Signed-off-by:
-
Krzysztof Kozlowski authored
The driver will match mostly by DT table (even thought there is regular ID table) so there is little benefit in of_match_ptr (this also allows ACPI matching via PRP0001, even though it might not be relevant here). This also fixes !CONFIG_OF error: drivers/media/i2c/ov7740.c:1203:34: error: ‘ov7740_of_match’ defined but not used [-Werror=unused-const-variable=] Signed-off-by:
-
