[alsa-devel] [PATCH v2 1/3] ACPI / utils: Introduce acpi_dev_get_dev_name()
Andy Shevchenko
andriy.shevchenko at linux.intel.com
Fri Jan 5 13:43:55 CET 2018
On Thu, 2018-01-04 at 18:47 -0600, Pierre-Louis Bossart wrote:
>
> On 01/04/2018 10:47 AM, Andy Shevchenko wrote:
> > Sometimes the user want to have device name of the match rather than
> > just checking if device present or not. To make life easier for such
> > users introduce acpi_dev_get_dev_name() helper based on code for
> > acpi_dev_present().
> >
> > To be more consistent with the purpose rename
> >
> > struct acpi_dev_present_info -> struct acpi_dev_match_info
> > acpi_dev_present_cb() -> acpi_dev_match_cb()
> >
> > in the utils.c file.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko at linux.intel.com>
>
> This works fine on a Dell 5585 where the default codec dai name needs
> to
> be updated based on the actual HID information, so
> Tested-by: Pierre-Louis Bossart <pierre-louis.bossart at linux.intel.com>
Thanks!
Is this only for patch 1, or for both 1 and 2 ?
> the next patch does not apply directly however, and needs additional
> changes for the ES8316 machine driver. see the changes here:
> https://github.com/plbossart/sound/tree/topic/bytcht-acpi-fixes
You mean because of this
https://github.com/plbossart/sound/commit/2416827fa6d221b27edd6397f17daa
a1f3cd5fb0
?
I.e. I need to rebase on top of your series.
> It's probably best to let this patch go through the acpi tree, and
> the
> next one through Mark's tree once the first is merged and all the
> other
> Kconfig/acpi stuff is also in -next?
It wouldn't prevent to push patch 3 as well via linux-pm at the same
time as patch 1.
Linus, do you have any objection on that?
--
Andy Shevchenko <andriy.shevchenko at linux.intel.com>
Intel Finland Oy
More information about the Alsa-devel
mailing list