Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1696593pxj; Wed, 19 May 2021 11:42:00 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyJiKZe/NJGdO6KrNAVnf1gWOWsG86IQq5i0o1v1J7Mhyb+P3PBSs7tOb/Ulv+Omm/2EPn8 X-Received: by 2002:a17:906:d1d1:: with SMTP id bs17mr544108ejb.492.1621449720033; Wed, 19 May 2021 11:42:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621449720; cv=none; d=google.com; s=arc-20160816; b=EoCN0JlnmK6SFly44QQ9biIt5WzBhJYw2KCC+vl06B7CRd3HTnIMg65xlA7ky1QM08 CD2SIpmH9DV6Q7gdkWg82L9XI4xTcA8Yw0AoQPmAjSTW0Rk9OPRU2BK3BiWohHl/Edu8 rEyZdUU3tfjMzBG2YEMjxbSAL5gaAoRrUdMNZ8B4bBFjRWNrH/eDtdjwGqzYgA28HPJJ Qly3F9JJACnYe+3+XnCTl0WzSfeZODWXmeyJAbfnGZKpKH4hDxm10kzteUxeCGf2Ak9W 3wKp4J9Tzcix8l2Tsw7fjpZIzRBx1+qqwfDxaamgtpVj2xwBN9BjZa4fDJbsbXxNA7Qy I2HQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=6ljTRHwDIGzKo93ro0EyJFj979FSc4cfbPsSrjnxUwY=; b=nMQk7VOPbMZhtGGuqIMfwWx1sof8rkSG66F7R/7C9sRJaGSwfkWBHGI4yhIm59l9sR N8jidCfu8xe63aAt9JVcD/uq/MfVGHWXkJUXjd18He5vqZAv5KCRJQAnpKfydrNidYIu 92BNEZoX98zBbmTvuBpjokGEMoknWBAYkN5FH3yggjiuQtPSHdxWI/+WE2/J15J4JzZY p7ECuWZyzKzIh1ua+ScgmTgzO2QcU7B+NKlOuxASKobKO2ax4CxH7mPSg9cS+BueoxF4 yYShO132mK7eyj/T1fTTj817WbIaKhmy0Op8+SjDedUTCGREvsCRq2Mf9wnbGZzniZw1 ifdA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=EZ1892QS; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m2si376765ejk.237.2021.05.19.11.41.36; Wed, 19 May 2021 11:42:00 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=EZ1892QS; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242460AbhERWcu (ORCPT + 99 others); Tue, 18 May 2021 18:32:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51480 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237154AbhERWcu (ORCPT ); Tue, 18 May 2021 18:32:50 -0400 Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 94374C061573; Tue, 18 May 2021 15:31:31 -0700 (PDT) Received: by mail-lf1-x135.google.com with SMTP id i9so16095522lfe.13; Tue, 18 May 2021 15:31:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=6ljTRHwDIGzKo93ro0EyJFj979FSc4cfbPsSrjnxUwY=; b=EZ1892QSAlcdInwXoIsMLGfBxydo1KcRAPSMXGWFBtVz33HsOcLCnYuXraX+CikYq4 MXk/yi+C6QME/uL9aalttKXxoKix8sL2suoO/6QP2322m4DLH4p3GWCPMULIumAk5Lfk 3hpwqiEIOLOKEeSXwUI4Vpsry4X1eQOjE5kTns+E01m4ssxuXe0n5u1xjBQw0wFrSl6U ZLcF3ehyVwO4z2qWjoCfKfn9ej4x65SZ2Vex3P9E+OsEDzm94CWjj0JxOUZxAKfklGY6 JR76fvBSQw8qjEKE2CGcEvuBVjFThmoVeDlA5WFQxFs8CIPKsi4mumcG2vsAKlt697iH JXNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=6ljTRHwDIGzKo93ro0EyJFj979FSc4cfbPsSrjnxUwY=; b=GsQpfUFBAwTLnie9swUvAEMSmBBRtxjFsbGnV8DNZf+GxhuotgrDTk5vG3Y7Af8qMb VQsp8LMqjFOC4CRXiSZjvWI/Z7p7ISvCFihgUj2uZytLsv/NsPzfcMwIhcoXQ7x/3cLM fg2coUSRP9lWSGntYR2nfzr7VCY5vOBxB3vMsylCOXxTVWPtRP7XInJQhAlcQp43XQCe 4p9D5rjt3lYz9pjeEryfc28pbWqQMfGd6zS/dC2xGHWSfkW8PZHvF/rTuCen9IYTmLzJ mmr9kExJqhRm8b20aMIkvyCj7SXyD/jTcDUl9F+Um5tEpFxATC+Vb0PHy9235GFYLPLa wvjQ== X-Gm-Message-State: AOAM530cFFg1/8/FLDJVcjZj1F5FRB2C23xlPbschHubWchpr6pqaJlr PROxpd58NI3T6ZeiGesJwDg= X-Received: by 2002:a19:431b:: with SMTP id q27mr5484708lfa.226.1621377089928; Tue, 18 May 2021 15:31:29 -0700 (PDT) Received: from [192.168.2.145] (109-252-193-91.dynamic.spd-mgts.ru. [109.252.193.91]) by smtp.googlemail.com with ESMTPSA id m22sm2392071lfu.219.2021.05.18.15.31.29 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 18 May 2021 15:31:29 -0700 (PDT) Subject: Question about Tegra UCMs To: Mark Brown , Jaroslav Kysela Cc: Thierry Reding , Jonathan Hunter , Takashi Iwai , Ion Agorria , Svyatoslav Ryhel , Frank Rowand , Liam Girdwood , linux-tegra@vger.kernel.org, devicetree@vger.kernel.org, alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org, Rob Herring References: <20210518001356.19227-1-digetx@gmail.com> <20210518001356.19227-3-digetx@gmail.com> <20210518180949.GA949047@robh.at.kernel.org> <20210518183455.GE4358@sirena.org.uk> From: Dmitry Osipenko Message-ID: <92cef674-c454-e08c-b44d-d8c08b1e8ccf@gmail.com> Date: Wed, 19 May 2021 01:31:28 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <20210518183455.GE4358@sirena.org.uk> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Mark, could you please help me to understand the UCM naming scheme that ALSA uses.. About a year ago I tried to complain to Jaroslav Kysela in a comment to the UCM change [1] that it should be breaking the naming scheme of Tegra UCMs, but haven't got a meaningful reply and moved on to other things. [1] https://github.com/alsa-project/alsa-ucm-conf/commit/8ff2d50745efbb6959324f672460e413f0b618b8 Today I noticed that the naming scheme changed again and I still don't understand what to do about it. I have two devices: 1. Acer Picasso tablet that uses "Acer Iconia Tab A500 WM8903" for the card model name. 2. Google Nexus 7 that uses "ASUS Google Nexus 7 ALC5642". Previously UCMs were picked up by pulseaudio from these paths: 1. /usr/share/alsa/ucm2/Acer Iconia Tab A500 WM8903/ 2. /usr/share/alsa/ucm2/ASUS Google Nexus 7 ALC5642/ Now the lookup paths are changed to: 1. /usr/share/alsa/ucm2/Acer_Iconia_Tab/ 2. /usr/share/alsa/ucm2/ASUS_Google_Nex/ Strace shows that pulseaudio searches UCMs only at these paths. The output of /proc/asound/cards: 0 [WM8903 ]: Acer_Iconia_Tab - Acer Iconia Tab A500 WM8903 Acer Iconia Tab A500 WM8903 0 [ALC5642 ]: ASUS_Google_Nex - ASUS Google Nexus 7 ALC5642 ASUS Google Nexus 7 ALC5642 IIUC, the "ucm2/Tegra/codec_name" scheme [2] that the current ALSA UCM uses simply doesn't work at all. Is there anything on the kernel side that I could change to get a working naming scheme? If yes, I may try to do something about it in the v2, thanks in advance. [2] https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/Tegra