mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Radoslaw Smigielski <radoslaw.smigielski@interia.pl>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	alsa-devel@alsa-project.org, corbet@lwn.net, tiwai@suse.com,
	perex@perex.cz
Subject: Re: [alsa-devel] [PATCH] ALSA: doc: fix snd_hda_intel driver name
Date: Thu, 13 Feb 2020 11:58:04 +0100	[thread overview]
Message-ID: <s5ha75mrbyb.wl-tiwai@suse.de> (raw)
In-Reply-To: <20200213103636.733463-1-radoslaw.smigielski@interia.pl>

On Thu, 13 Feb 2020 11:36:37 +0100,
Radoslaw Smigielski wrote:
> 
> Update driver name snd-hda-intel to proper, existing driver
> name snd_hda_intel in Documentation/sound/hd-audio/notes.rst.

snd-hda-intel is correct from the module file name POV.
Both are handled equivalently.


thanks,

Takashi

> 
> Signed-off-by: Radoslaw Smigielski <radoslaw.smigielski@interia.pl>
> ---
>  Documentation/sound/hd-audio/notes.rst | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/Documentation/sound/hd-audio/notes.rst b/Documentation/sound/hd-audio/notes.rst
> index 0f3109d9abc8..56ccc15f4d26 100644
> --- a/Documentation/sound/hd-audio/notes.rst
> +++ b/Documentation/sound/hd-audio/notes.rst
> @@ -17,12 +17,12 @@ methods for the	HD-audio hardware.
>  
>  The HD-audio component consists of two parts: the controller chip and 
>  the codec chips on the HD-audio bus.  Linux provides a single driver
> -for all controllers, snd-hda-intel.  Although the driver name contains
> +for all controllers, snd_hda_intel.  Although the driver name contains
>  a word of a well-known hardware vendor, it's not specific to it but for
>  all controller chips by other companies.  Since the HD-audio
>  controllers are supposed to be compatible, the single snd-hda-driver
>  should work in most cases.  But, not surprisingly, there are known
> -bugs and issues specific to each controller type.  The snd-hda-intel
> +bugs and issues specific to each controller type.  The snd_hda_intel
>  driver has a bunch of workarounds for these as described below.
>  
>  A controller may have multiple codecs.  Usually you have one audio
> @@ -31,7 +31,7 @@ multiple audio codecs, e.g. for analog and digital outputs, and the
>  driver might not work properly because of conflict of mixer elements.
>  This should be fixed in future if such hardware really exists.
>  
> -The snd-hda-intel driver has several different codec parsers depending
> +The snd_hda_intel driver has several different codec parsers depending
>  on the codec.  It has a generic parser as a fallback, but this
>  functionality is fairly limited until now.  Instead of the generic
>  parser, usually the codec-specific parser (coded in patch_*.c) is used
> @@ -226,7 +226,7 @@ the external amplifier bits.  Thus a headphone output has a slightly
>  better chance.
>  
>  Before making a bug report, double-check whether the mixer is set up
> -correctly.  The recent version of snd-hda-intel driver provides mostly
> +correctly.  The recent version of snd_hda_intel driver provides mostly
>  "Master" volume control as well as "Front" volume (where Front
>  indicates the front-channels).  In addition, there can be individual
>  "Headphone" and "Speaker" controls.
> @@ -596,7 +596,7 @@ For example, if you have two cards, one for an on-board analog and one
>  for an HDMI video board, you may pass patch option like below:
>  ::
>  
> -    options snd-hda-intel patch=on-board-patch,hdmi-patch
> +    options snd_hda_intel patch=on-board-patch,hdmi-patch
>  
>  
>  Power-Saving
> -- 
> 2.24.1
> 

  reply	other threads:[~2020-02-13 10:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 10:36 Radoslaw Smigielski
2020-02-13 10:58 ` Takashi Iwai [this message]
2020-02-13 11:43   ` Radoslaw Smigielski
2020-02-13 11:46     ` 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=s5ha75mrbyb.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=radoslaw.smigielski@interia.pl \
    --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

all inboxes | Powered by JetHome®