From: Jamie Iles <jamie@jamieiles.com>
To: devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: ARM/DT: registering clks from DT in .init_early
Date: Thu, 9 Jun 2011 17:45:57 +0100 [thread overview]
Message-ID: <20110609164557.GK3711@pulham.picochip.com> (raw)
I'm currently working on moving our platform to device tree with the aim
of mainlining it. Before device tree we registered the clks in the
.init_early machine callback which is fine as the clks are static data.
I'm now trying to dynamically register these clks from the device tree
but the slab allocator isn't available at this stage so I can't allocate
them dynamically.
Am I heading in the wrong direction here? We currently get the
clocksource and clock event frequency from a clk so I don't think this
can be made later (though I guess this could come from device tree
instead).
Jamie
next reply other threads:[~2011-06-09 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 16:45 Jamie Iles [this message]
[not found] ` <20110609164557.GK3711-apL1N+EY0C9YtYNIL7UdTEEOCMrvLtNR@public.gmane.org>
2011-06-09 19:28 ` ARM/DT: registering clks from DT in .init_early Jamie Iles
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=20110609164557.GK3711@pulham.picochip.com \
--to=jamie@jamieiles.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--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).