From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>, <vkoul@kernel.org>
Cc: <dmaengine@vger.kernel.org>, <dan.j.williams@intel.com>
Subject: Re: [PATCH v2 0/5] dmaengine: ti: k3-udma: cleanups for 5.8
Date: Tue, 7 Jul 2020 15:57:18 +0300 [thread overview]
Message-ID: <559a6306-27b7-cbed-ca55-60709a94744e@ti.com> (raw)
In-Reply-To: <20200707102352.28773-1-peter.ujfalusi@ti.com>
On 07/07/2020 13:23, Peter Ujfalusi wrote:
> Hi Vinod,
>
> Changes since v1:
> - drop the check against NULL for uc in the IO functions as pointed out by
> Grygorii
>
> Tested on top of linux-next, but they apply (with offsets) on top of
> dmaengine/next.
>
> Few patches to clean up the code mostly with the exception of removing the use
> of ring_get_occ() from udma_pop_from_ring().
>
> This series should not conflict with Grygorii's ringacc update patch, they touch
> the code in different areas.
>
> Regards,
> Peter
> ---
> Peter Ujfalusi (5):
> dmaengine: ti: k3-udma: Remove dma_sync_single calls for descriptors
> dmaengine: ti: k3-udma: Do not use ring_get_occ in udma_pop_from_ring
> dmaengine: ti: k3-udma: Use common defines for TCHANRT/RCHANRT
> registers
> dmaengine: ti: k3-udma-private: Use udma_read/write for register
> access
> dmaengine: ti: k3-udma: Use udma_chan instead of tchan/rchan for IO
> functions
>
> drivers/dma/ti/k3-udma-glue.c | 79 +++++------
> drivers/dma/ti/k3-udma-private.c | 8 +-
> drivers/dma/ti/k3-udma.c | 236 +++++++++++++------------------
> drivers/dma/ti/k3-udma.h | 61 +++-----
> 4 files changed, 161 insertions(+), 223 deletions(-)
>
Thank you
Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
--
Best regards,
grygorii
next prev parent reply other threads:[~2020-07-07 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 10:23 [PATCH v2 0/5] dmaengine: ti: k3-udma: cleanups for 5.8 Peter Ujfalusi
2020-07-07 10:23 ` [PATCH v2 1/5] dmaengine: ti: k3-udma: Remove dma_sync_single calls for descriptors Peter Ujfalusi
2020-07-07 10:23 ` [PATCH v2 2/5] dmaengine: ti: k3-udma: Do not use ring_get_occ in udma_pop_from_ring Peter Ujfalusi
2020-07-07 10:23 ` [PATCH v2 3/5] dmaengine: ti: k3-udma: Use common defines for TCHANRT/RCHANRT registers Peter Ujfalusi
2020-07-07 10:23 ` [PATCH v2 4/5] dmaengine: ti: k3-udma-private: Use udma_read/write for register access Peter Ujfalusi
2020-07-07 10:23 ` [PATCH v2 5/5] dmaengine: ti: k3-udma: Use udma_chan instead of tchan/rchan for IO functions Peter Ujfalusi
2020-07-07 12:57 ` Grygorii Strashko [this message]
2020-07-15 6:07 ` [PATCH v2 0/5] dmaengine: ti: k3-udma: cleanups for 5.8 Vinod Koul
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=559a6306-27b7-cbed-ca55-60709a94744e@ti.com \
--to=grygorii.strashko@ti.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=peter.ujfalusi@ti.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