summaryrefslogtreecommitdiff
path: root/sound/usb
diff options
context:
space:
mode:
authorBryan O'Donoghue <bryan.odonoghue@linaro.org>2023-11-23 17:03:00 +0000
committerHans Verkuil <hverkuil-cisco@xs4all.nl>2023-12-07 08:31:15 +0100
commitac6494e0ca444d82ff9dc0df87fcfca1d91c5cd2 (patch)
treeadc3615efcd3e20e8fcdeab49242e9f5093d322b /sound/usb
parentb3695e86d25aafbe175dd51f6aaf6f68d341d590 (diff)
media: qcom: camss: Flag which VFEs require a power-domain
At the moment we have some complex code for determining if a VFE requires a power-domain attachment. Particularly discordant in this scheme is the subtle reliance on VFE and VFE Lite declaration ordering in our resources. VFE id is used to determine if a VFE is lite or not and consequently if a VFE requires power-domain attachment. VFE Lite though is not a correct delineation between power-domain and non power-domain state since early SoCs have neither VFE Lite nor power-domains attached to VFEs. Introduce has_pd to the VFE resource structure to allow the CAMSS code to understand if it needs to try to attach a power-domain for a given VFE. As a side-effect from this we no longer need to care about VFE Lite or non-Lite or the id number associated with either and which order the VFE/VFE Lite was declared in. Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org> Tested-by: Matti Lehtimäki <matti.lehtimaki@gmail.com> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Diffstat (limited to 'sound/usb')
0 files changed, 0 insertions, 0 deletions