Re: [PATCH] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER

2012-11-11 Thread Igor Grinberg
On 11/12/12 08:38, Hiremath, Vaibhav wrote: > On Sun, Nov 11, 2012 at 17:05:07, Igor Grinberg wrote: >> >> >> On 11/08/12 20:34, Jon Hunter wrote: >>> >>> On 11/08/2012 12:17 PM, Paul Walmsley wrote: On Thu, 8 Nov 2012, Jon Hunter wrote: > On 11/08/2012 11:58 AM, Paul Walmsley wrote:

RE: [PATCH] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER

2012-11-11 Thread Hiremath, Vaibhav
On Fri, Nov 09, 2012 at 06:25:49, Hunter, Jon wrote: > > On 11/08/2012 12:06 PM, Hiremath, Vaibhav wrote: > > On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote: > >> > >> On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote: > >>> On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote: > >> > >> [snip]

RE: [PATCH] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER

2012-11-11 Thread Hiremath, Vaibhav
On Sun, Nov 11, 2012 at 17:05:07, Igor Grinberg wrote: > > > On 11/08/12 20:34, Jon Hunter wrote: > > > > On 11/08/2012 12:17 PM, Paul Walmsley wrote: > >> On Thu, 8 Nov 2012, Jon Hunter wrote: > >> > >>> On 11/08/2012 11:58 AM, Paul Walmsley wrote: > On Thu, 8 Nov 2012, Jon Hunter wrote: >

Re: [RFC] Device Tree Overlays Proposal (Was Re: capebus moving omap_devices to mach-omap2)

2012-11-11 Thread Rob Landley
On 11/09/2012 10:28:59 AM, Grant Likely wrote: On Tue, Nov 6, 2012 at 10:37 PM, Stephen Warren wrote: > On 11/05/2012 01:40 PM, Grant Likely wrote: I'm not actually opposed to it, but it needs to be done in an elegant way. The DT data model already imposes more of a conceptual le

Re: [PATCH] pwm-backlight: Pinctrl-fy

2012-11-11 Thread Linus Walleij
On Fri, Nov 9, 2012 at 9:06 AM, Thierry Reding wrote: > On Wed, Oct 31, 2012 at 05:57:27PM +0200, Pantelis Antoniou wrote: >> + pinctrl = devm_pinctrl_get_select_default(&pdev->dev); >> + if (IS_ERR(pinctrl)) >> + dev_warn(&pdev->dev, "unable to select pin group\n"); >> + > >

Re: [PATCHv2] Input: omap4-keypad: Add pinctrl support

2012-11-11 Thread Linus Walleij
On Thu, Nov 1, 2012 at 3:01 PM, Linus Walleij wrote: > On Thu, Nov 1, 2012 at 1:07 PM, Mark Brown > wrote: >> On Thu, Nov 01, 2012 at 09:54:00AM +0100, Linus Walleij wrote: > >> For the pin hogging I'd actually been thinking separately that we should >> just have the device core do a devm_pinctrl

Re: [PATCH] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER

2012-11-11 Thread Igor Grinberg
On 11/08/12 20:34, Jon Hunter wrote: > > On 11/08/2012 12:17 PM, Paul Walmsley wrote: >> On Thu, 8 Nov 2012, Jon Hunter wrote: >> >>> On 11/08/2012 11:58 AM, Paul Walmsley wrote: On Thu, 8 Nov 2012, Jon Hunter wrote: > Igor was mentioning a h/w scenario where the 32kHz source is no

Re: [PATCH] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER

2012-11-11 Thread Igor Grinberg
On 11/08/12 21:16, Jon Hunter wrote: > > On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote: >> On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote: >>> >>> On 11/08/2012 01:59 AM, Igor Grinberg wrote: >>> >>> [snip] >>> There is no reliable way to determine which source should be used in >>>

Re: [PATCH] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER

2012-11-11 Thread Igor Grinberg
On 11/08/12 18:16, Jon Hunter wrote: > > On 11/08/2012 01:59 AM, Igor Grinberg wrote: >> On 11/07/12 23:36, Jon Hunter wrote: >>> Hi Igor, >>> >>> On 11/07/2012 08:42 AM, Igor Grinberg wrote: CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way. Make OMAP2+ timer code indep

Re: [PATCH v5 0/6] Move rest of omap-iommu to live in drivers/iommu

2012-11-11 Thread Ohad Ben-Cohen
On Fri, Nov 2, 2012 at 9:23 PM, Tony Lindgren wrote: > We need to move the iommu code to live under drivers > for arm common zImage support. For the iommu changes in the entire series: Acked-by: Ohad Ben-Cohen Joerg, it might relieve some pain if this will go through Tony's tree, as there are

Re: [PATCH] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER

2012-11-11 Thread Igor Grinberg
On 11/08/12 18:20, Tony Lindgren wrote: > * Igor Grinberg [121107 23:15]: >> On 11/07/12 19:33, Tony Lindgren wrote: >>> >>> I think this should be the default for the timers as that counter >>> does not stop during deeper idle states. >> >> Well, it is the default as you can see from the patch. >