From: David Henningsson <david.henningsson@canonical.com>
To: Vinod Koul <vinod.koul@intel.com>, alsa-devel@alsa-project.org
Cc: tiwai@suse.de, broonie@kernel.org, lgirdwood@gmail.com,
pathes.audio@intel.com
Subject: Re: [RFC 0/3] ALSA: Add soc hda bus support
Date: Wed, 08 Apr 2015 08:28:57 +0200 [thread overview]
Message-ID: <5524CAA9.8030209@canonical.com> (raw)
In-Reply-To: <1427968651-7821-1-git-send-email-vinod.koul@intel.com>
On 2015-04-02 11:57, Vinod Koul wrote:
> This series of 3 patches adds support for ASoC HDA
> bus. ASoC HDA bus is essentially a wrapper for
> HDA core bus and it manages ASoC hda drivers
Hi,
I'm seeing several patch sets - as well as the added hdac indirection
layer earlier - related to HDA and ASoC. But I'm curious about the
bigger picture here.
In addition, I notice the rt286/rt288 ASoC driver looks very much
hda-like, i e, we're in practice sending HDA commands over an i2s (or
i2c) bus.
Adding two and two together it could mean you're trying to move
rt286/rt288 over to use the hda codec driver (which would be awesome!).
And perhaps other, similar ASoC codecs as well, if there are any.
But I still feel I'm missing the bigger roadmap here. Anyone who wants
to enlighten me? :-)
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next prev parent reply other threads:[~2015-04-08 6:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 9:57 [RFC 0/3] ALSA: Add soc hda bus support Vinod Koul
2015-04-02 9:57 ` [RFC 1/3] ALSA: hda - remove assigning dev type inside core Vinod Koul
2015-04-04 12:18 ` Takashi Iwai
2015-04-02 9:57 ` [RFC 2/3] ALSA: hda - add ASoC device type for hda core Vinod Koul
2015-04-02 9:57 ` [RFC 3/3] ALSA: hda - add soc hda bus wrapper Vinod Koul
2015-04-04 12:31 ` Takashi Iwai
2015-04-06 17:08 ` Mark Brown
2015-04-08 4:47 ` Ramesh Babu
2015-04-08 4:47 ` [alsa-devel] " Ramesh Babu
2015-04-08 6:28 ` David Henningsson [this message]
2015-04-14 4:22 ` [RFC 0/3] ALSA: Add soc hda bus support Vinod Koul
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=5524CAA9.8030209@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=pathes.audio@intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.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.