[PATCH v19 4/5] media: qcom: camss: Add support for PHY API devices

[sashiko-bot at kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] kconfig: selection of non-existent symbol PHY_QCOM_MIPI_CSI2
--

commit 585e1d52eb0f705ed19df22dc9f45b8bef14c8a9
Author: Bryan O'Donoghue <bryan.odonoghue at linaro.org>

media: qcom: camss: Add support for PHY API devices

This commit adds the ability to use a PHY pointer which interacts with the
standard PHY API. In the first instance the code will try to use the new
PHY interface, falling back to a legacy method if no PHYs are present in
the device tree.

> diff --git a/drivers/media/platform/qcom/camss/Kconfig b/drivers/media/platform/qcom/camss/Kconfig
> index 4eda48cb1adf0..1edc5e5a1829e 100644
> --- a/drivers/media/platform/qcom/camss/Kconfig
> +++ b/drivers/media/platform/qcom/camss/Kconfig
> @@ -7,3 +7,4 @@ config VIDEO_QCOM_CAMSS
>  	select VIDEO_V4L2_SUBDEV_API
>  	select VIDEOBUF2_DMA_SG
>  	select V4L2_FWNODE
> +	select PHY_QCOM_MIPI_CSI2

[Severity: Medium]
Does this statement select a Kconfig symbol that does not exist in the kernel
tree?

When a user configures the kernel with VIDEO_QCOM_CAMSS, this select
statement targets PHY_QCOM_MIPI_CSI2, which appears to be missing. This
leaves the required PHY driver disabled by default, causing the camera
subsystem to fail at runtime because the PHY device will not be present.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260917-b4-linux-next-25-03-13-dtsi-x1e80100-camss-v19-0-21ad8a76e941@linaro.org?part=4