From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
subhransu.s.prusty@intel.com, lgirdwood@gmail.com
Subject: Re: [PATCH v3 4/6] ASoC: Intel: mrfld- add ACPI module
Date: Mon, 10 Nov 2014 11:48:31 +0530 [thread overview]
Message-ID: <20141110061831.GB18555@intel.com> (raw)
In-Reply-To: <20141106134426.GI8509@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 685 bytes --]
On Thu, Nov 06, 2014 at 01:44:26PM +0000, Mark Brown wrote:
> On Thu, Nov 06, 2014 at 06:39:09PM +0530, Vinod Koul wrote:
> > On Thu, Nov 06, 2014 at 12:43:49PM +0000, Mark Brown wrote:
> > > On Tue, Nov 04, 2014 at 04:25:18PM +0530, Vinod Koul wrote:
>
> > > No, we should be able to build a kernel which runs with or without ACPI
> > > - make this a runtime check if it's required (a comment might be in
> > > order too since this is a weird thing to do).
>
> > yes that is doable by adding a parameter and setting that in specfic probe,
> > will add.
>
> There's a variable acpi_disabled you can check.
Thanks, thats a very good suggestion indeed :)
--
~Vinod
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-11-10 6:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 10:55 [PATCH v3 0/6] ASoC: Intel: ACPI support and machines Vinod Koul
2014-11-04 10:55 ` [PATCH v3 1/6] ASoC: Intel: mrfld - remove unnecessary check for pointer Vinod Koul
2014-11-06 12:36 ` Mark Brown
2014-11-04 10:55 ` [PATCH v3 2/6] ASoC: Intel: mrfld - create separate module for pci part Vinod Koul
2014-11-06 12:36 ` Mark Brown
2014-11-04 10:55 ` [PATCH v3 3/6] ASoC: Intel: mrfld - add shim save restore Vinod Koul
2014-11-06 12:36 ` Mark Brown
2014-11-04 10:55 ` [PATCH v3 4/6] ASoC: Intel: mrfld- add ACPI module Vinod Koul
2014-11-06 12:43 ` Mark Brown
2014-11-06 13:09 ` Vinod Koul
2014-11-06 13:44 ` Mark Brown
2014-11-10 6:18 ` Vinod Koul [this message]
2014-11-04 10:55 ` [PATCH v3 5/6] ASoC: Intel: add BYTCR machine driver with RT5640 Vinod Koul
2014-11-06 12:48 ` Mark Brown
2014-11-06 13:11 ` Vinod Koul
2014-11-06 13:46 ` Mark Brown
2014-11-10 6:20 ` Vinod Koul
2014-11-10 10:03 ` Mark Brown
2014-11-04 10:55 ` [PATCH v3 6/6] ASoC: Intel: Add Merrifield machine driver Vinod Koul
2014-11-06 12:51 ` Mark Brown
2014-11-06 13:18 ` 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=20141110061831.GB18555@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=subhransu.s.prusty@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox