summaryrefslogtreecommitdiff
path: root/drivers/media/i2c/adv7393.c
diff options
context:
space:
mode:
authorBryan O'Donoghue <bryan.odonoghue@linaro.org>2023-09-25 16:46:56 +0100
committerHans Verkuil <hverkuil-cisco@xs4all.nl>2023-10-07 10:55:44 +0200
commit91719b27926a2e382dba8cb161cb244aebddad71 (patch)
tree228fb8f25593fb50b81207dbec3e16d8c3f1ca37 /drivers/media/i2c/adv7393.c
parent5900b051959ebf56eb5c6687d8cafb48fc34b973 (diff)
media: qcom: camss: Pass line_num from compat resources
line_num indicates the number of RDI - raw data interface channels which are associated with a given IFE/VFE - image/video front end. On several SoCs the RDI number is not static for each VFE - for example on sm8250 VFE Lite has four RDIs where regular VFE has three. Assigning line_num statically in the subdev_init() phase initialises each VFE to the lower number, meaning in practical terms that we are lobbing off one RDI on some VFEs. Interrupt handling uses static for (i = RDI0; i < RDI2; i++) {} in some of our VFE blocks but this can't work for situations where we have a mixture of VFE @ 3 RDI and VFE-lite @ 4 RDI blocks. First step to remediate is to pass line_num from a compat string controlled data-structure and do so on a per-VFE basis. Later patches will assign the correct number of RDI blocks per VFE. Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Diffstat (limited to 'drivers/media/i2c/adv7393.c')
0 files changed, 0 insertions, 0 deletions