All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, yadi brar <yadi.brar01@gmail.com>,
	alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: Emulated IEC958 Card
Date: Fri, 17 Sep 2010 13:47:02 +0100	[thread overview]
Message-ID: <20100917124702.GE4322@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <AANLkTim3+i3zFC=G6tZyBf_wQf9C2xy2K0SYb5jfXF=j@mail.gmail.com>

On Fri, Sep 17, 2010 at 09:42:46PM +0900, Jassi Brar wrote:
> On Fri, Sep 17, 2010 at 9:27 PM, Mark Brown

> > The idea of having a full IEC958 emulation layer that just needs a
> > generic serial port or shifter accessed through some standard interface
> > seems entirely sensible.  This isn't so different to what things like
> > the McBSP, PXA SSP or FSL SSI ports do.

> Yup, I knew those features but am unaware of any situation where they drive out
> IEC958 - they just run I2S, SPI, TDM (?)

Me either, I just meant that this is a well known model for structuring
this sort of hardware and software so it should be a good model to
follow.

> Also, IMO, it would make more sense to implement it as a Virtual card
> independent
> of ASoC(outside of linux/sound/soc/), with number of devices equalling
> the number
> of shifters registered.

I agree, though it would be nice to have some facility for implementing
an interface between the two since you can get IEC958 I/O on ASoC
CODECs.  I don't think that's needed at first pass, but it may come up
at some point.

  reply	other threads:[~2010-09-17 12:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 14:05 Emulated IEC958 Card Jassi Brar
2010-09-17 12:20 ` Jassi Brar
2010-09-17 12:27   ` Mark Brown
2010-09-17 12:42     ` Jassi Brar
2010-09-17 12:47       ` Mark Brown [this message]
2010-09-17 13:01         ` Jassi Brar

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=20100917124702.GE4322@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=tiwai@suse.de \
    --cc=yadi.brar01@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.