Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp10776506ybi; Thu, 25 Jul 2019 05:06:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqy20AUR+tv7lUrftAwZy5G71vN0Mdgk053uzNKqIPDwhj0+/bDL5dNDK+4c95LR1YSNsadL X-Received: by 2002:a17:902:f089:: with SMTP id go9mr90428472plb.81.1564056383137; Thu, 25 Jul 2019 05:06:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564056383; cv=none; d=google.com; s=arc-20160816; b=RJZSh7NHhXRWgV39AxxzH01h/0+0Fc6NAr68L85X5mgSoNTjPFFYlW8TYcF/jN88dz ix+qDAH5GL8gbI5MWCCYeAR+KIAm9phPTPHJq4NgxvrtG1UOhfcQ//Uz+1xxHCfD1C5q 1Ar4oVjVrygPGgRCC5/oTBsdRZIMrMQchQ8nJI16ochGnB76uV3aBINxhRyOj46PFEQe CvJ51az+PTM+JWaSq7r1DV3gvvD4UmgqLOS4ugfjEn+pnTRcRe5pV72hepBMUwKnMITu 8HpSYuLBxafCKiAnKZQHQOxkwqlEO7jEVh+NpSSVXSerqmitF9XyG4M+6dw+rsx/tBaU MWWg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=pU+mAWOKuT+1icWHPxBVuENuKDz0OQKOsIOlqLtN9d4=; b=OATgK6gbpeY06iTi2NvKA0f+c8f65ZXQuMdKgqDbLEHsWHHamaq7LL9WnNu1aqFQWG /c1wXusjkU2oeom3LEyksl/eOOHmFsTGFXlbB6FJpSGhHBSD/9RDFcbI1opsitgNpimT TVjcEHT465T4NbjKzPk22gWalwWkb6hdaQWeeMKvVX6al9wIyGklGkdhnRLwl59jjcFd bPMEq4ItEa9q2G/l7SLjX63GWqBCAiJY2rjXQXdmzAw62eA0YgmxnIaiKAHOJ35Hg4f/ H4RaJuJpas77hiN8J5nfkzkc66rF0XLZK6bvgsb9sQzMS2tzXLuqxiL1+N3KHbZp8dXt kzmw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=tjDMGaLu; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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. [209.132.180.67]) by mx.google.com with ESMTP id 12si17294538pfi.199.2019.07.25.05.06.08; Thu, 25 Jul 2019 05:06:23 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=tjDMGaLu; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 S1729364AbfGYGCg (ORCPT + 99 others); Thu, 25 Jul 2019 02:02:36 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:35230 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726547AbfGYGCg (ORCPT ); Thu, 25 Jul 2019 02:02:36 -0400 Received: by mail-wr1-f68.google.com with SMTP id y4so49336325wrm.2 for ; Wed, 24 Jul 2019 23:02:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pU+mAWOKuT+1icWHPxBVuENuKDz0OQKOsIOlqLtN9d4=; b=tjDMGaLuEFwmnP5PNPyUU25EqT5kbEnRrw6KDGkV6Gb97e+iP5mC5KKgA/9r+l4VJf VzlSPmG+ybqde7hYfyiy8wQ15slKfYBqHc8co2TKeF5bNk29sNEiSCuIxIe8RmiMtckl ruT832weiB0FIxU08Z056Z5OTH0fbtYlNsfC7zBvhggV2X5Cd6Ep4w2ty6eTQo4qn6Mw TNoqdzn/0fNab2feocd7K0N9ekjF4zwAVTIa2IzxaUhlUDE4lTANZnmzQaFqbd3IWljy 88lR2KUYkwMOQS6i3w+XqHHBBQE7raT55qqJKS5V4zfYicQPto5wOsmF4FiwyV1MUQs2 Di8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pU+mAWOKuT+1icWHPxBVuENuKDz0OQKOsIOlqLtN9d4=; b=K2/UnPU4iKjUdv/rPfDCMllUjdwPwnJcm4r6zITz3CLP68stvevL4yEVO7PZeHwJPT LzyqVP1x1pRhp7Rcj3jOxwyVp6ljTKP5PKatrGYj0QHos3JdfjnoGjh4bQJEXuKpnvgL NxZKaxhZt5EYMRZzJp9LxxT1aUtulq/ZZkmqAwQoai0D4XAnfX/zuFvbn7b+p2JVFIiy cy4iYwF7L6XcMKndRNBbNkPT1RegyP0JEvTalBbx1+7G14A1Z3G4DA7W1yeRJxV8FIkw sIuQQ1n5JCjsUc9pJ5xsTEPAORKKKrOf8Vjdsn8NpYEMVQF/Ec2UdMlNvmPYM6Lzyp0r oDIA== X-Gm-Message-State: APjAAAWOxObIp8sNjCqygvUIidzM0I6iLK2A4Olblig/Qy/86VO50ySg fxW3ZWPPAiaMcVTrfn1FPFzL2qmtuu63NG3Ar3c= X-Received: by 2002:adf:c70e:: with SMTP id k14mr95081636wrg.201.1564034554176; Wed, 24 Jul 2019 23:02:34 -0700 (PDT) MIME-Version: 1.0 References: <20190722124833.28757-1-daniel.baluta@nxp.com> <20190722124833.28757-9-daniel.baluta@nxp.com> <20190724232209.GC6859@Asurada-Nvidia.nvidia.com> In-Reply-To: <20190724232209.GC6859@Asurada-Nvidia.nvidia.com> From: Daniel Baluta Date: Thu, 25 Jul 2019 09:02:22 +0300 Message-ID: Subject: Re: [alsa-devel] [PATCH 08/10] ASoC: dt-bindings: Document fcomb_mode property To: Nicolin Chen Cc: Daniel Baluta , Linux-ALSA , Viorel Suman , Timur Tabi , Xiubo Li , linuxppc-dev@lists.ozlabs.org, "S.j. Wang" , "Angus Ainslie (Purism)" , Takashi Iwai , Mark Brown , dl-linux-imx , Pengutronix Kernel Team , Fabio Estevam , Linux Kernel Mailing List , Lucas Stach Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 25, 2019 at 2:22 AM Nicolin Chen wrote: > > On Mon, Jul 22, 2019 at 03:48:31PM +0300, Daniel Baluta wrote: > > This allows combining multiple-data-line FIFOs into a > > single-data-line FIFO. > > > > Signed-off-by: Daniel Baluta > > --- > > Documentation/devicetree/bindings/sound/fsl-sai.txt | 4 ++++ > > This should be sent to devicetree mail-list also. > > > 1 file changed, 4 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/sound/fsl-sai.txt b/Documentation/devicetree/bindings/sound/fsl-sai.txt > > index 59f4d965a5fb..ca27afd840ba 100644 > > --- a/Documentation/devicetree/bindings/sound/fsl-sai.txt > > +++ b/Documentation/devicetree/bindings/sound/fsl-sai.txt > > @@ -54,6 +54,10 @@ Optional properties: > > represents first data line, bit 1 represents second > > data line and so on. Data line is enabled if > > corresponding bit is set to 1. > > + - fsl,fcomb_mode : list of two integers (first for RX, second for TX) > > + representing FIFO combine mode. Possible values for > > + combined mode are: 0 - disabled, 1 - Rx/Tx from shift > > + registers, 2 - Rx/Tx by software, 3 - both. > > Looks like a software configuration to me, instead of a device > property. Is this configurable by user case, or hard-coded by > SoC/hardware design? Indeed this is a software configuration and configurable by user case. Will think of a another way to specify it.