All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v5] dmaengine: sh: Add Support SuperH DMA Engine driver
Date: Tue, 12 May 2009 03:02:32 +0000	[thread overview]
Message-ID: <4A08E6C8.8050802@renesas.com> (raw)
In-Reply-To: <49E41BA8.4090807@renesas.com>

Hi, Dan.

Thank you for your check.

Dan Williams wrote:
> Nobuhiro Iwamatsu wrote:
>> This supported all DMA channels, and it was tested in SH7722,
>> SH7780 and SH7763.
>> This can not use with SH DMA API.
>>
>> Signed-off-by: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
>> Reviewed-by: Matt Fleming <matt@console-pimps.org>
>> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
>> Acked-by: Maciej Sosnowski <maciej.sosnowski@intel.com>
>> ---
>>  v5: Fix some bug.
>>      Add Cyclic extention API (got hint from dw_dmac.c)
> 
> Have you run this with CONFIG_PROVE_LOCKING=y?  I suspect it will find 
> some issues.  It looks like desc_lock in the interrupt handler is only 
> protecting updates to the CHCR register.  In other places desc_lock is 
> protecting descriptor chain updates.  And the code varies from spin_lock 
> to spin_lock_bh?  If you can't move all register manipulations to bh or 
> process context then you will most likely need a separate register_lock 
> which can be taken with spin_lock_irq... see what CONFIG_PROVE_LOCKING 
> reports.

OK, I check this point, and send report.
> 
>> diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
>> index 3b3c01b..0a27f3c 100644
>> --- a/drivers/dma/Kconfig
>> +++ b/drivers/dma/Kconfig
>> @@ -81,6 +81,14 @@ config MX3_IPU_IRQS
>>           To avoid bloating the irq_desc[] array we allocate a sufficient
>>           number of IRQ slots and map them dynamically to specific 
>> sources.
>>
>> +config SH_DMAE
>> +       tristate "Renesas SuperH DMAC support"
>> +       depends on SUPERH && SH_DMA
>> +       depends on !SH_DMA_API
>> +       select DMA_ENGINE
>> +       help
>> +         Enable support for the Renesas SuperH DMA controllers.
>> +
>>  config DMA_ENGINE
>>         bool
>>
> 
> This will collide with the TXX9_DMAC config option now sitting in Ralf's 
> tree.  Please put this entry somewhere before MX3_IPU.

OK, I fix this next patch.


Best regards,
 Nobuhiro

      parent reply	other threads:[~2009-05-12  3:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14  5:14 [PATCH v5] dmaengine: sh: Add Support SuperH DMA Engine driver Nobuhiro Iwamatsu
2009-04-14  5:16 ` Paul Mundt
2009-04-24 17:28 ` Dan Williams
2009-05-12  3:02 ` Nobuhiro Iwamatsu [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=4A08E6C8.8050802@renesas.com \
    --to=iwamatsu.nobuhiro@renesas.com \
    --cc=linux-sh@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.