Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1401491
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC PATCH 2/7] ALSA: ac97: add an ac97 bus |
| Date | 2016-05-16 15:20 +0200 |
| Message-ID | <rzqBb-7x7-19@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <ryJwd-2VN-3@gated-at.bofh.it> <rzg8Y-u7-287@gated-at.bofh.it> <rzjzH-2Ul-1@gated-at.bofh.it> <rzmxz-4JQ-3@gated-at.bofh.it> <rzqhQ-7bz-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Mon, May 16, 2016 at 02:58:13PM +0200, Takashi Iwai wrote: > Robert Jarzmik wrote: > > Even if I'd like to not have these in bus operations, the struct snd_ac97 had a > > need for a 'caps', 'ext_id', ... fields for example. Yet these could be > > contained in the ac97_codec_device structure and not exposed to bus operations. > Do we have any example of such exceptions? For AC97, we don't need to > think of future extensions at all. I can't think of any, even for some of the more fancy CODECs used in embedded systems.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [RFC PATCH 2/7] ALSA: ac97: add an ac97 bus Robert Jarzmik <robert.jarzmik@free.fr> - 2016-05-14 12:00 +0200
Re: [RFC PATCH 2/7] ALSA: ac97: add an ac97 bus Takashi Iwai <tiwai@suse.de> - 2016-05-14 17:20 +0200
Re: [RFC PATCH 2/7] ALSA: ac97: add an ac97 bus Robert Jarzmik <robert.jarzmik@free.fr> - 2016-05-16 04:10 +0200
Re: [RFC PATCH 2/7] ALSA: ac97: add an ac97 bus Takashi Iwai <tiwai@suse.de> - 2016-05-16 07:50 +0200
Re: [RFC PATCH 2/7] ALSA: ac97: add an ac97 bus Robert Jarzmik <robert.jarzmik@free.fr> - 2016-05-16 11:00 +0200
Re: [RFC PATCH 2/7] ALSA: ac97: add an ac97 bus Takashi Iwai <tiwai@suse.de> - 2016-05-16 15:00 +0200
Re: [RFC PATCH 2/7] ALSA: ac97: add an ac97 bus Mark Brown <broonie@kernel.org> - 2016-05-16 15:20 +0200
csiph-web