From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3 v4] arm: kirkwood: add dreamplug (fdt) support.
Date: Thu, 1 Mar 2012 00:53:26 +0100 [thread overview]
Message-ID: <20120229235326.GA3207@lunn.ch> (raw)
In-Reply-To: <20120229144450.GB23524@titan.lakedaemon.net>
On Wed, Feb 29, 2012 at 09:44:50AM -0500, Jason wrote:
> Andrew,
>
> On Fri, Feb 24, 2012 at 08:57:53AM +0100, Andrew Lunn wrote:
> > I have some patches under development which will help.
>
> Any chance you could shoot those to me? (on-list preferable) I'm
> thinking we could convert it to an interim solution eg
> kirkwood_{get,put}_clock() that would be easy to migrate to generic
> CLK/clkdev once it lands.
Hi Jason
It is not that easy. It is not kirkwood, but all platform orion, so
includes dove, orion5x, mv78xx0 and kirkwood. All these share the same
device drivers, since they all share the same SoC peripheral
cores. However, only kirkwood has per peripheral gated clocks and all
the others share tclk.
I've also broke orion5x twice so far with my patches, since i don't
have any hardware with that SoC. So this time i was hoping to ask for
testing on orion5x before submitting to mainline.
Mike did say he hoped the generic clk would be ready last week. Maybe
we should ping him and ask for a new ETA?
Andrew
next prev parent reply other threads:[~2012-02-29 23:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120224075753.GA24858@lunn.ch>
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
2012-02-29 23:53 ` Andrew Lunn [this message]
2012-03-01 12:20 ` Jason
2012-02-22 19:18 [PATCH 0/3 v4] arm: kirkwood: add dreamplug/devicetree support Jason Cooper
2012-02-22 19:18 ` [PATCH 2/3 v4] arm: kirkwood: add dreamplug (fdt) support Jason Cooper
2012-02-22 20:46 ` Arnd Bergmann
2012-02-22 21:17 ` Nicolas Pitre
2012-02-23 3:19 ` Rob Herring
2012-02-23 7:34 ` Arnd Bergmann
2012-02-23 16:12 ` Jason
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=20120229235326.GA3207@lunn.ch \
--to=andrew@lunn.ch \
--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).