From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Shevchenko Subject: Re: [PATCH v2 1/3] ACPI / utils: Introduce acpi_dev_get_dev_name() Date: Fri, 05 Jan 2018 14:39:34 +0200 Message-ID: <1515155974.7000.735.camel@linux.intel.com> References: <20180104164709.64387-1-andriy.shevchenko@linux.intel.com> <20180104164709.64387-2-andriy.shevchenko@linux.intel.com> <1515154920.7000.732.camel@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-gpio-owner@vger.kernel.org To: "Rafael J. Wysocki" Cc: "Rafael J. Wysocki" , Erik Schmauss , ACPI Devel Maling List , Pierre-Louis Bossart , Liam Girdwood , Mark Brown , "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..." , Linus Walleij , linux-gpio@vger.kernel.org, Mika Westerberg List-Id: alsa-devel@alsa-project.org On Fri, 2018-01-05 at 13:34 +0100, Rafael J. Wysocki wrote: > On Fri, Jan 5, 2018 at 1:22 PM, Andy Shevchenko > wrote: > > On Fri, 2018-01-05 at 13:06 +0100, Rafael J. Wysocki wrote: > > > On Thu, Jan 4, 2018 at 5:47 PM, Andy Shevchenko > > > wrote: > > "Subset of Intel ASoC drivers is an existing user of this API when > > they > > need to find an actual instance of the codec device based on its > > ACPI > > HID." > > And why do they need the name (and not something else)? I don't know the guts of Intel ASoC implementation, so, can't answer this without investigation. Pierre, can you elaborate this piece? > > So, acpi_dev_get_name() then? > > It would be somewhat clearer to call it > acpi_dev_get_first_match_name() IMO. > > Otherwise it may not be clear what name this is going to return. Works for me. -- Andy Shevchenko Intel Finland Oy