From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Barnabás Czémán" <barnabas.czeman@mainlining.org>,
"Georgi Djakov" <djakov@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
Vladimir Lypak <vladimir.lypak@gmail.com>
Subject: Re: [PATCH v2 2/2] interconnect: qcom: Add MSM8953 driver
Date: Fri, 28 Jun 2024 09:41:39 +0200 [thread overview]
Message-ID: <68e56d01-6cda-4101-a8dc-659cc5160afc@kernel.org> (raw)
In-Reply-To: <20240627-msm8953-interconnect-v2-2-b4940a8eab69@mainlining.org>
On 27/06/2024 17:08, Barnabás Czémán wrote:
> From: Vladimir Lypak <vladimir.lypak@gmail.com>
>
> Add driver for interconnect busses found in MSM8953 based platforms.
> The topology consists of four NoCs that are partially controlled by a
> RPM processor.
>
> Note that one of NoCs (System NoC) has a counterpart (System NoC MM)
> that is modelled as child device to avoid resource conflicts, since it
> uses same MMIO space for configuration.
>
> Signed-off-by: Vladimir Lypak <vladimir.lypak@gmail.com>
> Signed-off-by: Barnabás Czémán <barnabas.czeman@mainlining.org>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-28 7:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 15:08 [PATCH v2 0/2] Add interconnect driver for MSM8953/SDM450/SDM632 Barnabás Czémán
2024-06-27 15:08 ` [PATCH v2 1/2] dt-bindings: interconnect: qcom: Add Qualcomm MSM8953 NoC Barnabás Czémán
2024-06-28 7:41 ` Krzysztof Kozlowski
2024-06-27 15:08 ` [PATCH v2 2/2] interconnect: qcom: Add MSM8953 driver Barnabás Czémán
2024-06-28 7:41 ` Krzysztof Kozlowski [this message]
2024-06-28 9:32 ` Georgi Djakov
2024-06-28 9:41 ` Krzysztof Kozlowski
2024-06-28 14:06 ` barnabas.czeman
2024-06-28 21:25 ` kernel test robot
2024-06-28 23:15 ` kernel test robot
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=68e56d01-6cda-4101-a8dc-659cc5160afc@kernel.org \
--to=krzk@kernel.org \
--cc=barnabas.czeman@mainlining.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@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 \
--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;
as well as URLs for NNTP newsgroup(s).