lkml.org 
[lkml]   [2013]   [Nov]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [PATCH V2] cpufreq: Make sure CPU is running on a freq from freq-table
    From
    On 26 November 2013 02:43, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
    > On Monday, November 25, 2013 09:43:59 AM Dirk Brandewie wrote:
    >> This is a platform specific bug fix AFAICT and belongs in a platform
    >> specific piece of code

    In case we end up doing that, we will do lots of code redundancy in
    cpufreq drivers. And as Rafael said, some platforms might never
    know they have booted with an out of table frequency and so taking
    care of this at a single place is better, where we are sure that it
    will get fixed.

    >> The core should not be working around bootloader bugs IMHO. Silently
    >> fixing it is evil IMHO at a minimum the core should complain LOUDLY
    >> about this happening otherwise the bootloaders will have no incentive to
    >> get their act together.

    That looks correct..

    > Yes, we can add a WARN_ON() there. Still, though, the core's responsibility
    > is to ensure that (a) either we can continue safely or (b) we can't, in which
    > case it should just fail the initialization. Whether or not it should panic()
    > I'm not sure.

    But is this that big crime, that we do a WARN on it? CPU was running on
    a workable frequency, it wasn't mentioned in the table, that's it.

    Probably just throw an print message that CPU found to be running on
    out of table frequency, and that got fixed..


    \
     
     \ /
      Last update: 2013-11-26 03:41    [W:2.379 / U:0.500 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site