Move DT kirkwood into mach-mvebu
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest posting 4/40 of 23 patches 0 repliesNew
- v2 posting 3/40 of 23 patches 0 repliesSuperseded
- v2 posting 2/40 of 23 patches 0 repliesSuperseded
Earlier versions · 1
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v2 posting 1/4 | 1 of 23 patches | 0 replies | Superseded |
Patches in v2 posting 4/4 No applies recorded yet
None of the 23 patches the cover letter announces are in this archive.
Reviews trailers per patch
| Patch | Jason Gunthorpe |
|---|---|
| Series | T-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v2 00/23] Move DT kirkwood into mach-mvebu
Quoted 10 lines · Ezequiel Garcia
Quoted 9 lines
Thanks, I tested v3 of the patchset.
It boots, but I can't do very much because the watchdog driver doesn't build and my system is configured to watchdog timeout if there is no watchdog driver.
Presumably the watchdog patchset needs to be a dependency for this? Is there a git URL for it?
Quoted 7 lines
Andrew's v3 and the mvebu/watchdog branch merges without any conflicts:
https://github.com/lunn/linux/tree/v3.14-rc1-mvebu-v3
http://git.infradead.org/linux-mvebu.git/shortlog/refs/heads/mvebu/watchdog
And multi v5 works great here!
It is working now for me as well, I haven't noticed any strangeness at least..
Ezequiel, after I applied your watchdog branch the .dtsi files lacked the new 2nd register:
wdt: watchdog-timer at 20300 {
compatible = "marvell,orion-wdt";
reg = <0x20300 0x28>;
interrupt-parent = <&bridge_intc>;
interrupts = <3>;
clocks = <&gate_clk 7>;
status = "okay";
};Which creates a nasty warn-on during boot - is that expected?
BTW, for both patche sets:
Also, there seems to be some missing request_region in drivers (can be fixedup later)
f1001418-f100141b : kirkwood_cpuidle
f1001500-f100151f : /mbus/internal at f1000000/mbus-controller at 20000 f1010030-f1010033 : /mbus/internal at f1000000/core-clocks at 10030 f1020000-f102007f : /mbus/internal at f1000000/mbus-controller at 20000 f1020104-f1020107 : kirkwood-cpufreq
f1020108-f102010b : /mbus/internal at f1000000/wdt at 20300 f102011c-f102011f : /mbus/internal at f1000000/clock-gating-control at 2011c f1020128-f102012b : /mbus/internal at f1000000/l2-cache at 20128 f1020300-f102031f : /mbus/internal at f1000000/timer at 20300 f1040000-f1041fff : /mbus/pex at e0000000/pcie at 1,0 f1072000-f1075fff : /mbus/internal at f1000000/egiga0
f1072004-f1072087 : /mbus/internal at f1000000/mdio at 72000
f4000000-f40003ff : /mbus/nand at f4000000/nand at 0
In general it should be:
f1012100-f10121ff : /mbus/internal at f1000000/serial at 12100 (<-- OF stanza)
f1012100-f101211f : serial (<-- Driver request region)
Jason