1. 23 7月, 2013 5 次提交
  2. 17 7月, 2013 1 次提交
    • A
      USB: global suspend and remote wakeup don't mix · e583d9db
      Alan Stern 提交于
      The hub driver was recently changed to use "global" suspend for system
      suspend transitions on non-SuperSpeed buses.  This means that we don't
      suspend devices individually by setting the suspend feature on the
      upstream hub port; instead devices all go into suspend automatically
      when the root hub stops transmitting packets.  The idea was to save
      time and to avoid certain kinds of wakeup races.
      
      Now it turns out that many hubs are buggy; they don't relay wakeup
      requests from a downstream port to their upstream port if the
      downstream port's suspend feature is not set (depending on the speed
      of the downstream port, whether or not the hub is enabled for remote
      wakeup, and possibly other factors).
      
      We can't have hubs dropping wakeup requests.  Therefore this patch
      goes partway back to the old policy: It sets the suspend feature for a
      port if the device attached to that port or any of its descendants is
      enabled for wakeup.  People will still be able to benefit from the
      time savings if they don't care about wakeup and leave it disabled on
      all their devices.
      
      In order to accomplish this, the patch adds a new field to the usb_hub
      structure: wakeup_enabled_descendants is a count of how many devices
      below a suspended hub are enabled for remote wakeup.  A corresponding
      new subroutine determines the number of wakeup-enabled devices at or
      below an arbitrary suspended USB device.
      
      This should be applied to the 3.10 stable kernel.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Reported-and-tested-by: NToralf Förster <toralf.foerster@gmx.de>
      Cc: stable <stable@vger.kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      e583d9db
  3. 15 7月, 2013 16 次提交
  4. 08 7月, 2013 1 次提交
  5. 04 7月, 2013 1 次提交
  6. 26 6月, 2013 3 次提交
  7. 25 6月, 2013 11 次提交
  8. 23 6月, 2013 1 次提交
    • G
      console/font: Refactor font support code selection logic · d1e183c8
      Geert Uytterhoeven 提交于
      The current Makefile rules to build font support are messy and buggy.
      Replace them by Kconfig rules:
        - Introduce CONFIG_FONT_SUPPORT, which controls the building of all font
          code,
        - Select CONFIG_FONT_SUPPORT for all drivers that use fonts,
        - Select CONFIG_FONT_8x16 for all drivers that default to the VGA8x16
          font,
        - Drop the bogus console dependency for CONFIG_VIDEO_VIVI,
        - Always process drivers/video/console/Makefile, as some drivers need
          fonts even if CONFIG_VT is not set.
      
      This fixes (if CONFIG_SOLO6X10=y and there are no built-in console
      drivers):
      
      drivers/built-in.o: In function `solo_osd_print':
      drivers/staging/media/solo6x10/solo6x10-enc.c:144: undefined reference to `.find_font'
      
      This fixes (if CONFIG_VT=n):
      
      drivers/built-in.o: In function `vivi_init':
      vivi.c:(.init.text+0x1a3da): undefined reference to `find_font'
      Signed-off-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      Acked-by: Hans Verkuil <hans.verkuil@cisco.com> [original part]
      Acked-by: Randy Dunlap <rdunlap@infradead.org> [drivers/video/Makefile]
      d1e183c8
  9. 21 6月, 2013 1 次提交