Skip to content

Migrate PXA27x platforms to clock framework

Robert Jarzmik linux-arm-kernel linux-devicetree 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 4 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 4 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/4] Migrate PXA27x platforms to clock framework
Quoted 17 lines · Arnd Bergmann
Quoted 16 lines · On Sunday 29 June 2014 20:32:20 Robert Jarzmik wrote:

As the RFC posted in [1] didn't meet an unrivaled success for review, I'm posting this serie for PXA27x transition to clock framework.

This transition is needed :
- to enable device-tree drivers port, as clocks are needed almost everywhere
- to enable the long term multi-platform kernel to support PXA

As I had said before, this serie aims at :
- keeping legacy platforms working (ie. without device-tree)
- enable PXA27x to work with a device-tree kernel, and hence open the way to drivers conversion
- be robust enough to support pxa25x and pxa3xx later inclusion with almost no change to clk-pxa-dt.c.

Quoted 8 lines
Quoted 3 lines

As this serie is holding the rest of the device-tree drivers port, I'd like it to be reviewed, even it's an old unsexy platform.

I have one basic question about this series: if pxa27x gets moved to used the common-clk framework but the others (pxa25x, pxa26x, pxa3xx, pxa93x) don't, does that imply that they become mutually exclusiv at compile-time?

Unfortunately yes, they become exclusive.
The reason being that arch/arm/mach-pxa/clock.c defines the function "clk_enable()", which of course is also defined by the clock framework.

Quoted 3 lines

If so, do you plan to first complete all of them before merging upstream, or do you intend to have one or more kernel releases that don't allow building a combined kernel for all pxa platforms?

I intend to have first only pxa27x.
Then in a second stage pxa27x + pxa25x + pxa3xx.

Quoted 3 lines

I don't object to doing the latter, but if that is the plan, you need to make that very clear in the changelog and have all the relevant maintainers agree to that.

OK, that would be Haojian then, I think he maintains all PXA platforms.

Haojian, are you ok with that ? And BTW, does a combined kernel for PXA platforms even exists (mixing pxa3xx and pxa2xx for example) ?

Quoted 2 lines

Also (for my understanding) when you say that you plan to do pxa25x and pxa3xx next, does that include pxa26x and pxa93x?

I don't have the Technical Reference Manuals for these ones so the answer is no. And Google wasn't a great friend at providing them.

Quoted 2 lines

I assume it does as they are apparently minor revisions of the former, but it's not completely clear from your description.

My description doesn't mention them, as I have no information about them, nor any hardware to test on.

Cheers.

Signature · 1 line
Robert