1. 11 8月, 2010 6 次提交
    • G
      omap_hsmmc: add init_card pass-through callback · 4816858c
      Grazvydas Ignotas 提交于
      This will allow us to set up special cards in machine drivers just after
      they are detected by MMC core.
      Signed-off-by: NGrazvydas Ignotas <notasas@gmail.com>
      Cc: Adrian Hunter <adrian.hunter@nokia.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Bob Copeland <me@bobcopeland.com>
      Cc: Kalle Valo <kvalo@adurom.com>
      Cc: Madhusudhan Chikkature <madhu.cr@ti.com>
      Cc: Kishore Kadiyala <kishore.kadiyala@ti.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: <linux-mmc@vger.kernel.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      4816858c
    • L
      x86: fix up system call numbering nit · 8cbd84f2
      Linus Torvalds 提交于
      As pointed out by Jiri Slaby: when I resolved the the 32-bit x85 system
      call entry tables for prlimit (due to the conflict with fanotify), I
      forgot to add the numbering in comments that we do for every fifth entry.
      Reported-by: NJiri Slaby <jslaby@suse.cz>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      8cbd84f2
    • B
      USB: s3c-hsotg: Add initial detection and setup for dedicated FIFO mode · 10aebc77
      Ben Dooks 提交于
      Add support for the dedicated FIFO mode on newer SoCs such as the S5PV210
      partly to improve support and to fix the bug where any non-EP0 IN endpoint
      requires its own FIFO allocation.
      
      To fix this, we ensure that any non-zero IN endpoint is given a TXFIFO
      using the same allocation method as the periodic case (all our current
      hardware has enough FIFOs and FIFO memory for a 1:1 mapping) and ensure
      that the necessary transmission done interrupt is enabled.
      
      The default settings from reset for the core point all EPs at FIFO0,
      used for the control endpoint. However, the controller documentation
      states that all IN endpoints _must_ have a unique FIFO to avoid any
      contention during transmission.
      
      Note, this leaves us with a large IN FIFO for EP0 (which re-uses the
      old NPTXFIFO) for an endpoint which cannot shift more than a pair of
      packets at a time... this is a waste, but it looks like we cannot
      re-allocate space to the individual IN FIFOs as they are already
      maxed out (to be confirmed).
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      10aebc77
    • I
      USB: otg/ulpi: extend the generic ulpi driver. · 13dd0c97
      Igor Grinberg 提交于
      1) Introduce ulpi specific flags for control of the ulpi phy
      2) Extend the generic ulpi driver with support for Function and
      Interface control of upli phy
      3) Update the platforms using the generic ulpi driver with new ulpi
      flags
      4) Remove the otg control flags not in use
      Signed-off-by: NIgor Grinberg <grinberg@compulab.co.il>
      Signed-off-by: NMike Rapoport <mike@compulab.co.il>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      13dd0c97
    • H
      tty: Add EXTPROC support for LINEMODE · 26df6d13
      hyc@symas.com 提交于
      This patch is against the 2.6.34 source.
      
      Paraphrased from the 1989 BSD patch by David Borman @ cray.com:
      
           These are the changes needed for the kernel to support
           LINEMODE in the server.
      
           There is a new bit in the termios local flag word, EXTPROC.
           When this bit is set, several aspects of the terminal driver
           are disabled.  Input line editing, character echo, and mapping
           of signals are all disabled.  This allows the telnetd to turn
           off these functions when in linemode, but still keep track of
           what state the user wants the terminal to be in.
      
           New ioctl:
               TIOCSIG         Generate a signal to processes in the
                               current process group of the pty.
      
           There is a new mode for packet driver, the TIOCPKT_IOCTL bit.
           When packet mode is turned on in the pty, and the EXTPROC bit
           is set, then whenever the state of the pty is changed, the
           next read on the master side of the pty will have the TIOCPKT_IOCTL
           bit set.  This allows the process on the server side of the pty
           to know when the state of the terminal has changed; it can then
           issue the appropriate ioctl to retrieve the new state.
      
      Since the original BSD patches accompanied the source code for telnet
      I've left that reference here, but obviously the feature is useful for
      any remote terminal protocol, including ssh.
      
      The corresponding feature has existed in the BSD tty driver since 1989.
      For historical reference, a good copy of the relevant files can be found
      here:
      
      http://anonsvn.mit.edu/viewvc/krb5/trunk/src/appl/telnet/?pathrev=17741Signed-off-by: NHoward Chu <hyc@symas.com>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      26df6d13
    • G
      tty: remove remaining Hayes ESP ioctls · a3c8ed69
      Greg Kroah-Hartman 提交于
      As Jeff Dike pointed out, the Hayes ESP driver was removed in commit
      f53a2ade, so these ioctl definitions
      should also be removed.  This cleans up the remaining arch-specific
      locations of this ioctl value.
      
      Thanks to Arnd for pointing these out.
      
      Cc: Jeff Dike <jdike@addtoit.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Alan Cox <alan@linux.intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      a3c8ed69
  2. 10 8月, 2010 26 次提交
  3. 09 8月, 2010 7 次提交
  4. 08 8月, 2010 1 次提交
    • A
      block: push down BKL into .open and .release · 6e9624b8
      Arnd Bergmann 提交于
      The open and release block_device_operations are currently
      called with the BKL held. In order to change that, we must
      first make sure that all drivers that currently rely
      on this have no regressions.
      
      This blindly pushes the BKL into all .open and .release
      operations for all block drivers to prepare for the
      next step. The drivers can subsequently replace the BKL
      with their own locks or remove it completely when it can
      be shown that it is not needed.
      
      The functions blkdev_get and blkdev_put are the only
      remaining users of the big kernel lock in the block
      layer, besides a few uses in the ioctl code, none
      of which need to serialize with blkdev_{get,put}.
      
      Most of these two functions is also under the protection
      of bdev->bd_mutex, including the actual calls to
      ->open and ->release, and the common code does not
      access any global data structures that need the BKL.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NChristoph Hellwig <hch@infradead.org>
      Signed-off-by: NJens Axboe <jaxboe@fusionio.com>
      6e9624b8