public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/7] arm64: ARMv8 RTSM model (SoC) support
Date: Wed, 19 Dec 2012 15:28:06 +0000	[thread overview]
Message-ID: <1355930886.22260.53.camel@hornet> (raw)
In-Reply-To: <201212181759.45394.arnd@arndb.de>

On Tue, 2012-12-18 at 17:59 +0000, Arnd Bergmann wrote:
> On Tuesday 18 December 2012, Catalin Marinas wrote:
> > After some more thinking, none of these would work for arch/arm since
> > vexpress_clk_of_init() is called very early via the time_init() ...
> > v2m_dt_timer_init(). On arm64 we rely on the architected timers to be
> > always present but this assumption is not valid on arm where clocks
> > would need to be initialised early.
> > 
> > While I'd really like to get rid of the SoC code in arch/arm64, the best
> > place I see for the vexpress_clk_of_init() call is still the arch code
> > (unless we add #ifdefs in the clk-vexpress.c code).
> 
> I think I'd prefer the #ifdef in this case. Ideally, we would get rid
> of most of the early init functions in ARM as well, but that is
> a different battle for now. Getting the arch/arm64 to look nice
> IMHO is more important in this case, and we can fix the 32 bit
> version later.

I'm sure we'll be able to make the vexpress_clk_* functions behave
correctly, either with a help of #ifdef or in some other way - don't
concern yourself with this detail.

The bigger fish to fry is the generic initialization of the clocks (as
in: when to call the of_clk_init() and how to gather all possible
of_match-es)...

Pawe?

  reply	other threads:[~2012-12-19 15:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07 21:06 [PATCH 0/7] arm64: Initial SoC support (ARMv8 RTSM model) Catalin Marinas
2012-12-07 21:06 ` [PATCH 1/7] arm: Move sp810.h to include/linux/amba/ Catalin Marinas
2012-12-07 21:06 ` [PATCH 2/7] arm64: Add dtbs target for building all the enabled dtb files Catalin Marinas
2012-12-07 21:47   ` Rob Herring
2012-12-10 18:04     ` Catalin Marinas
2012-12-11  2:30       ` Rob Herring
2012-12-07 21:06 ` [PATCH 3/7] arm64: SoC infrastructure preparation Catalin Marinas
2012-12-07 21:06 ` [PATCH 4/7] arm64: Populate the platform devices Catalin Marinas
2012-12-07 21:06 ` [PATCH 5/7] arm64: ARMv8 RTSM model (SoC) support Catalin Marinas
2012-12-11 15:41   ` Arnd Bergmann
2012-12-11 16:39     ` Catalin Marinas
2012-12-11 17:21       ` Pawel Moll
2012-12-11 17:45         ` Catalin Marinas
2012-12-18 16:29       ` Catalin Marinas
2012-12-18 17:59         ` Arnd Bergmann
2012-12-19 15:28           ` Pawel Moll [this message]
2012-12-19 15:52             ` Catalin Marinas
2012-12-07 21:06 ` [PATCH 6/7] arm64: Add dts files for the ARMv8 RTSM model Catalin Marinas
2012-12-07 21:06 ` [PATCH 7/7] arm64: Add simple earlyprintk support Catalin Marinas

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=1355930886.22260.53.camel@hornet \
    --to=pawel.moll@arm.com \
    --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