Received: by 10.213.65.68 with SMTP id h4csp206700imn; Tue, 13 Mar 2018 01:18:32 -0700 (PDT) X-Google-Smtp-Source: AG47ELu0GshTLiqM2RE5Ms0Dm/HSssC396OCTLMUe4dIBD2YedCt3pnubObLcWO1uwooWbcRBeiS X-Received: by 2002:a17:902:7082:: with SMTP id z2-v6mr10807989plk.130.1520929112179; Tue, 13 Mar 2018 01:18:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1520929112; cv=none; d=google.com; s=arc-20160816; b=UXSsqNdmCObejMmm6KHrwi6bsRpjvYC8I3eoDov0pUtuOkx1t5s/woP9cgFiGtpuua K3/7nI2ogWCpQO/mpnfan5uJUt1/VMLvyXxY4gXgkMK2kIEthUNAyAot2ZFJ70kmNlci +3f4MNS9DLLC0kmn+DQuke3OpXW+Nb1ymKeTZ/TOya5/jMz2uhlL19A17RF6R+fXx4Sh PUdLPOacjc5OA/0wuyuR98VXjUFfUWi3Gja7YQr/UvsLbRSxo6Hfpk8ihMdRTioBtCNO BwvrsStqczSobsCVhISC4klAzGmryt/pAXynIUCqRIKO3ogsKzYZqwqq5bn0REuY5Cjh 9TGA== 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 :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=D+vG9Wt0CT28Z+m+wMqKq2mDvVRvQYpo2uhTyIeyigs=; b=kpjvrBfyUcndpoT1ovaub58NcMoLvwm/rzYR6JMskv3pYGdr0JIbcsBXIM60BnXfCc AjZPgumgNc2qiertD5OYUAkZkYd0MtGK9xe4VnTTO7qwRu7TxuGoSla1AmrPXxBdechc MD73Y/pgd4ip66w+8tOyUtqkUsNuOPJPCV2uVsEDfSqom01gsFkkZG0R/EGphM8e9gfO UpYh4bED7P7Gf8sibuzJCV6/9ZLYPhmRVGQEBW04e2kNAzOJe1mXxUE+4sWhXrhgyPiI w01+6lEsa3KODOnu4vjkrT+05czUeMkoi1rjoY6WrRfgmo05BUHNgPbDt+x7dh5noWIb eC5g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=DLLfwQkC; 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 bc11-v6si7295222plb.43.2018.03.13.01.18.18; Tue, 13 Mar 2018 01:18:32 -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=DLLfwQkC; 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 S1752263AbeCMIPv (ORCPT + 99 others); Tue, 13 Mar 2018 04:15:51 -0400 Received: from mail-io0-f194.google.com ([209.85.223.194]:37080 "EHLO mail-io0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751964AbeCMIPu (ORCPT ); Tue, 13 Mar 2018 04:15:50 -0400 Received: by mail-io0-f194.google.com with SMTP id d71so14691838iog.4 for ; Tue, 13 Mar 2018 01:15:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=D+vG9Wt0CT28Z+m+wMqKq2mDvVRvQYpo2uhTyIeyigs=; b=DLLfwQkCUCa8lkL0mz81HdPN4DEM3FLK+q8H5CbOXEtFjgLByW3fw0o7YDKFChAExd knjH8O75xQtKk/3NytgEzpvphcEUqeQUD9bBQoAHsTSU6RoIpwQALkmYUyBHA+JA/YC2 EZ2TXhNaulFPArY2TF/J0NsQqGHztEcSbH02k/dijHHqE3q46Rh3NPQ4dJc5OlE37YeV 1D9vs+qvjpiG3UY+6ujtUdo4jtxutQBhzsTY/9PXm7gzbwof8Z6CCRIxbdEEg+bRU8IU kItGb+N0RH7GUV0SYKmxdJUb4czhOGR/3i7/6NQzm9OQzMFcoAY/jFhh8x0l2RxWpKFb vspw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=D+vG9Wt0CT28Z+m+wMqKq2mDvVRvQYpo2uhTyIeyigs=; b=MBi58dkzbuTmswslFUbHniVnArznF8h2NnU6QW0Vd0AwoRVgb6adySqSeZo8IgBrte N3DmX5597qjlU9X7iqH0/MzKOgQ+mqhzqVc6pgLbxcW19MxruIX5mZlsrY1/y0zFz8Qy YPZ2s0nuNla4UPInffmMjQRA9jkpNeI9/w4oF/GweI//kP0VPCrTVYo6rN3twf52awv+ DRvYUcHMsKCLmfOl5GpcpunxgorrifLU4jAJDczSQ3yKN8Ovuk6U8R3f7QSb3cSHj1im 0pG/3o5WtHivRU9170bMUWdvU7gzgyN3VbSd/mwCqjHtaTkSemQRcD9Wh9UlMG/ieUFt 28ug== X-Gm-Message-State: AElRT7GOqzh5/2SkuWOKmp4G7j47WP+/Bo/uMSTXMuuXWjOjgCU+rkde u77NM9WyVQtymNO9RV4I5d3ypq4IT4NdrmFoVIw= X-Received: by 10.107.63.131 with SMTP id m125mr11575965ioa.211.1520928949856; Tue, 13 Mar 2018 01:15:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.152.14 with HTTP; Tue, 13 Mar 2018 01:15:49 -0700 (PDT) In-Reply-To: <20180313080026.jtag4w46koxzeqe2@flea> References: <20180312155753.9478-1-codekipper@gmail.com> <20180312155753.9478-5-codekipper@gmail.com> <20180313080026.jtag4w46koxzeqe2@flea> From: Code Kipper Date: Tue, 13 Mar 2018 09:15:49 +0100 Message-ID: Subject: Re: [PATCH v2 4/6] ASoC: sun4i-i2s: Add multi-lane functionality To: Maxime Ripard Cc: Chen-Yu Tsai , linux-sunxi , linux-arm-kernel , Liam Girdwood , Mark Brown , linux-kernel , Linux-ALSA , "Andrea Venturi (pers)" 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 13 March 2018 at 09:00, Maxime Ripard wrote: > On Mon, Mar 12, 2018 at 04:57:51PM +0100, codekipper@gmail.com wrote: >> From: Marcus Cooper >> >> The i2s block supports multi-lane i2s output however this functionality >> is only possible in earlier SoCs where the pins are exposed and for >> the i2s block used for HDMI audio on the later SoCs. >> >> To enable this functionality, an optional property has been added to >> the bindings. >> >> Signed-off-by: Marcus Cooper >> --- >> .../devicetree/bindings/sound/sun4i-i2s.txt | 3 ++ >> sound/soc/sunxi/sun4i-i2s.c | 48 +++++++++++++++++----- >> 2 files changed, 41 insertions(+), 10 deletions(-) >> >> diff --git a/Documentation/devicetree/bindings/sound/sun4i-i2s.txt b/Documentation/devicetree/bindings/sound/sun4i-i2s.txt >> index 48addef65b8f..3f966ac61b9e 100644 >> --- a/Documentation/devicetree/bindings/sound/sun4i-i2s.txt >> +++ b/Documentation/devicetree/bindings/sound/sun4i-i2s.txt >> @@ -33,6 +33,9 @@ Optional properties: >> configured to extend the slot width to the >> value specified. Min 8, Max 32. >> >> +- allwinner,playback-channels: if this property is present then the number >> + of available channels is extended and the >> + outputs enabled. > > Isn't it something that is fixed for each generation of SoCs? Can't we > attach it to the compatible? I'm not sure as the documentation is pretty poor. It looks like it is supported by all of the variations that we've seen but only exposed as pins on A10 and A20. I'm also not sure who would ever use it with external devices. The reason why I've added it is that it is required by HDMI for supporting surround sound on the newer SoCs. CK > > Maxime > > -- > Maxime Ripard, Bootlin (formerly Free Electrons) > Embedded Linux and Kernel engineering > https://bootlin.com