lkml.org 
[lkml]   [2013]   [Aug]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Enable arm_global_timer for Zynq brakes boot
    On 08/12/2013 06:03 PM, Sören Brinkmann wrote:
    > On Fri, Aug 09, 2013 at 10:27:57AM -0700, Stephen Boyd wrote:
    >> On 08/09, Daniel Lezcano wrote:
    >>>
    >>> yes, but at least the broadcast mechanism should send an IPI to cpu0 to
    >>> wake it up, no ? As Stephen stated this kind of configuration should has
    >>> never been tested before so the tick broadcast code is not handling this
    >>> case properly IMHO.
    >>>
    >>
    >> If you have a per-cpu tick device that isn't suffering from
    >> FEAT_C3_STOP why wouldn't you use that for the tick versus a
    >> per-cpu tick device that has FEAT_C3_STOP? It sounds like there
    >> is a bug in the preference logic or you should boost the rating
    >> of the arm global timer above the twd. Does this patch help? It
    >> should make the arm global timer the tick device and whatever the
    >> cadence timer you have into the broadcast device.
    >
    > I finally got to test your patch. Unfortunately, it makes the system
    > hang even earlier:

    [ ... ]

    Can you boot with maxcpus=1 and then give the result of timer_list ?


    --
    <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

    Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
    <http://twitter.com/#!/linaroorg> Twitter |
    <http://www.linaro.org/linaro-blog/> Blog

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2013-08-12 18:21    [W:4.708 / U:0.104 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site