development kernel tree: Changes to 'andy'

git at git at
Wed Jun 11 17:10:40 CEST 2008

 arch/arm/mach-s3c2440/mach-gta02.c |   38 +++++---------
 drivers/i2c/chips/pcf50633.c       |   97 ++++++++++++++++++++++--------------
 drivers/video/display/jbt6k74.c    |    2 +-
 include/linux/pcf50633.h           |    5 ++
 4 files changed, 79 insertions(+), 63 deletions(-)

New commits:
commit a143e495b0eac064b188a7dfa04f7fe8ebb3f48c
Author: Andy Green <andy at>
Date:   Wed Jun 11 15:51:45 2008 +0100

    Sean McNeil reports that without the reset for LCM in suspend, he
    gets a monochromatic mode on it somehow.
    Signed-off-by: Andy Green <andy at>

commit dcdd3e9fc41e1f5db9f098100fa7bdc61cdce83b
Author: Andy Green <andy at>
Date:   Wed Jun 11 15:51:39 2008 +0100

    After protecting pcf50633 read and write primitives against
    operation after suspend or before resume (by blowing a
    stack_trace()) I saw glamo-mci was trying to use pcf50633
    at these bad times on its own suspend and resume.  Since that
    part was already done via platform callback, I added an
    export in pcf50633 that tells you if it is ready or busy,
    and used it to defer (resume power on case) or ignore
    (suspend power off case, since pcf50633 already did it)
    the mci power call.
    Signed-off-by: Andy Green <andy at>

commit 9768baa6cb50948cb070d8fe7c60e45bd1b92cbe
Author: Andy Green <andy at>
Date:   Wed Jun 11 15:49:25 2008 +0100

     - speed up suspend and resume by using one hit i2c bulk transactions
     - don't bother storing int mask set on suspend, the default one is
       what we use anyway
     - put stack_trace() on pcf50633 low level access that fire if we
       try to touch them before we resumed
     - cosmetic source cleanup
     - reduces resume time for pcf50633 from 450ms to 255ms
    Signed-off-by: Andy Green <andy at>

More information about the commitlog mailing list