From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Matt Sealey <matt@genesi-usa.com>,
Robert Schwebel <r.schwebel@pengutronix.de>,
Anton Vorontsov <anton.vorontsov@linaro.org>,
Russell King <linux@arm.linux.org.uk>,
John Stultz <john.stultz@linaro.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linaro-kernel@lists.linaro.org,
Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [PATCH 4/9] ASoC: imx: Don't use {en,dis}able_fiq() calls
Date: Tue, 7 Aug 2012 17:50:20 +0100 [thread overview]
Message-ID: <20120807165019.GT16861@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120807063558.GE1451@pengutronix.de>
On Tue, Aug 07, 2012 at 08:35:58AM +0200, Sascha Hauer wrote:
> Nowadays the FIQ support is necessary only for AC97. The AC97 support in
> the SSI unit is buggy: It does not allow you to select the slots you
> want to receive. At least the wm9712 codec always sends (apart from the
> stereo data) data in slot (I think it is) 12. You find this data mixed
> in your audio stream. The FIQ driver skips this data to get a valid
> audio stream.
Right, any device with GPIO support will do this - it's how GPIO works
in AC'97.
> One other way to solve this would be to use dma here and to filter out
> the data afterwards.
Yup. That's probably more sane but also more work to implement.
next prev parent reply other threads:[~2012-08-07 16:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 23:02 [PATCH 0/9] Get rid of FIQ_START/enable/disable_fiq() + some FIQ cleanups Anton Vorontsov
2012-08-05 23:03 ` [PATCH 1/9] ARM: mach-rpc: Don't register FIQs with genirq Anton Vorontsov
2012-08-05 23:03 ` [PATCH 2/9] ARM: plat-s3c24xx: Don't use FIQ_START Anton Vorontsov
2012-08-08 10:47 ` Kukjin Kim
2012-08-08 11:00 ` Anton Vorontsov
2012-08-05 23:03 ` [PATCH 3/9] [media] mx1_camera: Don't use {en,dis}able_fiq() calls Anton Vorontsov
2012-08-08 6:57 ` Sascha Hauer
2012-08-05 23:03 ` [PATCH 4/9] ASoC: imx: " Anton Vorontsov
2012-08-06 15:19 ` Matt Sealey
2012-08-06 15:49 ` Mark Brown
2012-08-06 18:09 ` Matt Sealey
2012-08-06 19:37 ` Mark Brown
2012-08-06 20:16 ` Robert Schwebel
2012-08-06 20:39 ` Matt Sealey
2012-08-06 21:41 ` Mark Brown
2012-08-06 23:26 ` Matt Sealey
2012-08-07 6:35 ` Sascha Hauer
2012-08-07 16:50 ` Mark Brown [this message]
2012-08-07 2:09 ` Shawn Guo
2012-08-07 16:48 ` Dave Martin
2012-08-08 6:57 ` Sascha Hauer
2012-08-05 23:03 ` [PATCH 5/9] ARM: FIQ: Remove enable_fiq() and disable_fiq() calls Anton Vorontsov
2012-08-05 23:03 ` [PATCH 6/9] ARM: FIQ: Remove FIQ_START Anton Vorontsov
2012-08-05 23:03 ` [PATCH 7/9] ARM: FIQ: Should include asm/mach/irq.h Anton Vorontsov
2012-08-05 23:03 ` [PATCH 8/9] ARM: FIQ: Implement !CONFIG_FIQ stubs Anton Vorontsov
2012-08-05 23:03 ` [PATCH 9/9] ARM: FIQ: Make show_fiq_list() return void Anton Vorontsov
2012-08-26 4:24 ` [PATCH 0/9] Get rid of FIQ_START/enable/disable_fiq() + some FIQ cleanups Anton Vorontsov
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=20120807165019.GT16861@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=anton.vorontsov@linaro.org \
--cc=john.stultz@linaro.org \
--cc=kernel@pengutronix.de \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=matt@genesi-usa.com \
--cc=r.schwebel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
/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).