development kernel tree: Changes to 'stable'

git at git at
Tue Jul 15 10:04:36 CEST 2008

 arch/arm/mach-s3c2440/mach-gta02.c        |    6 +
 arch/arm/plat-s3c24xx/Makefile            |    3 +-
 arch/arm/plat-s3c24xx/neo1973_memconfig.c |  186 ++++++++++++++++++++
 drivers/i2c/chips/pcf50633.c              |   29 ++--
 drivers/mfd/glamo/glamo-core.c            |  266 ++++++++++++++---------------
 drivers/mfd/glamo/glamo-core.h            |    2 +
 drivers/mfd/glamo/glamo-regs.h            |    6 +-
 7 files changed, 344 insertions(+), 154 deletions(-)

New commits:
commit fd25f90517322fc6c07bfb8d34752d3cb41cb4b6
Author: Andy Green <andy at>
Date:   Tue Jul 15 09:04:11 2008 +0100

    A few questions have been flying around about how optimal
    our waitstates are for various things including Glamo.
    This patch introduces new sysfs nodes
    If you cat them you get translated info about bus speed on
    that chip select, eg,
    # cat /sys/devices/platform/neo1973-memconfig.0/BANKCON1
    BANKCON1 = 0x00000A40
     Type = ROM / SRAM
     PMC  = normal (1 data)
     Tacp = 2 clocks
     Tcah = 0 clocks
     Tcoh = 1 clock
     Tacc = 3 clocks
     Tcos = 1 clock
     Tacs = 0 clocks
    You can write them in hex too
    # echo 0x200 > /sys/devices/platform/neo1973-memconfig.0/BANKCON1
    The write format for BANKCON0 - 5 looks like this
     b1..b0   PMC  Page Mode Config
     b3..b2   Tacp Page Mode Access Cycle
     b5..b4   Tcah Address hold after CS deasserted
     b7..b6   Tcoh CS hold after OE deasserted
     b10..b8  Tacc Access Cycle Period
     b12..b11 Tcos CS setup before OE asserted
     b14..b13 Tacs Address setup before CS asserted
    BANKCON 6 and 7 have two extra bits
     b16..b15  MT  Memory type (00=ROM/SRAM, 11=DRAM)
    If it's ROM/SRAM, the rest of the bits are as described above.
    For DRAM
     b1..b0   SCAN Column address number
     b3..b2   RAS to CAS delay
    The patch is intended to let people experiement on their own.  But
    of course you will crash things for sure if the timing is wrong, and
    you can also trash SD Card data if you make Glamo unstable, so remove
    it or remount ro first.  Other horrible things are possible, but
    because the settings aren't sticky, you should always be able to
    recover by either normal reboot usually or at worst NOR boot and then
    dfu.  Most likely you will just crash your session and have to reboot
    if your settings are bad, but consider yourself warned bad things are
    possible. :-)
    Signed-off-by: Andy Green <andy at>

commit db07519c1dfe916bcf9644bfdc4d7c03707a979e
Author: Andy Green <andy at>
Date:   Tue Jul 15 09:04:05 2008 +0100

    We at least always enabled backlight on resume, this patch
    changes us to set backlight back to last requested backlight
    brightness level on resume.  Note it means that you can
    resume with screen blanked, but it should come back if that
    happened with touchscreen action as usual.
    seem to agree after resume when reportedly they didn't before.
    Signed-off-by: Andy Green <andy at>

commit e1673170182af199be7c6a2a346d8bad7e4dc532
Author: Andy Green <andy at>
Date:   Tue Jul 15 09:04:00 2008 +0100

    Two issues... we never took care to take down engines in suspend
    and bring them back in resume.  This was part of the display
    corruption that could be seen briefly on resume.  The other issue
    that made the "noise" corruption was bad ordering of resume steps.
    This patch simplifies (removing needless re-init) resume actions
    and makes explicit the suspend and resume steps.  It also adds
    code to track which engines are up and push them down in suspend
    and bring them back in resume.
    The result is no more corruption of display buffer in suspend, it
    comes back completely clean.
    Signed-off-by: Andy Green <andy at>

More information about the commitlog mailing list