ARM: nomadik: initial devicetree support
Subsystems (5)
PATCH 2/11 ARM: nomadik: initial devicetree support
Support basic device tree boot on the Nomadik. Implement the support in the cpu file with the intent of deleting the board files later. At this stage IRQ controllers, system timer, l2x0 cache, UARTs and thus console boot is fully functional. Patch out the code adding devices by initcalls for now so as not to disturb the boot.
--- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/ste-nomadik-s8815.dts | 18 ++++++ arch/arm/boot/dts/ste-nomadik-stn8815.dtsi | 77 +++++++++++++++++++++++++ arch/arm/mach-nomadik/board-nhk8815.c | 4 ++ arch/arm/mach-nomadik/cpu-8815.c | 90 ++++++++++++++++++++++++++++++ arch/arm/mach-nomadik/cpu-8815.h | 1 + arch/arm/mach-nomadik/i2c-8815nhk.c | 5 ++ 7 files changed, 196 insertions(+) create mode 100644 arch/arm/boot/dts/ste-nomadik-s8815.dts create mode 100644 arch/arm/boot/dts/ste-nomadik-stn8815.dtsi
arch/arm/boot/dts/Makefile +1 -0
@@ -100,6 +100,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \ imx28-m28evk.dtb \ imx28-sps1.dtb \ imx28-tx28.dtb +dtb-$(CONFIG_ARCH_NOMADIK) += ste-nomadik-s8815.dtb dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \ omap3-beagle.dtb \ omap3-beagle-xm.dtb \
arch/arm/boot/dts/ste-nomadik-s8815.dts new file +18 -0
@@ -0,0 +1,18 @@ +/* + * Device Tree for the ST-Ericsson Nomadik S8815 board + * Produced by Calao Systems + */ + +/dts-v1/; +/include/ "ste-nomadik-stn8815.dtsi" + +/ { + model = "ST-Ericsson Nomadik S8815"; + compatible = "stericsson,nomadik"; + #address-cells = <1>; + #size-cells = <1>; + + chosen { + bootargs = "root=/dev/ram0 console=ttyAMA1,115200n8 earlyprintk"; + }; +};
arch/arm/boot/dts/ste-nomadik-stn8815.dtsi new file +77 -0
77 lines not on this page · raw message
arch/arm/mach-nomadik/board-nhk8815.c +4 -0
@@ -205,6 +205,10 @@ static int __init nhk8815_mmcsd_init(void) {int ret; +/* For e.g. devicetree boot */ +if (!machine_is_nomadik ()) +return 0 ; + ret =gpio_request (112 ,"card detect bias" );if (ret)return ret;
arch/arm/mach-nomadik/cpu-8815.c +90 -0
103 lines not on this page · raw message
arch/arm/mach-nomadik/cpu-8815.h +1 -0
@@ -2,3 +2,4 @@ extern void cpu8815_map_io(void);extern void cpu8815_platform_init (void );extern void cpu8815_init_irq (void );extern void cpu8815_restart (char ,const char *); +extern struct sys_timer cpu8815_timer;
arch/arm/mach-nomadik/i2c-8815nhk.c +5 -0
@@ -4,6 +4,7 @@#include <linux/i2c-algo-bit.h> #include <linux/i2c-gpio.h> #include <linux/platform_device.h> +#include <asm/mach-types.h> /* * There are two busses in the 8815NHK.
@@ -58,6 +59,10 @@ static struct platform_device nhk8815_i2c_dev2 = {static int __init nhk8815_i2c_init (void ) { +/* For e.g. devicetree boot */ +if (!machine_is_nomadik ()) +return 0 ; +platform_device_register (&nhk8815_i2c_dev0);platform_device_register (&nhk8815_i2c_dev1);platform_device_register (&nhk8815_i2c_dev2);
Signature · 1 line
1.7.11.7
PATCH 2/11 ARM: nomadik: initial devicetree support
Hi,
I have a couple of comments on the dts{,i} portion.
Quoted 41 lines · Linus Walleij
Support basic device tree boot on the Nomadik. Implement the support in the cpu file with the intent of deleting the board files later. At this stage IRQ controllers, system timer, l2x0 cache, UARTs and thus console boot is fully functional. Patch out the code adding devices by initcalls for now so as not to disturb the boot.
Signed-off-by Linus Walleij <[email protected]>--- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/ste-nomadik-s8815.dts | 18 ++++++ arch/arm/boot/dts/ste-nomadik-stn8815.dtsi | 77 +++++++++++++++++++++++++ arch/arm/mach-nomadik/board-nhk8815.c | 4 ++ arch/arm/mach-nomadik/cpu-8815.c | 90 ++++++++++++++++++++++++++++++ arch/arm/mach-nomadik/cpu-8815.h | 1 + arch/arm/mach-nomadik/i2c-8815nhk.c | 5 ++ 7 files changed, 196 insertions(+) create mode 100644 arch/arm/boot/dts/ste-nomadik-s8815.dts create mode 100644 arch/arm/boot/dts/ste-nomadik-stn8815.dtsiarch/arm/boot/dts/Makefile +1
-0@@ -100,6 +100,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \ imx28-m28evk.dtb \ imx28-sps1.dtb \ imx28-tx28.dtb +dtb-$(CONFIG_ARCH_NOMADIK) += ste-nomadik-s8815.dtb dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \ omap3-beagle.dtb \ omap3-beagle-xm.dtb \arch/arm/boot/dts/ste-nomadik-s8815.dts new file +3
-0@@ -0,0 +1,18 @@ +/* + * Device Tree for the ST-Ericsson Nomadik S8815 board + * Produced by Calao Systems
arch/arm/boot/dts/ste-nomadik-s8815.dts line 13
Quoted 10 lines
arch/arm/boot/dts/ste-nomadik-s8815.dts new file +10
-0+ */ + +/dts-v1/; +/include/ "ste-nomadik-stn8815.dtsi" + +/ { + model = "ST-Ericsson Nomadik S8815"; + compatible = "stericsson,nomadik"; + #address-cells = <1>; + #size-cells = <1>;
Given there are addresses and sizes in the dtsi (but none in the dts), should #address-cells and #size-cells not be in the dtsi?
Quoted 11 lines
arch/arm/boot/dts/ste-nomadik-s8815.dts new file +5
-0+ + chosen { + bootargs = "root=/dev/ram0 console=ttyAMA1,115200n8 earlyprintk"; + }; +};arch/arm/boot/dts/ste-nomadik-stn8815.dtsi new file +0
-0
arch/arm/boot/dts/ste-nomadik-stn8815.dtsi line 9
Quoted 9 lines
arch/arm/boot/dts/ste-nomadik-stn8815.dtsi new file +9
-0@@ -0,0 +1,77 @@ +/* + * Device Tree for the ST-Ericsson Nomadik 8815 STn8815 SoC + */ +/include/ "skeleton.dtsi" + +/ { + memory { + reg = <0x00000000 0x04000000>; + reg = <0x08000000 0x04000000>;
I believe that's not valid (duplicate property name).
Judging by other dts files under arch/arm/boot/dts, these should be two nodes, with their unit addresses set (and possibly device_type, which I see is set for some dts files, but not all).
Quoted 58 lines
arch/arm/boot/dts/ste-nomadik-stn8815.dtsi new file +58
-0+ }; + + L2: l2-cache { + compatible = "arm,l210-cache"; + reg = <0x10210000 0x1000>; + interrupt-parent = <&vica>; + interrupts = <30>; + cache-unified; + cache-level = <2>; + }; + + mtu0 { + /* Nomadik system timer */ + reg = <0x101e2000 0x1000>; + interrupt-parent = <&vica>; + interrupts = <4>; + }; + + mtu1 { + /* Secondary timer */ + reg = <0x101e3000 0x1000>; + interrupt-parent = <&vica>; + interrupts = <5>; + }; + + amba { + compatible = "arm,amba-bus"; + #address-cells = <1>; + #size-cells = <1>; + ranges; + + vica: intc at 0x10140000 { + compatible = "arm,versatile-vic"; + interrupt-controller; + #interrupt-cells = <1>; + reg = <0x10140000 0x20>; + }; + + vicb: intc at 0x10140020 { + compatible = "arm,versatile-vic"; + interrupt-controller; + #interrupt-cells = <1>; + reg = <0x10140020 0x20>; + }; + + uart0: uart at 101fd000 { + compatible = "arm,pl011", "arm,primecell"; + reg = <0x101fd000 0x1000>; + interrupt-parent = <&vica>; + interrupts = <12>; + }; + + uart1: uart at 101fb000 { + compatible = "arm,pl011", "arm,primecell"; + reg = <0x101fb000 0x1000>; + interrupt-parent = <&vica>; + interrupts = <17>; + };
arch/arm/boot/dts/ste-nomadik-stn8815.dtsi line 77
Quoted 10 lines
arch/arm/boot/dts/ste-nomadik-stn8815.dtsi new file +10
-0+ + uart2: uart at 101f2000 { + compatible = "arm,pl011", "arm,primecell"; + reg = <0x101f2000 0x1000>; + interrupt-parent = <&vica>; + interrupts = <28>; + status = "disabled"; + }; + }; +};
Maybe I've misunderstood how this is laid out, but I can't see where we get a cpus node from in the board's dts. Has this just been forgotten?
[...]
Thanks,
Mark.
PATCH 2/11 ARM: nomadik: initial devicetree support
Quoted 83 lines · Mark Rutland
Hi,
I have a couple of comments on the dts{,i} portion.
Quoted 41 lines · Linus Walleij
Support basic device tree boot on the Nomadik. Implement the support in the cpu file with the intent of deleting the board files later. At this stage IRQ controllers, system timer, l2x0 cache, UARTs and thus console boot is fully functional. Patch out the code adding devices by initcalls for now so as not to disturb the boot.
Signed-off-by Linus Walleij <[email protected]>--- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/ste-nomadik-s8815.dts | 18 ++++++ arch/arm/boot/dts/ste-nomadik-stn8815.dtsi | 77 +++++++++++++++++++++++++ arch/arm/mach-nomadik/board-nhk8815.c | 4 ++ arch/arm/mach-nomadik/cpu-8815.c | 90 ++++++++++++++++++++++++++++++ arch/arm/mach-nomadik/cpu-8815.h | 1 + arch/arm/mach-nomadik/i2c-8815nhk.c | 5 ++ 7 files changed, 196 insertions(+) create mode 100644 arch/arm/boot/dts/ste-nomadik-s8815.dts create mode 100644 arch/arm/boot/dts/ste-nomadik-stn8815.dtsiarch/arm/boot/dts/Makefile +1
-0@@ -100,6 +100,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \ imx28-m28evk.dtb \ imx28-sps1.dtb \ imx28-tx28.dtb +dtb-$(CONFIG_ARCH_NOMADIK) += ste-nomadik-s8815.dtb dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \ omap3-beagle.dtb \ omap3-beagle-xm.dtb \arch/arm/boot/dts/ste-nomadik-s8815.dts new file +3
-0@@ -0,0 +1,18 @@ +/* + * Device Tree for the ST-Ericsson Nomadik S8815 board + * Produced by Calao Systemsarch/arm/boot/dts/ste-nomadik-s8815.dts line 13
Quoted 10 lines
arch/arm/boot/dts/ste-nomadik-s8815.dts new file +10
-0+ */ + +/dts-v1/; +/include/ "ste-nomadik-stn8815.dtsi" + +/ { + model = "ST-Ericsson Nomadik S8815"; + compatible = "stericsson,nomadik"; + #address-cells = <1>; + #size-cells = <1>;Given there are addresses and sizes in the dtsi (but none in the dts), should #address-cells and #size-cells not be in the dtsi?
Quoted 11 lines
arch/arm/boot/dts/ste-nomadik-s8815.dts new file +5
-0+ + chosen { + bootargs = "root=/dev/ram0 console=ttyAMA1,115200n8 earlyprintk"; + }; +};arch/arm/boot/dts/ste-nomadik-stn8815.dtsi new file +0
-0arch/arm/boot/dts/ste-nomadik-stn8815.dtsi line 9
Quoted 9 lines
arch/arm/boot/dts/ste-nomadik-stn8815.dtsi new file +9
-0@@ -0,0 +1,77 @@ +/* + * Device Tree for the ST-Ericsson Nomadik 8815 STn8815 SoC + */ +/include/ "skeleton.dtsi" + +/ { + memory { + reg = <0x00000000 0x04000000>; + reg = <0x08000000 0x04000000>;I believe that's not valid (duplicate property name).
Quoted 3 lines
Judging by other dts files under
arch/arm/boot/dts, these should be two nodes, with their unit addresses set (and possiblydevice_type, which I see is set for some dts files, but not all).
One node should be just fine if the following form is used:
memory {
reg = <0x00000000 0x04000000>,
<0x08000000 0x04000000>;
};Quoted 3 lines
Maybe I've misunderstood how this is laid out, but I can't see where we get a cpus node from in the board's dts. Has this just been forgotten?
A cpus node isn't required if it doesn't provide any non-discoverable information.
g.
PATCH 2/11 ARM: nomadik: initial devicetree support
Quoted 88 lines · Grant Likely
Quoted 83 lines · Mark Rutland
Hi,
I have a couple of comments on the dts{,i} portion.
Quoted 41 lines · Linus Walleij
Support basic device tree boot on the Nomadik. Implement the support in the cpu file with the intent of deleting the board files later. At this stage IRQ controllers, system timer, l2x0 cache, UARTs and thus console boot is fully functional. Patch out the code adding devices by initcalls for now so as not to disturb the boot.
Signed-off-by Linus Walleij <[email protected]>--- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/ste-nomadik-s8815.dts | 18 ++++++ arch/arm/boot/dts/ste-nomadik-stn8815.dtsi | 77 +++++++++++++++++++++++++ arch/arm/mach-nomadik/board-nhk8815.c | 4 ++ arch/arm/mach-nomadik/cpu-8815.c | 90 ++++++++++++++++++++++++++++++ arch/arm/mach-nomadik/cpu-8815.h | 1 + arch/arm/mach-nomadik/i2c-8815nhk.c | 5 ++ 7 files changed, 196 insertions(+) create mode 100644 arch/arm/boot/dts/ste-nomadik-s8815.dts create mode 100644 arch/arm/boot/dts/ste-nomadik-stn8815.dtsiarch/arm/boot/dts/Makefile +1
-0@@ -100,6 +100,7 @@ dtb-$(CONFIG_ARCH_MXS) += imx23-evk.dtb \ imx28-m28evk.dtb \ imx28-sps1.dtb \ imx28-tx28.dtb +dtb-$(CONFIG_ARCH_NOMADIK) += ste-nomadik-s8815.dtb dtb-$(CONFIG_ARCH_OMAP2PLUS) += omap2420-h4.dtb \ omap3-beagle.dtb \ omap3-beagle-xm.dtb \arch/arm/boot/dts/ste-nomadik-s8815.dts new file +3
-0@@ -0,0 +1,18 @@ +/* + * Device Tree for the ST-Ericsson Nomadik S8815 board + * Produced by Calao Systemsarch/arm/boot/dts/ste-nomadik-s8815.dts line 13
Quoted 10 lines
arch/arm/boot/dts/ste-nomadik-s8815.dts new file +10
-0+ */ + +/dts-v1/; +/include/ "ste-nomadik-stn8815.dtsi" + +/ { + model = "ST-Ericsson Nomadik S8815"; + compatible = "stericsson,nomadik"; + #address-cells = <1>; + #size-cells = <1>;Given there are addresses and sizes in the dtsi (but none in the dts), should #address-cells and #size-cells not be in the dtsi?
Quoted 11 lines
arch/arm/boot/dts/ste-nomadik-s8815.dts new file +5
-0+ + chosen { + bootargs = "root=/dev/ram0 console=ttyAMA1,115200n8 earlyprintk"; + }; +};arch/arm/boot/dts/ste-nomadik-stn8815.dtsi new file +0
-0arch/arm/boot/dts/ste-nomadik-stn8815.dtsi line 9
Quoted 9 lines
arch/arm/boot/dts/ste-nomadik-stn8815.dtsi new file +9
-0@@ -0,0 +1,77 @@ +/* + * Device Tree for the ST-Ericsson Nomadik 8815 STn8815 SoC + */ +/include/ "skeleton.dtsi" + +/ { + memory { + reg = <0x00000000 0x04000000>; + reg = <0x08000000 0x04000000>;I believe that's not valid (duplicate property name).
Quoted 3 lines
Judging by other dts files under
arch/arm/boot/dts, these should be two nodes, with their unit addresses set (and possiblydevice_type, which I see is set for some dts files, but not all).
Quoted 7 lines
One node should be just fine if the following form is used:
memory { reg = <0x00000000 0x04000000>, <0x08000000 0x04000000>; };
That also makes sense.
Quoted 7 lines
Quoted 3 lines
Maybe I've misunderstood how this is laid out, but I can't see where we get a cpus node from in the board's dts. Has this just been forgotten?
A cpus node isn't required if it doesn't provide any non-discoverable information.
Seeing the discussion around the Tegra #CPUs detection code, I'd think we should have one:
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/140209.html
Thanks,
Mark.
PATCH 2/11 ARM: nomadik: initial devicetree support
Quoted 6 lines · Mark Rutland
Quoted 5 lines · Grant Likely
Quoted 3 lines · Mark Rutland
Maybe I've misunderstood how this is laid out, but I can't see where we get a cpus node from in the board's dts. Has this just been forgotten?
Quoted 7 lines
Quoted 2 lines
A cpus node isn't required if it doesn't provide any non-discoverable information.
Seeing the discussion around the Tegra #CPUs detection code, I'd think we should have one:
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/140209.html
Sorry I cannot figure out how to handle this request.
The Nomadik has one (1) ARM926EJ-S CPU.
Currently there is no other uniprocessor machine in arch/arm/* doing this, so have I understood it correctly that you are asking me to do something that has never been done before, and that all the existing device tree implementations should also do this in the end?
The references discussion introduce ARM_CPU_PART_CORTEX_A15 and ARM_CPU_PART_CORTEX_A9 and these are vastly newer systems than the Nomadik, there is no handling of the older CPU types.
Are you asking for some new infrastructure to support, mainly for the sake of itself (like the nice completeness of the device tre), cpu nodes in these device trees?
Does this reasoning also extend to the MIPS, PPC and Sun use of device trees as well then, as they don't do that, or do you mean this should be done only for the ARM family?
As you see I don't quite get it, could you elaborate?
Yours,
Linus Walleij
PATCH 2/11 ARM: nomadik: initial devicetree support
Quoted 10 lines · Linus Walleij
Quoted 9 lines · Mark Rutland
Quoted 7 lines · Grant Likely
Quoted 3 lines · Mark Rutland
Maybe I've misunderstood how this is laid out, but I can't see where we get a cpus node from in the board's dts. Has this just been forgotten?
A cpus node isn't required if it doesn't provide any non-discoverable information.
Quoted 8 lines
Quoted 4 lines
Seeing the discussion around the Tegra #CPUs detection code, I'd think we should have one:
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/140209.html
Sorry I cannot figure out how to handle this request.
The Nomadik has one (1) ARM926EJ-S CPU.
Oh! I hadn't realised the Nomadik was v5. The above will be completely irrelevant. Sorry for wasting everyone's timer over this.
In way of an explanation, further down the thread [1,2] it becomes a discussion of /cpus node requirements. The long and short of it is that for v{6,7} there's no standard way of detecting the number of CPUs, and no way of detecting the CPU IDs (MPIDR.Aff{2,1,0}), so we should always describe this in dt.
For v5 this is indeed useless.
Quoted 4 lines
Currently there is no other uniprocessor machine in
arch/arm/*doing this, so have I understood it correctly that you are asking me to do something that has never been done before, and that all the existing device tree implementations should also do this in the end?
I think all v6+ platforms should have /cpus/cpu at N nodes for consistency across UP and SMP systems. For v{4,5}, this isn't really necessary, unless people want to conform to the letter of the law from ePAPR ("A cpus node is required for all device trees."). I'm not too worried about this.
Quoted 3 lines
The references discussion introduce
ARM_CPU_PART_CORTEX_A15andARM_CPU_PART_CORTEX_A9and these are vastly newer systems than the Nomadik, there is no handling of the older CPU types.
Sorry, I should've linked to the more relevant parts of the thread [1,2].
Quoted 3 lines
Are you asking for some new infrastructure to support, mainly for the sake of itself (like the nice completeness of the device tre), cpu nodes in these device trees?
I was asking for a /cpus/cpu node, but as you've pointed out this is a v5 platform, and as such this isn't needed.
Quoted 5 lines
Does this reasoning also extend to the MIPS, PPC and Sun use of device trees as well then, as they don't do that, or do you mean this should be done only for the ARM family?
As you see I don't quite get it, could you elaborate?
Hopefully the above explanation makes sense?
Quoted 2 lines
Yours,
Linus Walleij
Thanks,
Mark.
PATCH 2/11 ARM: nomadik: initial devicetree support
In reply to Linus WalleijQuoted 8 lines · Linus Walleij
Support basic device tree boot on the Nomadik. Implement the support in the cpu file with the intent of deleting the board files later. At this stage IRQ controllers, system timer, l2x0 cache, UARTs and thus console boot is fully functional. Patch out the code adding devices by initcalls for now so as not to disturb the boot.
Signed-off-by Linus Walleij <[email protected]>
...
Quoted 20 lines
arch/arm/mach-nomadik/cpu-8815.c +20
-0+static void __init cpu8815_timer_init_of (void ) +{ +struct device_node *mtu; +void __iomem *base; +int irq; +u32 src_cr; + + mtu =of_find_node_by_path ("/mtu0" ); +if (!mtu) +return ; + base =of_iomap (mtu,0 ); +if (WARN_ON (!base)) +return ; + irq =irq_of_parse_and_map (mtu,0 ); + +pr_info ("Remapped MTU @ %p, irq: %d\n" , base, irq); + +/* Configure timer sources in "system reset controller" ctrl reg */ + src_cr =readl (base); + src_cr &=SRC_CR_INIT_MASK ;
arch/arm/mach-nomadik/cpu-8815.c void cpu8815_restart(char mode, const char *cmd) · line 217
Quoted 10 lines
arch/arm/mach-nomadik/cpu-8815.c +10
-0+ src_cr |=SRC_CR_INIT_VAL ; +writel (src_cr, base); + +nmdk_timer_init (base, irq); +} + +struct sys_timer cpu8815_of_timer = { + .init = cpu8815_timer_init_of, +}; +
struct sys_timer is disappearing in 3.9
arch/arm/mach-nomadik/cpu-8815.c void cpu8815_restart(char mode, const char *cmd) · line 250
Quoted 9 lines
arch/arm/mach-nomadik/cpu-8815.c +9
-0+DT_MACHINE_START (NOMADIK_DT ,"ST-Ericsson Nomadik 8815" ) + .map_io = cpu8815_map_io, + .init_irq = cpu8815_init_irq_of, + .handle_irq = vic_handle_irq, + .timer = &cpu8815_of_timer, + .init_machine = cpu8815_init_of, + .restart = cpu8815_restart, + .dt_compat = cpu8815_board_compat, +MACHINE_END
You will be able to use .init_timer = cpu8815_of_timer in place of the struct sys_timer.
The patches for this change are in arm-soc: timer/cleanup.
Regards
Tony P
PATCH 2/11 ARM: nomadik: initial devicetree support
Quoted 6 lines · Tony Prisk
arch/arm/mach-nomadik/cpu-8815.c void cpu8815_restart(char mode, const char *cmd) · line 217
Quoted 4 lines
arch/arm/mach-nomadik/cpu-8815.c +4
-0+struct sys_timer cpu8815_of_timer = { + .init = cpu8815_timer_init_of, +}; +struct
sys_timeris disappearing in 3.9
I know, but I have to develop against something.
Do you know if there a now a frozen branch I can base my patches on?
Yours,
Linus Walleij
PATCH 2/11 ARM: nomadik: initial devicetree support
Quoted 6 lines · Linus Walleij
On Mon, Jan 14, 2013 at 8:26 AM, Tony Prisk <[email protected]> wrote:
Do you know if there a now a frozen branch I can base my patches on?
Quoted 1 line
The patches for this change are in arm-soc: timer/cleanup.
Ooops stupid me. Too little coffee.
I'll fix!
Yours,
Linus Walleij