development kernel tree: Changes to 'andy'

git at git.openmoko.org git at git.openmoko.org
Sat Aug 23 12:04:01 CEST 2008


Rebased ref, commits from common ancestor:
commit 37a56324458b38768ed6bd3ccfb2535f9b6bd44e
Author: Andy Green <andy at openmoko.com>
Date:   Sat Aug 23 11:03:24 2008 +0100

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

commit d6b522571b9b095d48b6a7ac0cfe3fbf9bfedf33
Author: Neil Brown <neilb at suse.de>
Date:   Sat Aug 23 11:03:24 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 7c95f691898ff796e24eb1f4f3f7280f31997146
Author: Andy Green <andy at openmoko.com>
Date:   Sat Aug 23 11:03:23 2008 +0100

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

commit 162dcc9221615ec077d6b7c89f61a8ca91e72940
Author: Andy Green <andy at openmoko.com>
Date:   Sat Aug 23 11:03:23 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 d7fcdbbc174f7608cec949ac7789e6b94521971d
Author: Andy Green <andy at openmoko.com>
Date:   Sat Aug 23 11:03:22 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 585abb56b6aff82cf1ed697272d78f20dd13f6f3
Author: Andy Green <andy at openmoko.com>
Date:   Sat Aug 23 11:03:22 2008 +0100

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

commit 11d3f25004de8be41122a4c010f3ae8a84266c87
Author: Andy Green <andy at openmoko.com>
Date:   Sat Aug 23 11:03:21 2008 +0100

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

commit 55c95e71e5ad1b15751886ea1109ceaa4497147a
Author: Andy Green <andy at openmoko.com>
Date:   Sat Aug 23 11:03:21 2008 +0100

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

commit 1fdea9aadf05ed0f5bab7139a4093561047ac6f6
Author: Mike Westerhof <mwester at dls.net>
Date:   Sat Aug 23 11:03:21 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 b7c12042f7934740a2db49edc815bab47465eeb3
Author: Andy Green <andy at openmoko.com>
Date:   Sat Aug 23 11:03:21 2008 +0100

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

commit 5d18377d23e7c89940cb1a53ddb6382ccd2dcabb
Author: Andy Green <andy at openmoko.com>
Date:   Sat Aug 23 11:03:20 2008 +0100

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

commit a1e97c611253511ffc2d8c45e3e6d6894fa03fa3
Author: Andy Green <andy at openmoko.com>
Date:   Sat Aug 23 11:01:50 2008 +0100

    gta02-accel-isr-fix-more.patch
    
    Fix all of the mismatches Andrzej put us on to.
    
    Found-by: Andrzej Zaborowski <balrogg at gmail.com>
    Signed-off-by: Andy Green <andy at openmoko.com>

commit 4a728e4772d53767fcbccd0b2b7e7278c961ce34
Author: Andy Green <agreen at pads.home.warmcat.com>
Date:   Sat Aug 23 11:01:25 2008 +0100

    From: Andrzej Zaborowski <balrogg at gmail.com>
    
    fix-accel-irq-mismatch.patch
    
    I just found a while to start doing something cool with the
    accelerometers but I hit #1613 (both accelerometer nodes can't be read
    concurrently for longer than a moment). Turns out to be very silly.
    I'll continue the cool stuff another day,
    Cheers

commit 2d61a7406ec89893cdb4246d3f0144818278a5d8
Author: Andy Green <andy at openmoko.com>
Date:   Fri Aug 15 11:51:04 2008 +0100

    checkpatch-accel-fixes.patch
    
    style cleanups for accel threshold setting patch
    
    Signed-off-by: Andy Green <andy at openmoko.com>

commit 69acbd477fb7024d2cfa3702036b92ecb6c8e7b5
Author: Simon Kagstrom <simon.kagstrom at gmail.com>
Date:   Fri Aug 15 11:50:56 2008 +0100

    interface for configuring freefall/wakeup interrupts for the accelerometers
    
    Hi!
    
    First: Unfortunately, the freerunner currently wakes up immediately on
    suspend when the accelerometer IRQ is selected as a wakeup source. I'm
    posting this for comments and if someone else wants to have a look at
    this problem.
    
    The patch should be safe to apply even though the sleep portion doesn't
    work - as long as it's configured it will not disturb anything.
    
    // Simon
    --
    lis302dl-configure-wakeup-interrupts.patch
    
    From: simon.kagstrom <simon.kagstrom at gmail.com>
    
    First: Unfortunately, the freerunner currently wakes up immediately on
    suspend when the accelerometer IRQ is selected as a wakeup source.
    
    
    Add configuration of wakeup/freefall interrupts through a sysfs
    interface. Configuration is done through echoing a value of the
    form
    
       X Y Z THRESHOLD DURATION SPEC
    
    to freefall_wakeup_1/2. X, Y and Z are threshold values, given as a
    value > 0, < 0 or 0 to specify if an interrupt should be generated for
    high or low thresholds or neither (off). THRESHOLD specifies the
    threshold that must be exceeded. DURATION specifies the time in
    milliseconds for which the acceleration should be measured. SPEC is
    either '1' or '0' and specifies if the thresholds should be taken all
    together or one at a time ('and' or 'or' mode).
    
    Echoing '0' to the file turns off the interrupts.
    
    Example:
    
      echo "1 1 1 60 60 0" > freefall_wakeup_1   # Turn on x,y,z, 60ms/60 threshold, or-mode
      echo "0" > freefall_wakeup_1 # Turn off interrupt
    
    The hardware supports two simulataneous wakeup sources to be configured,
    but the freerunner only connects one of the interrupt outputs. The patch
    exports both. Similarly, only the "top" accelerometer can be used as a
    wake-up source, and it's not possible to generate DATA_READY interrupts
    while the wakeup interrupts are active.
    
    Signed-off-by: Simon Kagstrom <simon.kagstrom at gmail.com>




More information about the commitlog mailing list