public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>, <tiwai@suse.com>,
	<perex@perex.cz>
Cc: <linux-sound@vger.kernel.org>,
	<pierre-louis.bossart@linux.intel.com>, <broonie@kernel.org>
Subject: Re: [PATCH] ALSA/hda: intel-dsp-config: Document AVS as dsp_driver option
Date: Fri, 7 Jun 2024 09:41:53 +0200	[thread overview]
Message-ID: <0c9116a7-58b3-4e2a-b257-162a57a02bd7@intel.com> (raw)
In-Reply-To: <20240607060021.11503-1-peter.ujfalusi@linux.intel.com>

On 2024-06-07 8:00 AM, Peter Ujfalusi wrote:
> dsp_driver=4 will force the AVS driver stack to be used, it is better to
> docuement this.
> 
> Fixes: 1affc44ea5dd ("ASoC: Intel: avs: PCI driver implementation")
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
> ---
>   sound/hda/intel-dsp-config.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/sound/hda/intel-dsp-config.c b/sound/hda/intel-dsp-config.c
> index 537863447358..478d2b50c571 100644
> --- a/sound/hda/intel-dsp-config.c
> +++ b/sound/hda/intel-dsp-config.c
> @@ -18,7 +18,7 @@
>   static int dsp_driver;
>   
>   module_param(dsp_driver, int, 0444);
> -MODULE_PARM_DESC(dsp_driver, "Force the DSP driver for Intel DSP (0=auto, 1=legacy, 2=SST, 3=SOF)");
> +MODULE_PARM_DESC(dsp_driver, "Force the DSP driver for Intel DSP (0=auto, 1=legacy, 2=SST, 3=SOF, 4=AVS)");
>   
>   #define FLAG_SST			BIT(0)
>   #define FLAG_SOF			BIT(1)

Reviewed-by: Cezary Rojewski <cezary.rojewski@intel.com>

  reply	other threads:[~2024-06-07  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  6:00 [PATCH] ALSA/hda: intel-dsp-config: Document AVS as dsp_driver option Peter Ujfalusi
2024-06-07  7:41 ` Cezary Rojewski [this message]
2024-06-13 12:11 ` Takashi Iwai

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=0c9116a7-58b3-4e2a-b257-162a57a02bd7@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=broonie@kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox