From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Wan ZongShun <mcuos.com@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Ben Dooks <ben-linux@fluff.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] NUC900/audio: add nuc900 audio driver support
Date: Mon, 17 May 2010 06:46:22 -0700 [thread overview]
Message-ID: <20100517134622.GA5257@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4BF0E184.204@gmail.com>
On Mon, May 17, 2010 at 02:26:12PM +0800, Wan ZongShun wrote:
> >On Sun, May 16, 2010 at 11:34:01PM +0800, Wan ZongShun wrote:
> >>+ if (!(AUDIO_READ(nuc900_audio->mmio + ACTL_ACIS0) & CODEC_READY))
> >>+ dev_err(nuc900_audio->dev, "AC97 codec cold reset failed!\n");
> >What is this actually checking in the hardware? Not all CODECs enable
> >the AC97 link by default after a cold reset, the standard allows them to
> >power up in a low power state which will
> The bit 'CODEC_READY' indicates the external AC97 audio CODEC is ready,
> I just forget to implement the warm reset operation, if need, I will do
> it. In addition, Can I add the checking CODEC_READY operation to
> warm reset function?
That sounds fine. For defensiveness it might be worth checking the
CODEC on register reads and writes too (it'd make diagnostics a bit
easier).
> >>+#define IIS_EN 0x0002
> >Looks like there's I2S support to come?
> Yes,nuc900 supports both IIS and AC97,but my board only enable AC97 support,
> what's up here?
Nothing, just curious.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] NUC900/audio: add nuc900 audio driver support
Date: Mon, 17 May 2010 06:46:22 -0700 [thread overview]
Message-ID: <20100517134622.GA5257@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4BF0E184.204@gmail.com>
On Mon, May 17, 2010 at 02:26:12PM +0800, Wan ZongShun wrote:
> >On Sun, May 16, 2010 at 11:34:01PM +0800, Wan ZongShun wrote:
> >>+ if (!(AUDIO_READ(nuc900_audio->mmio + ACTL_ACIS0) & CODEC_READY))
> >>+ dev_err(nuc900_audio->dev, "AC97 codec cold reset failed!\n");
> >What is this actually checking in the hardware? Not all CODECs enable
> >the AC97 link by default after a cold reset, the standard allows them to
> >power up in a low power state which will
> The bit 'CODEC_READY' indicates the external AC97 audio CODEC is ready,
> I just forget to implement the warm reset operation, if need, I will do
> it. In addition, Can I add the checking CODEC_READY operation to
> warm reset function?
That sounds fine. For defensiveness it might be worth checking the
CODEC on register reads and writes too (it'd make diagnostics a bit
easier).
> >>+#define IIS_EN 0x0002
> >Looks like there's I2S support to come?
> Yes,nuc900 supports both IIS and AC97,but my board only enable AC97 support,
> what's up here?
Nothing, just curious.
next prev parent reply other threads:[~2010-05-17 13:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 15:34 [PATCH] NUC900/audio: add nuc900 audio driver support Wan ZongShun
2010-05-16 15:34 ` Wan ZongShun
2010-05-17 2:44 ` Mark Brown
2010-05-17 2:44 ` Mark Brown
2010-05-17 6:26 ` Wan ZongShun
2010-05-17 6:26 ` Wan ZongShun
2010-05-17 13:46 ` Mark Brown [this message]
2010-05-17 13:46 ` Mark Brown
2010-05-17 21:53 ` Wan ZongShun
2010-05-17 21:53 ` Wan ZongShun
2010-05-18 2:59 ` [PATCH v2] " Wan ZongShun
2010-05-18 2:59 ` Wan ZongShun
2010-05-18 5:36 ` Wan ZongShun
2010-05-18 5:36 ` Wan ZongShun
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=20100517134622.GA5257@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lrg@slimlogic.co.uk \
--cc=mcuos.com@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 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.