From: Raviteja Laggyshetty <quic_rlaggysh@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Stephan Gerhold <stephan.gerhold@kernkonzept.com>,
Danila Tikhonov <danila@jiaxyga.com>,
"Adam Skladowski" <a39.skl@gmail.com>,
Vladimir Lypak <vladimir.lypak@gmail.com>,
Andrew Halaney <ahalaney@redhat.com>,
Odelu Kukatla <quic_okukatla@quicinc.com>,
Mike Tipton <quic_mdtipton@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <linux-pm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3 2/2] interconnect: qcom: add QCS8300 interconnect provider driver
Date: Wed, 18 Sep 2024 15:10:34 +0530 [thread overview]
Message-ID: <40dd23e7-9ea5-4eb3-bb6b-e1952d746958@quicinc.com> (raw)
In-Reply-To: <3xjvx2kwrlruhhxw4aald26qjf5fzikay2ypzr3mwv75mlmf5q@lmn2o64npfg2>
On 9/11/2024 4:18 PM, Dmitry Baryshkov wrote:
> On Tue, Sep 10, 2024 at 10:10:13AM GMT, Raviteja Laggyshetty wrote:
>> Add driver for the Qualcomm interconnect buses found in QCS8300
>> based platforms. The topology consists of several NoCs that are
>> controlled by a remote processor that collects the aggregated
>> bandwidth for each master-slave pairs.
>>
>> Signed-off-by: Raviteja Laggyshetty <quic_rlaggysh@quicinc.com>
>> ---
>> drivers/interconnect/qcom/Kconfig | 11 +
>> drivers/interconnect/qcom/Makefile | 2 +
>> drivers/interconnect/qcom/qcs8300.c | 2088 +++++++++++++++++++++++++++
>> drivers/interconnect/qcom/qcs8300.h | 177 +++
>> 4 files changed, 2278 insertions(+)
>> create mode 100644 drivers/interconnect/qcom/qcs8300.c
>> create mode 100644 drivers/interconnect/qcom/qcs8300.h
>
> The driver looks pretty close to sa8775p one. Would it make sense to
> have a single driver instead? Or would it complicate things
> significantly?
>
Yes, the target is close to sa8775p. but there are differences in the topology and same driver cannot be used for both targets.
Thanks,
Raviteja
next prev parent reply other threads:[~2024-09-18 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 10:10 [PATCH V3 0/2] Add interconnect support for QCS8300 SoC Raviteja Laggyshetty
2024-09-10 10:10 ` [PATCH V3 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in " Raviteja Laggyshetty
2024-09-10 10:10 ` [PATCH V3 2/2] interconnect: qcom: add QCS8300 interconnect provider driver Raviteja Laggyshetty
2024-09-11 10:48 ` Dmitry Baryshkov
2024-09-18 9:40 ` Raviteja Laggyshetty [this message]
2024-09-18 12:37 ` Dmitry Baryshkov
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=40dd23e7-9ea5-4eb3-bb6b-e1952d746958@quicinc.com \
--to=quic_rlaggysh@quicinc.com \
--cc=a39.skl@gmail.com \
--cc=ahalaney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=danila@jiaxyga.com \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=dmitry.baryshkov@linaro.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-pm@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_mdtipton@quicinc.com \
--cc=quic_okukatla@quicinc.com \
--cc=robh@kernel.org \
--cc=stephan.gerhold@kernkonzept.com \
--cc=vladimir.lypak@gmail.com \
/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®