Message ID | alpine.DEB.2.00.1110101342010.5205@utopia.booyaka.com |
---|---|
State | New |
Headers | show |
* Paul Walmsley <paul@pwsan.com> [111010 17:09]: > Hi Tony > > The following changes since commit be73246058737beec52ae232bcab7776332a9e06: > > ARM: OMAP2+: Remove custom init_irq for remaining boards (2011-09-26 17:50:37 -0700) > > are available in the git repository at: > git://git.pwsan.com/linux-2.6 clock_hwmod_devel_3.2 > > This pull request drops the EHCI/OHCI hwmod data due to some > inconsistencies that were just found in the data. > > Santosh Shilimkar (1): > ARM: OMAP4: clock: Add CPU local timer clock node. > > arch/arm/mach-omap2/clock44xx_data.c | 9 +++++++++ > 1 files changed, 9 insertions(+), 0 deletions(-) Should this be pulled into fixes for v3.2 -rc cycle? Tony
On Fri, 4 Nov 2011, Tony Lindgren wrote: > * Paul Walmsley <paul@pwsan.com> [111010 17:09]: > > The following changes since commit be73246058737beec52ae232bcab7776332a9e06: > > > > ARM: OMAP2+: Remove custom init_irq for remaining boards (2011-09-26 17:50:37 -0700) > > > > are available in the git repository at: > > git://git.pwsan.com/linux-2.6 clock_hwmod_devel_3.2 > > > > This pull request drops the EHCI/OHCI hwmod data due to some > > inconsistencies that were just found in the data. > > > > Santosh Shilimkar (1): > > ARM: OMAP4: clock: Add CPU local timer clock node. > > > > arch/arm/mach-omap2/clock44xx_data.c | 9 +++++++++ > > 1 files changed, 9 insertions(+), 0 deletions(-) > > Should this be pulled into fixes for v3.2 -rc cycle? Santosh would be the right person to ask. Santosh, is anything broken in 3.2 if this patch doesn't get merged in -rc? Or is it just a feature which could be added in 3.3? - Paul
On Tue, Nov 8, 2011 at 1:23 PM, Paul Walmsley <paul@pwsan.com> wrote: > On Fri, 4 Nov 2011, Tony Lindgren wrote: > >> * Paul Walmsley <paul@pwsan.com> [111010 17:09]: >> > The following changes since commit be73246058737beec52ae232bcab7776332a9e06: >> > >> > ARM: OMAP2+: Remove custom init_irq for remaining boards (2011-09-26 17:50:37 -0700) >> > >> > are available in the git repository at: >> > git://git.pwsan.com/linux-2.6 clock_hwmod_devel_3.2 >> > >> > This pull request drops the EHCI/OHCI hwmod data due to some >> > inconsistencies that were just found in the data. >> > >> > Santosh Shilimkar (1): >> > ARM: OMAP4: clock: Add CPU local timer clock node. >> > >> > arch/arm/mach-omap2/clock44xx_data.c | 9 +++++++++ >> > 1 files changed, 9 insertions(+), 0 deletions(-) >> >> Should this be pulled into fixes for v3.2 -rc cycle? > > Santosh would be the right person to ask. Santosh, is anything broken in > 3.2 if this patch doesn't get merged in -rc? Or is it just a feature > which could be added in 3.3? > Nope nothing broken now since OMAP CPUFreq has not got into mainline yet. We need this patch to present once we start supporting MPU frequency scaling which I guess would happen now in 3.3. Regards Santosh
* Shilimkar, Santosh <santosh.shilimkar@ti.com> [111107 23:33]: > On Tue, Nov 8, 2011 at 1:23 PM, Paul Walmsley <paul@pwsan.com> wrote: > > On Fri, 4 Nov 2011, Tony Lindgren wrote: > > > >> * Paul Walmsley <paul@pwsan.com> [111010 17:09]: > >> > The following changes since commit be73246058737beec52ae232bcab7776332a9e06: > >> > > >> > ARM: OMAP2+: Remove custom init_irq for remaining boards (2011-09-26 17:50:37 -0700) > >> > > >> > are available in the git repository at: > >> > git://git.pwsan.com/linux-2.6 clock_hwmod_devel_3.2 > >> > > >> > This pull request drops the EHCI/OHCI hwmod data due to some > >> > inconsistencies that were just found in the data. > >> > > >> > Santosh Shilimkar (1): > >> > ARM: OMAP4: clock: Add CPU local timer clock node. > >> > > >> > arch/arm/mach-omap2/clock44xx_data.c | 9 +++++++++ > >> > 1 files changed, 9 insertions(+), 0 deletions(-) > >> > >> Should this be pulled into fixes for v3.2 -rc cycle? > > > > Santosh would be the right person to ask. Santosh, is anything broken in > > 3.2 if this patch doesn't get merged in -rc? Or is it just a feature > > which could be added in 3.3? > > > Nope nothing broken now since OMAP CPUFreq has not > got into mainline yet. We need this patch to present once we > start supporting MPU frequency scaling which I guess would > happen now in 3.3. OK thanks for the update. Tony