From: Vinod Koul <vinod.koul@intel.com>
To: David Henningsson <david.henningsson@canonical.com>
Cc: tiwai@suse.de, patches.audio@intel.com,
alsa-devel@alsa-project.org, broonie@kernel.org,
lgirdwood@gmail.com
Subject: Re: [RFC 0/3] ALSA: Add soc hda bus support
Date: Tue, 14 Apr 2015 09:52:37 +0530 [thread overview]
Message-ID: <20150414042237.GC2963@intel.com> (raw)
In-Reply-To: <5524CAA9.8030209@canonical.com>
On Wed, Apr 08, 2015 at 08:28:57AM +0200, David Henningsson wrote:
>
>
> 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.
Sure, as we discussed in last meeting, the SKL audio controller is HDA audio
controller which also supports a DSP and I2S ports. Although if you get a
SKL board with a HDA codec you can bypass DSP and it will work as previuos
gen Intel HDA controller so current hda code works well for "legacy" HDA
mode
Now we are moving bits and pieces out of current hda code into hdac layer
(hda-core) which will be used by SKL ASoC driver as well as current
implementations.
So first remaining parts of hdac will be merged follow by asoc wrappers,
then SKL controller driver and fllowed up by DSP and I2S support.
> 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.
some of the RT codecs support both HDA and I2S, but right now merging them
is not in my radar but yes it is doable and I will look into this once base
driver and merged
>
> But I still feel I'm missing the bigger roadmap here. Anyone who
> wants to enlighten me? :-)
Hope this would have helped, do let me know if you have more questions :)
--
~Vinod
prev parent reply other threads:[~2015-04-14 4:27 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 ` [RFC 0/3] ALSA: Add soc hda bus support David Henningsson
2015-04-14 4:22 ` Vinod Koul [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=20150414042237.GC2963@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=david.henningsson@canonical.com \
--cc=lgirdwood@gmail.com \
--cc=patches.audio@intel.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.