From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Xiubo Li-B47053 <Li.Xiubo@freescale.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: fsl_sai: Add isr to deal with error flag
Date: Thu, 27 Mar 2014 10:56:48 +0800 [thread overview]
Message-ID: <20140327025647.GC16197@MrMyself> (raw)
In-Reply-To: <1e2d210764724c7e834c5307b54c37ab@BY2PR03MB505.namprd03.prod.outlook.com>
On Thu, Mar 27, 2014 at 10:53:50AM +0800, Xiubo Li-B47053 wrote:
> > On Thu, Mar 27, 2014 at 10:13:48AM +0800, Xiubo Li-B47053 wrote:
> > > > + regmap_read(sai->regmap, FSL_SAI_TCSR, &xcsr);
> > > > + regmap_write(sai->regmap, FSL_SAI_TCSR, xcsr);
> > > > +
> > > > + if (xcsr & FSL_SAI_CSR_WSF)
> > > > + dev_dbg(dev, "isr: Start of Tx word detected\n");
> > > > +
> > > > + if (xcsr & FSL_SAI_CSR_SEF)
> > > > + dev_dbg(dev, "isr: Tx Frame sync error detected\n");
> > > > +
> > > > + if (xcsr & FSL_SAI_CSR_FEF)
> > > > + dev_dbg(dev, "isr: Transmit underrun detected\n");
> > > > +
> > >
> > > Actually, the above three isrs should to write a logic 1 to this field
> > > to clear this flag.
> > >
> > >
> > > > + if (xcsr & FSL_SAI_CSR_FWF)
> > > > + dev_dbg(dev, "isr: Enabled transmit FIFO is empty\n");
> > > > +
> > > > + if (xcsr & FSL_SAI_CSR_FRF)
> > > > + dev_dbg(dev, "isr: Transmit FIFO watermark has been reached\n");
> > > > +
> > >
> > > While are these ones really needed to clear manually ?
> >
> > The reference manual doesn't mention about the requirement. So SAI should do
> > the self-clearance.
>
> Yes, I do think we should let it do the self-clearance, and shouldn't interfere
> of them...
SAI is supposed to ignore the interference, isn't it?
next prev parent reply other threads:[~2014-03-27 3:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 11:48 [PATCH] ASoC: fsl_sai: Add isr to deal with error flag Nicolin Chen
2014-03-26 11:59 ` David Laight
2014-03-27 1:14 ` Mark Brown
2014-03-27 2:29 ` [alsa-devel] " Nicolin Chen
2014-03-27 9:41 ` David Laight
2014-03-27 13:05 ` Mark Brown
2014-03-27 2:13 ` Li.Xiubo
2014-03-27 2:36 ` Nicolin Chen
2014-03-27 2:53 ` Li.Xiubo
2014-03-27 2:56 ` Nicolin Chen [this message]
2014-03-27 3:41 ` Li.Xiubo
2014-03-27 3:31 ` Nicolin Chen
2014-03-27 4:06 ` Li.Xiubo
2014-03-27 3:57 ` Nicolin Chen
2014-03-27 4:18 ` Li.Xiubo
2014-03-27 10:54 ` Mark Brown
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=20140327025647.GC16197@MrMyself \
--to=guangyu.chen@freescale.com \
--cc=Li.Xiubo@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 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).