public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Alastair Bridgewater <alastair.bridgewater@gmail.com>
Cc: Connor McAdams <conmanx360@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/6] ALSA: hda/ca0132: Various cleanups and fixes
Date: Tue, 19 Jun 2018 15:19:52 +0200	[thread overview]
Message-ID: <s5hsh5ioqvb.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAEcYz2QSL5n12zonud4oB9mAK7aL2cx7xD7hF0dYaCfL4gjzuQ@mail.gmail.com>

On Tue, 19 Jun 2018 15:18:41 +0200,
Alastair Bridgewater wrote:
> 
> On Sun, Jun 17, 2018 at 3:22 AM, Takashi Iwai <tiwai@suse.de> wrote:
> 
> > On Sat, 16 Jun 2018 03:56:14 +0200,
> > Alastair Bridgewater wrote:
> > >
> > > The ca0132 codec support is fairly crufty, and the new R3Di and SBZ
> > > support hasn't exactly improved that situation.  This patch series
> > > tries to clean up a small amount of longstanding cruft, reverse some
> > > behavioral changes to other systems made by the recent R3Di/SBZ
> > > patches, and make the DMic work properly on the Alienware M17x R4.
> > >
> > > For two of these patches (the QUIRK_ALIENWARE patch and the DMic
> > > patch), it may be that the correct behavior is the exact OPPOSITE of
> > > what the patch does as far as quirk testing goes (that is, it should
> > > apply globally, rather than limited to some specific quirk or set of
> > > quirks), but I have no way to make such a determination at this time,
> > > so erring on the side of the status quo ante seems appropriate.
> > >
> > > Alastair Bridgewater (6):
> > >   ALSA: hda/ca0132: Delete pointless assignments to struct auto_pin_cfg
> > >     fields
> > >   ALSA: hda/ca0132: Delete redundant UNSOL event requests
> > >   ALSA: hda/ca0132: Restore behavior of QUIRK_ALIENWARE
> > >   ALSA: hda/ca0132: Don't test for QUIRK_NONE
> > >   ALSA: hda/ca0132: Restore PCM Analog Mic-In2
> > >   ALSA: hda/ca0132: Fix DMic data rate for Alienware M17x R4
> >
> > Since these look like reasonable fixes, I applied all six patches as
> > is now.
> >
> > If any further fixes are needed, please make on top of these.
> >
> 
> Wonderful!  Thank you.  About the only other patch that I can see
> making at this point is to call ca0132_alt_vol_setup() on all systems,
> and I could go either way on that.
> 
> With a bit of luck, I may have another patch series in a month or so.
> Not suitable for 4.18, but maybe for 4.19 or so?

Yes, sounds like a plan.


thanks,

Takashi

      reply	other threads:[~2018-06-19 13:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-16  1:56 [PATCH 0/6] ALSA: hda/ca0132: Various cleanups and fixes Alastair Bridgewater
2018-06-16  1:56 ` [PATCH 1/6] ALSA: hda/ca0132: Delete pointless assignments to struct auto_pin_cfg fields Alastair Bridgewater
2018-06-16  1:56 ` [PATCH 2/6] ALSA: hda/ca0132: Delete redundant UNSOL event requests Alastair Bridgewater
2018-06-16  1:56 ` [PATCH 3/6] ALSA: hda/ca0132: Restore behavior of QUIRK_ALIENWARE Alastair Bridgewater
2018-06-16  2:21   ` Connor McAdams
2018-06-16 15:37   ` Connor McAdams
2018-06-17  0:56     ` Alastair Bridgewater
2018-06-17  1:57       ` Connor McAdams
2018-06-16  1:56 ` [PATCH 4/6] ALSA: hda/ca0132: Don't test for QUIRK_NONE Alastair Bridgewater
2018-06-16  2:20   ` Connor McAdams
2018-06-16  3:11     ` Alastair Bridgewater
2018-06-16  7:08     ` Takashi Iwai
2018-06-16  1:56 ` [PATCH 5/6] ALSA: hda/ca0132: Restore PCM Analog Mic-In2 Alastair Bridgewater
2018-06-16  1:56 ` [PATCH 6/6] ALSA: hda/ca0132: Fix DMic data rate for Alienware M17x R4 Alastair Bridgewater
2018-06-16  2:34   ` Connor McAdams
2018-06-17  7:22 ` [PATCH 0/6] ALSA: hda/ca0132: Various cleanups and fixes Takashi Iwai
2018-06-19 13:18   ` Alastair Bridgewater
2018-06-19 13:19     ` Takashi Iwai [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=s5hsh5ioqvb.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alastair.bridgewater@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=conmanx360@gmail.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