From: Vinod Koul <vinod.koul@intel.com>
To: Chuah Kim Tatt <kim.tatt.chuah@intel.com>
Cc: gregkh@linuxfoundation.org, heikki.krogerus@linux.intel.com,
andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, linux-kernel@vger.kernel.org,
jui.nee.tan@intel.com, peter@hurleysoftware.com,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dmaengine: hsu: Export hsu_dma_get_status()
Date: Thu, 30 Jun 2016 10:04:00 +0530 [thread overview]
Message-ID: <20160630043359.GO14945@localhost> (raw)
In-Reply-To: <1465969453-16198-2-git-send-email-kim.tatt.chuah@intel.com>
On Wed, Jun 15, 2016 at 01:44:11PM +0800, Chuah Kim Tatt wrote:
> From: "Chuah, Kim Tatt" <kim.tatt.chuah@intel.com>
>
> To allow other code to safely read DMA Channel Status Register (where
> the register attribute for Channel Error, Descriptor Time Out &
> Descriptor Done fields are read-clear), export hsu_dma_get_status().
> hsu_dma_irq() is renamed to hsu_dma_do_irq() and requires Status
> Register value to be passed in.
Acked-by: Vinod Koul <vinod.koul@intel.com>
--
~Vinod
next prev parent reply other threads:[~2016-06-30 4:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 5:44 [PATCH v2 0/3] Fix DNV HSUART RX DMA timeout interrupt issue Chuah Kim Tatt
2016-06-15 5:44 ` [PATCH v2 1/3] dmaengine: hsu: Export hsu_dma_get_status() Chuah Kim Tatt
2016-06-30 4:34 ` Vinod Koul [this message]
2016-06-15 5:44 ` [PATCH v2 2/3] serial: 8250_dma: Export serial8250_rx_dma_flush() Chuah Kim Tatt
2016-06-15 5:44 ` [PATCH v2 3/3] serial: 8250_mid: Read RX buffer on RX DMA timeout for DNV Chuah Kim Tatt
2016-06-15 12:15 ` [PATCH v2 0/3] Fix DNV HSUART RX DMA timeout interrupt issue Andy Shevchenko
2016-06-16 9:34 ` Heikki Krogerus
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=20160630043359.GO14945@localhost \
--to=vinod.koul@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jui.nee.tan@intel.com \
--cc=kim.tatt.chuah@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=peter@hurleysoftware.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;
as well as URLs for NNTP newsgroup(s).