linux-kernel - Re: [PATCH 3/3] ALSA: hda/tegra: sound card name from device tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <s5hbm346tp7.wl-tiwai@suse.de>
Date:   Fri, 22 Feb 2019 10:47:16 +0100
From:   Takashi Iwai <tiwai@...e.de>
To:     "Sameer Pujar" <spujar@...dia.com>
Cc:     <mark.rutland@....com>, <robh+dt@...nel.org>, <perex@...ex.cz>,
        <alsa-devel@...a-project.org>, <thierry.reding@...il.com>,
        <jonathanh@...dia.com>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH 3/3] ALSA: hda/tegra: sound card name from device tree

On Wed, 20 Feb 2019 16:13:24 +0100,
Sameer Pujar wrote:
> 
> A platform can have multiple sound cards for different audio paths.
> Following is the print seen duirng device boot for jetson-xavier,
>   ALSA device list:
>     #0: nvidia,p2972-0000 at 0x3518000 irq 17
> By looking at above, it is not very clear if the sound card is for
> HDA. It becomes confusing when platform has registered multiple cards,
> and platform model name is used for card.
> 
> This patch uses "nvidia,model" property mentioned in hda device tree
> to get the card name. Since property is optional, legacy boards will
> continue to use "tegra-hda". Custom name can be passed wherever needed.
> This naming convention is conistent with the way sound cards are named
> in general.
> 
> Signed-off-by: Sameer Pujar <spujar@...dia.com>
> Reviewed-by: Jonathan Hunter <jonathanh@...dia.com>

Applied, thanks.


Takashi