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.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED,USER_AGENT_NEOMUTT autolearn=ham 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 4F0EBC10F0E for ; Mon, 15 Apr 2019 14:51:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 29AB32075B for ; Mon, 15 Apr 2019 14:51:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727590AbfDOOvl (ORCPT ); Mon, 15 Apr 2019 10:51:41 -0400 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:45869 "EHLO relay3-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727129AbfDOOvk (ORCPT ); Mon, 15 Apr 2019 10:51:40 -0400 X-Originating-IP: 90.88.18.121 Received: from localhost (aaubervilliers-681-1-63-121.w90-88.abo.wanadoo.fr [90.88.18.121]) (Authenticated sender: maxime.ripard@bootlin.com) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 03D1C60017; Mon, 15 Apr 2019 14:51:35 +0000 (UTC) Date: Mon, 15 Apr 2019 16:51:35 +0200 From: Maxime Ripard To: =?utf-8?B?Q2zDqW1lbnQgUMOpcm9u?= Cc: Rob Herring , Chen-Yu Tsai , Icenowy Zheng , Jagan Teki , Jernej Skrabec , devicetree , linux-kernel , linux-arm-kernel , linux-sunxi Subject: Re: [PATCH 1/4] dt-bindings: sound: sun4i-spdif: Add Allwinner H6 compatible Message-ID: <20190415145135.fjbcaldwy7w3eqcs@flea> References: <20190411214422.2267-1-peron.clem@gmail.com> <20190411214422.2267-2-peron.clem@gmail.com> <20190415080443.frubh4ln4agrdsfe@flea> <20190415081816.2pay4pioc5d4mojf@flea> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sxl5ukncdhkjkqsu" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --sxl5ukncdhkjkqsu Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 15, 2019 at 10:30:38AM +0200, Cl=E9ment P=E9ron wrote: > On Mon, 15 Apr 2019 at 10:18, Maxime Ripard w= rote: > > > > On Mon, Apr 15, 2019 at 10:09:11AM +0200, Cl=E9ment P=E9ron wrote: > > > Hi, > > > > > > On Mon, 15 Apr 2019 at 10:04, Maxime Ripard wrote: > > > > > > > > Hi, > > > > > > > > On Thu, Apr 11, 2019 at 11:44:19PM +0200, Cl=E9ment P=E9ron wrote: > > > > > Allwinner H6 has a SPDIF controller with an increase of the fifo > > > > > size and the possibility to output the master clock. > > > > > However it's still compatible with the already existing driver for > > > > > Allwiner H3. > > > > > > > > > > Add this compatible in the device-tree bindings documentation. > > > > > > > > How was this tested? > > > > > > Using Alsa utils on a Beelink GS1 and I check correct output sound on > > > my home cinema. > > > > > > > After looking at the datasheet, it looks like it's still significan= tly > > > > different. In particular: > > > > > > > > - The MCLK divider isn't at the same offset > > > > > > We don't use the MCLK > > > > > > > - The bits to flush the FIFO aren't at the same offset > > > > - The FIFO trigger levels aren't at the same offset > > > > - The FIFO status register layout is almost entirely different > > > > > > We use DMA not FIFO > > > > Well, DMA still uses the FIFOs. And even then, you're kind of missing > > the point. The device tree's compatible is about whether a particular > > device can be used as another one. How you are using it in the driver > > is completely irrelevant. > > Sorry I meant " We use DMA not PIO". I'm still not quite sure what you mean. Both DMA and PIO would be using the FIFOs. > I didn't change the driver and the SPDIF is working what's irrelevant > in declaring the driver as compatible ? It's working by accident. This won't work for example: https://elixir.bootlin.com/linux/latest/source/sound/soc/sunxi/sun4i-spdif.= c#L181 > If some feature are missing they can be introduce later as there is a > special binding for H6 no ? Again, that's irrelevant. The only question you need to ask yourself is whether, if you take an imaginary source code that would support all the H3 SPDIF features and run it on an H6, it works just as well. The examples above that it's not the case, so you can't claim that the device is compatible. Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com --sxl5ukncdhkjkqsu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCXLSadwAKCRDj7w1vZxhR xceAAP96JN2YhYM1zBkmyvK0GznWHP/qGjaXEu34Ymc9cr94WgEA5YRrzmmCqSra G/5VRd32UJzMeF3TWQFNRHrueDOylwI= =A0UO -----END PGP SIGNATURE----- --sxl5ukncdhkjkqsu-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxime Ripard Subject: Re: [PATCH 1/4] dt-bindings: sound: sun4i-spdif: Add Allwinner H6 compatible Date: Mon, 15 Apr 2019 16:51:35 +0200 Message-ID: <20190415145135.fjbcaldwy7w3eqcs@flea> References: <20190411214422.2267-1-peron.clem@gmail.com> <20190411214422.2267-2-peron.clem@gmail.com> <20190415080443.frubh4ln4agrdsfe@flea> <20190415081816.2pay4pioc5d4mojf@flea> Reply-To: maxime.ripard-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sxl5ukncdhkjkqsu" Return-path: Sender: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Content-Disposition: inline In-Reply-To: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , To: =?utf-8?B?Q2zDqW1lbnQgUMOpcm9u?= Cc: Rob Herring , Chen-Yu Tsai , Icenowy Zheng , Jagan Teki , Jernej Skrabec , devicetree , linux-kernel , linux-arm-kernel , linux-sunxi List-Id: devicetree@vger.kernel.org --sxl5ukncdhkjkqsu Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 15, 2019 at 10:30:38AM +0200, Cl=C3=A9ment P=C3=A9ron wrote: > On Mon, 15 Apr 2019 at 10:18, Maxime Ripard w= rote: > > > > On Mon, Apr 15, 2019 at 10:09:11AM +0200, Cl=C3=A9ment P=C3=A9ron wrote= : > > > Hi, > > > > > > On Mon, 15 Apr 2019 at 10:04, Maxime Ripard wrote: > > > > > > > > Hi, > > > > > > > > On Thu, Apr 11, 2019 at 11:44:19PM +0200, Cl=C3=A9ment P=C3=A9ron w= rote: > > > > > Allwinner H6 has a SPDIF controller with an increase of the fifo > > > > > size and the possibility to output the master clock. > > > > > However it's still compatible with the already existing driver fo= r > > > > > Allwiner H3. > > > > > > > > > > Add this compatible in the device-tree bindings documentation. > > > > > > > > How was this tested? > > > > > > Using Alsa utils on a Beelink GS1 and I check correct output sound on > > > my home cinema. > > > > > > > After looking at the datasheet, it looks like it's still significan= tly > > > > different. In particular: > > > > > > > > - The MCLK divider isn't at the same offset > > > > > > We don't use the MCLK > > > > > > > - The bits to flush the FIFO aren't at the same offset > > > > - The FIFO trigger levels aren't at the same offset > > > > - The FIFO status register layout is almost entirely different > > > > > > We use DMA not FIFO > > > > Well, DMA still uses the FIFOs. And even then, you're kind of missing > > the point. The device tree's compatible is about whether a particular > > device can be used as another one. How you are using it in the driver > > is completely irrelevant. > > Sorry I meant " We use DMA not PIO". I'm still not quite sure what you mean. Both DMA and PIO would be using the FIFOs. > I didn't change the driver and the SPDIF is working what's irrelevant > in declaring the driver as compatible ? It's working by accident. This won't work for example: https://elixir.bootlin.com/linux/latest/source/sound/soc/sunxi/sun4i-spdif.= c#L181 > If some feature are missing they can be introduce later as there is a > special binding for H6 no ? Again, that's irrelevant. The only question you need to ask yourself is whether, if you take an imaginary source code that would support all the H3 SPDIF features and run it on an H6, it works just as well. The examples above that it's not the case, so you can't claim that the device is compatible. Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com --=20 You received this message because you are subscribed to the Google Groups "= linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to linux-sunxi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit https://groups.google.com/d/optout. --sxl5ukncdhkjkqsu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCXLSadwAKCRDj7w1vZxhR xceAAP96JN2YhYM1zBkmyvK0GznWHP/qGjaXEu34Ymc9cr94WgEA5YRrzmmCqSra G/5VRd32UJzMeF3TWQFNRHrueDOylwI= =A0UO -----END PGP SIGNATURE----- --sxl5ukncdhkjkqsu-- 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.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_NEOMUTT autolearn=ham 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 EE105C10F0E for ; Mon, 15 Apr 2019 14:51:50 +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 BED1D20880 for ; Mon, 15 Apr 2019 14:51:50 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="c7oq04u7" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BED1D20880 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bootlin.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-Type:Cc: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: In-Reply-To:MIME-Version:References:Message-ID:Subject:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=MLo+2EcDHhmwSHISikQ+/ml8A6psipHn3rAuB1ELiuE=; b=c7oq04u7zNJrrGGP/8Phwa+qi A2GScZqHIPqSOQRr4FnjyHru4NfrCPGzGaDFCE/uLz+NC4g8rAgVP/iqR+NioQ6hsIWpZCZCs86a7 4ciROj7ScnuKOYnbVA2KwrH6feyPQLYvNtl6/WyysEwl2S8xAonynjj72AEaZj2NgXh6nQV9MXAMv Ym1LGuQOS6QOMgJP1nnMUY+K3SR/6Pp+/+xTK1j96ES/BUy0R+sF4lvSJaOCgrjWbGxwcYuKlgQCA Lw1WHr2tVN3zpKNisvDvLOUFN4MBWHM3C6JICESvq8qHXX7X2DOHjhzQzuo2AMi+pntMSbFnYoJtI 4baoOIrTA==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hG2xU-0002eT-SX; Mon, 15 Apr 2019 14:51:44 +0000 Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hG2xQ-0002dK-JM for linux-arm-kernel@lists.infradead.org; Mon, 15 Apr 2019 14:51:42 +0000 X-Originating-IP: 90.88.18.121 Received: from localhost (aaubervilliers-681-1-63-121.w90-88.abo.wanadoo.fr [90.88.18.121]) (Authenticated sender: maxime.ripard@bootlin.com) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 03D1C60017; Mon, 15 Apr 2019 14:51:35 +0000 (UTC) Date: Mon, 15 Apr 2019 16:51:35 +0200 From: Maxime Ripard To: =?utf-8?B?Q2zDqW1lbnQgUMOpcm9u?= Subject: Re: [PATCH 1/4] dt-bindings: sound: sun4i-spdif: Add Allwinner H6 compatible Message-ID: <20190415145135.fjbcaldwy7w3eqcs@flea> References: <20190411214422.2267-1-peron.clem@gmail.com> <20190411214422.2267-2-peron.clem@gmail.com> <20190415080443.frubh4ln4agrdsfe@flea> <20190415081816.2pay4pioc5d4mojf@flea> MIME-Version: 1.0 In-Reply-To: User-Agent: NeoMutt/20180716 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190415_075140_931073_B2EA5FD2 X-CRM114-Status: GOOD ( 24.76 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: devicetree , Jernej Skrabec , linux-sunxi , linux-kernel , Chen-Yu Tsai , Rob Herring , Jagan Teki , linux-arm-kernel , Icenowy Zheng Content-Type: multipart/mixed; boundary="===============3992211713391228281==" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org --===============3992211713391228281== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sxl5ukncdhkjkqsu" Content-Disposition: inline --sxl5ukncdhkjkqsu Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 15, 2019 at 10:30:38AM +0200, Cl=E9ment P=E9ron wrote: > On Mon, 15 Apr 2019 at 10:18, Maxime Ripard w= rote: > > > > On Mon, Apr 15, 2019 at 10:09:11AM +0200, Cl=E9ment P=E9ron wrote: > > > Hi, > > > > > > On Mon, 15 Apr 2019 at 10:04, Maxime Ripard wrote: > > > > > > > > Hi, > > > > > > > > On Thu, Apr 11, 2019 at 11:44:19PM +0200, Cl=E9ment P=E9ron wrote: > > > > > Allwinner H6 has a SPDIF controller with an increase of the fifo > > > > > size and the possibility to output the master clock. > > > > > However it's still compatible with the already existing driver for > > > > > Allwiner H3. > > > > > > > > > > Add this compatible in the device-tree bindings documentation. > > > > > > > > How was this tested? > > > > > > Using Alsa utils on a Beelink GS1 and I check correct output sound on > > > my home cinema. > > > > > > > After looking at the datasheet, it looks like it's still significan= tly > > > > different. In particular: > > > > > > > > - The MCLK divider isn't at the same offset > > > > > > We don't use the MCLK > > > > > > > - The bits to flush the FIFO aren't at the same offset > > > > - The FIFO trigger levels aren't at the same offset > > > > - The FIFO status register layout is almost entirely different > > > > > > We use DMA not FIFO > > > > Well, DMA still uses the FIFOs. And even then, you're kind of missing > > the point. The device tree's compatible is about whether a particular > > device can be used as another one. How you are using it in the driver > > is completely irrelevant. > > Sorry I meant " We use DMA not PIO". I'm still not quite sure what you mean. Both DMA and PIO would be using the FIFOs. > I didn't change the driver and the SPDIF is working what's irrelevant > in declaring the driver as compatible ? It's working by accident. This won't work for example: https://elixir.bootlin.com/linux/latest/source/sound/soc/sunxi/sun4i-spdif.= c#L181 > If some feature are missing they can be introduce later as there is a > special binding for H6 no ? Again, that's irrelevant. The only question you need to ask yourself is whether, if you take an imaginary source code that would support all the H3 SPDIF features and run it on an H6, it works just as well. The examples above that it's not the case, so you can't claim that the device is compatible. Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com --sxl5ukncdhkjkqsu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCXLSadwAKCRDj7w1vZxhR xceAAP96JN2YhYM1zBkmyvK0GznWHP/qGjaXEu34Ymc9cr94WgEA5YRrzmmCqSra G/5VRd32UJzMeF3TWQFNRHrueDOylwI= =A0UO -----END PGP SIGNATURE----- --sxl5ukncdhkjkqsu-- --===============3992211713391228281== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel --===============3992211713391228281==--