From: robert.jarzmik@free•fr (Robert Jarzmik)
To: linux-arm-kernel@lists•infradead.org
Subject: PXA 2xx devictree port and clock infrastructure
Date: Wed, 28 May 2014 01:20:00 +0200 [thread overview]
Message-ID: <87vbsqdd27.fsf@free.fr> (raw)
In-Reply-To: <4580668.Rz95HmpxUr@wuerfel> (Arnd Bergmann's message of "Tue, 27 May 2014 17:49:46 +0200")
Arnd Bergmann <arnd@arndb•de> writes:
> Right, that is the general recommendation at least. I'm always a bit cautious
> when it comes to PXA because I don't expect that platform to fully get
> converted to DT in the long run, and very little new work is going on there.
>
> OTOH, if people like Robert and Daniel do this for fun, it's definitely
> great to see the full solution.
OK, so let's suppose I go for (c), and :
- create drivers/clk/clk-pxa2xx.c
=> OF clock driver
- amend the mach-pxa accordingly to move all clock stuff to this driver
Is there a clean way for the transition phase, where devicetree pxa-dt machine
will have to exist with non-DT machine code ? ie. is there around a clock driver
I can look at where both OF *and* non-OF are working ?
Ah, and given that PXA clocks are very simple :
- their rate is almost always constant, and not changeable
- only one register exists to enable/disable all the clocks (bitmask of 32
possible clock enables)
Isn't there already a skeleton to handle this type of clocks ? It looks to me
pretty generic, yet I haven't found it in drivers/clk. Maybe I missed something
?
Cheers.
--
Robert
next prev parent reply other threads:[~2014-05-27 23:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 13:02 PXA 2xx devictree port and clock infrastructure Robert Jarzmik
2014-05-27 15:17 ` Arnd Bergmann
2014-05-27 15:43 ` Mark Rutland
2014-05-27 15:49 ` Arnd Bergmann
2014-05-27 23:20 ` Robert Jarzmik [this message]
2014-05-28 1:05 ` Mike Turquette
2014-06-05 3:01 ` Andrew Ruder
2014-06-07 18:49 ` Robert Jarzmik
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=87vbsqdd27.fsf@free.fr \
--to=robert.jarzmik@free$(echo .)fr \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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