From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Nikhil Mahale <nmahale@nvidia.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: Re: [alsa-devel] [PATCH 0/4] ALSA: hda/hdmi: Clean up jack handling
Date: Fri, 7 Feb 2020 17:48:08 +0200 (EET) [thread overview]
Message-ID: <alpine.DEB.2.21.2002071744030.2957@eliteleevi.tm.intel.com> (raw)
In-Reply-To: <20200206162804.4734-1-tiwai@suse.de>
Hi,
On Thu, 6 Feb 2020, Takashi Iwai wrote:
> this is a series of cleanup of the jack handling in HD-audio HDMI
> codec driver, which I realized after the recent regression fix.
another welcome change to the hda/hdmi code!
For patches 1, 3 and 4:
Reviewed-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
For second patch, the code modified is less familiar to me, so review
will take more time. Great if Nikhil you can go over this.
I did do a test of the whole series with SOF on some devices and no
regressions found.
Br, Kai
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2020-02-07 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 16:28 [alsa-devel] [PATCH 0/4] ALSA: hda/hdmi: Clean up jack handling Takashi Iwai
2020-02-06 16:28 ` [alsa-devel] [PATCH 1/4] ALSA: hda/hdmi: Reduce hda_jack_tbl lookup at unsol event handling Takashi Iwai
2020-02-10 3:39 ` Nikhil Mahale
2020-02-06 16:28 ` [alsa-devel] [PATCH 2/4] ALSA: hda/hdmi: Don't use standard hda_jack for generic HDMI jacks Takashi Iwai
2020-02-10 5:08 ` Nikhil Mahale
2020-02-06 16:28 ` [alsa-devel] [PATCH 3/4] ALSA: hda/hdmi: Move runtime PM resume into hdmi_present_sense_via_verbs() Takashi Iwai
2020-02-10 5:09 ` Nikhil Mahale
2020-02-06 16:28 ` [alsa-devel] [PATCH 4/4] ALSA: hda/hdmi: Move ELD parse and jack reporting into update_eld() Takashi Iwai
2020-02-10 5:16 ` Nikhil Mahale
2020-02-07 15:48 ` Kai Vehmanen [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=alpine.DEB.2.21.2002071744030.2957@eliteleevi.tm.intel.com \
--to=kai.vehmanen@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=nmahale@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.