15 Jan, 2010

1 commit


24 Dec, 2009

2 commits


17 Dec, 2009

1 commit

  • * git://git.kernel.org/pub/scm/linux/kernel/git/lethal/sh-2.6: (33 commits)
    sh: Fix test of unsigned in se7722_irq_demux()
    sh: mach-ecovec24: Add FSI sound support
    sh: mach-ecovec24: Add mt9t112 camera support
    sh: mach-ecovec24: Add tw9910 support
    sh: MSIOF/mmc_spi platform data for the Ecovec24 board
    sh: ms7724se: Add ak4642 support
    sh: Fix up FPU build for SH5
    sh: Remove old early serial console code V2
    sh: sh5 scif pdata (sh5-101/sh5-103)
    sh: sh4a scif pdata (sh7757/sh7763/sh7770/sh7780/sh7785/sh7786/x3)
    sh: sh4a scif pdata (sh7343/sh7366/sh7722/sh7723/sh7724)
    sh: sh4 scif pdata (sh7750/sh7760/sh4-202)
    sh: sh3 scif pdata (sh7705/sh770x/sh7710/sh7720)
    sh: sh2a scif pdata (sh7201/sh7203/sh7206/mxg)
    sh: sh2 scif pdata (sh7616)
    sh-sci: Extend sh-sci driver with early console V2
    sh: Stub in P3 ioremap support for nommu parts.
    sh: wire up vmallocinfo support in ioremap() implementations.
    sh: Make the unaligned trap handler always obey notification levels.
    sh: Couple kernel and user write page perm bits for CONFIG_X2TLB
    ...

    Linus Torvalds
     

16 Dec, 2009

1 commit


15 Dec, 2009

1 commit

  • This is V2 of early serial console support for the sh-sci
    driver. The early serial console is using early platform
    devices and "earlyprintk". To use this feature the early
    platform devices must be broken out to one device per port
    and the desired port should be selected on the kernel command
    line like: "earlyprintk=sh-sci.N[,baudrate][,keep]"

    Signed-off-by: Magnus Damm
    Signed-off-by: Paul Mundt

    Magnus Damm
     

04 Dec, 2009

1 commit

  • Currently serial ports on SH CPUs get disabled too early, because the
    sci_tx_empty() routine claims to not be able to detect whether the
    transmission has been completed and just always returns TIOCSER_TEMT. This
    results in corrupt output of last characters if the port is not open for
    reading at the same time. It is however possible to detect whether
    transmission has been completed. Use the TEND bit of the status register
    for this.

    Signed-off-by: Guennadi Liakhovetski
    Signed-off-by: Paul Mundt

    Guennadi Liakhovetski
     

25 Nov, 2009

2 commits

  • The sh-sci code conditionalized the clock framework support in order to
    give the other platforms a chance to catch up. sh64 supported this some
    time ago and the forthcoming ARM changes handle this as well, this leaves
    h8300 as the odd one out. H8300 has had since 2.5 to merge it's sh-sci
    support upstream, and has yet to do so. At this point I will no longer be
    holding back the driver to support an unreponsive architecture, 7 years
    is quite enough of a grace period. Support is easily implemented on the
    architecture if and when it ever decides to merge its changes upstream.

    Signed-off-by: Paul Mundt

    Paul Mundt
     
  • The function sci_remove is defined without any section modifier, so
    don't use __devexit_p to wrap it.

    Signed-off-by: Uwe Kleine-König
    Cc: Magnus Damm
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Paul Mundt

    Uwe Kleine-König
     

06 Nov, 2009

1 commit


20 Sep, 2009

1 commit


21 Aug, 2009

1 commit


29 Jul, 2009

1 commit

  • This cleans up the irqflags tracing code quite a bit and ties it
    in to various missing callsites that caused an imbalance when
    CONFIG_PROVE_LOCKING was enabled.

    Previously this was catching on:

    987 #ifdef CONFIG_PROVE_LOCKING
    988 DEBUG_LOCKS_WARN_ON(!p->hardirqs_enabled);
    989 DEBUG_LOCKS_WARN_ON(!p->softirqs_enabled);
    990 #endif
    991 retval = -EAGAIN;

    with hardirqs being doubly enabled, and subsequently bailing out
    with the following call trace:

    Call trace:
    [] __lock_acquire+0x616/0x6a6
    [] do_fork+0xf8/0x2b0
    [] trace_hardirqs_on_caller+0xd4/0x114
    [] _spin_unlock_irq+0x20/0x64
    [] __lock_acquire+0x616/0x6a6
    [] kernel_thread+0x48/0x70
    [] ____call_usermodehelper+0x0/0x110
    [] ____call_usermodehelper+0x0/0x110
    [] kernel_thread_helper+0x0/0x14
    [] __call_usermodehelper+0x38/0x70
    [] worker_thread+0x150/0x274
    [] lock_release+0x0/0x198
    [] __call_usermodehelper+0x0/0x70
    [] autoremove_wake_function+0x0/0x30
    [] kthread+0x3e/0x70
    [] worker_thread+0x0/0x274
    [] kernel_thread_helper+0x8/0x14
    [] kthread+0x0/0x70
    [] kernel_thread_helper+0x0/0x14

    Reported-by: Nobuhiro Iwamatsu
    Signed-off-by: Stuart Menefy
    Signed-off-by: Matt Fleming
    Signed-off-by: Paul Mundt

    Stuart Menefy
     

07 Jul, 2009

1 commit


03 Jul, 2009

1 commit

  • This patch updates the receive error code for muxed
    interrupts in the sh-sci driver.

    Receive error interrupts may be generated by the hardware
    if RE or REIE bits in SCSCR are set. Update the muxed
    interrupt handling code to acknowledge error interrupts
    if RE or REIE is set, instead of only acknowledging if
    REIE is set.

    Without this patch error interrupts may be generated but
    never acked resulting in a "nobody cared" crash.

    Signed-off-by: Magnus Damm
    Signed-off-by: Paul Mundt

    Magnus Damm
     

15 Jun, 2009

1 commit


02 Jun, 2009

1 commit


13 May, 2009

1 commit


08 May, 2009

10 commits


07 May, 2009

1 commit

  • Presently this is special-cased for early initialization. While there are
    situations where these static early initializations are still necessary,
    with minor changes it is possible to use this for the regular ioremap
    implementation as well. This allows us to kill off the special-casing for
    the remap completely and to start tidying up all of the SH-5
    special-casing in drivers.

    Signed-off-by: Paul Mundt

    Paul Mundt
     

03 Mar, 2009

1 commit

  • This adds preliminary support for the SH7786 CPU subtype.

    While this is a dual-core CPU, only UP is supported for now. L2 cache
    support is likewise not yet implemented.

    More information on this particular CPU subtype is available at:

    http://www.renesas.com/fmwk.jsp?cnt=sh7786_root.jsp&fp=/products/mpumcu/superh_family/sh7780_series/sh7786_group/

    Signed-off-by: Kuninori Morimoto
    Signed-off-by: Paul Mundt

    Kuninori Morimoto
     

27 Feb, 2009

1 commit


22 Dec, 2008

8 commits


13 Nov, 2008

1 commit

  • Under qemu there is a race between the TDxE read-and-clear and the SCxTDR
    write. While on hardware it can be gauranteed that the read-and-clear
    will happen prior to the character being written out, no such assumption
    can be made under emulation. As this path happens with IRQs off and the
    hardware itself doesn't care about the ordering, move the SCxTDR write
    until after the read-and-clear.

    Signed-off-by: Vladimir Prus
    Signed-off-by: Paul Mundt

    Paul Mundt