Re: [PATCH] ARM: oprofile: Always allow backtraces

On Thu, 20 Jan 2011, Robert Richter wrote: Hi, On 20.01.11 04:42:24, Will Deacon wrote: Hi Ari, Always allow backtrace when using oprofile on ARM, even if a PMU isn't present. Restores functionality originally introduced in 1b7b56982fdcd9d85effd76f3928cf5d6eb26155 by Richard Purdie. Well

[PATCH v2 0/3] oprofile: ARM backtraces and few minors

This patchset re-enables ARM backtraces with non-PMU capable CPUs. In V2 I have tried to address the comments received for the V1 patches. arch/sh/oprofile/common.c is untouched but should work as earlier. Compile tested with arm/omap2plus_defconfig (with and without CONFIG_HW_PERF_EVENTS). Ari

[PATCH v2 1/3] oprofile: Use CONFIG_HW_PERF_EVENTS for oprofile_perf_init and friends

The implementations are flagged in Makefile with CONFIG_HW_PERF_EVENTS instead of CONFIG_PERF_EVENTS. Signed-off-by: Ari Kauppi kau...@papupata.org --- include/linux/oprofile.h |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/include/linux/oprofile.h b/include/linux

[PATCH v2 2/3] oprofile: Provide stubs for oprofile_perf_{init,exit}

If CONFIG_HW_PERF_EVENTS is not defined, provide stubs for oprofile_perf_init and oprofile_perf_exit. Allows cleaning of architecture specific implementations. Signed-off-by: Ari Kauppi kau...@papupata.org --- include/linux/oprofile.h |9 + 1 files changed, 9 insertions(+), 0

[PATCH v2 3/3] ARM: oprofile: Always allow backtraces

) by Richard Purdie. Signed-off-by: Ari Kauppi kau...@papupata.org --- arch/arm/oprofile/common.c | 12 ++-- 1 files changed, 2 insertions(+), 10 deletions(-) diff --git a/arch/arm/oprofile/common.c b/arch/arm/oprofile/common.c index 8aa9744..2b66391 100644 --- a/arch/arm/oprofile/common.c

[PATCH] ARM: oprofile: Always allow backtraces

Always allow backtrace when using oprofile on ARM, even if a PMU isn't present. Restores functionality originally introduced in 1b7b56982fdcd9d85effd76f3928cf5d6eb26155 by Richard Purdie. Signed-off-by: Ari Kauppi kau...@papupata.org Cc: Richard Purdie rpur...@rpsys.net Cc: Will Deacon will.dea

[PATCH v2] OMAP3: PM: Add milliseconds interface to suspend wakeup timer

Millisecond resolution is possible and there are use cases for it (automatic testing). Seconds-based interface is preserved for compatibility. Signed-off-by: Ari Kauppi ext-ari.kau...@nokia.com --- v2: Keep seconds and milliseconds interfaces strictly separate: - Consistent interface, setting

[PATCH 0/2] i2c: i2c-omap: Reliablity and register fixes

Two patches for i2c-omap driver. Ari Kauppi (1): i2c: i2c-omap: Call request_irq with IRQF_DISABLED Eero Nurkkala (1): i2c: i2c-omap: Fix BUFSTAT_REG reading drivers/i2c/busses/i2c-omap.c | 12 +++- 1 files changed, 7 insertions(+), 5 deletions(-) -- To unsubscribe from

[PATCH 1/2] i2c: i2c-omap: Fix BUFSTAT_REG reading

. Moreover, only the 6 LSB:s are relevant for the TXSTAT field. Signed-off-by: Eero Nurkkala ext-eero.nurkk...@nokia.com Signed-off-by: Tony Lindgren t...@atomide.com Signed-off-by: Ari Kauppi ext-ari.kau...@nokia.com Acked-by: Felipe Balbi felipe.ba...@nokia.com --- drivers/i2c/busses/i2c-omap.c

[PATCH 2/2] i2c: i2c-omap: Call request_irq with IRQF_DISABLED

I have observed some Spurious IRQ's for I2C1 when all kernel hacking options (and thus LOCKDEP) are disabled. Applying Richard Woodruff's 'I2C bug fixes for L-O and L-Z' seems to help but IRQF_DISABLED is needed for proper behaviour. Signed-off-by: Ari Kauppi ext-ari.kau...@nokia.com Acked

[PATCH] I2C: Call request_irq with IRQF_DISABLED

I have observed some Spurious IRQ's for I2C1 when all kernel hacking options (and thus LOCKDEP) are disabled. Applying Richard Woodruff's 'I2C bug fixes for L-O and L-Z' seems to help but IRQF_DISABLED is needed for proper behaviour. Signed-off-by: Ari Kauppi ext-ari.kau...@nokia.com