From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756886AbcBIRKp (ORCPT ); Tue, 9 Feb 2016 12:10:45 -0500 Received: from down.free-electrons.com ([37.187.137.238]:39170 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754160AbcBIRKm (ORCPT ); Tue, 9 Feb 2016 12:10:42 -0500 Date: Tue, 9 Feb 2016 18:10:40 +0100 From: Maxime Ripard To: Krzysztof Adamski Cc: Jean-Francois Moine , inus Walleij , Chen-Yu Tsai , Hans de Goede , Lee Jones , Rob Herring , Jens Kuske , Fabian Frederick , Vishnu Patekar , linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com Subject: Re: [PATCH v3 1/5] clk: sunxi: Add apb0 gates for H3 Message-ID: <20160209171040.GR31506@lukather> References: <1454542430-16572-1-git-send-email-k@japko.eu> <1454542430-16572-2-git-send-email-k@japko.eu> <20160204154752.4df7808be3364a98c496c030@free.fr> <20160205111152.GA31506@lukather> <20160205115837.GD12071@box2.japko.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GDLQamdgIxhPcIwq" Content-Disposition: inline In-Reply-To: <20160205115837.GD12071@box2.japko.eu> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --GDLQamdgIxhPcIwq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 05, 2016 at 12:58:37PM +0100, Krzysztof Adamski wrote: > On Fri, Feb 05, 2016 at 12:11:52PM +0100, Maxime Ripard wrote: > >Hi, > > > >On Thu, Feb 04, 2016 at 03:47:52PM +0100, Jean-Francois Moine wrote: > >>On Thu, 4 Feb 2016 00:33:46 +0100 > >>Krzysztof Adamski wrote: > >> > >>> This patch adds support for APB0 in H3. It seems to be compatible with > >>> earlier SOCs. apb0 gates controls R_ block peripherals (R_PIO, R_IR, > >>> etc). > >>> > >>> Signed-off-by: Krzysztof Adamski > >>> --- > >>> Documentation/devicetree/bindings/clock/sunxi.txt | 1 + > >>> drivers/clk/sunxi/clk-simple-gates.c | 2 ++ > >>> 2 files changed, 3 insertions(+) > >>> > >>> diff --git a/Documentation/devicetree/bindings/clock/sunxi.txt b/Docu= mentation/devicetree/bindings/clock/sunxi.txt > >>> index e59f57b..751c8b9f0 100644 > >>> --- a/Documentation/devicetree/bindings/clock/sunxi.txt > >>> +++ b/Documentation/devicetree/bindings/clock/sunxi.txt > >>> @@ -45,6 +45,7 @@ Required properties: > >>> "allwinner,sun6i-a31-apb0-gates-clk" - for the APB0 gates on A31 > >>> "allwinner,sun7i-a20-apb0-gates-clk" - for the APB0 gates on A20 > >>> "allwinner,sun8i-a23-apb0-gates-clk" - for the APB0 gates on A23 > >>> + "allwinner,sun8i-h3-apb0-gates-clk" - for the APB0 gates on H3 > >>> "allwinner,sun9i-a80-apb0-gates-clk" - for the APB0 gates on A80 > >>> "allwinner,sun4i-a10-apb1-clk" - for the APB1 clock > >>> "allwinner,sun9i-a80-apb1-clk" - for the APB1 bus clock on A80 > >>> diff --git a/drivers/clk/sunxi/clk-simple-gates.c b/drivers/clk/sunxi= /clk-simple-gates.c > >>> index f4da52b..6753c87 100644 > >>> --- a/drivers/clk/sunxi/clk-simple-gates.c > >>> +++ b/drivers/clk/sunxi/clk-simple-gates.c > >>> @@ -130,6 +130,8 @@ CLK_OF_DECLARE(sun8i_a23_apb2, "allwinner,sun8i-a= 23-apb2-gates-clk", > >>> sunxi_simple_gates_init); > >>> CLK_OF_DECLARE(sun8i_a33_ahb1, "allwinner,sun8i-a33-ahb1-gates-clk", > >>> sunxi_simple_gates_init); > >>> +CLK_OF_DECLARE(sun8i_h3_apb0, "allwinner,sun8i-h3-apb0-gates-clk", > >>> + sunxi_simple_gates_init); > >>> CLK_OF_DECLARE(sun9i_a80_ahb0, "allwinner,sun9i-a80-ahb0-gates-clk", > >>> sunxi_simple_gates_init); > >>> CLK_OF_DECLARE(sun9i_a80_ahb1, "allwinner,sun9i-a80-ahb1-gates-clk", > >> > >>It seems that the other compatible strings are there for historical > >>reasons. Why do you need a new one with such a specific name? > >> > >>It would have been more sensible to add a generic compatible string as > >>"allwinner,apb-gates", letting the removal of the other strings for a > >>later patch... > > > >Yeah, it's a good idea, and it's probably time that we move to that. > > > >However, I'd like to keep per-soc and per-clocks compatibles in the > >DT, in case we need to protect a clock in the future. That doesn't > >prevent to have two compatibles thoughe, the specific and the generic. > > >=20 > So now I'm not sure what you mean. You suggest that I should keep using > specific (sun8i_h3_apb0) or change to generic (apb-gates) in my patch? Both. To have something like that: compatible =3D "allwinner,sun8i-h3-apb0-gates-clk", "allwinner,sun4i-a10-ga= tes-clk"; sun4i-a10-gates-clk being the generic compatible that we would use, and we can always match against the h3 specific compatible if we need to have a different behaviour. Maxime --=20 Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com --GDLQamdgIxhPcIwq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJWuh2QAAoJEBx+YmzsjxAgkNwQAJp4NXlRTU6oMs43e9xcWaWF YmXU6KosBZAH0QHh9QqHZdN2FwQ/YbV707uxS7Oms9lizozcCjmH7Hy1z21aAiZK rH/Qpve5UFoGAFAvp1bgz4xJ++PochGn4SaA+2PcS1L2UhL8bsn4CZ9J/Du9OHcE n+mB15WokhomjCRVnkqBK1MB4kFJR+zDvKzMroNnFDSNKR7EVpWKL0barLJ0PwQo h+3YPK/h4u15ervlMYicTZxoczyJHYesTH3qjHAhr01KsRWyHvH8iq2TEkJDxWIH Xd1OXAwBcL4K7kjL499YbCiVGYrM6gIHNTEFjFDrP/QkJPDMoB0ymaHiYoPOsTig i4sL12qcdYs3s3DrwDk+5bTaqpvLpYJC/PTAwhbjtlwHaPoyMslvLtNXJ6lRj7Od 56uicMI2vaL4q45Uq+t0FCut1RPBnOb0MbhMJvNybGT30WntpxpusD8sGf2nSOUc Mcmv63ugJWsGJ7DPUP1kFWflbtASqtag49b9DHmLFVBGtGLho0NcUXees2aajDHs KlA9muBYVLivLyTm4fx8eDtzKds766Y9397jPe3p2cA+aqZce+rTL70l1TNT3z5E nj/XCIQAWcMljobd5LTrGIgIXomu+VflmiIW3FqHebhacHYieTQVZypYSLvmbs0X 0TTLvLxvpPrHUxRjX3ON =21n+ -----END PGP SIGNATURE----- --GDLQamdgIxhPcIwq--