linux-toradex.git/drivers/media/platform/qcom/camss, branch master

media: qcom: camss: Drop csiphy_res_8300 phy resource table

2026-09-29T16:09:51+00:00

The qcs8300 phys are identical to the sa8775p's phys drop the duplicate
info and use csiphy_res_8775p[] for the qcs8300_resources.

The only difference is that the qcs8300 has 3 phys vs 4 phys for
the sa8775p, so explicitly set csiphy_num to 3 rather then using
ARRAY_SIZE().

Reviewed-by: Bryan O'Donoghue 
Reviewed-by: Loic Poulain 
Signed-off-by: Hans de Goede 
Reviewed-by: Vladimir Zapolskiy 
Signed-off-by: Bryan O'Donoghue

media: qcom: camss: Drop icc_res_qcs8300 resource table

2026-09-29T16:09:51+00:00

The icc_res_qcs8300 icc resource table is identical to the icc_res_sa8775p
icc resource table and qcs8300_resources already uses the sa8775p resources
for most things.

Reviewed-by: Bryan O'Donoghue 
Reviewed-by: Loic Poulain 
Signed-off-by: Hans de Goede 
Reviewed-by: Vladimir Zapolskiy 
Signed-off-by: Bryan O'Donoghue

media: qcom: camss: Use data-lanes starting at 1 for new CSIPHY mode

2026-09-29T16:09:51+00:00

Introducing a dedicated CSIPHY driver community feedback was both to move
to data-lanes starting at index 1 on the PHY side and also to match that
indexing scheme in the CSI decoder - CSID.

CSID consumes the data-lanes property to determine which CSID lanes to
switch on. For indexes starting at 1 we need to amend the logic somewhere.
The PHY side code normalises the input data to register level meanings so,
replicate that logic on the CSID side.

Introduce a simple flag to differentiate between legacy indexing @ 0 and
new indexing @ 1.

Existing bindings are not affected.

Reviewed-by: Loic Poulain 
Tested-by: Oleg Keri  # Lenovo Yoga Slim 7x Gen 11 (Glymur)
Signed-off-by: Bryan O'Donoghue 
Signed-off-by: Bryan O'Donoghue

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

2026-09-29T16:09:50+00:00

Add 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. If no
PHYs are present in the DT then the legacy method will be attempted.

Acked-by: Manivannan Sadhasivam 
Tested-by: Oleg Keri  # Lenovo Yoga Slim 7x Gen 11 (Glymur)
Signed-off-by: Bryan O'Donoghue 
Reviewed-by: Loic Poulain 
Signed-off-by: Bryan O'Donoghue

media: qcom: camss: Add Glymur compatible

2026-09-29T16:09:50+00:00

Glymur's camera subsystem hardware is a functional subset of X1E80100.
TPG, CSID, VFE, CSID wrapper and ICC resources are shared; Glymur has
three CSIPHY instances versus X1E80100's four.

qcom,x1e80100-camss is not used as a fallback compatible since it is
already claimed by its own binding schema, causing a duplicate
compatible warning in the DT schema checker.

Signed-off-by: Nihal Kumar Gupta 
Signed-off-by: Bryan O'Donoghue

media: qcom: camss: Report hardware version via media controller

2026-09-29T16:09:48+00:00

Populate media_dev.hw_revision with the top-level CAMSS hardware version
so that user space can query the exact hardware variant through the media
controller (e.g. via media-ctl or MEDIA_IOC_DEVICE_INFO). This can help
identify the platform variant and adapt behaviour accordingly, for example
allowing libcamera to apply quirks or enable features that cannot be
discovered through standard V4L2 or media-controller APIs.

The version register is exposed by some platforms through the top-level
"top" reg region (offset 0). When present, map it and read the version
once at probe. This is a no-op on platforms not mapping the region (yet).

Reported media info on Agatti/CM2290 (Spectra 520):
Media Driver Info:
        Driver name      : qcom-camss
        Model            : Qualcomm Camera Subsystem
        Bus info         : platform:5c11000.camss
        Hardware revision: 0x00050200 (328192)

Reviewed-by: Konrad Dybcio 
Reviewed-by: Bryan O'Donoghue 
Signed-off-by: Loic Poulain 
Signed-off-by: Bryan O'Donoghue

media: qcom: camss: Drop top_ahb/ahb/axi from QCM2290 subdevice clocks

2026-09-29T16:09:48+00:00

Remove the top_ahb, ahb and axi clocks from QCM2290 subdevice clock
lists. These clocks are now handled centrally as global CAMSS PM clocks
and are automatically enabled when CAMSS is runtime resumed.

This avoids redundant clock references in individual subdevices and
ensures consistent clock management across the CAMSS pipeline.

Reviewed-by: Bryan O'Donoghue 
Reviewed-by: Frank Li 
Signed-off-by: Loic Poulain 
Signed-off-by: Bryan O'Donoghue

media: qcom: camss: Add PM clock definitions for QCM2290

2026-09-29T16:09:47+00:00

Provide the required CAMSS PM clock descriptors for the QCM2290
platform. Register the top_ahb, ahb and axi clocks so they can be
managed automatically through the PM clock framework (they are part
of the camss-top group).

Reviewed-by: Bryan O'Donoghue 
Reviewed-by: Frank Li 
Signed-off-by: Loic Poulain 
Signed-off-by: Bryan O'Donoghue

media: qcom: camss: Add PM clock support and integrate with runtime PM

2026-09-29T16:09:47+00:00

Add optional PM clock support to the CAMSS driver using the PM clock
framework. This allows CAMSS clocks to be registered once and
automatically managed during runtime suspend and resume.

This is especially useful for global CAMSS clocks that are shared across
multiple CAMSS subblocks.

This avoids the need for each subblock to reference and manage the
shared clocks individually. A typical example is the set of clocks in
the top_group, which may be used by CSID, PHY, CCI, and other CAMSS
blocks.

Introduce a small PM clock descriptor table in the CAMSS resources
structure to describe clocks and their optional rates. Initialize
these clocks at probe time and delegate clock ownership to the PM
core.

Hook PM clock handling into the runtime PM callbacks to ensure clocks
are properly suspended and resumed alongside power domains and ICC
paths.

Reviewed-by: Bryan O'Donoghue 
Reviewed-by: Frank Li 
Signed-off-by: Loic Poulain 
Signed-off-by: Bryan O'Donoghue

media: qcom: camss: Add "gcc_axi_hf" to 8775p VFE lite clock lists

2026-09-29T16:09:47+00:00

The "gcc_axi_hf" clock is correctly listed in the clock list of the
8775p 2 main VFE-s, but it is missing from all the VFE-lite clock lists,
causing these to not work on platforms where the firmware allows turning
off "gcc_axi_hf".

Add the missing "gcc_axi_hf" to fix the VFE-lite blocks not working on
these platforms.

Fixes: 924f45e58b1fe ("media: qcom: camss: Add missing clocks for VFE lite on sa8775p")
Cc: stable@vger.kernel.org
Suggested-by: Wenmeng Liu 
Reviewed-by: Bryan O'Donoghue 
Signed-off-by: Hans de Goede 
Tested-by: Cory Keitz 
Reviewed-by: Loic Poulain 
Reviewed-by: Vladimir Zapolskiy 
Signed-off-by: Bryan O'Donoghue