From: thomas.petazzoni@free-electrons•com (Thomas Petazzoni)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 4/5] dt-bindings: arm: add DT binding for Marvell CP110 system controller
Date: Wed, 13 Apr 2016 18:01:22 +0200 [thread overview]
Message-ID: <20160413180122.4f997a9a@free-electrons.com> (raw)
In-Reply-To: <20160328194756.GA28967@rob-hp-laptop>
Hello,
On Mon, 28 Mar 2016 14:47:56 -0500, Rob Herring wrote:
> > + - reg: register area of the CP110 system controller 0
> > + - #clock-cells: must be set to 2
> > + - core-clock-output-names must be set to:
> > + "cpm-apll", "cpm-ppv2-core", "cpm-eip", "cpm-core", "cpm-nand-core"
> > + - gatable-clock-indices must be set to:
> > + <0>, <1>, <2>, <3>, <4>, <5>, <6>, <7>, <8>,
> > + <9>, <11>, <12>, <13>, <14>, <15>, <16>, <18>,
> > + <22>, <23>, <24>, <25>, <26>
>
> You aren't skipping very many spots. I'd just fill the unused names in
> with "none" or something.
>
> > + - gatable-clock-output-names must be set to:
> > + "cpm-audio", "cpm-communit", "cpm-nand", "cpm-ppv2", "cpm-sdio",
> > + "cpm-mg-domain", "cpm-mg-core", "cpm-xor1", "cpm-xor0", "cpm-gop-dp", "cpm-pcie_x10",
> > + "cpm-pcie_x11", "cpm-pcie_x4", "cpm-pcie-xor", "cpm-sata", "cpm-sata-usb",
> > + "cpm-gop-macro", "cpm-usb3h0", "cpm-usb3h1", "cpm-usb3dev", "cpm-eip150",
> > + "cpm-eip197"
In fact, the more I think of it, the less I find encoding the clock
output names in the DT to be useful for such a driver. For generic
clock drivers, it makes complete sense, but here the driver is really
tied to the specific system controller of that SoC, so the clock names
will not change.
In addition, those gatable clocks are not independent from each other:
many of them are parent from others (this wasn't encoded into the
driver until now, because I didn't had this info until now). So the
driver will anyway have to have a lot of knowledge about which clock is
child/parent of which one. Which means the driver is anyway really
tied to that specific system controller.
Does it still make sense to encode the clock names in the DT in such a
case, or should the driver be providing the clock names?
(I don't have a strong opinion either way, I'm just asking what is the
preference of the DT and clock maintainers on the matter.).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-13 16:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 9:26 [PATCH v4 0/5] clk: mvebu: clock drivers for Marvell Armada 7K/8K Thomas Petazzoni
2016-03-27 9:26 ` [PATCH v4 1/5] clk: unconditionally recurse into clk/mvebu/ Thomas Petazzoni
2016-04-02 1:25 ` Stephen Boyd
2016-03-27 9:26 ` [PATCH v4 2/5] dt-bindings: arm: add DT binding for Marvell AP806 system controller Thomas Petazzoni
2016-04-02 1:26 ` Stephen Boyd
2016-03-27 9:26 ` [PATCH v4 3/5] clk: mvebu: new driver for Armada " Thomas Petazzoni
2016-04-02 1:27 ` Stephen Boyd
2016-04-13 14:32 ` Thomas Petazzoni
2016-03-27 9:26 ` [PATCH v4 4/5] dt-bindings: arm: add DT binding for Marvell CP110 " Thomas Petazzoni
2016-03-28 19:47 ` Rob Herring
2016-04-11 15:59 ` Thomas Petazzoni
2016-04-13 16:01 ` Thomas Petazzoni [this message]
2016-04-14 7:49 ` Thomas Petazzoni
2016-04-14 19:19 ` Geert Uytterhoeven
2016-04-23 14:22 ` Thomas Petazzoni
2016-04-24 9:15 ` Geert Uytterhoeven
2016-03-27 9:26 ` [PATCH v4 5/5] clk: mvebu: new driver for Armada " Thomas Petazzoni
2016-04-02 1:25 ` Stephen Boyd
2016-04-13 15:30 ` Thomas Petazzoni
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=20160413180122.4f997a9a@free-electrons.com \
--to=thomas.petazzoni@free-electrons$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox