- 10 Apr, 2024 1 commit
-
-
Sakari Ailus authored
Call devm_request_irq() before registering the async notifier, as otherwise it would be possible to use the device before the interrupts could be delivered to the driver. Fixes: c2a6a07a ("media: intel-ipu3: cio2: add new MIPI-CSI2 driver") Signed-off-by:
Sakari Ailus <sakari.ailus@linux.intel.com> Signed-off-by:
Hans Verkuil <hverkuil-cisco@xs4all.nl>
-
- 09 Apr, 2024 17 commits
-
-
Paweł Anikiel authored
After the conversion of dv timing calls to use a pad argument is done, remove the old callbacks. Update the subdev ioctl handlers to use the new callbacks. Signed-off-by:
Paweł Anikiel <panikiel@google.com> Signed-off-by:
-
Paweł Anikiel authored
Use the pad variant for all (s|g|query)_dv_timings subdev calls, which includes a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Use the pad variant for all (s|g|query)_dv_timings subdev calls, which includes a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Use the pad variant for all (s|g|query)_dv_timings subdev calls, which includes a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Use the pad variant for all (s|g|query)_dv_timings subdev calls, which includes a pad argument. Signed-off-by:
Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se> Signed-off-by:
-
Paweł Anikiel authored
Use the pad variant for all (s|g|query)_dv_timings subdev calls, which includes a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Change all (s|g|query)_dv_timings subdev callbacks to include a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Change all (s|g|query)_dv_timings subdev callbacks to include a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Change all (s|g|query)_dv_timings subdev callbacks to include a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Change all (s|g|query)_dv_timings subdev callbacks to include a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Change all (s|g|query)_dv_timings subdev callbacks to include a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Change all (s|g|query)_dv_timings subdev callbacks to include a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Change all (s|g|query)_dv_timings subdev callbacks to include a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Change all (s|g|query)_dv_timings subdev callbacks to include a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Change all (s|g|query)_dv_timings subdev callbacks to include a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Change all (s|g|query)_dv_timings subdev callbacks to include a pad argument. Signed-off-by:
-
Paweł Anikiel authored
Currently, subdev dv timing calls (i.e. g/s/query_dv_timings) are video ops without a pad argument. This is a problem if the subdevice can have different dv timings for each pad (e.g. a DisplayPort receiver with multiple virtual channels). To solve this, change these calls to include a pad argument, and put them into pad ops. Keep the old ones temporarily to make the switch easier. Signed-off-by:
-
- 08 Apr, 2024 22 commits
-
-
Bryan O'Donoghue authored
vfe-170 and vfe-175 can be supported in the same file with some minimal indirection to differentiate between the silicon versions. sdm845 uses vfe-170, sc8280xp uses vfe-175-200. Lets rename the file to capture its wider scope than vfe-170 only. Acked-by:
Konrad Dybcio <konrad.dybcio@linaro.org> Signed-off-by:
Bryan O'Donoghue <bryan.odonoghue@linaro.org> Signed-off-by:
-
Bryan O'Donoghue authored
Add in functional logic throughout the code to support the sc8280xp. Acked-by:
-
Bryan O'Donoghue authored
This commit describes the hardware layout for the sc8280xp for the following hardware blocks: - 4 x VFE, 4 RDI per VFE - 4 x VFE Lite, 4 RDI per VFE - 4 x CSID - 4 x CSID Lite - 4 x CSI PHY Signed-off-by:
-
Bryan O'Donoghue authored
Adds a CAMSS SoC identifier for the SC8280XP. Signed-off-by:
-
Bryan O'Donoghue authored
Add a PHY configuration sequence for the sc8280xp which uses a Qualcomm Gen 2 version 1.1 CSI-2 PHY. The PHY can be configured as two phase or three phase in C-PHY or D-PHY mode. This configuration supports two-phase D-PHY mode. Reviewed-by:
-
Bryan O'Donoghue authored
Add bindings for qcom,sc8280xp-camss in order to support the camera subsystem for sc8280xp as found in the Lenovo x13s Laptop. Signed-off-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Signed-off-by:
-
Tzung-Bi Shih authored
Instead of using fallback driver name match, provide ID table[1] for the primary match. [1]: https://elixir.bootlin.com/linux/v6.8/source/drivers/base/platform.c#L1353Reviewed-by:
Benson Leung <bleung@chromium.org> Reviewed-by:
Tzung-Bi Shih <tzungbi@kernel.org> Signed-off-by:
-
Krzysztof Kozlowski authored
This driver's initialization functions do not perform any custom code, except printing messages. Printing messages on modules loading/unloading is discouraged because it pollutes the dmesg regardless whether user actually has this device. Core kernel code already gives tools to investigate whether module was loaded or not. Drop the printing messages which allows to replace open-coded module_sdio_driver(). Signed-off-by:
-
hanchunchao authored
Fix "The the" typo in the documentation. Signed-off-by:
hanchunchao <hanchunchao@inspur.com> Signed-off-by:
-
Ricardo Ribalda authored
Because the size passed to copy_from_user() cannot be known beforehand, it needs to be checked during runtime with check_object_size. That makes gcc believe that the content of sbuf can be used before init. Fix: ./include/linux/thread_info.h:215:17: warning: ‘sbuf’ may be used uninitialized [-Wmaybe-uninitialized] Signed-off-by:
Ricardo Ribalda <ribalda@chromium.org> Signed-off-by:
-
Ricardo Ribalda authored
Increase the size of led_names so it can fit any valid v4l2 device name. Fixes: drivers/media/radio/radio-shark2.c:197:17: warning: ‘%s’ directive output may be truncated writing up to 35 bytes into a region of size 32 [-Wformat-truncation=] Signed-off-by:
-
Ricardo Ribalda authored
Make sure that tegra20_vi_get_input_formats always assign a value for yuv_input_format. Fix: drivers/staging/media/tegra-video/tegra20.c:624:72: warning: ‘yuv_input_format’ may be used uninitialized [-Wmaybe-uninitialized] Signed-off-by:
Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by:
-
Arnd Bergmann authored
clang-19 warns about mixing two enum types here: drivers/media/platform/renesas/rcar-vin/rcar-vin.h:296:12: error: conditional expression between different enumeration types ('enum rvin_csi_id' and 'enum rvin_isp_id') [-Werror,-Wenum-compare-conditional] drivers/media/platform/renesas/rcar-vin/rcar-core.c:216:18: error: conditional expression between different enumeration types ('enum rvin_csi_id' and 'enum rvin_isp_id') [-Werror,-Wenum-compare-conditional] drivers/media/platform/renesas/rcar-vin/rcar-vin.h:296:12: error: conditional expression between different enumeration types ('enum rvin_csi_id' and 'enum rvin_isp_id') [-Werror,-Wenum-compare-conditional] drivers/media/platform/renesas/rcar-vin/rcar-vin.h:296:12: error: conditional expression between different enumeration types ('enum rvin_csi_id' and 'enum rvin_isp_id') [-Werror,-Wenum-compare-conditional] This one is intentional, and there is already a cast to work around another warning, so address this by adding another cast. Fixes: 406bb586 ("media: rcar-vin: Add r8a779a0 support") Signed-off-by:Arnd Bergmann <arnd@arndb.de> Reviewed-by:
-
Martin Tůma authored
Fix the mgb4 driver documentation structure that breaks the "Video4Linux (V4L) driver-specific documentation" outline. Signed-off-by:
Martin Tůma <martin.tuma@digiteqautomotive.com> Signed-off-by:
-
Matthijs Kooijman authored
The v4l2_buffer type has an "offset" field, but the corresponding field in the v4l2_plane type is called "mem_offset". Use the correct name in this example. Signed-off-by:
Matthijs Kooijman <matthijs@stdin.nl> Signed-off-by:
-
Jacopo Mondi authored
According to the formats description in videodev2.h Y210, Y212 and Y216 are YCbCr packed formats. For each Y2xx format, xx bits of valid data occupy the MSBs of the 16 bit components, and 16-xx bits of zero padding occupy the LSBs. The Y210 and Y216 formats are missing an entry in the v4l2_format_info[] table. Add it. Signed-off-by:
Jacopo Mondi <jacopo.mondi@ideasonboard.com> Reviewed-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by:
-
Changhuang Liang authored
Need to remove links when unregistering devices. Fixes: ac7da4a7 ("media: staging: media: starfive: camss: Register devices") Signed-off-by:
Changhuang Liang <changhuang.liang@starfivetech.com> Signed-off-by:
-
Prasad Pandit authored
Add terminating new line to the Kconfig file. Signed-off-by:
Prasad Pandit <pjp@fedoraproject.org> Signed-off-by:
-
Uwe Kleine-König authored
The .remove() callback for a platform driver returns an int which makes many driver authors wrongly assume it's possible to do error handling by returning an error code. However the value returned is ignored (apart from emitting a warning) and this typically results in resource leaks. To improve here there is a quest to make the remove callback return void. In the first step of this quest all drivers are converted to .remove_new(), which already returns void. Eventually after all drivers are converted, .remove_new() will be renamed to .remove(). Trivially convert this driver from always returning zero in the remove callback to the void returning variant. Signed-off-by:
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Reviewed-by:
-
Hans Verkuil authored
A 'case V4L2_CTRL_TYPE_AREA' was missing in v4l2_ctrl_type_op_log, which led to an 'unknown type' message in the kernel log. Add support for controls of this type. Signed-off-by: -
Aleksandr Burakov authored
The return value of dvb_ca_en50221_init() is not checked here that may cause undefined behavior in case of nonzero value return. Found by Linux Verification Center (linuxtesting.org) with SVACE. Fixes: 25aee3de ("[media] Rename media/dvb as media/pci") Signed-off-by:
Aleksandr Burakov <a.burakov@rosalinux.ru> Signed-off-by:
-
István Váradi authored
anysee_master_xfer currently accepts read messages of length 2 only. However, several frontends, e.g. tda10023 send buffers of length 1, containing an 8-bit register number (see tda10023_readreg). These buffers are rejected currently, making many Anysee variants to not work. In these cases the "Unsupported Anysee version" message is logged. This patch alters the function to accept buffers of a length of 1 too. Signed-off-by:
István Váradi <ivaradi@varadiistvan.hu> Signed-off-by:
-
