From: Jyothi Kumar Seerapu <quic_jseerapu@quicinc.com>
To: Mark Brown <broonie@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-spi@vger.kernel.org>, <quic_msavaliy@quicinc.com>,
<quic_vtanuku@quicinc.com>
Subject: Re: [PATCH v1 0/1] Add immediate DMA support
Date: Thu, 28 Nov 2024 19:05:54 +0530 [thread overview]
Message-ID: <56bf2e08-e8e3-4aca-9d51-176c009bedd5@quicinc.com> (raw)
In-Reply-To: <073ae0ed-32bf-4097-850c-832cccda6b58@sirena.org.uk>
On 11/21/2024 5:32 PM, Mark Brown wrote:
> On Thu, Nov 21, 2024 at 05:22:00PM +0530, Jyothi Kumar Seerapu wrote:
>> The DMA TRE(Transfer ring element) buffer contains the DMA
>> buffer address. Accessing data from this address can cause
>> significant delays in SPI transfers, which can be mitigated to
>> some extent by utilizing immediate DMA support.
>
> Please don't send cover letters for single patches, if there is anything
> that needs saying put it in the changelog of the patch or after the ---
> if it's administrative stuff. This reduces mail volume and ensures that
> any important information is recorded in the changelog rather than being
> lost.
Sure, thanks. will follow it for single patch.
prev parent reply other threads:[~2024-11-28 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 11:52 [PATCH v1 0/1] Add immediate DMA support Jyothi Kumar Seerapu
2024-11-21 11:52 ` [PATCH v1 1/1] spi: spi-geni-qcom: " Jyothi Kumar Seerapu
2024-11-21 22:08 ` Dmitry Baryshkov
2024-11-28 13:36 ` Jyothi Kumar Seerapu
2024-11-28 14:02 ` Dmitry Baryshkov
2024-11-29 11:12 ` Jyothi Kumar Seerapu
2024-11-21 12:02 ` [PATCH v1 0/1] " Mark Brown
2024-11-28 13:35 ` Jyothi Kumar Seerapu [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=56bf2e08-e8e3-4aca-9d51-176c009bedd5@quicinc.com \
--to=quic_jseerapu@quicinc.com \
--cc=broonie@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_vtanuku@quicinc.com \
--cc=vkoul@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