linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars Persson <lars.persson@axis.com>
To: <mturquette@baylibre.com>, <sboyd@codeaurora.org>
Cc: <devicetree@vger.kernel.org>, <linux-clk@vger.kernel.org>,
	<robh+dt@kernel.org>, <pawel.moll@arm.com>,
	<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
	<galak@codeaurora.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/2] clk: Add Artpec-6 SoC support
Date: Wed, 23 Mar 2016 09:41:13 +0100	[thread overview]
Message-ID: <56F256A9.6040405@axis.com> (raw)
In-Reply-To: <cover.1456411894.git.larper@axis.com>

Michael & Stephen,

Should we resubmit this series for 4.7 ?

Also to follow up on your previous request to use the platform driver 
framework. We have noticed recent submissions use a style that mixes 
early clocks registered with CLK_OF_DECLARE and the remaining clocks 
registered through a platform driver. Is this the style we should 
implement ?

Best Regards,
  Lars Persson


On 02/25/2016 03:58 PM, Lars Persson wrote:
> Add clock support for the Artpec-6 SoC port. The ARM parts are in the series
> "arm: Add Artpec-6 SoC" and it goes through the arm-soc tree.
>
> Changes since v3:
> - The binding was corrected to handle two fractional divider clocks as input to
>    the clock controller.
> - Updated clk-artpec6.c to handle a distinct fractional divider input for each
>    i2s clock mux.
>
> Changes since v2:
> - Moved axis,artpec6-clkctrl.h to the first patch with the DT bindings.
>
> Changes since v1:
>
> - The driver now provides all clocks from the main clock controller block
>    through one DT node.
> - Added a header file for the clock indexes.
> - Refer to clock-bindings.txt in the bindings document.
>
> A platform driver was not possible because the clocks are needed earlier in the
> kernel startup.
>
> Lars Persson (2):
>    clk: add device tree binding for Artpec-6 clock controller
>    clk: add artpec-6 clock controller
>
>   .../devicetree/bindings/clock/artpec6.txt          |  41 +++++
>   drivers/clk/Makefile                               |   1 +
>   drivers/clk/axis/Makefile                          |   1 +
>   drivers/clk/axis/clk-artpec6.c                     | 189 +++++++++++++++++++++
>   include/dt-bindings/clock/axis,artpec6-clkctrl.h   |  38 +++++
>   5 files changed, 270 insertions(+)
>   create mode 100644 Documentation/devicetree/bindings/clock/artpec6.txt
>   create mode 100644 drivers/clk/axis/Makefile
>   create mode 100644 drivers/clk/axis/clk-artpec6.c
>   create mode 100644 include/dt-bindings/clock/axis,artpec6-clkctrl.h
>

  parent reply	other threads:[~2016-03-23  8:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 14:58 [PATCH v4 0/2] clk: Add Artpec-6 SoC support Lars Persson
2016-02-25 14:58 ` [PATCH v4 1/2] clk: add device tree binding for Artpec-6 clock controller Lars Persson
2016-02-25 14:58 ` [PATCH v4 2/2] clk: add artpec-6 " Lars Persson
2016-03-23  8:41 ` Lars Persson [this message]
2016-03-25 23:08   ` [PATCH v4 0/2] clk: Add Artpec-6 SoC support 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=56F256A9.6040405@axis.com \
    --to=lars.persson@axis.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.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).