From: Vinod Koul <vkoul@kernel.org>
To: manivannan.sadhasivam@linaro.org, fancer.lancer@gmail.com,
Mrinmay Sarkar <quic_msarkar@quicinc.com>
Cc: quic_shazhuss@quicinc.com, quic_nitegupt@quicinc.com,
quic_ramkri@quicinc.com, quic_nayiluri@quicinc.com,
quic_krichai@quicinc.com, quic_vbadigan@quicinc.com,
Cai Huoqing <cai.huoqing@linux.dev>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] Fix unmasking interrupt bit and remove watermark interrupt enablement
Date: Wed, 28 Aug 2024 23:38:38 +0530 [thread overview]
Message-ID: <172486851833.309756.677991791964410222.b4-ty@kernel.org> (raw)
In-Reply-To: <1724674261-3144-1-git-send-email-quic_msarkar@quicinc.com>
On Mon, 26 Aug 2024 17:40:59 +0530, Mrinmay Sarkar wrote:
> This patch series reset STOP_INT_MASK and ABORT_INT_MASK bit and unmask
> these interrupt for HDMA.
>
> and also remove enablement of local watermark interrupt enable(LWIE)
> and remote watermarek interrupt enable(RWIE) bit to avoid unnecessary
> watermark interrupt event.
>
> [...]
Applied, thanks!
[1/2] dmaengine: dw-edma: Fix unmasking STOP and ABORT interrupts for HDMA
commit: 383baf5c8f062091af34c63f28d37642a8f188ae
[2/2] dmaengine: dw-edma: Do not enable watermark interrupts for HDMA
commit: 9f646ff25c09c52cebe726601db27a60f876f15e
Best regards,
--
~Vinod
next prev parent reply other threads:[~2024-08-28 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 12:10 Mrinmay Sarkar
2024-08-26 12:11 ` [PATCH v4 1/2] dmaengine: dw-edma: Fix unmasking STOP and ABORT interrupts for HDMA Mrinmay Sarkar
2024-08-26 12:11 ` [PATCH v4 2/2] dmaengine: dw-edma: Do not enable watermark " Mrinmay Sarkar
2024-08-28 18:08 ` Vinod Koul [this message]
2024-08-29 7:12 ` [PATCH v4 0/2] Fix unmasking interrupt bit and remove watermark interrupt enablement Serge Semin
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=172486851833.309756.677991791964410222.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=cai.huoqing@linux.dev \
--cc=dmaengine@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_krichai@quicinc.com \
--cc=quic_msarkar@quicinc.com \
--cc=quic_nayiluri@quicinc.com \
--cc=quic_nitegupt@quicinc.com \
--cc=quic_ramkri@quicinc.com \
--cc=quic_shazhuss@quicinc.com \
--cc=quic_vbadigan@quicinc.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
all inboxes | Powered by JetHome®