From: Stephen Boyd <sboyd@codeaurora.org>
To: Rob Herring <robh@kernel.org>
Cc: Dinh Nguyen <dinguyen@kernel.org>,
mark.rutland@arm.com, mturquette@baylibre.com,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv1 1/4] ARM: dts: socfpga: update documentation for clock bindings
Date: Fri, 21 Jul 2017 13:38:47 -0700 [thread overview]
Message-ID: <20170721203847.GI19878@codeaurora.org> (raw)
In-Reply-To: <20170710155134.d6egwhncc3mw5ch5@rob-hp-laptop>
On 07/10, Rob Herring wrote:
> On Fri, Jul 07, 2017 at 02:03:16PM -0500, Dinh Nguyen wrote:
> > Update the bindings document for the Arria10 and Stratix10 clock bindings.
> >
> > Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>
> > ---
> > Documentation/devicetree/bindings/clock/altr_socfpga.txt | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/clock/altr_socfpga.txt b/Documentation/devicetree/bindings/clock/altr_socfpga.txt
> > index f72e80e..1c32658 100644
> > --- a/Documentation/devicetree/bindings/clock/altr_socfpga.txt
> > +++ b/Documentation/devicetree/bindings/clock/altr_socfpga.txt
> > @@ -12,6 +12,20 @@ Required properties:
> > "altr,socfpga-gate-clk" - Clocks that directly feed peripherals and
> > can get gated.
> >
> > + For Arria10:
> > + "altr,socfpga-a10-pll-clock" - for a PLL clock
> > + "altr,socfpga-a10-perip-clock" - The peripheral clock divided from the
> > + PLL clock.
> > + "altr,socfpga-a10-gate-clk" - Clocks that directly feed peripherals and
> > + can get gated.
> > +
> > + For Stratix10:
> > + "altr,socfpga-s10-pll-clock" - for a PLL clock
> > + "altr,socfpga-s10-perip-clock" - The peripheral clock divided from the
> > + PLL clock.
> > + "altr,socfpga-s10-gate-clk" - Clocks that directly feed peripherals and
> > + can get gated.
>
> We're generally not doing a clock per node clock providers on new
> platforms and doing a single (or few) clock controller nodes instead. It
> doesn't look like there's much or any reuse here from older platforms
> which would be the main reason to keep this style.
Agreed. Can this be rewritten to new style binding?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-07-21 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 19:03 [PATCHv1 1/4] ARM: dts: socfpga: update documentation for clock bindings Dinh Nguyen
2017-07-07 19:03 ` [PATCHv1 3/4] arm64: dts: add complete clock tree for SoCFPGA Stratix10 Dinh Nguyen
[not found] ` <1499454199-31901-1-git-send-email-dinguyen-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-07-07 19:03 ` [PATCHv1 2/4] ARM: dts: socfpga: add a bypass-reg binding for Stratix10 Dinh Nguyen
2017-07-07 19:03 ` [PATCHv1 4/4] clk: socfpga: Add a clock driver for the SoCFPGA Stratix10 platform Dinh Nguyen
2017-07-10 15:51 ` [PATCHv1 1/4] ARM: dts: socfpga: update documentation for clock bindings Rob Herring
2017-07-21 20:38 ` Stephen Boyd [this message]
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=20170721203847.GI19878@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--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;
as well as URLs for NNTP newsgroup(s).