From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: getting dynamic state from ac97 bus ops
Date: Mon, 28 Mar 2011 11:33:15 +0100 [thread overview]
Message-ID: <20110328103314.GD4781@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTinFhaKBjwgbMr8BH5JhCzX-apBRZiHdveNg1+q9@mail.gmail.com>
On Mon, Mar 28, 2011 at 06:20:23AM -0400, Mike Frysinger wrote:
> this is state specific to the ac97 bus connection (snd_ac97_bus_ops),
> not the specific machine driver which links the codec to the
> transport, and currently all of these guys do it globally. which
> means only 1 AC97 codec can be in play in the system.
These drivers all predate multi-component and in many cases they only
physically support a single device.
> the Blackfin has multiple SPORTs and could do one AC97 codec per
> SPORT. but atm, there is only one global soc_ac97_ops structure, and
> i cant see how the functions in that structure could get at the
> link-specific state so that the bus driver would work with multiple
> AC97 codecs.
> granted, no customer that i know of has asked for this (more than AC97
> codec), it's just a limitation i noticed when working on an AC97
> driver, and i figured i might as well do it right while i'm cleaning
> so atm i have:
I wouldn't worry about it unless someone actually comes up with a
multi-CODEC embedded AC'97 system. New designs tend to be I2S based
rather than AC'97 based as the PC market moved away from AC'97 so
there's less benefit to designing with it - it's likely that any effort
spent here wouldn't actually benefit anyone.
prev parent reply other threads:[~2011-03-28 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 2:48 getting dynamic state from ac97 bus ops Mike Frysinger
2011-03-28 10:06 ` Mark Brown
2011-03-28 10:20 ` Mike Frysinger
2011-03-28 10:33 ` Mark Brown [this message]
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=20110328103314.GD4781@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=vapier.adi@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 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).