From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
hverkuil-cisco@xs4all.nl, laurent.pinchart@ideasonboard.com,
rfoss@kernel.org, todor.too@gmail.com, andersson@kernel.org,
mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/5] media: qcom: camss: Convert to per-VFE pointer for power-domain linkages
Date: Fri, 27 Oct 2023 10:38:25 +0100 [thread overview]
Message-ID: <d62d65b8-da05-4dfb-bf38-1c102564a5a0@linaro.org> (raw)
In-Reply-To: <9fec3a90-b3dd-4b2e-bb7f-27890ad2b4e0@linaro.org>
On 27/10/2023 10:10, Bryan O'Donoghue wrote:
> power-domains = <VFE_0>,
> <VFE_1>,
> <TITAN_TOP>; // the controller pd
>
> vfe-set = <VFE_0>, // has its own PD vfe->id = 0
> <VFE_1>, // has its own PD vfe->id = 1
> <VFE_LITE_N>; // has no PD vfe->id = 2
>
> The basic problem this series fixes is magic indexing.
So be a little clearer; this would be an invalid declaration in dtsi
right now
power-domains = <TITAN_TOP>, // has to come last
<VFE_0>,
<VFE_1>; // the code would think this TOP
The TOP GDSC must come last.
Similarly this would an invalid declaration in our resource structure
vfe-set = <VFE_LITE_0>, //the code thinks this is a VFE
<VFE_LITE_1>, //the code thinks this is a VFE
<VFE_0>,
<VFE_1>; // and that this is VFE Lite
vfe_num = 2;
vfe-id = {0..3}
// don't hook a PD for VFE Lite
if (vfe->id >= camss->res->vfe_num)
return 0;
has_pd fixes checks like that. Eventually we will throw away has_pd when
legacy indexing is dropped - in which case if vfe->id has a res->pd_name
we hook it, if not, then not.
The order of declaration won't matter.
---
bod
next prev parent reply other threads:[~2023-10-27 9:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 15:50 [PATCH v2 0/5] media: qcom: camss: Introduce support for named power-domains Bryan O'Donoghue
2023-10-26 15:50 ` [PATCH v2 1/5] media: qcom: camss: Flag which VFEs require a power-domain Bryan O'Donoghue
2023-10-26 20:05 ` Konrad Dybcio
2023-10-26 15:50 ` [PATCH v2 2/5] media: qcom: camss: Convert to per-VFE pointer for power-domain linkages Bryan O'Donoghue
2023-10-26 20:08 ` Konrad Dybcio
2023-10-27 9:10 ` Bryan O'Donoghue
2023-10-27 9:38 ` Bryan O'Donoghue [this message]
2023-10-26 15:50 ` [PATCH v2 3/5] media: qcom: camss: Use common VFE pm_domain_on/pm_domain_off where applicable Bryan O'Donoghue
2023-10-26 15:50 ` [PATCH v2 4/5] media: qcom: camss: Move VFE power-domain specifics into vfe.c Bryan O'Donoghue
2023-10-31 10:54 ` Konrad Dybcio
2023-10-31 11:51 ` Bryan O'Donoghue
2023-10-31 15:04 ` Konrad Dybcio
2023-10-26 15:50 ` [PATCH v2 5/5] media: qcom: camss: Add support for named power-domains Bryan O'Donoghue
2023-10-31 10:53 ` Konrad Dybcio
2023-10-31 11:38 ` Bryan O'Donoghue
2023-10-31 17:10 ` Bryan O'Donoghue
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d62d65b8-da05-4dfb-bf38-1c102564a5a0@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andersson@kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=konrad.dybcio@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=todor.too@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®