From: "Gjorgji Rosikopulos (Consultant)" <gjorgji.rosikopulos@oss.qualcomm.com>
To: Bryan O'Donoghue <bod@kernel.org>,
Atanas Filipov <atanas.filipov@oss.qualcomm.com>,
Georgi Djakov <djakov@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org
Cc: 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 0/3] Add Qualcomm CAMNOC ICC provider
Date: Tue, 29 Sep 2026 14:43:58 +0300 [thread overview]
Message-ID: <63cc2480-a8b7-460f-b89d-8526cb17db36@oss.qualcomm.com> (raw)
In-Reply-To: <8df7fdb2-813c-402c-99c0-9de6b0dbcd0e@kernel.org>
Hi Bryan,
On 9/29/2026 11:39 AM, Bryan O'Donoghue wrote:
> On 19/08/2026 10:32, Atanas Filipov wrote:
>> This series adds a device tree binding and driver for the Qualcomm
>> Camera Network-on-Chip (CAMNOC) interconnect provider for SM8250.
>>
>> CAMNOC is the internal AXI interconnect within the camera subsystem.
>> Multiple camera sub-devices (IFE, JPEG, BPS, IPE, etc.) share
>> CAM_CC_CAMNOC_AXI_CLK. Direct clk_set_rate() calls from each consumer
>> cause a last-writer-wins race. This series introduces a lightweight ICC
>> provider that aggregates bandwidth votes from all consumers and applies
>> a single clk_set_rate() call.
>>
>> Changes since v1:
>> - dt-bindings: add all SM8250 CAMNOC master port IDs to qcom,camnoc.h
>> (IFE 0/1, IFE Lite 0-4, BPS, IPE 0/1, JPEG, JPEG DMA, CDM, FD, SBI,
>> ICP) with a short comment per group (Dmitry Baryshkov)
>> - dt-bindings: add IFE simple consumer example alongside the JPEG
>> OPP-based example; clarify opp-hz and opp-peak-kBps semantics in
>> comments; fix maintainer email; align provider node name with DTS
>> - driver: register all SM8250 CAMNOC master nodes
>>
>> Atanas Filipov (3):
>> dt-bindings: interconnect: Add Qualcomm CAMNOC ICC binding
>> interconnect: qcom: Add CAMNOC interconnect provider driver
>> arm64: dts: qcom: sm8250: Add CAMNOC ICC provider node
>>
>> .../bindings/interconnect/qcom,camnoc.yaml | 124 ++++++++
>> arch/arm64/boot/dts/qcom/sm8250.dtsi | 8 +
>> drivers/interconnect/qcom/Kconfig | 10 +
>> drivers/interconnect/qcom/Makefile | 2 +
>> drivers/interconnect/qcom/qcom-camnoc.c | 279 ++++++++++++++++++
>> .../dt-bindings/interconnect/qcom,camnoc.h | 52 ++++
>> 6 files changed, 475 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/interconnect/qcom,camnoc.yaml
>> create mode 100644 drivers/interconnect/qcom/qcom-camnoc.c
>> create mode 100644 include/dt-bindings/interconnect/qcom,camnoc.h
>>
>>
>> base-commit: 9e970952a9503d6ab471a2fea4c10b6a2785406f
>> --
>> 2.34.1
>>
>>
>
> I'd like to see the code for actually _using_ this in CAMSS, seems a bit
> incomplete without that part.
Yes the next patchset will include the CAMSS part.
~Gjorgji
>
> ---
> bod
prev parent reply other threads:[~2026-09-29 11:44 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 ` 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)
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) [this message]
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=63cc2480-a8b7-460f-b89d-8526cb17db36@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=djakov@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-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®