From: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>
To: jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 2/3 v4] arm: kirkwood: add dreamplug (fdt) support.
Date: Fri, 24 Feb 2012 08:57:53 +0100 [thread overview]
Message-ID: <20120224075753.GA24858@lunn.ch> (raw)
Hi Jason
Great to see this work going forward. I hope we can cooperating in the
future. I have an out of tree kirkwood board i would like to supported
via DT, and i also have a QNAP T119+ i can use for testing.
I have some patches under development which will help. I've been
porting the different Orion machines to use Mike Turquette generic CLK
and clkdev so that the device drivers can determine for themselves
what the clock is. tclk is then removed from the platform data
structures, making DT a little bit simpler. This work should also
solve the kirkwood clock gating which is going to be an issue for
DT. For example, your board file is probably currently calling
kirkwood_spi_init(), in order to use SPI. This does:
kirkwood_clk_ctrl |= CGC_RUNIT;
and so ensures that the RUNIT clock does not get turned off in a
lateinit call. Once you have DT, this flag is not going to be set, and
so you have the danger of the clock to the SPI core gets turned
off. The clk framework should solve this, since the SPI device driver
will claim the clock and ensure it keeps running.
I'm hoping the next version of Mike Turquette patches get included in
the tree soon, so i can finish my patches for integration.
Andrew
next reply other threads:[~2012-02-24 7:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 7:57 Andrew Lunn [this message]
[not found] ` <20120224075753.GA24858-g2DYL2Zd6BY@public.gmane.org>
2012-02-24 15:55 ` [PATCH 2/3 v4] arm: kirkwood: add dreamplug (fdt) support Jason
2012-02-24 19:36 ` Jason
2012-02-29 14:44 ` Jason
[not found] ` <20120229144450.GB23524-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2012-02-29 23:53 ` Andrew Lunn
[not found] ` <20120229235326.GA3207-g2DYL2Zd6BY@public.gmane.org>
2012-03-01 12:20 ` Jason
-- strict thread matches above, loose matches on Subject: below --
2012-02-22 19:18 [PATCH 0/3 v4] arm: kirkwood: add dreamplug/devicetree support Jason Cooper
[not found] ` <cover.1312906908.git.jason@lakedaemon.net>
2012-02-22 19:18 ` [PATCH 2/3 v4] arm: kirkwood: add dreamplug (fdt) support Jason Cooper
[not found] ` <8532afcdc4adbb3771e6f742bcc33ef9c0347858.1329936660.git.jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>
2012-02-22 20:46 ` Arnd Bergmann
[not found] ` <201202222046.28707.arnd-r2nGTMty4D4@public.gmane.org>
2012-02-22 21:17 ` Nicolas Pitre
2012-02-23 3:19 ` Rob Herring
[not found] ` <4F45B043.1080302-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-02-23 7:34 ` Arnd Bergmann
2012-02-23 16:12 ` Jason
[not found] ` <20120223161210.GN23524-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2012-02-23 18:56 ` Grant Likely
2012-02-23 19:00 ` Jason
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=20120224075753.GA24858@lunn.ch \
--to=andrew-g2dyl2zd6by@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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).