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=-3.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED 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 3A634C433FF for ; Wed, 14 Aug 2019 11:17:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0F9942083B for ; Wed, 14 Aug 2019 11:17:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="NBBp8OKe" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727595AbfHNLRF (ORCPT ); Wed, 14 Aug 2019 07:17:05 -0400 Received: from mail-lj1-f193.google.com ([209.85.208.193]:35628 "EHLO mail-lj1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726121AbfHNLRE (ORCPT ); Wed, 14 Aug 2019 07:17:04 -0400 Received: by mail-lj1-f193.google.com with SMTP id l14so14482766lje.2 for ; Wed, 14 Aug 2019 04:17:03 -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=bpg3G9Etz4OvVx8IFQ1AOlUEfhUeo6540gz6ahfkyQc=; b=NBBp8OKeUdGlXRspVtZwJ2kI+diM9Z8irDSmvjLWSlMQywy/iDOLn5EcBHgEfSEWxr Z2gSzonKyTcHG6gUnhDnB1eFo5D5hXbbe48aL8blx8qICeJOJG8HVwjowH+quM8P/I/T K8l3T2I4tweMSQsWBChGVUVmZv5DTbaiwPmTLhOSryHxcpofpxwl2R3CzHblxmzkHGkq Q2FicIyvRL7qxuNyoHosJXKcHXfvp3GBmjbwa6oH2WhVOST71ON2vFfOSbdwvAvsGBwj EYi3RdP2gOM5cwR5tzZ2+qYjCX1QILUBZ1Ye9xl/cpDjh+HiMDNy7uRm/AtVZ6BmOehf f+Mg== 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=bpg3G9Etz4OvVx8IFQ1AOlUEfhUeo6540gz6ahfkyQc=; b=L+CYj/4A5dMVZKX6S5E8nkwU8OML6mJOL0SqHbHv6oj0RAInMQqnThM+kwsE4yYrgX Z5PKd9wf8LMV0tLU35W8knGClbCQD5wmiDhtbz1r8i06OwGQQolMkka7+XlsqR2drGU4 78vWVCLgxy87UnHIbQPD7jTtYJqixdBFGFCTpZv8tCkmPP8Rvh5umkCZsT/EuTZr6h6k 7fazsXa4tdiD2JrJW/MIR1QAOw4i0EXQPGGc7NgpUjokmVQW8Q9/qwIxCbGEl3zxMzjd dWhx1wobwazMj3ZzdzHRrXScF0YL+AeHJcTvRvrLDw4+Qc8CUQJIkP17obxjE4M9c4gL 82aw== X-Gm-Message-State: APjAAAVSCTm/692ZV6zA2MZOC5oC7LcxGGLC0pxtux2dzFAVbZm8hNwg rz3p44WMNZ58vN+cc4zAxOgysURGYgdRvtiH9/8= X-Google-Smtp-Source: APXvYqym+y7qghCuVZ7uMfBL4Y09yZokgyk/DRxedzjSbW1CvgLMDhOhWj6uS4zbGCv6Y9EwZB1FMZYrLmlojOLTh1s= X-Received: by 2002:a2e:978e:: with SMTP id y14mr10027268lji.10.1565781422625; Wed, 14 Aug 2019 04:17:02 -0700 (PDT) MIME-Version: 1.0 References: <20190814060854.26345-1-codekipper@gmail.com> <20190814060854.26345-13-codekipper@gmail.com> <20190814072046.metavychqvhuohwy@flea> In-Reply-To: <20190814072046.metavychqvhuohwy@flea> From: Code Kipper Date: Wed, 14 Aug 2019 13:16:51 +0200 Message-ID: Subject: Re: [PATCH v5 12/15] 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 Wed, 14 Aug 2019 at 13:08, Maxime Ripard wrote: > > On Wed, Aug 14, 2019 at 08:08:51AM +0200, 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 > > Wasn't the plan to support only stereo for now? Stereo HDMI can be introduced on the H3 and later if we get the first three patches merged. Post those patches is the work to get multi-channel working. > > Either way, that property should be documented. I can do this...but I'm thinking we should bang our heads together to find a solution that we all agree on...especially if we're considering multi-channel tdm support. Thanks, CK > > Maxime > -- > Maxime Ripard, Bootlin > Embedded Linux and Kernel engineering > https://bootlin.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: Code Kipper Subject: Re: [PATCH v5 12/15] ASoC: sun4i-i2s: Add multi-lane functionality Date: Wed, 14 Aug 2019 13:16:51 +0200 Message-ID: References: <20190814060854.26345-1-codekipper@gmail.com> <20190814060854.26345-13-codekipper@gmail.com> <20190814072046.metavychqvhuohwy@flea> Reply-To: codekipper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Sender: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org In-Reply-To: <20190814072046.metavychqvhuohwy@flea> List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , To: Maxime Ripard Cc: Chen-Yu Tsai , linux-sunxi , linux-arm-kernel , Liam Girdwood , Mark Brown , linux-kernel , Linux-ALSA , "Andrea Venturi (pers)" List-Id: alsa-devel@alsa-project.org On Wed, 14 Aug 2019 at 13:08, Maxime Ripard wrote: > > On Wed, Aug 14, 2019 at 08:08:51AM +0200, codekipper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 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 > > Wasn't the plan to support only stereo for now? Stereo HDMI can be introduced on the H3 and later if we get the first three patches merged. Post those patches is the work to get multi-channel working. > > Either way, that property should be documented. I can do this...but I'm thinking we should bang our heads together to find a solution that we all agree on...especially if we're considering multi-channel tdm support. Thanks, CK > > Maxime > -- > Maxime Ripard, Bootlin > Embedded Linux and Kernel engineering > https://bootlin.com 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=-3.5 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,DKIM_VALID,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS 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 3DC8FC32753 for ; Wed, 14 Aug 2019 11:17:15 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (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 0FC882083B for ; Wed, 14 Aug 2019 11:17:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="pYtQ0gbM"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="NBBp8OKe" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0FC882083B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=4mAsxQ39c9BAIWRCF4ZM5q+kW6upnOzUTxmB+3zsO7o=; b=pYtQ0gbMBbsr2V AkebEJjRfKq9UUufXYgK7AmSnHUKoPrkfAFUNTUnVoRS2vmsXS98IwQcPTJNOGYSuZoaHS1/FEkxG pHg7rQSaa40lHQpzIa93+0BaV6og725Gu/22ki8MoMcdYajD96gQNIOEMR+lxT+zrwOyb7I7RuW7R BH291H3+MSRwYPaIDUUpoGXNcqELl0cZzhgQrChF4v0pS2cHtMORAofkrYEWhXmHZHIa3iKwOC0zn w8EX0CwDH0fbsGw+BGH9jAeGr2qUpZH/jbECvAHTJyA3nyeJmZ+/E4hktQCxg61RoOl/tjy8vqIla E7/mlNTAzRoLHAJJdLBQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hxrHA-0003hX-SB; Wed, 14 Aug 2019 11:17:08 +0000 Received: from mail-lj1-x243.google.com ([2a00:1450:4864:20::243]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1hxrH7-0003gs-59 for linux-arm-kernel@lists.infradead.org; Wed, 14 Aug 2019 11:17:06 +0000 Received: by mail-lj1-x243.google.com with SMTP id m24so1975246ljg.8 for ; Wed, 14 Aug 2019 04:17:03 -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=bpg3G9Etz4OvVx8IFQ1AOlUEfhUeo6540gz6ahfkyQc=; b=NBBp8OKeUdGlXRspVtZwJ2kI+diM9Z8irDSmvjLWSlMQywy/iDOLn5EcBHgEfSEWxr Z2gSzonKyTcHG6gUnhDnB1eFo5D5hXbbe48aL8blx8qICeJOJG8HVwjowH+quM8P/I/T K8l3T2I4tweMSQsWBChGVUVmZv5DTbaiwPmTLhOSryHxcpofpxwl2R3CzHblxmzkHGkq Q2FicIyvRL7qxuNyoHosJXKcHXfvp3GBmjbwa6oH2WhVOST71ON2vFfOSbdwvAvsGBwj EYi3RdP2gOM5cwR5tzZ2+qYjCX1QILUBZ1Ye9xl/cpDjh+HiMDNy7uRm/AtVZ6BmOehf f+Mg== 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=bpg3G9Etz4OvVx8IFQ1AOlUEfhUeo6540gz6ahfkyQc=; b=QWL54MLGADT96ifxhA1Gc8tWVNb7r5FMfu5K704eXdwIgHgad1+V/FkcB7WzK34suv 5RRsxq7Gb4L2L8PE0DoJ2EUeR/tLHU2gCGEGBwjl32jR68Gi4m1Ox9zl1RcLTz1ee/5y nOu/K1hpqPMCFkjSH78bin8ILolRiYgnMWYSGeU+6Jp7d3ZyMKwl++RPvv4J1KPYeITn zU97077b55YPdM1JuKIibGct1l3qvM8jQsSAKU5Yi1PbN5dtAiJlNJfxI1YQCJBnjZXV KVhHBmeHtTTBhQHbuOZczVPoX16kcxwG6OXdKQ/ru32wwfwcwcDlShsWtL5cw0qXXhOQ 7o3g== X-Gm-Message-State: APjAAAWJWs4H7x2ZaOz8teloFCVa1/GmHCYW+m8+K85IrWygyvKJZOjf 58Y6gU9XrttVgyXE07cg7Zk8pzNnzO6ddANwXZI= X-Google-Smtp-Source: APXvYqym+y7qghCuVZ7uMfBL4Y09yZokgyk/DRxedzjSbW1CvgLMDhOhWj6uS4zbGCv6Y9EwZB1FMZYrLmlojOLTh1s= X-Received: by 2002:a2e:978e:: with SMTP id y14mr10027268lji.10.1565781422625; Wed, 14 Aug 2019 04:17:02 -0700 (PDT) MIME-Version: 1.0 References: <20190814060854.26345-1-codekipper@gmail.com> <20190814060854.26345-13-codekipper@gmail.com> <20190814072046.metavychqvhuohwy@flea> In-Reply-To: <20190814072046.metavychqvhuohwy@flea> From: Code Kipper Date: Wed, 14 Aug 2019 13:16:51 +0200 Message-ID: Subject: Re: [PATCH v5 12/15] ASoC: sun4i-i2s: Add multi-lane functionality To: Maxime Ripard X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190814_041705_221997_7B963794 X-CRM114-Status: GOOD ( 16.83 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Linux-ALSA , linux-sunxi , linux-kernel , Liam Girdwood , "Andrea Venturi \(pers\)" , Chen-Yu Tsai , Mark Brown , linux-arm-kernel Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, 14 Aug 2019 at 13:08, Maxime Ripard wrote: > > On Wed, Aug 14, 2019 at 08:08:51AM +0200, 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 > > Wasn't the plan to support only stereo for now? Stereo HDMI can be introduced on the H3 and later if we get the first three patches merged. Post those patches is the work to get multi-channel working. > > Either way, that property should be documented. I can do this...but I'm thinking we should bang our heads together to find a solution that we all agree on...especially if we're considering multi-channel tdm support. Thanks, CK > > Maxime > -- > Maxime Ripard, Bootlin > Embedded Linux and Kernel engineering > https://bootlin.com _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel