linux-kernel - Re: [PATCH 5/5] Input: arizona-haptics - Use SoC component pin control functions

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20161128185357.GA28810@dtor-glaptop>
Date:   Mon, 28 Nov 2016 10:53:57 -0800
From:   Dmitry Torokhov <dmitry.torokhov@...il.com>
To:     Richard Fitzgerald <rf@...nsource.wolfsonmicro.com>
Cc:     broonie@...nel.org, cw00.choi@...sung.com,
        linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
        patches@...nsource.wolfsonmicro.com, myungjoo.ham@...sung.com,
        linux-input@...r.kernel.org
Subject: Re: [PATCH 5/5] Input: arizona-haptics - Use SoC component pin
 control functions

Hi Richard,

On Mon, Nov 28, 2016 at 05:32:30PM +0000, Richard Fitzgerald wrote:
> The name of a codec pin can have an optional prefix string, which is
> defined by the SoC machine driver. The snd_soc_dapm_x_pin functions
> take the fully-specified name including the prefix and so the existing
> code would fail to find the pin if the audio machine driver had added
> a prefix.
> 
> Switch to using the snd_soc_component_x_pin equivalent functions that
> take a specified SoC component and automatically add the name prefix to
> the provided pin name.
> 
> Signed-off-by: Richard Fitzgerald <rf@...nsource.wolfsonmicro.com>

If ASOC folks are fine with this then I am otto. Please merge with the rest of
Arizona changes.

Acked-by: Dmitry Torokhov <dmitry.torokhov@...il.com>

Thanks.

-- 
Dmitry