From: Paul Burton <paul.burton@imgtec.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>,
"Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>," <linux-clk@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 16/18] dt-bindings: Document img,boston-clock binding
Date: Tue, 11 Oct 2016 16:56:01 +0100 [thread overview]
Message-ID: <7552292.CRP11Bd59v@np-p-burton> (raw)
In-Reply-To: <20161010130121.GA31827@rob-hp-laptop>
[-- Attachment #1.1: Type: text/plain, Size: 2410 bytes --]
On Monday, 10 October 2016 08:01:21 BST Rob Herring wrote:
> On Wed, Oct 05, 2016 at 06:18:22PM +0100, Paul Burton wrote:
> > Add device tree binding documentation for the clocks provided by the
> > MIPS Boston development board from Imagination Technologies, and a
> > header file describing the available clocks for use by device trees &
> > driver.
> >
> > Signed-off-by: Paul Burton <paul.burton@imgtec.com>
> > Cc: Michael Turquette <mturquette@baylibre.com>
> > Cc: Stephen Boyd <sboyd@codeaurora.org>
> > Cc: linux-clk@vger.kernel.org
> > Cc: Rob Herring <robh+dt@kernel.org>
> > Cc: Mark Rutland <mark.rutland@arm.com>
> > Cc: devicetree@vger.kernel.org
> >
> > ---
> >
> > Changes in v3: None
> > Changes in v2:
> > - Add BOSTON_CLK_INPUT to expose the input clock.
> >
> > .../devicetree/bindings/clock/img,boston-clock.txt | 27
> > ++++++++++++++++++++++ include/dt-bindings/clock/boston-clock.h
> > | 14 +++++++++++ 2 files changed, 41 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/clock/img,boston-clock.txt create mode
> > 100644 include/dt-bindings/clock/boston-clock.h
> >
> > diff --git a/Documentation/devicetree/bindings/clock/img,boston-clock.txt
> > b/Documentation/devicetree/bindings/clock/img,boston-clock.txt new file
> > mode 100644
> > index 0000000..c01ea60
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/clock/img,boston-clock.txt
> > @@ -0,0 +1,27 @@
> > +Binding for Imagination Technologies MIPS Boston clock sources.
> > +
> > +This binding uses the common clock binding[1].
> > +
> > +[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
> > +
> > +Required properties:
> > +- compatible : Should be "img,boston-clock".
> > +- #clock-cells : Should be set to 1.
> > + Values available for clock consumers can be found in the header file:
> > + <dt-bindings/clock/boston-clock.h>
> > +- regmap : Phandle to the Boston platform register system controller.
> > + This should contain a phandle to the system controller node covering
> > the
> > + platform registers provided by the Boston board.
>
> Can you just make the clock node a child of the system controller and
> drop this?
>
> Rob
Hi Rob,
As I mentioned before technically that could be done, but it would really not be at all
reflective of the hardware & so seems somewhat contrary to the purpose of a device tree.
Thanks,
Paul
[-- Attachment #1.2: Type: text/html, Size: 11783 bytes --]
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-10-11 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161005171824.18014-1-paul.burton@imgtec.com>
2016-10-05 17:18 ` [PATCH v3 16/18] dt-bindings: Document img,boston-clock binding Paul Burton
[not found] ` <20161005171824.18014-17-paul.burton-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2016-10-10 13:01 ` Rob Herring
2016-10-11 15:56 ` Paul Burton [this message]
2016-10-11 16:00 ` Paul Burton
2016-10-11 20:06 ` Rob Herring
2016-10-11 21:15 ` Paul Burton
2016-10-19 0:46 ` Stephen Boyd
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=7552292.CRP11Bd59v@np-p-burton \
--to=paul.burton@imgtec.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=ralf@linux-mips.org \
--cc=robh@kernel.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: link
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