From: Stephen Boyd <sboyd@codeaurora.org>
To: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
clk <linux-clk@vger.kernel.org>, Mason <slash.tmp@free.fr>
Subject: Re: [PATCH v4] clk: tango4: clkgen driver for Tango4 platforms
Date: Fri, 30 Oct 2015 09:29:25 -0700 [thread overview]
Message-ID: <20151030162925.GC19782@codeaurora.org> (raw)
In-Reply-To: <563361B8.7090300@sigmadesigns.com>
On 10/30, Marc Gonzalez wrote:
> diff --git a/Documentation/devicetree/bindings/clock/tango4-clock.txt b/Documentation/devicetree/bindings/clock/tango4-clock.txt
> new file mode 100644
> index 000000000000..19c580a7bda2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/tango4-clock.txt
> @@ -0,0 +1,23 @@
> +* Sigma Designs Tango4 Clock Generator
> +
> +The Tango4 clock generator outputs cpu_clk and sys_clk (the latter is used
> +for RAM and various peripheral devices). The clock binding described here
> +is applicable to all Tango4 SoCs.
> +
> +Required Properties:
> +
> +- compatible: should be "sigma,tango4-clkgen".
You should add sigma to the vendor prefix file
Documentation/devicetree/bindings/vendor-prefixes.txt
Send that patch to the DT maintainers (Rob has been applying most
vendor prefix patches).
Otherwise this patch looks fine and I'll apply it to clk-next
after v4.4-rc1 comes out (in about 2 weeks). We'll target v4.5.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-10-30 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 15:40 [PATCH v3] clk: tango4: clkgen driver for Tango4 ARM platforms Marc Gonzalez
2015-10-28 9:02 ` Marc Gonzalez
2015-10-29 0:56 ` Stephen Boyd
2015-10-30 12:25 ` [PATCH v4] clk: tango4: clkgen driver for Tango4 platforms Marc Gonzalez
2015-10-30 16:29 ` Stephen Boyd [this message]
2015-10-30 18:48 ` Mason
2015-10-30 19:10 ` 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=20151030162925.GC19782@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-clk@vger.kernel.org \
--cc=marc_gonzalez@sigmadesigns.com \
--cc=mturquette@baylibre.com \
--cc=slash.tmp@free.fr \
/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 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.