From: patchwork-bot+linux-arm-msm@kernel.org
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: interconnect: sdm845: Add IDs for the QUP ports
Date: Mon, 30 Nov 2020 19:00:07 +0000 [thread overview]
Message-ID: <160676280710.32741.3702743058843786554.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201105135211.7160-1-georgi.djakov@linaro.org>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Thu, 5 Nov 2020 15:52:09 +0200 you wrote:
> The QUP ports exist in the topology, but are not exposed as an
> endpoints in DT. Fix this by creating IDs and attach them to their
> NoCs, so that the various QUP drivers (i2c/spi/uart etc.) are able
> to request their interconnect paths and scale their bandwidth.
>
> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
>
> [...]
Here is the summary with links:
- [1/3] dt-bindings: interconnect: sdm845: Add IDs for the QUP ports
https://git.kernel.org/qcom/c/8742bb4bf203
- [2/3] interconnect: qcom: sdm845: Add the missing nodes for QUP
https://git.kernel.org/qcom/c/cd5fc457e5d2
- [3/3] arm64: dts: sdm845: Add interconnect properties for QUP
https://git.kernel.org/qcom/c/05b801afb7d7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-11-30 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 13:52 [PATCH 1/3] dt-bindings: interconnect: sdm845: Add IDs for the QUP ports Georgi Djakov
2020-11-05 13:52 ` [PATCH 2/3] interconnect: qcom: sdm845: Add the missing nodes for QUP Georgi Djakov
2020-11-11 4:37 ` Bjorn Andersson
2020-11-13 12:00 ` Georgi Djakov
2020-11-05 13:52 ` [PATCH 3/3] arm64: dts: sdm845: Add interconnect properties " Georgi Djakov
2020-11-09 20:02 ` [PATCH 1/3] dt-bindings: interconnect: sdm845: Add IDs for the QUP ports Rob Herring
2020-11-11 4:37 ` Bjorn Andersson
2020-11-30 19:00 ` patchwork-bot+linux-arm-msm [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=160676280710.32741.3702743058843786554.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.