From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarkko Nikula Subject: Re: [RFC] ASoC: core: Allow DAI links to be specified by using ACPI names Date: Fri, 04 Oct 2013 10:38:10 +0300 Message-ID: <524E7062.10405@linux.intel.com> References: <1380803636-24079-1-git-send-email-jarkko.nikula@linux.intel.com> <20131003161929.GA27287@sirena.org.uk> <524E600B.4070202@linux.intel.com> <1674991.zl8kYFEb4V@vostro.rjw.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1674991.zl8kYFEb4V@vostro.rjw.lan> Sender: linux-acpi-owner@vger.kernel.org To: "Rafael J. Wysocki" Cc: Mark Brown , alsa-devel@alsa-project.org, linux-acpi@vger.kernel.org, Liam Girdwood , Mika Westerberg List-Id: alsa-devel@alsa-project.org On 10/04/2013 09:55 AM, Rafael J. Wysocki wrote: > You're misreading my suggestion. What I'm saying is that it seems like > it might be useful to have dev_name() return the ACPI name - this would > mean that everything, including all the dev_ prints, would use the same > name which would then become stable and tied to hardware. >> I see. Indeed, this sounds a better idea. At quick look is even more simple. > Well, this is slightly ambiguous. What exactly do you mean by "ACPI names"? > Ah, yes. What I meant as ACPI name was the based ACPI device name/object (or what is the correct terminology), not the hardware ID. -- Jarkko