From: Bryan O'Donoghue <bod@kernel.org>
To: Loic Poulain <loic.poulain@oss.qualcomm.com>
Cc: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Hangxiang Ma <hangxiang.ma@oss.qualcomm.com>,
Robert Foss <rfoss@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Todor Tomov <todor.too@gmail.com>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH] media: qcom: camss: Enable setting the rate to camnoc_rt_axi clock
Date: Thu, 16 Oct 2025 16:31:28 +0100 [thread overview]
Message-ID: <33513b43-f6d1-4c76-887b-39611a75e1f4@kernel.org> (raw)
In-Reply-To: <CAFEp6-2=GJL-gc+PSyAL4=prp_sXdZJS=Ewg5nP2kcp_Gu85Fw@mail.gmail.com>
On 16/10/2025 13:22, Loic Poulain wrote:
>> I'm - perhaps naively - assuming this clock really is required ... and
>> that both will be needed concurrently.
> AFAIU, the NRT clock is not in use for the capture part, and only
> required for the offline processing engine (IPE, OPE), which will
> likely be described as a separated node.
Maybe yeah though we already have bindings.
@Hangxiang I thought we had discussed this clock was required for your
setup.
Can you confirm with a test and then
1. Repost with my RB - I assume you included this on purpose
2. Respond that you can live without it.
---
bod
next prev parent reply other threads:[~2025-10-16 15:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 2:43 [PATCH] media: qcom: camss: Enable setting the rate to camnoc_rt_axi clock Hangxiang Ma
2025-10-15 8:23 ` Bryan O'Donoghue
2025-10-16 5:54 ` Krzysztof Kozlowski
2025-10-16 11:30 ` Konrad Dybcio
2025-10-16 11:50 ` Bryan O'Donoghue
2025-10-16 12:22 ` Loic Poulain
2025-10-16 14:59 ` Vladimir Zapolskiy
2025-10-16 15:31 ` Bryan O'Donoghue [this message]
2025-10-16 20:53 ` Vijay Kumar Tumati
2025-10-17 11:41 ` Bryan O'Donoghue
2025-10-20 3:23 ` Hangxiang Ma
2025-10-20 8:13 ` Loic Poulain
2025-10-20 13:35 ` Vladimir Zapolskiy
2025-10-20 13:46 ` Vijay Kumar Tumati
2025-10-21 19:19 ` Vijay Kumar Tumati
2025-10-22 16:00 ` Bryan O'Donoghue
2025-10-22 17:39 ` Vijay Kumar Tumati
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=33513b43-f6d1-4c76-887b-39611a75e1f4@kernel.org \
--to=bod@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hangxiang.ma@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=vladimir.zapolskiy@linaro.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