Skip to content
  1. Nov 13, 2012
    • Peter Ujfalusi's avatar
      ARM: OMAP2: Fix compillation error in cm_common · cc4b1e24
      Peter Ujfalusi authored
      
      
      Fixes the following error:
        CC      arch/arm/mach-omap2/cm_common.o
      arch/arm/mach-omap2/cm_common.c: In function ‘cm_register’:
      arch/arm/mach-omap2/cm_common.c:42:11: error: ‘EINVAL’ undeclared (first use in this function)
      arch/arm/mach-omap2/cm_common.c:42:11: note: each undeclared identifier is reported only once for each function it appears in
      arch/arm/mach-omap2/cm_common.c:45:11: error: ‘EEXIST’ undeclared (first use in this function)
      arch/arm/mach-omap2/cm_common.c: In function ‘cm_unregister’:
      arch/arm/mach-omap2/cm_common.c:66:11: error: ‘EINVAL’ undeclared (first use in this function)
      make[1]: *** [arch/arm/mach-omap2/cm_common.o] Error 1
      make: *** [arch/arm/mach-omap2] Error 2
      
      Signed-off-by: default avatarPeter Ujfalusi <peter.ujfalusi@ti.com>
      Acked-by: default avatarPaul Walmsley <paul@pwsan.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      cc4b1e24
  2. Nov 10, 2012
  3. Nov 09, 2012
  4. Oct 30, 2012
    • Paul Walmsley's avatar
      ARM: OMAP2+: WDT: move init; add read_reset_sources pdata function pointer · 37c67d03
      Paul Walmsley authored
      
      
      The OMAP watchdog timer driver directly calls a function exported by
      code in arch/arm/mach-omap2.  This is not good; it tightly couples
      this driver to the mach-omap2 integration code.  Instead, add a
      temporary platform_data function pointer to abstract this function
      call.  A subsequent patch will convert the watchdog driver to use this
      function pointer.
      
      This patch also moves the device creation code out of
      arch/arm/mach-omap2/devices.c and into arch/arm/mach-omap2/wd_timer.c.
      This is another step towards the removal of
      arch/arm/mach-omap2/devices.c.
      
      Cc: Wim Van Sebroeck <wim@iguana.be>
      Acked-by: default avatarWim Van Sebroeck <wim@iguana.be>
      [paul@pwsan.com: skip wd_timer device creation when DT blob is present]
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      37c67d03
    • Paul Walmsley's avatar
      ARM: OMAP1: CGRM: fix omap1_get_reset_sources() return type · 508c0d47
      Paul Walmsley authored
      
      
      An older version of the patch "ARM: OMAP1: create read_reset_sources()
      function (for initial use by watchdog)" was sent upstream, which used
      the wrong return type for the omap1_get_reset_sources() function.
      Fix it to return a u32, which is what the WDTIMER platform_data
      function pointer read_reset_sources() expects.
      
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      508c0d47
  5. Oct 27, 2012
  6. Oct 26, 2012
  7. Oct 25, 2012
  8. Oct 24, 2012
    • Daniel Vetter's avatar
      console: use might_sleep in console_lock · 6b898c07
      Daniel Vetter authored
      
      
      Instead of BUG_ON(in_interrupt()), since that doesn't check for all
      the newfangled stuff like preempt.
      
      Note that this is valid since the console_sem is essentially used like
      a real mutex with only two twists:
      - we allow trylock from hardirq context
      - across suspend/resume we lock the logical console_lock, but drop the
        semaphore protecting the locking state.
      
      Now that doesn't guarantee that no one is playing tricks in
      single-thread atomic contexts at suspend/resume/boot time, but
      - I couldn't find anything suspicious with some grepping,
      - might_sleep shouldn't die,
      - and I think the upside of catching more potential issues is worth
        the risk of getting a might_sleep backtrace that would have been
        save (and then dealing with that fallout).
      
      Cc: Dave Airlie <airlied@gmail.com>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      6b898c07
  9. Oct 23, 2012
    • Jiri Slaby's avatar
      TTY: move tty buffers to tty_port · ecbbfd44
      Jiri Slaby authored
      
      
      So this is it. The big step why we did all the work over the past
      kernel releases. Now everything is prepared, so nothing protects us
      from doing that big step.
      
                 |  |            \  \ nnnn/^l      |  |
                 |  |             \  /     /       |  |
                 |  '-,.__   =>    \/   ,-`    =>  |  '-,.__
                 | O __.´´)        (  .`           | O __.´´)
                  ~~~   ~~          ``              ~~~   ~~
      The buffers are now in the tty_port structure and we can start
      teaching the buffer helpers (insert char/string, flip etc.) to use
      tty_port instead of tty_struct all around.
      
      Signed-off-by: default avatarJiri Slaby <jslaby@suse.cz>
      Acked-by: default avatarAlan Cox <alan@linux.intel.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      ecbbfd44
    • Jiri Slaby's avatar
      TTY: add port -> tty link · 967fab69
      Jiri Slaby authored
      
      
      For that purpose we have to temporarily introduce a second tty back
      pointer into tty_port. It is because serial layer, and maybe others,
      still do not use tty_port_tty_set/get. So that we cannot set the
      tty_port->tty to NULL at will now.
      
      Yes, the fix would be to convert whole serial layer and all its users
      to tty_port_tty_set/get. However we are in the process of removing the
      need of tty in most of the call sites, so this would lead to a
      duplicated work.
      
      Instead we have now tty_port->itty (internal tty) which will be used
      only in flush_to_ldisc. For that one it is ensured that itty is valid
      wherever the work is run. IOW, the work is synchronously cancelled
      before we set itty to NULL and also before hangup is processed.
      
      After we need only tty_port and not tty_struct in most code, this
      shall be changed to tty_port_tty_set/get and itty removed completely.
      
      Signed-off-by: default avatarJiri Slaby <jslaby@suse.cz>
      Acked-by: default avatarAlan Cox <alan@linux.intel.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      967fab69
    • Jiri Slaby's avatar
      TTY: tty_buffer, cache pointer to tty->buf · 5cff39c6
      Jiri Slaby authored
      
      
      During the move of tty buffers from tty_struct to tty_port, we will
      need to switch all users of buf to tty->port->buf. There are many
      functions where this is accessed directly in their code many times.
      Cache the tty->buf pointer in such functions now and change only
      single lines in each function in the next patch.
      
      Not that it is convenient for the next patch, but the code is now also
      more readable.
      
      Signed-off-by: default avatarJiri Slaby <jslaby@suse.cz>
      Acked-by: default avatarAlan Cox <alan@linux.intel.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      5cff39c6