From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Viresh Kumar <viresh.linux@gmail.com>,
Vinod Koul <vinod.koul@intel.com>,
linux-kernel@vger.kernel.org,
spear-devel <spear-devel@list.st.com>,
balbi@ti.com
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCHv3 5/6] dw_dmac: change dev_crit to dev_WARN in dwc_handle_error
Date: Thu, 18 Oct 2012 17:34:11 +0300 [thread overview]
Message-ID: <1350570852-10398-6-git-send-email-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <1350570852-10398-1-git-send-email-andriy.shevchenko@linux.intel.com>
In case of handling a bad descriptor the dwc_handle_error() will dump a stack
as well. It's a lot more verbose and more likely to get user's attention.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
drivers/dma/dw_dmac.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/dma/dw_dmac.c b/drivers/dma/dw_dmac.c
index 180ffd5..826ff8d 100644
--- a/drivers/dma/dw_dmac.c
+++ b/drivers/dma/dw_dmac.c
@@ -485,14 +485,14 @@ static void dwc_handle_error(struct dw_dma *dw, struct dw_dma_chan *dwc)
dwc_dostart(dwc, dwc_first_active(dwc));
/*
- * KERN_CRITICAL may seem harsh, but since this only happens
+ * WARN may seem harsh, but since this only happens
* when someone submits a bad physical address in a
* descriptor, we should consider ourselves lucky that the
* controller flagged an error instead of scribbling over
* random memory locations.
*/
- dev_crit(chan2dev(&dwc->chan), "Bad descriptor submitted for DMA!\n");
- dev_crit(chan2dev(&dwc->chan), " cookie: %d\n", bad_desc->txd.cookie);
+ dev_WARN(chan2dev(&dwc->chan), "Bad descriptor submitted for DMA!\n"
+ " cookie: %d\n", bad_desc->txd.cookie);
dwc_dump_lli(dwc, &bad_desc->lli);
list_for_each_entry(child, &bad_desc->tx_list, desc_node)
dwc_dump_lli(dwc, &child->lli);
--
1.7.10.4
next prev parent reply other threads:[~2012-10-18 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 14:34 [PATCHv3 0/6] dw_dmac: few cleanups to the driver Andy Shevchenko
2012-10-18 14:34 ` [PATCHv3 1/6] dmaengine: dw_dmac: remove CLK dependency Andy Shevchenko
2012-10-18 14:34 ` [PATCHv3 2/6] dmaengine: dw_dmac: amend description and indentation Andy Shevchenko
2012-10-18 14:34 ` [PATCHv3 3/6] dw_dmac: change dev_printk() to corresponding macros Andy Shevchenko
2012-10-18 14:34 ` [PATCHv3 4/6] dw_dmac: don't call platform_get_drvdata twice Andy Shevchenko
2012-10-18 14:34 ` Andy Shevchenko [this message]
2012-10-18 14:34 ` [PATCHv3 6/6] dw_dmac: introduce to_dw_desc() macro Andy Shevchenko
2012-10-18 17:04 ` [PATCHv3 0/6] dw_dmac: few cleanups to the driver viresh kumar
2012-10-18 17:28 ` Felipe Balbi
2012-10-25 8:06 ` 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=1350570852-10398-6-git-send-email-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spear-devel@list.st.com \
--cc=vinod.koul@intel.com \
--cc=viresh.linux@gmail.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