From: "Gjorgji Rosikopulos (Consultant)" <gjorgji.rosikopulos@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Atanas Filipov <atanas.filipov@oss.qualcomm.com>
Cc: Georgi Djakov <djakov@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v2 2/3] interconnect: qcom: Add CAMNOC interconnect provider driver
Date: Mon, 21 Sep 2026 18:17:50 +0300 [thread overview]
Message-ID: <a51d8129-0167-4b9f-89d6-9623e4d41c49@oss.qualcomm.com> (raw)
In-Reply-To: <07aeb266-927c-46f6-8363-f26fac7e3aab@oss.qualcomm.com>
Hi Konrad,
On 9/21/2026 5:17 PM, Konrad Dybcio wrote:
> On 9/9/26 2:58 PM, Gjorgji Rosikopulos (Consultant) wrote:
>> Hi Krzysztof,
>>
>> Thanks for the review.
>>
>> On 8/27/2026 12:25 PM, Krzysztof Kozlowski wrote:
>>> On Wed, Aug 19, 2026 at 12:32:10PM +0300, Atanas Filipov wrote:
>>>> Add an ICC provider for the Qualcomm Camera NOC (CAMNOC). Multiple
>>>> camera sub-devices share CAM_CC_CAMNOC_AXI_CLK; direct clk_set_rate()
>>>> calls from each consumer cause a last-writer-wins race.
>>>>
>>>> Each consumer obtains an ICC path to SLAVE_CAMNOC_AXI and votes via
>>>> icc_set_bw(). The ICC core aggregates votes (max peak_bw) and the
>>>> set() callback converts the result to clk_set_rate(). Consumers
>>>> encode the required frequency as peak_bw in kBps.
>>>>
>>>> Signed-off-by: Atanas Filipov <atanas.filipov@oss.qualcomm.com>
>>>> ---
>
> [...]
>
>> Maybe those series should be marked as RFC. The basic idea is to manage clocks as interconnect providers,
>> similar to this change: https://lore.kernel.org/all/20230512001334.2983048-3-dmitry.baryshkov@linaro.org/
>>
>> There is requirement to maintain higher clock rate on source clocks and some place to aggregate them.
>> One example is camnoc axi clock which is used by jpeg, camss, ope and maybe other drivers.
>> The interconnect has already functionality inplace to maintain higher
>> bw per request which can be used for maintaining higher clock frequency from requested drivers.
>>
>> One option is to use already available icc-clk provider, but we have to add many icc providers
>> instead one provider with many ports.
>
> icc-clk provides N clocks, it has M clients voting on each one and
> avg/peak bandwidth aggregation happens at the icc core so this
> should just work - or are we thinking about different problems?
That is correct thanks for pointing that, i have double checked, please ignore this series new version will use icc-clk.
Regards,
~Gjorgji
next prev parent reply other threads:[~2026-09-21 15:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <w3u_oVZRxmZkAlC5RmxuB0v5k970jezsVHDZvryQ3oYkStqmsp79LjODiA0mYkNl1jkRya-7Ncvk8KGrE1vnUQ==@protonmail.internalid>
2026-08-19 9:32 ` [PATCH v2 0/3] Add Qualcomm CAMNOC ICC provider Atanas Filipov
2026-08-19 9:32 ` [PATCH v2 1/3] dt-bindings: interconnect: Add Qualcomm CAMNOC ICC binding Atanas Filipov
2026-08-27 9:23 ` Krzysztof Kozlowski
2026-08-27 9:26 ` Krzysztof Kozlowski
2026-08-19 9:32 ` [PATCH v2 2/3] interconnect: qcom: Add CAMNOC interconnect provider driver Atanas Filipov
2026-08-27 9:25 ` Krzysztof Kozlowski
2026-08-27 9:28 ` Krzysztof Kozlowski
2026-09-09 12:58 ` Gjorgji Rosikopulos (Consultant)
2026-09-21 14:17 ` Konrad Dybcio
2026-09-21 15:05 ` Atanas Filipov
2026-09-21 15:17 ` Gjorgji Rosikopulos (Consultant) [this message]
2026-09-29 8:36 ` Bryan O'Donoghue
2026-08-19 9:32 ` [PATCH v2 3/3] arm64: dts: qcom: sm8250: Add CAMNOC ICC provider node Atanas Filipov
2026-09-29 8:39 ` [PATCH v2 0/3] Add Qualcomm CAMNOC ICC provider Bryan O'Donoghue
2026-09-29 11:43 ` 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=a51d8129-0167-4b9f-89d6-9623e4d41c49@oss.qualcomm.com \
--to=gjorgji.rosikopulos@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=atanas.filipov@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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
all inboxes | Powered by JetHome®