From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel <alsa-devel@alsa-project.org>,
Timur Tabi <timur@freescale.com>,
Nobin Mathew <nobin.mathew@gmail.com>
Subject: Re: [RFC][ASoC] New device/driver arch
Date: Fri, 15 Jun 2007 10:04:19 +0100 [thread overview]
Message-ID: <1181898259.26658.53.camel@localhost.localdomain> (raw)
In-Reply-To: <20070614180656.GA22664@roarinelk.homelinux.net>
On Thu, 2007-06-14 at 20:06 +0200, Manuel Lauss wrote:
> Hi Liam,
>
> Is it possible to have 2 physical I2S units (which are connected to the same
> codec) be repesented as a single ASoC device? (The SH7760 has 2 I2S units
> which are "halfduplex" (only transmit OR capture at a time). My dev platform
> simply uses the second unit for capture
>
Yes. I would create two struct snd_soc_device_drivers in your i2s.c
file. The first would be the driver for the 2 halfduplex I2S units and
the second would be a full duplex driver for a merged I2S controller
(made up of the 2 halfduplex units). This way a device can either probe
against the halfduplex or full duplex driver based on the driver ID.
>
> I need a trigger callback in the machine driver to properly support
> multichannel I2S audio on Au1200 (the Au1200 can only do stereo; to get
> more channels we double/quadruple the I2S LRCLK coming from the codec;
> however the CPLD needs to be told when a new sample starts; although
> maybe that can be worked around in VHDL)
>
I'll add trigger. Probably easier to do this in C than VHDL ;)
Liam
next prev parent reply other threads:[~2007-06-15 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 17:40 [RFC][ASoC] New device/driver arch Liam Girdwood
2007-06-14 18:06 ` Manuel Lauss
2007-06-15 9:04 ` Liam Girdwood [this message]
2007-06-15 12:06 ` Nobin Mathew
2007-06-15 15:40 ` Liam Girdwood
2007-06-15 15:01 ` Seth Forshee
2007-06-15 15:36 ` Liam Girdwood
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=1181898259.26658.53.camel@localhost.localdomain \
--to=lg@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=mano@roarinelk.homelinux.net \
--cc=nobin.mathew@gmail.com \
--cc=timur@freescale.com \
--cc=tiwai@suse.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 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.