Re: [PATCH v5 00/15] Renesas CMT, MTU2 and TMU platform cleanups

[Laurent Pinchart <laurent.pinchart@ideasonboard.com>]

Hi Geert,

Thank you for testing the patch series.

On Monday 12 May 2014 14:11:13 Geert Uytterhoeven wrote:
> On Sun, May 11, 2014 at 4:24 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Wed, Apr 23, 2014 at 01:15:07PM +0200, Laurent Pinchart wrote:
> >> This patch set switches all Renesas platforms to the new style CMT, MTU2
> >> and TMU device platform data. All patches have been previously posted as
> >> part of the "[PATCH v3 00/52] Renesas CMT and TMU cleanups" and "[PATCH
> >> 00/22] SH MTU2 DT support" patch series.
> >> 
> >> This new version fixes an interrupt-related bug introduced when switching
> >> the sh7372 and sh73a0 platforms to the new style TMU device, caused by
> >> mistakenly using evt2irq instead of intcs_evt2irq for the IRQ resources.
> >> 
> >> Simon, I've tested this on Mackerel and the board now boots correctly.
> >> Could you please assist me in debugging the Bock-W boot hang issue, as I
> >> don't have access to that board ?
> > 
> > Thanks Laurent,
> > 
> > I have queued this up locally using v6 of patch 12 after resolving some
> > conflicts which I will highlight by responding to the patches that are
> > affected.
> > 
> > I plan to push this once I have done some testing: especially of the
> > resolution to the bockw problem. (I am on a plane with neither internet
> > access nor a consignment of boards.)
> 
> Tested on Koelsch/r8a7791 (legacy and reference), Armadillo/r8a7740
> (legacy and reference), and Genmai/r7s72100 (legacy, reference, and
> multiplatform+CCF).
> 
> On Koelsch (both legacy and reference), I get:
> 
> -sh_cmt sh_cmt.0: used for clock events
> -sh_cmt sh_cmt.0: used for periodic clock events
> +sh_cmt sh-cmt-48-gen2.0: ch0: used for clock events
> +sh_cmt sh-cmt-48-gen2.0: ch0: used for periodic clock events
> +sh_cmt sh-cmt-48-gen2.0: ch1: used as clock source
> +Switched to clocksource sh-cmt-48-gen2.0
> +Clockevents: could not switch to one-shot mode:
> +Clockevents: could not switch to one-shot mode: dummy_timer is not
> functional.
> +Could not switch to high resolution mode on CPU 1
> + dummy_timer is not functional.
> +Could not switch to high resolution mode on CPU 0
> 
> What's up with the high resolution mode?

That's surprising, I haven't noticed anything similar before. I've just tested 
Simon's latest devel branch on both Koelsch legacy and Koelsch reference, and 
I can't reproduce the problem.

-- 
Regards,

Laurent Pinchart