Devicetree
 help / color / mirror / Atom feed
From: "Gjorgji Rosikopulos (Consultant)" <gjorgji.rosikopulos@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Bryan O'Donoghue <bod@kernel.org>
Cc: Atanas Filipov <atanas.filipov@oss.qualcomm.com>,
	linux-media@vger.kernel.org, mchehab@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, andersson@kernel.org,
	konradybcio@kernel.org, loic.poulain@linaro.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 3/3] arm64: dts: qcom: sm8250: Add JPEG encoder node
Date: Tue, 4 Aug 2026 08:44:25 +0300	[thread overview]
Message-ID: <cff2cfb1-619b-4f93-b6dc-f7f34a66bdec@oss.qualcomm.com> (raw)
In-Reply-To: <mpiuqkxaq4bvz4pc7iug3aoar5jkxz4tpetbg72olrzfar4zlc@w7sgfwfksl4r>

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.

~Gjorgji

> 
>>
>> 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
> 


  reply	other threads:[~2026-08-04  5:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 15:05 [PATCH v6 0/3] Add Qualcomm JPEG V4L2 encoder for SM8250 Atanas Filipov
2026-07-30 15:05 ` [PATCH v6 1/3] dt-bindings: media: qcom: Add JPEG encoder binding Atanas Filipov
2026-07-30 15:39   ` Dmitry Baryshkov
2026-07-30 16:24     ` Atanas Filipov
2026-07-31 19:26       ` Gjorgji Rosikopulos (Consultant)
2026-08-01 19:48         ` Loic Poulain
2026-08-02 13:53           ` Atanas Filipov
2026-08-03 18:16         ` Dmitry Baryshkov
2026-08-04  5:56           ` Gjorgji Rosikopulos (Consultant)
2026-07-30 15:05 ` [PATCH v6 2/3] media: qcom: jpeg: Add Qualcomm JPEG V4L2 encoder Atanas Filipov
2026-07-30 15:20   ` sashiko-bot
2026-07-30 15:57   ` Dmitry Baryshkov
2026-08-03 15:57     ` Gjorgji Rosikopulos (Consultant)
2026-08-03 18:37       ` Dmitry Baryshkov
2026-08-04  5:53         ` Gjorgji Rosikopulos (Consultant)
2026-07-30 15:05 ` [PATCH v6 3/3] arm64: dts: qcom: sm8250: Add JPEG encoder node Atanas Filipov
2026-07-30 15:31   ` sashiko-bot
2026-07-30 16:01   ` Dmitry Baryshkov
2026-07-30 18:02     ` Atanas Filipov
2026-07-31 19:30       ` Gjorgji Rosikopulos (Consultant)
2026-08-01 10:04         ` Bryan O'Donoghue
2026-08-03  6:38           ` Gjorgji Rosikopulos (Consultant)
2026-08-03 19:09           ` Dmitry Baryshkov
2026-08-04  5:44             ` Gjorgji Rosikopulos (Consultant) [this message]
2026-08-03 18:44       ` Dmitry Baryshkov
2026-08-04  5:48         ` Gjorgji Rosikopulos (Consultant)

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=cff2cfb1-619b-4f93-b6dc-f7f34a66bdec@oss.qualcomm.com \
    --to=gjorgji.rosikopulos@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=atanas.filipov@oss.qualcomm.com \
    --cc=bod@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=mchehab@kernel.org \
    --cc=robh@kernel.org \
    /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