From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH v2 0/2] ALSA: hda: add module flag snd_adsp_enable
Date: Mon, 22 Jun 2015 16:28:35 +0530 [thread overview]
Message-ID: <20150622105835.GD19530@localhost> (raw)
In-Reply-To: <s5hioak9bf1.wl-tiwai@suse.de>
On Fri, Jun 19, 2015 at 01:37:22PM +0200, Takashi Iwai wrote:
> At Thu, 18 Jun 2015 12:08:23 +0530,
> Vinod Koul wrote:
> >
> > This is second attempt for creating a module option for hda core to
> > select either legacy HDA driver or upcoming ASoC driver. This series
> > still relies on module flag (with feedback from previous series baked
> > in). The eventual plan is to rely on HW advertised capabilities and
> > BIOS configuration to load either driver, but since ASoC driver has
> > still some time to get fully merged and matured on various system, we
> > will rely on module flag till the who ASoC HDA systems is completed
> > and available is all distros
>
> Well, somehow I prefer postponing this. The method would work but is
> indeed hackish, so let's put this together with other pieces as a last
> resort unless any better solution is found. For the driver
> development itself, this isn't really needed; you can put blacklist at
> any time.
Okay blacklist will work too...
--
~Vinod
prev parent reply other threads:[~2015-06-22 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 6:38 [PATCH v2 0/2] ALSA: hda: add module flag snd_adsp_enable Vinod Koul
2015-06-18 6:38 ` [PATCH v2 1/2] ALSA: hda: add snd_adsp_enable module flag Vinod Koul
2015-06-18 6:38 ` [PATCH v2 2/2] ALSA: hda: use snd_adsp_enable in HDA driver Vinod Koul
2015-06-19 11:37 ` [PATCH v2 0/2] ALSA: hda: add module flag snd_adsp_enable Takashi Iwai
2015-06-22 10:58 ` 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=20150622105835.GD19530@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.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.