From: Jie Hai <haijie1@huawei.com>
To: <vkoul@kernel.org>, <wangzhou1@hisilicon.com>
Cc: <dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RESENT PATCH v5 0/7] dmaengine: hisilicon: Add support for hisi dma driver
Date: Tue, 30 Aug 2022 15:45:14 +0800 [thread overview]
Message-ID: <bf8ccd6f-b58d-8296-9e33-e7c32243922f@huawei.com> (raw)
In-Reply-To: <20220830060555.50781-1-haijie1@huawei.com>
On 2022/8/30 14:05, Jie Hai wrote:
Sorry for incorrect titles with "RESENT", please drop this patch set and
follow the latest.
> The HiSilicon IP08 and HiSilicon IP09 are DMA iEPs, they share the
> same pci device id but different pci revision and register layouts.
>
> The original version supports HiSilicon IP08 but not HiSilicon IP09.
> This series support DMA driver for HIP08 and HIP09:
> 1. Fix bugs for HIP08 DMA driver
> - Disable hardware channels when driver detached
> - Update cq_head whenever accessed it
> - Support multi-thread for one DMA channel
> 2. Use macros instead of magic number
> 3. Add support for HIP09 DMA driver
> 4. Add debugfs for HIP08 and HIP09 DMA driver
> 5. Add myself as maintainer of hisi_dma.c
>
> Changes since version 4:
> - Fix hdma_dev->base to hdma_dev->queue_base in hisi_dma_reset_or_disable_hw_chan
>
> Changes since version 3:
> - remove reduldant braces
> - add "Acked-by: Zhou Wang <wangzhou1@hisilicon.com>" in commit log
>
> Changes since version 2:
> - fix unnecessary line breaks
> - fix register bit with BIT/GENMASK and adjust hisi_dma_update_bit to it
> - remove "Reported-by" in commit message
> - use dmaengine root instead of hisi_dma root
> - ignore errors for creating debugfs
>
> Changes since version 1:
> - remove error changes casuse compile failure
> - remove reduldant "*" in comment
> - remove debugfs-hisi-dma doc and path in MAINTAINERS
>
> Jie Hai (7):
> dmaengine: hisilicon: Disable channels when unregister hisi_dma
> dmaengine: hisilicon: Fix CQ head update
> dmaengine: hisilicon: Add multi-thread support for a DMA channel
> dmaengine: hisilicon: Use macros instead of magic number
> dmaengine: hisilicon: Adapt DMA driver to HiSilicon IP09
> dmaengine: hisilicon: Dump regs to debugfs
> MAINTAINERS: Add myself as maintainer for hisi_dma
>
> MAINTAINERS | 1 +
> drivers/dma/hisi_dma.c | 650 +++++++++++++++++++++++++++++++++++------
> 2 files changed, 555 insertions(+), 96 deletions(-)
>
prev parent reply other threads:[~2022-08-30 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 6:05 Jie Hai
2022-08-30 6:05 ` [RESENT PATCH v5 1/7] dmaengine: hisilicon: Disable channels when unregister hisi_dma Jie Hai
2022-08-30 6:05 ` [RESENT PATCH v5 2/7] dmaengine: hisilicon: Fix CQ head update Jie Hai
2022-08-30 6:05 ` [RESENT PATCH v5 3/7] dmaengine: hisilicon: Add multi-thread support for a DMA channel Jie Hai
2022-08-30 6:05 ` [RESENT PATCH v5 4/7] dmaengine: hisilicon: Use macros instead of magic number Jie Hai
2022-08-30 6:05 ` [RESENT PATCH v5 5/7] dmaengine: hisilicon: Adapt DMA driver to HiSilicon IP09 Jie Hai
2022-08-30 6:05 ` [RESENT PATCH v5 6/7] dmaengine: hisilicon: Dump regs to debugfs Jie Hai
2022-08-30 6:05 ` [RESENT PATCH v5 7/7] MAINTAINERS: Add myself as maintainer for hisi_dma Jie Hai
2022-08-30 7:45 ` Jie Hai [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=bf8ccd6f-b58d-8296-9e33-e7c32243922f@huawei.com \
--to=haijie1@huawei.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.org \
--cc=wangzhou1@hisilicon.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®