From: Bryan O'Donoghue <bod@kernel.org>
To: Atanas Filipov <atanas.filipov@oss.qualcomm.com>,
linux-media@vger.kernel.org
Cc: mchehab@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, andersson@kernel.org,
konradybcio@kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/4] arm64: dts: qcom: sm8550: Add JPEG encoder node
Date: Sun, 14 Jun 2026 01:53:22 +0100 [thread overview]
Message-ID: <be6f78ce-d347-4225-a03e-6d1adecbfd4c@kernel.org> (raw)
In-Reply-To: <2a0fc1ce-2f19-4268-8117-cd90b512312a@oss.qualcomm.com>
On 13/06/2026 17:05, Atanas Filipov wrote:
> Checked. The MMCX/MXC dependency is covered transitively — camcc
> itself declares:
>
> power-domains = <&rpmhpd RPMHPD_MMCX>, <&rpmhpd RPMHPD_MXC>;
>
> CAM_CC_TITAN_TOP_GDSC is a subdomain of camcc, so the RPMh votes are
> enforced before any consumer is powered on.
Powered on yes, scaling the voltage correctly no.
> This matches the pattern used by every other single-GDSC camera node
> in the upstream tree (cci0/1/2 on sm8250, sm8550, sm8650) — none of
> them list MMCX/MXC directly. No change needed.
CCI doesn't have any operating points. Please check the clock frequency
plans.
> afilipov
>
> On 6/13/2026 2:52 AM, Bryan O'Donoghue wrote:
Honestly. Stop top posting !
Documentation/process/submitting-patches.rst:.. _interleaved_replies:
sm8650 which you have cited, has operating points for the JPEG encoder
and votes, must vote, on MXC. I believe the same as Hamoa for the JPEG
core clock.
This is melting my head a bit now TBH.
---
bod
next prev parent reply other threads:[~2026-06-14 0:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 19:44 [PATCH v1 0/4] This series adds support for the Qualcomm JPEG V4L2 mem2mem encoder Atanas Filipov
2026-06-12 19:44 ` [PATCH v1 1/4] dt-bindings: media: qcom: Add JPEG encoder binding Atanas Filipov
2026-06-12 19:57 ` sashiko-bot
2026-06-12 20:42 ` Frank Li
2026-06-12 23:17 ` Bryan O'Donoghue
2026-06-12 23:38 ` Bryan O'Donoghue
2026-06-13 18:42 ` Krzysztof Kozlowski
2026-06-12 19:44 ` [PATCH v1 2/4] arm64: dts: qcom: sm8550: Add JPEG encoder node Atanas Filipov
2026-06-12 20:06 ` sashiko-bot
2026-06-12 23:14 ` Bryan O'Donoghue
2026-06-13 9:24 ` Atanas Filipov
2026-06-13 9:52 ` Bryan O'Donoghue
2026-06-13 11:16 ` Atanas Filipov
2026-06-14 1:13 ` Bryan O'Donoghue
2026-06-12 23:52 ` Bryan O'Donoghue
2026-06-13 16:05 ` Atanas Filipov
2026-06-14 0:53 ` Bryan O'Donoghue [this message]
2026-06-12 19:44 ` [PATCH v1 3/4] arm64: dts: qcom: sm8250: " Atanas Filipov
2026-06-12 19:44 ` [PATCH v1 4/4] media: qcom: jpeg: Add Qualcomm JPEG V4L2 encoder Atanas Filipov
2026-06-12 20:23 ` sashiko-bot
2026-06-12 20:53 ` Frank Li
2026-06-13 18:43 ` Krzysztof Kozlowski
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=be6f78ce-d347-4225-a03e-6d1adecbfd4c@kernel.org \
--to=bod@kernel.org \
--cc=andersson@kernel.org \
--cc=atanas.filipov@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=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