From: Jean-Francois Moine <moinejf@free.fr> To: Maxime Ripard <maxime.ripard@free-electrons.com> Cc: Chen-Yu Tsai <wens@csie.org>, Mike Turquette <mturquette@baylibre.com>, Stephen Boyd <sboyd@codeaurora.org>, Jens Kuske <jenskuske@gmail.com>, Vishnu Patekar <vishnupatekar0510@gmail.com>, Hans de Goede <hdegoede@redhat.com>, linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org Subject: Re: [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused Date: Wed, 10 Feb 2016 18:04:20 +0100 [thread overview] Message-ID: <20160210180420.0968c2018bf5fbe54a28a505@free.fr> (raw) In-Reply-To: <20160210125333.GC31506@lukather> On Wed, 10 Feb 2016 13:53:33 +0100 Maxime Ripard <maxime.ripard@free-electrons.com> wrote: > > I don't agree: > > - you changed the DTs of many SoCs without any valid reason, >=20 > I did give you a significant number of reasons [1]. The fact that you > chose to ignore them is up to you. Sorry, I don't see any reason for changing the DT definition of the pll6. The clock is named "pll6" with "#clock-cells =3D <1>;" in all DTs, and it works as it is. If you want an other clock as "pll8", with the same HW description, you must add new code for this clock. > Except that it doesn't match the hardware and that the parenthood > relationship is inversed. The pll6 output is 24 MHz * n * k / 2, as > seen in any datasheet that uses it. Your clock driver doesn't > represent that fact. The datasheet says that the pll6x2 output is 24 MHz * n * k, then, if I remember correctly my lessons at primary school, defining pll6 as (pll6x2 / 2) gives 24 MHz * n * k / 2 as the pll6 output. No? --=20 Ken ar c'henta=F1 | ** Breizh ha Linux atav! ** Jef | http://moinejf.free.fr/
WARNING: multiple messages have this Message-ID (diff)
From: moinejf@free.fr (Jean-Francois Moine) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused Date: Wed, 10 Feb 2016 18:04:20 +0100 [thread overview] Message-ID: <20160210180420.0968c2018bf5fbe54a28a505@free.fr> (raw) In-Reply-To: <20160210125333.GC31506@lukather> On Wed, 10 Feb 2016 13:53:33 +0100 Maxime Ripard <maxime.ripard@free-electrons.com> wrote: > > I don't agree: > > - you changed the DTs of many SoCs without any valid reason, > > I did give you a significant number of reasons [1]. The fact that you > chose to ignore them is up to you. Sorry, I don't see any reason for changing the DT definition of the pll6. The clock is named "pll6" with "#clock-cells = <1>;" in all DTs, and it works as it is. If you want an other clock as "pll8", with the same HW description, you must add new code for this clock. > Except that it doesn't match the hardware and that the parenthood > relationship is inversed. The pll6 output is 24 MHz * n * k / 2, as > seen in any datasheet that uses it. Your clock driver doesn't > represent that fact. The datasheet says that the pll6x2 output is 24 MHz * n * k, then, if I remember correctly my lessons at primary school, defining pll6 as (pll6x2 / 2) gives 24 MHz * n * k / 2 as the pll6 output. No? -- Ken ar c'henta? | ** Breizh ha Linux atav! ** Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2016-02-10 17:04 UTC|newest] Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-02-01 20:20 [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused Maxime Ripard 2016-02-01 20:20 ` Maxime Ripard 2016-02-04 12:05 ` Maxime Ripard 2016-02-04 12:05 ` Maxime Ripard 2016-02-04 15:25 ` Jean-Francois Moine 2016-02-04 15:25 ` Jean-Francois Moine 2016-02-10 12:53 ` Maxime Ripard 2016-02-10 12:53 ` Maxime Ripard 2016-02-10 17:04 ` Jean-Francois Moine [this message] 2016-02-10 17:04 ` Jean-Francois Moine 2016-02-11 9:53 ` Maxime Ripard 2016-02-11 9:53 ` Maxime Ripard 2016-02-05 17:59 ` Andre Przywara 2016-02-05 17:59 ` Andre Przywara 2016-02-10 12:30 ` breaking DT compatibility (was: Re: [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused) Andre Przywara 2016-02-10 12:30 ` Andre Przywara 2016-02-10 13:42 ` Rob Herring 2016-02-10 13:42 ` Rob Herring 2016-02-10 14:37 ` Maxime Ripard 2016-02-10 14:37 ` Maxime Ripard 2016-02-10 14:45 ` Arnd Bergmann 2016-02-10 14:45 ` Arnd Bergmann 2016-02-10 14:45 ` Arnd Bergmann 2016-02-10 16:14 ` breaking DT compatibility Andre Przywara 2016-02-10 16:14 ` Andre Przywara 2016-02-11 10:16 ` Maxime Ripard 2016-02-11 10:16 ` Maxime Ripard 2016-02-10 16:30 ` breaking DT compatibility (was: Re: [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused) Mark Rutland 2016-02-10 16:30 ` Mark Rutland 2016-02-11 10:00 ` Maxime Ripard 2016-02-11 10:00 ` Maxime Ripard 2016-02-11 11:44 ` Mark Rutland 2016-02-11 11:44 ` Mark Rutland 2016-02-11 12:29 ` breaking DT compatibility Andre Przywara 2016-02-11 12:29 ` Andre Przywara 2016-02-11 17:08 ` breaking DT compatibility (was: Re: [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused) Maxime Ripard 2016-02-11 17:08 ` Maxime Ripard 2016-02-12 9:40 ` Lucas Stach 2016-02-12 9:40 ` Lucas Stach 2016-02-12 9:40 ` Lucas Stach 2016-02-16 8:44 ` Maxime Ripard 2016-02-16 8:44 ` Maxime Ripard 2016-02-16 19:40 ` Michael Turquette 2016-02-16 19:40 ` Michael Turquette 2016-02-16 19:40 ` Michael Turquette 2016-02-16 21:11 ` Rob Herring 2016-02-11 14:51 ` Richard Cochran 2016-02-11 14:51 ` Richard Cochran 2016-02-11 15:16 ` breaking DT compatibility Andre Przywara 2016-02-11 15:16 ` Andre Przywara 2016-02-11 21:46 ` breaking DT compatibility (was: Re: [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused) Rob Herring 2016-02-11 21:46 ` Rob Herring 2016-02-11 21:46 ` Rob Herring 2016-02-10 12:59 ` [PATCH v4] clk: sunxi: Refactor A31 PLL6 so that it can be reused Maxime Ripard 2016-02-10 12:59 ` Maxime Ripard 2016-02-10 14:02 ` Rob Herring 2016-02-10 14:02 ` Rob Herring 2016-02-11 9:41 ` Maxime Ripard 2016-02-11 9:41 ` Maxime Ripard 2016-02-10 18:41 ` Mark Rutland 2016-02-10 18:41 ` Mark Rutland
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20160210180420.0968c2018bf5fbe54a28a505@free.fr \ --to=moinejf@free.fr \ --cc=hdegoede@redhat.com \ --cc=jenskuske@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-clk@vger.kernel.org \ --cc=maxime.ripard@free-electrons.com \ --cc=mturquette@baylibre.com \ --cc=sboyd@codeaurora.org \ --cc=vishnupatekar0510@gmail.com \ --cc=wens@csie.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.