From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Stephan Gerhold <stephan.gerhold@kernkonzept.com>,
Mark Brown <broonie@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] spi: dt-bindings: qup: Document interconnects
Date: Wed, 13 Sep 2023 10:19:05 +0200 [thread overview]
Message-ID: <16040f40-3938-d324-d916-ffa5775525c6@linaro.org> (raw)
In-Reply-To: <20230912-spi-qup-dvfs-v1-3-3e38aa09c2bd@kernkonzept.com>
On 12/09/2023 16:30, Stephan Gerhold wrote:
> When the SPI QUP controller is used together with a DMA engine it needs
> to vote for the interconnect path to the DRAM. Otherwise it may be
> unable to access the memory quickly enough.
>
> Signed-off-by: Stephan Gerhold <stephan.gerhold@kernkonzept.com>
> ---
> Documentation/devicetree/bindings/spi/qcom,spi-qup.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-09-13 9:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 14:30 [PATCH 0/4] spi: qup: Allow scaling power domains and interconnect Stephan Gerhold
2023-09-12 14:30 ` [PATCH 1/4] spi: dt-bindings: qup: Document power-domains and OPP Stephan Gerhold
2023-09-13 8:18 ` Krzysztof Kozlowski
2023-09-12 14:30 ` [PATCH 2/4] spi: qup: Parse OPP table for DVFS support Stephan Gerhold
2023-09-13 8:54 ` Konrad Dybcio
2023-09-12 14:30 ` [PATCH 3/4] spi: dt-bindings: qup: Document interconnects Stephan Gerhold
2023-09-13 8:19 ` Krzysztof Kozlowski [this message]
2023-09-12 14:30 ` [PATCH 4/4] spi: qup: Vote for interconnect bandwidth to DRAM Stephan Gerhold
2023-09-13 9:26 ` Stephan Gerhold
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=16040f40-3938-d324-d916-ffa5775525c6@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stephan.gerhold@kernkonzept.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).