linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Switch pxa architecture to clock framework
Date: Mon, 23 Feb 2015 22:59:12 +0100	[thread overview]
Message-ID: <87sidw47db.fsf@free.fr> (raw)
In-Reply-To: <1423346043-7391-1-git-send-email-robert.jarzmik@free.fr> (Robert Jarzmik's message of "Sat, 7 Feb 2015 22:54:01 +0100")

Robert Jarzmik <robert.jarzmik@free.fr> writes:

> This is it, everything looks ready for the leap of faith.
>
> This serie removes all legacy clock code, and pxa25x, pxa27x and pxa3xx are
> migrated to clock framework. This serie was tested on lubbock (pxa250), mioa701
> (pxa270) and zylonite (pxa310). I plan to test also cm-x300 and mainstone in the
> near future.
>
> This has the potential to break many pxa boards. The more test it receives, the
> better. I'd like this to hit v3.21.

I'll tentatively queue that up in pxa/for-next, as cm-x300 is also up and running.
If if the next 4 weeks the tests are still giving green lights, then 4.1 will be
the leap of faith for clocks.

This will settle one of the milestones, ie. several platforms (pxa3xx and
pxa27x) do work in both legacy and device-tree mode, with a subset of drivers.

The remaining parts I forsee are :
 - dmaengine conversion
   This is underway, but might take 1 or 2 cycles.
 - pxafb driver device-tree support

Cheers.

--
Robert

      parent reply	other threads:[~2015-02-23 21:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-07 21:54 [PATCH 0/2] Switch pxa architecture to clock framework Robert Jarzmik
2015-02-07 21:54 ` [PATCH 1/2] ARM: pxa: convert eseries " Robert Jarzmik
2015-02-07 21:54 ` [PATCH 2/2] ARM: pxa: Transition pxa25x, pxa27x, pxa3xx to clk framework Robert Jarzmik
2015-02-23 21:59 ` Robert Jarzmik [this message]

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=87sidw47db.fsf@free.fr \
    --to=robert.jarzmik@free.fr \
    --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).