1. 07 Nov, 2018 1 commit
  2. 19 Oct, 2018 1 commit
  3. 17 Oct, 2018 1 commit
  4. 11 Oct, 2018 3 commits
  5. 09 Oct, 2018 1 commit
  6. 04 Oct, 2018 1 commit
  7. 02 Oct, 2018 2 commits
  8. 28 Sep, 2018 1 commit
    • Jon Flatley's avatar
      usb: core: added uevent for over-current · 201af55d
      Jon Flatley authored
      After commit 1cbd53c8 ("usb: core: introduce per-port over-current
      counters") usb ports expose a sysfs value 'over_current_count'
      to user space. This value on its own is not very useful as it requires
      manual polling.
      
      As a solution, fire a udev event from the usb hub device that specifies
      the values 'OVER_CURRENT_PORT' and 'OVER_CURRENT_COUNT' that indicate
      the path of the usb port where the over-current event occurred and the
      value of 'over_current_count' in sysfs. Additionally, call
      sysfs_notify() so the sysfs value supports poll().
      Signed-off-by: default avatarJon Flatley <jflat@chromium.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      201af55d
  9. 24 Sep, 2018 3 commits
    • Joel Pepper's avatar
      usb: gadget: uvc: configfs: Add bFrameIndex attributes · b206548b
      Joel Pepper authored
      - Add bFrameIndex as a UVCG_FRAME_ATTR_RO for each frame size.
      - Automatically assign ascending bFrameIndex to each frame in a format.
      
      Before all "bFrameindex" attributes were set to "1" with no way to
      configure the gadget otherwise. This resulted in the host always
      negotiating for bFrameIndex 1 (i.e. the first frame size of the gadget).
      After the negotiation the host driver will set the user or application
      selected frame size, while the gadget is actually set to the first frame
      size.
      
      Now, when the containing format is linked into the streaming header,
      iterate over all child frame descriptors and assign ascending indices.
      The automatically assigned indices can be read from the new read only
      bFrameIndex configfs attribute in each frame descriptor item.
      Signed-off-by: default avatarJoel Pepper <joel.pepper@rwth-aachen.de>
      [Simplified documentation, renamed function, blank space update]
      Signed-off-by: default avatarLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      Reviewed-by: default avatarKieran Bingham <kieran.bingham@ideasonboard.com>
      b206548b
    • Laurent Pinchart's avatar
      usb: gadget: uvc: configfs: Add bFormatIndex attributes · 61ff10e0
      Laurent Pinchart authored
      The UVC format description are numbered using the descriptor's
      bFormatIndex field. The index is used in UVC requests, and is thus
      needed to handle requests in userspace. Make it dynamically discoverable
      by exposing it in a bFormatIndex configfs attribute of the uncompressed
      and mjpeg format config items.
      
      The bFormatIndex value exposed through the attribute is stored in the
      config item private data. However, that value is never set: the driver
      instead computes the bFormatIndex value when linking the stream class
      header in the configfs hierarchy and stores it directly in the class
      descriptors in a separate structure. In order to expose the value
      through the configfs attribute, store it in the config item private data
      as well. This results in a small code simplification.
      Signed-off-by: default avatarLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      Reviewed-by: default avatarKieran Bingham <kieran.bingham@ideasonboard.com>
      61ff10e0
    • Laurent Pinchart's avatar
      usb: gadget: uvc: configfs: Add interface number attributes · bf715448
      Laurent Pinchart authored
      The video control and video streaming interface numbers are needed in
      the UVC gadget userspace stack to reply to UVC requests. They are
      hardcoded to fixed values at the moment, preventing configurations with
      multiple functions.
      
      To fix this, make them dynamically discoverable by userspace through
      read-only configfs attributes in <function>/control/bInterfaceNumber and
      <function>/streaming/bInterfaceNumber respectively.
      Signed-off-by: default avatarLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      Reviewed-by: default avatarKieran Bingham <kieran.bingham@ideasonboard.com>
      bf715448
  10. 20 Sep, 2018 1 commit
  11. 19 Sep, 2018 1 commit
  12. 14 Sep, 2018 1 commit
    • Marek Marczykowski-Górecki's avatar
      xen/balloon: add runtime control for scrubbing ballooned out pages · 197ecb38
      Marek Marczykowski-Górecki authored
      Scrubbing pages on initial balloon down can take some time, especially
      in nested virtualization case (nested EPT is slow). When HVM/PVH guest is
      started with memory= significantly lower than maxmem=, all the extra
      pages will be scrubbed before returning to Xen. But since most of them
      weren't used at all at that point, Xen needs to populate them first
      (from populate-on-demand pool). In nested virt case (Xen inside KVM)
      this slows down the guest boot by 15-30s with just 1.5GB needed to be
      returned to Xen.
      
      Add runtime parameter to enable/disable it, to allow initially disabling
      scrubbing, then enable it back during boot (for example in initramfs).
      Such usage relies on assumption that a) most pages ballooned out during
      initial boot weren't used at all, and b) even if they were, very few
      secrets are in the guest at that time (before any serious userspace
      kicks in).
      Convert CONFIG_XEN_SCRUB_PAGES to CONFIG_XEN_SCRUB_PAGES_DEFAULT (also
      enabled by default), controlling default value for the new runtime
      switch.
      Signed-off-by: default avatarMarek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
      Reviewed-by: default avatarJuergen Gross <jgross@suse.com>
      Signed-off-by: default avatarBoris Ostrovsky <boris.ostrovsky@oracle.com>
      197ecb38
  13. 13 Sep, 2018 1 commit
  14. 12 Sep, 2018 1 commit
  15. 10 Sep, 2018 1 commit
  16. 07 Sep, 2018 1 commit
  17. 02 Sep, 2018 1 commit
  18. 30 Aug, 2018 1 commit
  19. 28 Aug, 2018 1 commit
  20. 27 Aug, 2018 1 commit
  21. 21 Aug, 2018 1 commit
  22. 10 Aug, 2018 1 commit
  23. 02 Aug, 2018 1 commit
  24. 29 Jul, 2018 1 commit
  25. 26 Jul, 2018 1 commit
  26. 23 Jul, 2018 3 commits
  27. 21 Jul, 2018 1 commit
  28. 19 Jul, 2018 2 commits
  29. 18 Jul, 2018 2 commits
  30. 15 Jul, 2018 2 commits