* Paul Walmsley <[email protected]> [090526 15:27]:
> Hello Russell,
>
> here is the next set of OMAP clock patches for review for the
> post-2.6.30 merge window. They apply on top of the previous set
> ("OMAP clock/SDRC patches on v2.6.30-rc5"). If you're happy with
> these patches, Tony will queue them up into his for-next branch.
Looks like Russell now has all the omap for-next merged to his
devel branch. Only this series is missing and the omap4 SMP patches.
Paul, can you please reply with the output from git request-pull
for Russell to pull these in too?
AFAIK, there should not be any need to rebase this series, it
should merge clean from v2.6.30-rc7 to Russell's devel branch.
Regards,
Tony
> This series completes basic support for OMAP3 CORE DVFS. A few other
> minor bugs are fixed by the off-by-one patch and the GPIO debounce
> clock patch.
>
>
> regards,
>
> - Paul
>
> ---
>
> Paul Walmsley (8):
> OMAP3 clock: GPIO de-bounce clocks don't affect module idle state
> OMAP3 SDRC: set FIXEDDELAY when disabling SDRC DLL
> OMAP3 SRAM: convert SRAM code to use macros rather than magic numbers
> OMAP3 SRAM: add more comments on the SRAM code
> OMAP3 clock/SDRC: program SDRC_MR register during SDRC clock change
> OMAP3 clock: add a short delay when lowering CORE clk rate
> OMAP3 clock: initialize SDRC timings at kernel start
> OMAP3 clock: remove wait for DPLL3 M2 clock to stabilize
>
> Roel Kluin (1):
> OMAP2 clock/powerdomain: off by 1 error in loop timeout comparisons
>
> Tero Kristo (1):
> OMAP3: Add support for DPLL3 divisor values higher than 2
>
>
> arch/arm/mach-omap2/clock.c | 2
> arch/arm/mach-omap2/clock34xx.c | 42 ++++++++--
> arch/arm/mach-omap2/clock34xx.h | 12 +--
> arch/arm/mach-omap2/io.c | 38 +++++++++
> arch/arm/mach-omap2/powerdomain.c | 2
> arch/arm/mach-omap2/sram34xx.S | 129 +++++++++++++++++++++-----------
> arch/arm/plat-omap/include/mach/sram.h | 6 +
> arch/arm/plat-omap/sram.c | 8 +-
> 8 files changed, 171 insertions(+), 68 deletions(-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Jun 01, 2009 at 09:56:24AM -0700, Tony Lindgren wrote:
> * Paul Walmsley <[email protected]> [090526 15:27]:
> > Hello Russell,
> >
> > here is the next set of OMAP clock patches for review for the
> > post-2.6.30 merge window. They apply on top of the previous set
> > ("OMAP clock/SDRC patches on v2.6.30-rc5"). If you're happy with
> > these patches, Tony will queue them up into his for-next branch.
>
> Looks like Russell now has all the omap for-next merged to his
> devel branch. Only this series is missing and the omap4 SMP patches.
This series I've avoided looking at due to lack of time. I only just
got around to sorting through your patches from the last two weeks
last Thursday/Friday, and I've spent Sunday evening and today boot
testing and debugging what's been merged on my LDP platform.
It'll be a week or so before I look at OMAP again.
* Russell King - ARM Linux <[email protected]> [090601 10:09]:
> On Mon, Jun 01, 2009 at 09:56:24AM -0700, Tony Lindgren wrote:
> > * Paul Walmsley <[email protected]> [090526 15:27]:
> > > Hello Russell,
> > >
> > > here is the next set of OMAP clock patches for review for the
> > > post-2.6.30 merge window. They apply on top of the previous set
> > > ("OMAP clock/SDRC patches on v2.6.30-rc5"). If you're happy with
> > > these patches, Tony will queue them up into his for-next branch.
> >
> > Looks like Russell now has all the omap for-next merged to his
> > devel branch. Only this series is missing and the omap4 SMP patches.
>
> This series I've avoided looking at due to lack of time. I only just
> got around to sorting through your patches from the last two weeks
> last Thursday/Friday, and I've spent Sunday evening and today boot
> testing and debugging what's been merged on my LDP platform.
Yeah it's been busy with omap patches again. The good news is that
after 2.6.30 we should be able to have linux-omap tree just contain
patches for the upcoming merge windows!
> It'll be a week or so before I look at OMAP again.
Thanks for the update. Sounds like we still have some time to deal
with the remaining two patch sets.
Regards,
Tony