From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 134C5C433E2 for ; Thu, 3 Sep 2020 21:33:28 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 87B9F206D4 for ; Thu, 3 Sep 2020 21:33:27 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="BYRDVi/B" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 87B9F206D4 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 16EDF1911; Thu, 3 Sep 2020 23:32:36 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 16EDF1911 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1599168806; bh=hgsM6WUyatqzZIVCn6QKUM2E8s+CFOQQE+wNmeXwRto=; h=Subject:To:References:From:Date:In-Reply-To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=BYRDVi/Bs2Ljb1WOvmw51fktUSONdbnIEZiKXHjwy4/xqW3I+Z7cLUHTxbhhs4+sR tDy/vjWtaTh1c8KqhXgZj3R3G9L6Gn0fPtxLqQRnyQvI482TodG20tMv3tBJ7/TZ5R L6MSnQDLDvXy729wXt31XPQngdzuomHSDVLdHPQ4= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 9E3A3F801DA; Thu, 3 Sep 2020 23:32:35 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 1C73BF80217; Thu, 3 Sep 2020 23:32:34 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id ADE20F801DA for ; Thu, 3 Sep 2020 23:32:28 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz ADE20F801DA IronPort-SDR: 46HDBq5AilW8/iKT4adF4tQjLBOGY71POIBYUiuYiVo+zB4030ji8ypRlMNlTohE8V4N3nBoXH S/rw/D4+cT2g== X-IronPort-AV: E=McAfee;i="6000,8403,9733"; a="242480823" X-IronPort-AV: E=Sophos;i="5.76,387,1592895600"; d="scan'208";a="242480823" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Sep 2020 14:32:23 -0700 IronPort-SDR: e8awDXon4Mr1mhSyZCzHoSe2rfJtQS+wW9vg6JZYBEsCK0w09YCsblZffNwWi/gZA9w+b250VA ZJbS6czWjUHg== X-IronPort-AV: E=Sophos;i="5.76,387,1592895600"; d="scan'208";a="478208877" Received: from mrcordie-mobl1.amr.corp.intel.com (HELO [10.212.195.28]) ([10.212.195.28]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Sep 2020 14:32:23 -0700 Subject: Re: [RFC PATCH 0/3] alsa-lib/ASoC: use inclusive language for bclk/fsync/topology To: Jaroslav Kysela , alsa-devel@alsa-project.org References: <20200903201024.1109914-1-pierre-louis.bossart@linux.intel.com> From: Pierre-Louis Bossart Message-ID: <9d1c96ad-6860-7a98-4e22-5f566665e7e7@linux.intel.com> Date: Thu, 3 Sep 2020 16:32:22 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Cc: tiwai@suse.de, broonie@kernel.org X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On 9/3/20 3:42 PM, Jaroslav Kysela wrote: > Dne 03. 09. 20 v 22:10 Pierre-Louis Bossart napsal(a): >> The SOF (Sound Open Firmware) tree contains a lot of references in >> topology files to 'codec_slave'/'codec_master' terms, which in turn >> come from alsa-lib and ALSA/ASoC topology support at the kernel >> level. These terms are no longer compatible with the guidelines >> adopted by the kernel community [1] and need to change in >> backwards-compatible ways. >> >> The main/secondary terms typically suggested in guidelines don't mean >> anything for clocks, this patchset suggests instead the use of >> 'provider' and 'follower' terms, with the 'codec' prefix kept to make >> it clear that the codec is the reference. The CM/CF suffixes are also >> replaced by CP/CF. > > Only my 2 cents: It's just another word combo. See bellow for sources for others. > > I would prefer probably provider/consumer . It sounds more technic. Thanks Jaroslav for chiming in. I had a similar set of comments in internal reviews, but we didn't really have any consensus and I have not seen good guidance specifically for clocks. Provider/consumer is typically used for discrete data exchange with some sort of locking and buffer fullness metric, but for clocks we'd want something that hints at one device following the timing defined by another. "follow" or "track" seem clearer than 'consume' IMHO, but I will side with the majority, this is an RFC which can be modified at will.