From: Felipe Balbi <balbi@ti.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: <balbi@ti.com>, Viresh Kumar <viresh.linux@gmail.com>,
Vinod Koul <vinod.koul@intel.com>, <linux-kernel@vger.kernel.org>,
spear-devel <spear-devel@list.st.com>
Subject: Re: [PATCHv2 3/4] dw_dmac: change {dev_}printk() to corresponding macros
Date: Wed, 17 Oct 2012 16:53:06 +0300 [thread overview]
Message-ID: <20121017135306.GG11394@arwen.pp.htv.fi> (raw)
In-Reply-To: <1350481018.3568.3.camel@smile>
[-- Attachment #1: Type: text/plain, Size: 2324 bytes --]
On Wed, Oct 17, 2012 at 04:36:58PM +0300, Andy Shevchenko wrote:
> On Wed, 2012-10-17 at 16:09 +0300, Felipe Balbi wrote:
> > Hi,
> >
> > On Wed, Oct 17, 2012 at 01:31:17PM +0300, Andy Shevchenko wrote:
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > ---
> > > drivers/dma/dw_dmac.c | 15 ++++++---------
> > > 1 file changed, 6 insertions(+), 9 deletions(-)
> > >
> > > diff --git a/drivers/dma/dw_dmac.c b/drivers/dma/dw_dmac.c
> > > index c27c125..60b172a 100644
> > > --- a/drivers/dma/dw_dmac.c
> > > +++ b/drivers/dma/dw_dmac.c
> > > @@ -456,9 +456,8 @@ static void dwc_scan_descriptors(struct dw_dma *dw, struct dw_dma_chan *dwc)
> > >
> > > static inline void dwc_dump_lli(struct dw_dma_chan *dwc, struct dw_lli *lli)
> > > {
> > > - dev_printk(KERN_CRIT, chan2dev(&dwc->chan),
> > > - " desc: s0x%x d0x%x l0x%x c0x%x:%x\n",
> > > - lli->sar, lli->dar, lli->llp, lli->ctlhi, lli->ctllo);
> > > + dev_crit(chan2dev(&dwc->chan), " desc: s0x%x d0x%x l0x%x c0x%x:%x\n",
> > > + lli->sar, lli->dar, lli->llp, lli->ctlhi, lli->ctllo);
> >
> > is this really critical ? To me it looks more like a debugging message.
> This one is used in two cases, where one is marked as "error", another -
> "critical"
fair enough
> > > static void dwc_handle_error(struct dw_dma *dw, struct dw_dma_chan *dwc)
> > > @@ -492,10 +491,8 @@ static void dwc_handle_error(struct dw_dma *dw, struct dw_dma_chan *dwc)
> > > * controller flagged an error instead of scribbling over
> > > * random memory locations.
> > > */
> > > - dev_printk(KERN_CRIT, chan2dev(&dwc->chan),
> > > - "Bad descriptor submitted for DMA!\n");
> > > - dev_printk(KERN_CRIT, chan2dev(&dwc->chan),
> > > - " cookie: %d\n", bad_desc->txd.cookie);
> > > + dev_crit(chan2dev(&dwc->chan), "Bad descriptor submitted for DMA!\n");
> > > + dev_crit(chan2dev(&dwc->chan), " cookie: %d\n", bad_desc->txd.cookie);
> >
> > now this is critical, indeed. I would suggest using dev_WARN_ONCE() so
> > that it's noisy enough to catch the failing user.
> To this and upper comment, there is an explanation why it's critical. I
> guess the WARN_ONCE is not good enough, for example if we have more than
> one user making such noise.
then use dev_WARN()
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-10-17 13:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 10:31 [PATCHv2 0/4] dw_dmac: few cleanups to the driver Andy Shevchenko
2012-10-17 10:31 ` [PATCHv2 1/4] dmaengine: dw_dmac: remove CLK dependency Andy Shevchenko
2012-10-17 10:31 ` [PATCHv2 2/4] dmaengine: dw_dmac: amend description and indentation Andy Shevchenko
2012-10-17 10:31 ` [PATCHv2 3/4] dw_dmac: change {dev_}printk() to corresponding macros Andy Shevchenko
2012-10-17 10:36 ` viresh kumar
2012-10-17 13:09 ` Felipe Balbi
2012-10-17 13:36 ` Andy Shevchenko
2012-10-17 13:53 ` Felipe Balbi [this message]
2012-10-18 8:15 ` Andy Shevchenko
2012-10-18 10:34 ` Felipe Balbi
2012-10-18 11:09 ` Andy Shevchenko
2012-10-18 13:59 ` Felipe Balbi
2012-10-18 14:11 ` Andy Shevchenko
2012-10-17 10:31 ` [PATCHv2 4/4] dw_dmac: don't call platform_get_drvdata twice Andy Shevchenko
2012-10-17 10:36 ` viresh kumar
2012-10-17 13:14 ` Felipe Balbi
2012-10-17 14:06 ` viresh kumar
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=20121017135306.GG11394@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=andriy.shevchenko@linux.intel.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
all inboxes | Powered by JetHome®