Re: [PATCH v6 3/3] arm64: dts: qcom: sm8250: Add JPEG encoder node

On Sat, Aug 01, 2026 at 11:04:10AM +0100, Bryan O'Donoghue wrote:
> On 31/07/2026 20:30, Gjorgji Rosikopulos (Consultant) wrote:
> > > > Is TITAN_TOP a part of the MMCX or CX domain? In the former case,
> > > > please drop separate mmcx vote here and let it come through the
> > > > titan_top (it might require camcc driver and node modifications).
> > > > 
> > > The change was requested by Brian, most likely in connection with
> > > upcoming migrations. I think he would be able to explain the exact
> > > reasons. As far as the facts are concerned, this is not currently
> > > necessary for the driver to be functional.
> > In the documentation we have this jpeg block need only TITAN_TOP_GDSC power domain.
> > However Bryan request to ad MMCX and MX.
> > As i can see same is for csiphy. Maybe is better to sync with Bryan.
> 
> Check hamoa - I believe it is the case there's a separate vote required for
> MMCX/MXA.

Assuming TITAN_TOP gates MMCX to the whole camera block (please correct
me if I'm wrong), why do we need a separate vote on MMCX? I might be
missing something here, sorry.

> 
> I'm prefectly fine if all that is required on kona is titan_top_gdsc but,
> basically I'm asking _you_ to go verify the difference and come back with an
> answer.
> 
> "Not required for Kona we checked" - its not about being asked its about
> checking what's actually required, I'm highlighting this because sm8550
> perhaps and hamoa definitely are different.
> 
> All of this is in the power-tree documentation. Please find the place where
> the power-rails are stipulated for venus/iris and then check to see what's
> required for the titan block and represent all of the necessary rails in the
> jpeg@{} such that jpeg@{} can run standalone without any of the rest of the
> block switched on.
> 
> I'll trust your diligence in that.
> 
> ---
> bod

-- 
With best wishes
Dmitry