Using Device Tree on ARM
identify topics for further discussion for DT on ARM
generate appropriate blueprints/specs for specific areas of development
Blueprint information
- Status:
- Complete
- Approver:
- Steve Langasek
- Priority:
- Essential
- Drafter:
- Jeremy Kerr
- Direction:
- Needs approval
- Assignee:
- Jeremy Kerr
- Definition:
- Approved
- Series goal:
- Accepted for maverick
- Implementation:
-
Implemented
- Milestone target:
-
ubuntu-10.10
- Started by
- Steve Langasek
- Completed by
- Steve Langasek
Whiteboard
[asac 22 Jun 10]: please consider split up the work items in per milestone blocks ... i doubt that everything will happen between beta and 10.10 :) ... and adjust the overall milestone accordingly.
Status:
* Proposed boot interface on linux-arm-kernel and devicetree-discuss
* Adapting clock domain patches to an upstream-friendly patchset
[vorlon] do we need work items here about making sure the patches are included in the kernel for 10.10?
work items for ubuntu-10.10:
[jk-ozlabs] boot interface: begin discussion on linux-arm-kernel list: DONE
[jk-ozlabs] clock infrastructure: bring clock infrastructure up to 2.6.34: DONE
[jk-ozlabs] clock infrastructure: basic port of imx clocks to new infrastructure: DONE
[jk-ozlabs] clock infrastructure: rework fixed imx clocks to clk_fixed: DONE
[jk-ozlabs] clock infrastructure: rework PLL clocks to clk_pll: DONE
[jk-ozlabs] clock infrastructure: rework CCM clocks to new infrastructure, where possible: DONE
[jk-ozlabs] power domains: adapt clock binding sheme to power domains: DONE
[jk-ozlabs] power domains: propose bindings: DONE
Work Items
Dependency tree
* Blueprints in grey have been implemented.
