Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kusanagi Kouichi <slash@ma.neweb.ne.jp>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: hda - Add digital BEEP	generator	support for Realtek codecs.
Date: Wed, 04 Feb 2009 12:17:14 +0100	[thread overview]
Message-ID: <s5hocxia1tx.wl%tiwai@suse.de> (raw)
In-Reply-To: <200902040837524161510006MA49@nm06mta.auone-net.jp>

At Wed, 4 Feb 2009 17:37:51 +0900,
Kusanagi Kouichi wrote:
> 
> On Tue, Feb 03, 2009 at 03:36:20PM +0100, Takashi Iwai wrote:
> > > > Another concern is that I don't want to add the digital beep control
> > > > unconditionally.  On many devices, the beep is implemented in the old
> > > > good analog way.  We'd need to add the check of analog/digital beep in
> > > > a new spec field and in the preset table not to duplicate beep
> > > > controls on these.
> > > 
> > > I don't think such a check is needed.  I presume that analog beep in
> > > is disabled while digital beep generetor is being used.
> > > Furthermore, keyboard bell rings only one device even if both
> > > HDA Digital PCBeep and PC Speaker have been registered.
> > 
> > However it's just annoying to have multiple controls for the very same
> > purpose.  If the digital beep works more reliably overall, let's get
> > rid of all existing analog beep stuff.  Having both makes no sense.
> > 
> > (Well, I don't remember exactly your patch so I suppose your patch
> >  doesn't remove the analog beep stuff...  Anyway reposting the patch
> >  and checking it's still applicable to the latest driver code would be
> >  helpful :)
> 
> Ah! I see the point. There is no duplicated control because I didn't
> add any new controls. Existing beep control controls digital beep, too.
> Analog beep and digital beep look to be routed through the same path.

Fair enough.

Though, there is still one problem -- not all models enabled the
analog beep path.  So, the next step is to create beep controls in all
possible situations.

But I'm going to apply your patch as now.
Could you repost the patch with a proper summary, a changelog text and
your sign-off so that I can apply it as is?


thanks,

Takashi

  reply	other threads:[~2009-02-04 11:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 14:28 [PATCH] ALSA: hda - Add digital BEEP generator support for Realtek codecs Kusanagi Kouichi
2009-02-03 14:36 ` Takashi Iwai
2009-02-04  8:37   ` Kusanagi Kouichi
2009-02-04 11:17     ` Takashi Iwai [this message]
2009-02-04 14:20       ` Kusanagi Kouichi
2009-02-04 14:44         ` Takashi Iwai
2009-02-06 16:25           ` Takashi Iwai
2009-02-07 10:40             ` Kusanagi Kouichi
2009-02-07 11:54               ` Takashi Iwai
2009-02-10 14:53                 ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2008-11-15  6:20 Kusanagi Kouichi
2008-11-17 16:53 ` 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=s5hocxia1tx.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=slash@ma.neweb.ne.jp \
    /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