From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: at_xdmac: fix bug about channel configuration
Date: Fri, 10 Jul 2015 13:30:02 +0530 [thread overview]
Message-ID: <20150710080002.GC836@localhost> (raw)
In-Reply-To: <1434550946-27750-1-git-send-email-ludovic.desroches@atmel.com>
On Wed, Jun 17, 2015 at 04:22:26PM +0200, Ludovic Desroches wrote:
> When using descriptor view 2 or higher, we don't write the configuration
> into AT_XDMAC_CC register because this configuration will be fetch from
> the descriptor. Unfortunately, the PROT bit is not updated with this
> method, we have to do it manually before enabling the channel.
>
Applied, thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Ludovic Desroches <ludovic.desroches@atmel.com>
Cc: linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, nicolas.ferre@atmel.com,
maxime.ripard@free-electrons.com
Subject: Re: [PATCH] dmaengine: at_xdmac: fix bug about channel configuration
Date: Fri, 10 Jul 2015 13:30:02 +0530 [thread overview]
Message-ID: <20150710080002.GC836@localhost> (raw)
In-Reply-To: <1434550946-27750-1-git-send-email-ludovic.desroches@atmel.com>
On Wed, Jun 17, 2015 at 04:22:26PM +0200, Ludovic Desroches wrote:
> When using descriptor view 2 or higher, we don't write the configuration
> into AT_XDMAC_CC register because this configuration will be fetch from
> the descriptor. Unfortunately, the PROT bit is not updated with this
> method, we have to do it manually before enabling the channel.
>
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2015-07-10 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 14:22 [PATCH] dmaengine: at_xdmac: fix bug about channel configuration Ludovic Desroches
2015-06-17 14:22 ` Ludovic Desroches
2015-06-30 13:03 ` Ludovic Desroches
2015-06-30 13:03 ` Ludovic Desroches
2015-07-10 8:00 ` Vinod Koul [this message]
2015-07-10 8:00 ` 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=20150710080002.GC836@localhost \
--to=vinod.koul@intel.com \
--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 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.