mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Georgi Djakov <djakov@kernel.org>
To: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Pankaj Patil <pankaj.patil@oss.qualcomm.com>
Cc: lumag@kernel.org, a39.skl@gmail.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	quic_rjendra@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 2/2] interconnect: qcom: add glymur interconnect provider driver
Date: Sun, 20 Jul 2025 18:02:48 +0300	[thread overview]
Message-ID: <ffc17695-25e1-44d4-843d-d06d17e8da32@kernel.org> (raw)
In-Reply-To: <0a1ff771-17c5-44d1-88da-5dd54c303d14@oss.qualcomm.com>

On 7/20/25 4:19 PM, Raviteja Laggyshetty wrote:
> 
> On 7/16/2025 8:58 PM, Dmitry Baryshkov wrote:
>> On Wed, Jul 16, 2025 at 08:45:35PM +0530, Pankaj Patil wrote:
>>> From: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
>>>
>>> Add driver for the Qualcomm interconnect buses found in glymur
>>> 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.
>> I'd kindly ask to rebase on top of [1] unless Georgi says otherwise.
> 
> I think you intend to rebase on top of [1], but forgot to mention the link.
> 
> Please provide the link.

Rebasing on linux-next is usually fine. But why not use dynamic ids?

Thanks,
Georgi

> 
> 
> Thanks,
> 
> Raviteja.
> 
>>
>>> Signed-off-by: Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>
>>> Signed-off-by: Pankaj Patil <pankaj.patil@oss.qualcomm.com>
>>> ---
>>>   drivers/interconnect/qcom/Kconfig  |    9 +
>>>   drivers/interconnect/qcom/Makefile |    2 +
>>>   drivers/interconnect/qcom/glymur.c | 2259 ++++++++++++++++++++++++++++
>>>   drivers/interconnect/qcom/glymur.h |  185 +++
>>>   4 files changed, 2455 insertions(+)
>>>   create mode 100644 drivers/interconnect/qcom/glymur.c
>>>   create mode 100644 drivers/interconnect/qcom/glymur.h
>>>

  reply	other threads:[~2025-07-20 15:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16 15:15 [PATCH 0/2] Add interconnect support for Glymur SoC Pankaj Patil
2025-07-16 15:15 ` [PATCH 1/2] dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in " Pankaj Patil
2025-07-20 23:14   ` Rob Herring (Arm)
2025-07-31 15:06   ` Krzysztof Kozlowski
2025-07-16 15:15 ` [PATCH 2/2] interconnect: qcom: add glymur interconnect provider driver Pankaj Patil
2025-07-16 15:28   ` Dmitry Baryshkov
2025-07-20 13:19     ` Raviteja Laggyshetty
2025-07-20 15:02       ` Georgi Djakov [this message]
2025-07-20 15:10         ` Raviteja Laggyshetty
2025-07-17 20:33   ` Konrad Dybcio
2025-07-20 13:34     ` Raviteja Laggyshetty

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=ffc17695-25e1-44d4-843d-d06d17e8da32@kernel.org \
    --to=djakov@kernel.org \
    --cc=a39.skl@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --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=lumag@kernel.org \
    --cc=pankaj.patil@oss.qualcomm.com \
    --cc=quic_rjendra@quicinc.com \
    --cc=raviteja.laggyshetty@oss.qualcomm.com \
    --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®