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

Dmitry Baryshkov <[email protected]>
Newsgroups org.kernel.vger.linux-media,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel
Message-ID <x7aje3k2jdf3skoafyd7ehteym4os4zp3y5hdavptjl6477oze@zsrzx763r3he>
On Tue, Aug 04, 2026 at 08:44:25AM +0300, Gjorgji Rosikopulos (Consultant) wrote:
> Hi Dmitry,
> 
> On 8/3/2026 10:09 PM, Dmitry Baryshkov wrote:
> > 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.
> 
> Honestly i really don't know, i am trying reach to correct people(find proper documentation) 
> for this. From what i have in the jpeg documentation only power domain which is required,
> for jpeg core is TITAN_TOP for sm8250, i did not check the other platforms.

The question is primarily about SM8250, since you are adding support for
it. 

-- 
With best wishes
Dmitry
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.