10 Jan, 2012

1 commit


05 Jan, 2012

1 commit


14 Nov, 2011

1 commit


12 Jul, 2011

1 commit


16 Mar, 2011

1 commit


16 Dec, 2010

1 commit

  • This patch introduces pxa2xx_map_io() and pxa3xx_map_io() to distinguish
    between PXA25x/PXA27x and PXA3xx memory mapping.

    Also, fixup for platforms broken after introducing pxa{25x,27x}_map_io()
    and pxa3xx_map_io() is included.

    Signed-off-by: Marek Vasut
    Signed-off-by: Eric Miao

    Marek Vasut
     

20 Oct, 2010

1 commit

  • Since we're now using addruart to establish the debug mapping, we can
    remove the io_pg_offst and phys_io members of struct machine_desc.

    The various declarations were removed using the following script:

    grep -rl MACHINE_START arch/arm | xargs \
    sed -i '/MACHINE_START/,/MACHINE_END/ { /\.\(phys_io\|io_pg_offst\)/d }'

    [ Initial patch was from Jeremy Kerr, example script from Russell King ]

    Signed-off-by: Nicolas Pitre
    Acked-by: Eric Miao

    Nicolas Pitre
     

02 Mar, 2010

1 commit


01 Dec, 2009

1 commit

  • For some platforms, it is inappropriate to register all PXA UARTs.
    In some cases, the UARTs may not be used, and in others we may want
    to avoid registering the UARTs to allow other drivers (eg, FICP) to
    make use of the UART.

    In addition, a while back there was a request to be able to pass
    platform data to the UART driver.

    This patch enables all of this by providing functions platforms can
    call to register each individual UART.

    Signed-off-by: Russell King
    Acked-by: Mike Rapoport
    Acked-by: Robert Jarzmik
    Signed-off-by: Eric Miao

    Russell King
     

10 Sep, 2009

1 commit

  • Several boards use always the same pattern with pxamci :
    request gpio, request irq for that gpio to detect MMC card
    insertion, request gpio for read-only mode detection, etc
    ...

    Now that pxamci provides platform_data to describe simple
    gpio management of the MMC external controls, use it.

    Signed-off-by: Robert Jarzmik
    Acked-by: Mike Rapoport
    Acked-by: Philipp Zabel
    Acked-by: Dmitry Eremin-Solenikov
    Cc: rpurdie@rpsys.net
    Cc: drwyrm@gmail.com
    Cc: sakoman@gmail.com
    Cc: marek.vasut@gmail.com
    Cc: s.hauer@pengutronix.de
    Signed-off-by: Eric Miao

    Robert Jarzmik
     

09 Mar, 2009

1 commit

  • Considering the header mess ATM, it is not always possible to include
    the correct header files within board code. Let's keep this simple:

    - for pxa25x based platforms
    - for pxa27x based platforms
    - for pxa300 based platforms
    - for pxa320 based platforms
    - for pxa930 based platforms

    NOTE:

    1. one header one board file, they are not compatible (i.e. they have
    conflicting definitions which won't compile if included together).

    2. Unless strictly necessary, the following header files are considered
    to be SoC files use _only_, and is not recommended to be included in
    board code:












    Signed-off-by: Eric Miao

    Eric Miao
     

27 Sep, 2008

3 commits


07 Aug, 2008

2 commits


19 Apr, 2008

1 commit

  • two reasons:
    1. GPIO namings and their mode definitions are conceptually not part
    of the PXA register definitions

    2. this is actually a temporary move in the transition of PXA2xx to
    use MFP-alike APIs (as what PXA3xx is now doing), so that legacy
    code will still work and new code can be added in step by step

    Signed-off-by: eric miao
    Signed-off-by: Russell King

    eric miao
     

28 Jan, 2008

1 commit

  • smc91x is shared between many different platforms. Each platform needs
    to specify the interrupt type, and in some cases the irq type depends
    on more than just the build configuration - it depends on runtime
    checks.

    Rather than throwing this code into the SMC_IRQ_FLAGS definition, provide
    a way for these flags to be passed via the IRQ resource itself.

    Note that IRQF_TRIGGER_* constants are intentionally defined to correspond
    with the IORESOURCE_IRQ_* interrupt type flags, in much the same way that
    the low bits of PCI iomem resources correspond with the BAR flag bits.

    Also provide a way to configure smc91x to read the IRQ flags from the
    resource. Once all platforms have been converted over (signified
    by all definitions of SMC_IRQ_FLAGS being -1) SMC_IRQ_FLAGS should
    be removed.

    Signed-off-by: Russell King
    Acked-by: Nicolas Pitre
    Acked-by: Jeff Garzik

    Russell King
     

12 Jul, 2007

2 commits


09 Oct, 2006

1 commit

  • Use the new typedef for interrupt handler function pointers rather than
    actually spelling out the full thing each time. This was scripted with the
    following small shell script:

    #!/bin/sh
    egrep -nHrl -e 'irqreturn_t[ ]*[(][*]' $* |
    while read i
    do
    echo $i
    perl -pi -e 's/irqreturn_t\s*[(]\s*[*]\s*([_a-zA-Z0-9]*)\s*[)]\s*[(]\s*int\s*,\s*void\s*[*]\s*[)]/irq_handler_t \1/g' $i || exit $?
    done

    Signed-Off-By: David Howells

    David Howells
     

07 Oct, 2006

1 commit


02 Oct, 2006

1 commit

  • Add the ability to have pxafb use only certain fixed video modes
    (selected on a per platform basis). This is useful on production
    hardware such as the Zaurus cxx00 models where the valid modes are
    known in advance and any other modes could result in hardware damage.

    Following this, add support for the cxx00 QVGA mode. Mode information
    is passed to the lcd_power call to allowing the panel drivers to
    configure the display hardware accordingly (corgi_lcd already contains
    the functionality for the cxx00 panel).

    This mirrors the setup already used by w100fb.

    Signed-off-by: Richard Purdie
    Signed-off-by: Russell King

    Richard Purdie
     

02 Jul, 2006

1 commit


14 Jan, 2006

1 commit


30 Oct, 2005

1 commit


28 Oct, 2005

1 commit


04 Jul, 2005

2 commits


17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds