development kernel tree: Changes to 'debug'

[git at git.openmoko.org]

Rebased ref, commits from common ancestor:
commit f539329e25c7b0c0a6ae35d3af26f271f5e2df46
Author: Cesar Eduardo Barros <cesarb at cesarb.net>
Date:   Wed Aug 13 12:47:23 2008 +0100

    PATCH-9_9-gta01-Tweak-pixclock-to-reduce-flicker-with-cpufreq.eml
    
    Experimenting with a GTA01 showed pixclock values near 40000 (after the
    rounding caused by the divider calculation) caused visible flicker. Values
    near 20000 caused only a slight flicker, and the default value after rounding
    with the default HCLK frequency of 133MHz is 30075.
    
    Change the value to 35000 to make it stay in the range 17500-35000 and thus
    reduce the flicker a bit.
    
    Signed-off-by: Cesar Eduardo Barros <cesarb at cesarb.net>

commit d20ebc090406e5a67d7b9b245f10530e9d4c7411
Author: Cesar Eduardo Barros <cesarb at cesarb.net>
Date:   Wed Aug 13 12:47:22 2008 +0100

    PATCH-8_9-Experimental-S3C2410A-cpufreq-driver-fb-.eml
    
    This is the cpufreq notifier for the S3C2410 framebuffer driver.
    
    Signed-off-by: Cesar Eduardo Barros <cesarb at cesarb.net>

commit 9a5045c92fa7b69157efa997a77e22973b3f9556
Author: Cesar Eduardo Barros <cesarb at cesarb.net>
Date:   Wed Aug 13 12:47:22 2008 +0100

    PATCH-7_9-Experimental-S3C2410A-cpufreq-driver-serial-.eml
    
    This is the cpufreq notifier for the S3C2410 serial driver.
    
    It uses the hardware flow control, when available, to avoid losing characters
    during the transition.
    
    Signed-off-by: Cesar Eduardo Barros <cesarb at cesarb.net>

commit 4c91f57c320e845eb00b6ccb5dee5903dbcbd98a
Author: Cesar Eduardo Barros <cesarb at cesarb.net>
Date:   Wed Aug 13 12:47:22 2008 +0100

    PATCH-6_9-s3c2410-serial-move-divisor-calculation-to-separate-function.eml
    
    The cpufreq notifier for the S3C2410 serial driver has to recalculate the
    baud rate divisor. The code which does the calculation is currently part of
    s3c24xx_serial_set_termios. Split it off to a separate function.
    
    Code movement only, no functional changes.
    
    Signed-off-by: Cesar Eduardo Barros <cesarb at cesarb.net>

commit 176881fde3ebbd8b3c26f9b1edbf92b3c2a85dca
Author: Cesar Eduardo Barros <cesarb at cesarb.net>
Date:   Wed Aug 13 12:47:22 2008 +0100

    PATCH-5_9-Experimental-S3C2410A-cpufreq-driver-nand-.eml
    
    This is the cpufreq notifier for the S3C2410 NAND driver.
    
    Signed-off-by: Cesar Eduardo Barros <cesarb at cesarb.net>

commit 8859e0d22d017f1d0e9f151902513e4ff1a7c2b5
Author: Cesar Eduardo Barros <cesarb at cesarb.net>
Date:   Wed Aug 13 12:47:22 2008 +0100

    PATCH-4_9-Experimental-S3C2410A-cpufreq-driver-timer-.eml
    
    This is the cpufreq notifier for the S3C2410 timer code.
    
    Signed-off-by: Cesar Eduardo Barros <cesarb at cesarb.net>

commit 014765f891dbc6d78bb47f251c5aa9133a220423
Author: Cesar Eduardo Barros <cesarb at cesarb.net>
Date:   Wed Aug 13 12:47:21 2008 +0100

    PATCH-3_9-cpufreq-Warn-whem-cpufreq_register_notifier-called-before-pure-initcalls.eml
    
    If cpufreq_register_notifier is called before pure initcalls,
    init_cpufreq_transition_notifier_list will overwrite whatever it did,
    causing notifiers to be ignored.
    
    Print some noise to the kernel log if that happens.
    
    Signed-off-by: Cesar Eduardo Barros <cesarb at cesarb.net>

commit 2f51f6c3d48a1dd868deca1b90ceb6c86c8ed329
Author: Cesar Eduardo Barros <cesarb at cesarb.net>
Date:   Wed Aug 13 12:47:21 2008 +0100

    PATCH-2_9-Experimental-S3C2410A-cpufreq-driver-core-.eml
    
    This is a cpufreq driver for the S3C2410A. It deals only with the main
    frequency switching part and with the SDRAM refresh counter. The rest of the
    hardware should be dealt with via cpufreq notifiers on each of the drivers.
    
    It also has experimental support for the S3C2442.
    
    Signed-off-by: Cesar Eduardo Barros <cesarb at cesarb.net>

commit 860dd3a938c3d53e0841a7bf39e0d6afe3fdf298
Author: Cesar Eduardo Barros <cesarb at cesarb.net>
Date:   Wed Aug 13 12:47:20 2008 +0100

    PATCH-1_9-cpufreq-fix-show_trans_table.eml
    
    Fix show_trans_table when it overflows PAGE_SIZE.
    
    * Not all snprintf calls were protected against being passed a negative
    length.
    * When show_trans_table overflows, len might be > PAGE_SIZE. In that case,
    returns PAGE_SIZE.
    
    Signed-off-by: Cesar Eduardo Barros <cesarb at cesarb.net>

commit b2e2acc9bfc1d92619783411d71aeba527092c3c
Author: warmcat <andy at warmcat.com>
Date:   Wed Aug 13 12:47:20 2008 +0100

    local-config-cpufreq.patch

commit 6c8cac7aff344b545ddcb89f8365473b39044064
Author: Andy Green <andy at openmoko.com>
Date:   Wed Aug 13 12:21:00 2008 +0100

    fix-eviocgrab-switch-type.patch
    
    Signed-off-by: Andy Green <andy at openmoko.com>

commit d4ed36d017e38d09266ced9224e836a15a2334ef
Author: Neil Brown <neilb at suse.de>
Date:   Wed Aug 13 12:21:00 2008 +0100

    fix-EVIOCGRAB-redone.patch
    
    On Wednesday August 13, mickey at openmoko.org wrote:
    > Am Mittwoch 13 August 2008 09:13:43 schrieb Neil Brown:
    > > Hi I just spent some time trying to figure out why the EVIOCGRAB ioctl
    > > wasn't behaving was I expected and I finally stumbled on to this
    > > patch, which substantially changes the behaviour of EVIOCGRAB.
    > >
    > > Would it be possible to find out what the purpose of this patch is (it
    > > unfortunately contains no documentation)?
    >
    > See http://lkml.org/lkml/2006/8/12/64
    
    Thanks for the pointer!  Interesting reading.
    
    So this is a 2 year old issue (almost to the day!) which does not
    appear to have been properly resolved yet.  Sad.
    
    An input device (e.g. touch pad, key board) can be attached to
    multiple handlers (/dev/mouseX, console, etc) one of which can be
    evdev which provides the /dev/input/event* files.
    evdev can support multiple clients on a single device, as multiple
    processes can open /dev/input/eventX.  The each get to see all the
    events.
    
    EVIOCGRAB is an ioctl on an evdev device which causes all events to go
    to that handler, and that client, exclusively.
    
    It is being used for two distinct purposes.
    
    1/ Stop events going to other handlers, so that e.g. absolute touchpad
       events don't get mapped to relative mouse events.  Keyboard events
       processed by X server don't get processed by console and control-C
       kills the X server.
    2/ Stop events going to any other client, so they can e.g. be mapped
       and fed back into a uinput device,
    
    So there are three levels of grab that are required:
    
     0/ no grab : all events go to all handlers and all clients
     1/ evdev grab: events only go to evdev, but can then go to any
           client of evdev
     2/ total grab:  events only go to the specific evdev client that
           requested the grab.
    
    
    0 is the default
    mainline allows you to select 2 but not 1.
    this patch allows you to select 1, but not 2.
    
    It seems that the "obvious" thing to do is to interpret the argument
    to EVIOCGRAB to select between these options.
    We cannot use 0, 1, 2 as above - despite the fact that it makes sense
    - because that would be a regression: working programs would break.
    Maybe it's best to use 0, 2, 1 and document it clearly.  The chance of
    anyone using 2 already has got to be very close to zero.
    
    We would then need to change the drivers in the X server to use '2'
    rather than '1', and (I think) everyone would be happy.
    
    Below is my proposed patch which provides the functionality of
    the patch in question without causing any regressions.
    It also fixes two minor buglets in the original.
    
    If anyone would like to comment, I'd appreciate it.  If I hear nothing
    bad I'll propose it to Dimitry Torokhov on some appropriate list.
    
    Thanks,
    NeilBrown

commit bd73c4840670faf8718b0b0434bd4a541d335c9d
Author: Andy Green <andy at openmoko.com>
Date:   Wed Aug 13 12:14:58 2008 +0100

    revert-mokopatches-EVIOCGRAB-patch
    
    Signed-off-by: Andy Green <andy at openmoko.com>

commit b160b7afd8196b98801574705c2906c2a6cfe668
Author: Andy Green <andy at openmoko.com>
Date:   Wed Aug 13 12:04:12 2008 +0100

    fix-glamo-crank-memory-to-90MHz.patch
    
    This changes Glamo memory and now host bus PLL to 90MHz from
    80MHz, as recommended by S-Media.  Bandwidth should go up
    by 12.5% by this in raw terms anyway.
    
    Signed-off-by: Andy Green <andy at openmoko.com>

commit b39594a3f1b2fc48625b57655412b8b8908bdfc3
Author: Andy Green <andy at openmoko.com>
Date:   Wed Aug 13 12:04:12 2008 +0100

    fix-glamo-turbo-host-interface.patch
    
    Until now, we forced Glamo wait states to 3 on read and write
    actions -- on the GLAMO side of the fence.  This reduces them
    to "0", although nWAIT is still briefly operated I saw.  This
    should reduce all memory bus timing by 3 Glamo Host bus clocks,
    60ns at 50MHz.
    
    In addition, until now we used PLL1 (50MHz) for host bus clock.
    Now, we use PLL2 (80MHz) for host bus clock, so all transactions
    complete quicker on Glamo side, it's a raw 60% improvement.
    
    These changes do not appear to impact correct operation of Glamo
    SD Card or video after testing for a week.
    
    Signed-off-by: Andy Green <andy at openmoko.com>

commit 9c247b3f54e9f49d50a7dc173665ff94ff9f6360
Author: Andy Green <andy at openmoko.com>
Date:   Wed Aug 13 12:04:12 2008 +0100

    fix-reote-install-for-ext3-only-sd.patch
    
    Signed-off-by: Andy Green <andy at openmoko.com>

commit cd12f22760bb8a5a0ef7248a359c2fafe4b7f3b2
Author: Andy Green <andy at openmoko.com>
Date:   Wed Aug 13 12:04:12 2008 +0100

    defconfig-nuke-cruft.patch
    
    Signed-off-by: Andy Green <andy at openmoko.com>

commit ec18c02e7bd4cbd756732324c14500a692b13789
Author: Andy Green <andy at openmoko.com>
Date:   Wed Aug 13 12:04:10 2008 +0100

    defconfig-kill-hxd8.patch
    
    Signed-off-by: Andy Green <andy at openmoko.com>

commit f537cbfbcea1621641fa11d4c955529363e10d1a
Author: Mike Westerhof <mwester at dls.net>
Date:   Wed Aug 13 11:29:19 2008 +0100

    fix-touchscreen-driver-gta01-missing-includes.patch
    
        Add missing initialization for the touchscreen driver for the
        gta01 platform.
    
        Signed-off-by: Mike Westerhof <mwester at dls.net>

commit 09883d3d0b38c7755307cd51bc92e86b9ce9dc1e
Author: Andy Green <andy at openmoko.com>
Date:   Wed Aug 13 11:29:18 2008 +0100

    test-touchscreen-median.patch
    
    Signed-off-by: Andy Green <andy at openmoko.com>

commit a3a7241b12d6137d69ae93e8ad60cddd4701c7da
Author: Andy Green <andy at openmoko.com>
Date:   Wed Aug 13 11:29:18 2008 +0100

    config-touchscreen-filters.patch
    
    Signed-off-by: Andy Green <andy at openmoko.com>

commit cb3cc53a76c7f1f7c827d048db7a849e77071515
Author: Holger Freyther <zecke at openmoko.org>
Date:   Wed Aug 13 11:28:00 2008 +0100

    From 5ee1ee9e1c8a652b0f9cde72ad5e547db87d4d67 Mon Sep 17 00:00:00 2001
    Subject: [PATCH] [gta02] Disable hardware ECC unless we get instructed to enable it
         This is restoring the old behavior in regard to ECC. Even if
         hardware ECC was compiled in we didn't use it. Make this a runtime
         option. If the bootloader passes hardware_ecc we will enable the
         hardware ECC for real.

commit ddf2ace51e940559c1fdc0e265624236fbe59ad5
Author: Holger Freyther <zecke at openmoko.org>
Date:   Wed Aug 13 11:27:47 2008 +0100

    From ca800f8b234299c56530e56018c031957c5c7ffb Mon Sep 17 00:00:00 2001
    Subject: [PATCH] [gta02] Disable the NAND debugging as it would print every hardware ECC

commit dca223223da5ebcea80f04b90e2fd7665bed5fb2
Author: Holger Freyther <zecke at openmoko.org>
Date:   Wed Aug 13 11:27:37 2008 +0100

    From 98d97ee93af676f7d6d0bf55aaae17e11304598a Mon Sep 17 00:00:00 2001
    Subject: [PATCH] Revert "s3c2440-nand-disable-hwecc.patch"
    
    This reverts commit 1d89da736ed33d3f7c398fb9f8dfddecb7c7c7a9.

commit 163a30f5ffcc4e7af9781bd6695fdc7b27d254f9
Author: Simon Kagstrom <simon.kagstrom at gmail.com>
Date:   Wed Aug 13 11:27:24 2008 +0100

    lis302dl-add-wakeup-defs.patch
    
    Add definitions for the rest of the wakeup defs and also change FFWUSRC1
    to FFWUSRC - there are two of these which are identical.
    
    Signed-off-by: Simon Kagstrom <simon.kagstrom at gmail.com>

commit 399efd68e115b6548fe943a7a9fbf04753970e61
Author: Simon Kagstrom <simon.kagstrom at gmail.com>
Date:   Wed Aug 13 11:27:11 2008 +0100

    lis302dl-allow-unloading-module.patch
    
    This patch fixes module unloading for the accelerometer (actually module
    loading failed before). The two problems were that the interrupt was not
    unregistered, and that the device was left in a "strange" state.
    
    Signed-off-by: Simon Kagstrom <simon.kagstrom at gmail.com>

commit d2703a13c696b5e4befbd17469bc6afd3d0a0066
Author: Simon Kagstrom <simon.kagstrom at gmail.com>
Date:   Wed Aug 13 11:27:04 2008 +0100

    mach-gta02-spell-fixes.patch
    
    Fix spelling error on function name
    
    Signed-off-by: Simon Kagstrom <simon.kagstrom at gmail.com>

commit 88bf43840b9df0eb0a077a1394eb564be80a412e
Author: Andy Green <andy at openmoko.com>
Date:   Mon Aug 11 20:50:05 2008 +0100

    clean-checkpatch-gsm-resume-dep.patch
    
    Signed-off-by: Andy Green <andy at openmoko.com>

commit 04c9c142a341af62081e856d32149d9f544dbfbe
Author: Andy Green <andy at openmoko.com>
Date:   Mon Aug 11 20:49:56 2008 +0100

    clean-remove-suspend-dependencies-syslog.patch
    
    Signed-off-by: Andy Green <andy at openmoko.com>

commit 36879992de8774cbf8686740bbda383cc6fbdcbb
Author: \\\\\\\"Mike (mwester)\\\\\\ <mwester at dls.net>
Date:   Mon Aug 11 20:16:09 2008 +0100

    always-call-resume-dependencies.patch
    
    Attached is a patch that has greatly reduced the frequency of failures
    to resume (due to an oops from the glamo resume handler), and the
    dreaded "white screen after resume".  I can't say that it fixes all of
    these, although I have yet to see the white-screen since applying this
    patch and suspending/resuming several hundred times (with the 30-second
    suspend on the 2008.8 image and the endless stream of GSM error messages
    generated by something in that image, it has proved to be very useful to
    do an automated stress test!)
    
    This patch will apply to stable, and should make stable slightly more,
    well, "stable".
    
    [Feel free to remove the debug messages if someone feels strongly about
    that; I left them in because I think they might be useful in triaging
    further crashes; I'm not at all convinced that this patch will fix all
    the cases of resume failures.]
    
    [[And, yes, this is ugly, really ugly.]]
    
    [[[Oh yeah - there's still one extreme case that will result in an oops:
     if a dependent driver is built as a module, and it is unloaded, and it
    happened that the preceding suspend/resume was aborted, and that abort
    happened between the dependent driver and the driver upon which it is
    dependent, then a list entry will be left behind referencing the
    unloaded module.  There's just no good way to fix that given the way the
    resume dependency plumbing is connected up right now, so just avoid
    using modules for any of the drivers involved in the resume dependency
    stuff.]]]
    
    Regards,
    Mike (mwester)
    commit 905d2fc9c45f622418ce9ef4e67c23453aab7571
    Author: Mike Westerhof <mwester at dls.net>
    Date:   Mon Aug 11 11:11:25 2008 -0500
    
        always-call-resume-dependencies.patch
    
        Ensure that a dependent resume handler is always executed,
        even if the resume handler for driver upon which it is
        dependent never suspends (and therefore never resumes either).
        Also make sure that we do not end up with duplicate
        dependencies registered, something that can happen if the
        suspend is aborted due to driver failure or an early resume
        (such as occurs when the GSM interrupts during suspend).
    
        Signed-off-by: Mike Westerhof <mwester at dls.net>