linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: zhangfei.gao@linaro.org (zhangfei)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] dmaengine: Add hisilicon k3 DMA engine driver
Date: Thu, 28 Nov 2013 09:07:11 +0800	[thread overview]
Message-ID: <5296973F.3070009@linaro.org> (raw)
In-Reply-To: <CAA9_cmd6crfVdeLQhnfWLcJViAwHG=c3V5SDgu9teEd3pfch7A@mail.gmail.com>


Dear Dan

On 11/28/2013 06:35 AM, Dan Williams wrote:
> On Mon, Aug 26, 2013 at 7:20 PM, Zhangfei Gao <zhangfei.gao@linaro.org> wrote:
>> Add dmaengine driver for hisilicon k3 platform based on virt_dma
>>
>> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
>> Tested-by: Kai Yang <jean.yangkai@huawei.com>
>> Acked-by: Arnd Bergmann <arnd@arndb.de>
>> ---

>> diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
>> index 6825957..2945ff0 100644
>> --- a/drivers/dma/Kconfig
>> +++ b/drivers/dma/Kconfig
>> @@ -300,6 +300,15 @@ config DMA_JZ4740
>>          select DMA_ENGINE
>>          select DMA_VIRTUAL_CHANNELS
>>
>> +config K3_DMA
>> +       tristate "Hisilicon K3 DMA support"
>> +       depends on ARCH_HI3xxx
>
> Unless I am missing something this driver cannot be built since
> ARCH_HI3xxx does not exist.  Is this arch still winding its way
> upstream?
>

The patch set "enable hi3xxx SoC" still on the way, suppose to be in 
3.13, including adding ARCH_HI3xxx.

Sorry for the confusion.

Thanks

      reply	other threads:[~2013-11-28  1:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27  2:20 [PATCH v4] dmaengine: add k3dma Zhangfei Gao
2013-08-27  2:20 ` [PATCH v4] dmaengine: Add hisilicon k3 DMA engine driver Zhangfei Gao
2013-08-28  5:54   ` Vinod Koul
2013-08-28  6:42     ` zhangfei
2013-11-27 22:35   ` Dan Williams
2013-11-28  1:07     ` zhangfei [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=5296973F.3070009@linaro.org \
    --to=zhangfei.gao@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).