2013/2/13 Rob Herring <robherri...@gmail.com>: > On 02/13/2013 10:21 AM, Michal Simek wrote: >> 2013/2/7 Rob Herring <robherri...@gmail.com>: >>> From: Rob Herring <rob.herr...@calxeda.com> >>> >>> In cases where we have multiple nodes of the same type, we may need the >>> node pointer to know which node was matched. Passing the node pointer >>> also keeps the init function from having to match the node a 2nd time. >>> >>> Signed-off-by: Rob Herring <rob.herr...@calxeda.com> >>> Cc: John Stultz <johns...@us.ibm.com> >>> Cc: Thomas Gleixner <t...@linutronix.de> >>> --- >>> drivers/clocksource/clksrc-of.c | 4 ++-- >>> 1 file changed, 2 insertions(+), 2 deletions(-) >> >> Tested-by: Michal Simek <michal.si...@xilinx.com> >> >> The rest is just the same as I have done. Any option to add these >> patches to v3.9? > > I would like to before we have more users to fix, but it will have to be > post rc1. If not, Arnd/Olof should be be able to provide a stable branch > for 3.10.
ok >> Because I need these patches for zynq timer because we have two in the soc. >> Is it OK to register several clock source and clockevent devices? > > If it is 1 DT node, then that should be fine. zynq is using two triple timer counter IP . There are also described by two different DT nodes because there are separated and uses different baseaddresses. Does it mean that if there are 2 DT nodes that it won't work? One more thing. Is there any rule which should describe which timer should be used for clockevent and for clocksource? >> btw: there is still one issue because you can just setup only one >> compatibility string. > > You can have multiple CLOCKSOURCE_OF_DECLARE statements. The gic code > does this for irqchips. Ok. Will look at it. Thanks, Michal -- Michal Simek, Ing. (M.Eng) w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/ Maintainer of Linux kernel - Xilinx Zynq ARM architecture Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
