linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.trumtrar@pengutronix.de (Steffen Trumtrar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 05/10] arm: zynq: Move slcr initialization to separate file
Date: Wed, 27 Mar 2013 07:55:51 +0100	[thread overview]
Message-ID: <20130327065551.GC16139@pengutronix.de> (raw)
In-Reply-To: <201303262143.23708.arnd@arndb.de>

Hi Arnd,

On Tue, Mar 26, 2013 at 09:43:23PM +0000, Arnd Bergmann wrote:
> On Tuesday 26 March 2013, Michal Simek wrote:
> > Create separate slcr driver instead of pollute common code.
> > 
> > Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> 
> Can't you move that code into the zynq_cpu_clk_setup function
> instead, and only call of_clk_init(NULL) from platform code?
> 
if you are talking about the slcr function, than moving it into
a separate file is the right move. This should actually become a
real driver. The slcr is master over all clock, reset, pinmux and
ddr registers. And as all those registers can be locked/unlocked
via a slcr register (for whatever reason one would do that), there
should be one master that controls this space.

> I would like to eventually add a default call to of_clk_init(NULL)
> for all platforms, and that would be a step in that direction.
> 

Regards,
Steffen

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2013-03-27  6:55 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 17:43 Zynq core changes v2 Michal Simek
2013-03-26 17:43 ` [PATCH v2 01/10] arm: zynq: Use standard timer binding Michal Simek
2013-03-26 20:14   ` Steffen Trumtrar
2013-03-27  7:40     ` Michal Simek
2013-03-27  9:04       ` Steffen Trumtrar
2013-03-27  9:25         ` Michal Simek
2013-03-27  9:37           ` Steffen Trumtrar
2013-03-27  9:54             ` Michal Simek
2013-03-26 17:43 ` [PATCH v2 02/10] arm: zynq: Move timer to clocksource interface Michal Simek
2013-03-26 17:43 ` [PATCH v2 03/10] arm: zynq: Move timer to generic location Michal Simek
2013-03-26 17:43 ` [PATCH v2 04/10] arm: zynq: Load scu baseaddress at run time Michal Simek
2013-03-26 21:44   ` Arnd Bergmann
2013-03-27  7:49     ` Michal Simek
2013-03-27  9:29       ` Arnd Bergmann
2013-03-27  9:37         ` Michal Simek
2013-03-27 10:00           ` Arnd Bergmann
2013-03-27 10:09             ` Michal Simek
2013-03-27 10:43               ` Steffen Trumtrar
2013-03-27 10:49                 ` Michal Simek
2013-03-27 10:45               ` Arnd Bergmann
2013-03-27 10:47                 ` Michal Simek
2013-03-26 17:43 ` [PATCH v2 05/10] arm: zynq: Move slcr initialization to separate file Michal Simek
2013-03-26 21:43   ` Arnd Bergmann
2013-03-27  6:55     ` Steffen Trumtrar [this message]
2013-03-27  9:31       ` Arnd Bergmann
2013-03-27  9:41         ` Steffen Trumtrar
2013-03-27 14:15           ` Michal Simek
2013-03-27 13:01   ` Philip Balister
2013-03-27 13:31     ` Michal Simek
2013-03-26 17:43 ` [PATCH v2 06/10] arm: zynq: Add support for system reset Michal Simek
2013-03-26 17:43 ` [PATCH v2 07/10] arm: zynq: Add support for pmu Michal Simek
2013-03-26 17:43 ` [PATCH v2 08/10] arm: zynq: Add smp support Michal Simek
2013-03-27  8:59   ` Michal Simek
2013-03-26 17:43 ` [PATCH v2 09/10] arm: zynq: Add hotplug support Michal Simek
2013-03-26 17:43 ` [PATCH v2 10/10] arm: zynq: Add cpuidle support Michal Simek
2013-03-26 21:46   ` Arnd Bergmann
2013-03-27  7:56     ` Michal Simek
2013-03-27  9:27       ` Arnd Bergmann
2013-03-27 10:15         ` Daniel Lezcano
2013-03-27 10:07   ` Daniel Lezcano
2013-03-27 10:31     ` Michal Simek
2013-03-27 10:37       ` Daniel Lezcano

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=20130327065551.GC16139@pengutronix.de \
    --to=s.trumtrar@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).