From mboxrd@z Thu Jan 1 00:00:00 1970 From: zhengxing Subject: Re: [PATCH 1/2] ASoC: rockchip: Add machine driver for max98090 codec Date: Fri, 17 Jul 2015 10:17:25 +0800 Message-ID: <55A865B5.7020609@rock-chips.com> References: <1436930143-31361-1-git-send-email-zhengxing@rock-chips.com> <1436930143-31361-2-git-send-email-zhengxing@rock-chips.com> <1437033944.27428.11.camel@tiscali.nl> <20150716110032.GU11162@sirena.org.uk> <1437047261.28351.6.camel@tiscali.nl> <20150716125529.GG4039@sirena.org.uk> <1437056116.28351.19.camel@tiscali.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; Format="flowed" Content-Transfer-Encoding: base64 Return-path: Received: from regular1.263xmail.com (regular1.263xmail.com [211.150.99.135]) by alsa0.perex.cz (Postfix) with ESMTP id CD92F26062E for ; Fri, 17 Jul 2015 04:23:34 +0200 (CEST) In-Reply-To: <1437056116.28351.19.camel@tiscali.nl> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Paul Bolle Cc: alsa-devel@alsa-project.org, heiko@sntech.de, Takashi Iwai , linux-kernel@vger.kernel.org, dianders@chromium.org, Liam Girdwood , linux-rockchip@lists.infradead.org, Mark Brown , dgreid@chromium.org, sonnyrao@chromium.org, linux-arm-kernel@lists.infradead.org List-Id: alsa-devel@alsa-project.org SGkgUGF1bCwKT24gMjAxNeW5tDA35pyIMTbml6UgMjI6MTUsIFBhdWwgQm9sbGUgd3JvdGU6Cj4K PiBUaGF0J3MgZXhhY3RseSBob3cgSSB1bmRlcnN0b29kIE1PRFVMRV9BTElBUygpIHRvIHdvcmsu Cj4KPiBBbmQgaXQgd29ya3MsIGluIHNob3J0LCBiZWNhdXNlIGEgcGxhdGZvcm0gZGV2aWNlIGZp cmVzIGEKPiAiTU9EQUxJQVM9cGxhdGZvcm06Wy4uLl0iIHVldmVudCB3aGVuIGl0J3MgY3JlYXRl ZC4gQW5kIHVzZXJzcGFjZSB1c2VzCj4gdGhhdCB1ZXZlbnQgdG8gbG9hZCB0aGUgbW9kdWxlIGNh cnJ5aW5nIHRoYXQgYWxpYXMuCj4KPiBMZXQncyBwdXQgaXQgdGhpcyB3YXMuIElmIG9uZSBkb2Vz Cj4gICAgICBzdWRvIGZpbmQgL3N5cyAtcGVybSAtbz1yIC1uYW1lIHVldmVudCAtZXhlYyBncmVw IC1IIE1PREFMSUFTPXBsYXRmb3JtOiB7fSBcOwo+Cj4gb3IKPiAgICAgIHN1ZG8gZmluZCAvc3lz IC1wZXJtIC1vPXIgLW5hbWUgbW9kYWxpYXMgLWV4ZWMgZ3JlcCAtSCBwbGF0Zm9ybToge30gXDsK Pgo+IChib3RoIGxpc3RzIHNob3VsZCBiZSBzaW1pbGFyKQo+Cj4gb24gdGhlIHN5c3RlbXMgdGhp cyBwYXRjaCBpcyB0YXJnZXRpbmcsIHdpbGwKPiAgICAgcGxhdGZvcm06cm9ja2NoaXAtc25kLW1h eDk4MDkwCj4KPiB0aGVuIHNob3cgdXA/Cj4KPiBUaGFua3MsCj4KPgo+IFBhdWwgQm9sbGUKPgpU aGFuayB5b3UgZm9yIHlvdXIgcGF0aWVuY2UgYW5kIGRldGFpbGVkIGV4cGxhbmF0aW9uLgpJIHRl c3RlZCB5b3VyIHR3byB3YXlzIGFuZCBkaWRuJ3QgZmluZCB0aGUgCiJwbGF0Zm9ybTpyb2NrY2hp cC1zbmQtbWF4OTgwOTAiIGluIG15IGRldmljZShrZXJuZWwgdjMuMTQpLCBhbmQgdGhlIApkcml2 ZXIgcGF0aCBpczoKbG9jYWxob3N0IHJvY2tjaGlwLXNuZC1tYXg5ODA5MCAjIHB3ZAovc3lzL2J1 cy9wbGF0Zm9ybS9kcml2ZXJzL3JvY2tjaGlwLXNuZC1tYXg5ODA5MAoKVGhhbmtzLgoKX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQWxzYS1kZXZlbCBtYWls aW5nIGxpc3QKQWxzYS1kZXZlbEBhbHNhLXByb2plY3Qub3JnCmh0dHA6Ly9tYWlsbWFuLmFsc2Et cHJvamVjdC5vcmcvbWFpbG1hbi9saXN0aW5mby9hbHNhLWRldmVsCg== From mboxrd@z Thu Jan 1 00:00:00 1970 From: zhengxing@rock-chips.com (zhengxing) Date: Fri, 17 Jul 2015 10:17:25 +0800 Subject: [PATCH 1/2] ASoC: rockchip: Add machine driver for max98090 codec In-Reply-To: <1437056116.28351.19.camel@tiscali.nl> References: <1436930143-31361-1-git-send-email-zhengxing@rock-chips.com> <1436930143-31361-2-git-send-email-zhengxing@rock-chips.com> <1437033944.27428.11.camel@tiscali.nl> <20150716110032.GU11162@sirena.org.uk> <1437047261.28351.6.camel@tiscali.nl> <20150716125529.GG4039@sirena.org.uk> <1437056116.28351.19.camel@tiscali.nl> Message-ID: <55A865B5.7020609@rock-chips.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Paul, On 2015?07?16? 22:15, Paul Bolle wrote: > > That's exactly how I understood MODULE_ALIAS() to work. > > And it works, in short, because a platform device fires a > "MODALIAS=platform:[...]" uevent when it's created. And userspace uses > that uevent to load the module carrying that alias. > > Let's put it this was. If one does > sudo find /sys -perm -o=r -name uevent -exec grep -H MODALIAS=platform: {} \; > > or > sudo find /sys -perm -o=r -name modalias -exec grep -H platform: {} \; > > (both lists should be similar) > > on the systems this patch is targeting, will > platform:rockchip-snd-max98090 > > then show up? > > Thanks, > > > Paul Bolle > Thank you for your patience and detailed explanation. I tested your two ways and didn't find the "platform:rockchip-snd-max98090" in my device(kernel v3.14), and the driver path is: localhost rockchip-snd-max98090 # pwd /sys/bus/platform/drivers/rockchip-snd-max98090 Thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752330AbbGQCXl (ORCPT ); Thu, 16 Jul 2015 22:23:41 -0400 Received: from regular1.263xmail.com ([211.150.99.135]:44062 "EHLO regular1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751861AbbGQCXk (ORCPT ); Thu, 16 Jul 2015 22:23:40 -0400 X-263anti-spam: KSV:0;BIG:0;ABS:1;DNS:0;ATT:0;SPF:S; X-MAIL-GRAY: 0 X-MAIL-DELIVERY: 1 X-KSVirus-check: 0 X-ABS-CHECKED: 1 X-SKE-CHECKED: 1 X-ADDR-CHECKED: 0 X-RL-SENDER: zhengxing@rock-chips.com X-FST-TO: pebolle@tiscali.nl X-SENDER-IP: 58.22.7.114 X-LOGIN-NAME: zhengxing@rock-chips.com X-UNIQUE-TAG: <0046abac22a96deeead0aeb47b5ca774> X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Message-ID: <55A865B5.7020609@rock-chips.com> Date: Fri, 17 Jul 2015 10:17:25 +0800 From: zhengxing User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120410 Thunderbird/11.0.1 MIME-Version: 1.0 To: Paul Bolle CC: Mark Brown , dgreid@chromium.org, dianders@chromium.org, heiko@sntech.de, sonnyrao@chromium.org, linux-rockchip@lists.infradead.org, Liam Girdwood , Jaroslav Kysela , Takashi Iwai , linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 1/2] ASoC: rockchip: Add machine driver for max98090 codec References: <1436930143-31361-1-git-send-email-zhengxing@rock-chips.com> <1436930143-31361-2-git-send-email-zhengxing@rock-chips.com> <1437033944.27428.11.camel@tiscali.nl> <20150716110032.GU11162@sirena.org.uk> <1437047261.28351.6.camel@tiscali.nl> <20150716125529.GG4039@sirena.org.uk> <1437056116.28351.19.camel@tiscali.nl> In-Reply-To: <1437056116.28351.19.camel@tiscali.nl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Paul, On 2015年07月16日 22:15, Paul Bolle wrote: > > That's exactly how I understood MODULE_ALIAS() to work. > > And it works, in short, because a platform device fires a > "MODALIAS=platform:[...]" uevent when it's created. And userspace uses > that uevent to load the module carrying that alias. > > Let's put it this was. If one does > sudo find /sys -perm -o=r -name uevent -exec grep -H MODALIAS=platform: {} \; > > or > sudo find /sys -perm -o=r -name modalias -exec grep -H platform: {} \; > > (both lists should be similar) > > on the systems this patch is targeting, will > platform:rockchip-snd-max98090 > > then show up? > > Thanks, > > > Paul Bolle > Thank you for your patience and detailed explanation. I tested your two ways and didn't find the "platform:rockchip-snd-max98090" in my device(kernel v3.14), and the driver path is: localhost rockchip-snd-max98090 # pwd /sys/bus/platform/drivers/rockchip-snd-max98090 Thanks.