Skip to content
Snippets Groups Projects
  1. May 09, 2017
  2. May 02, 2017
  3. Apr 27, 2017
  4. Apr 26, 2017
  5. Apr 21, 2017
    • Hareesh Gundu's avatar
      msm: kgsl: Allow draw context to perform only replay on recovery · 6ddd277a
      Hareesh Gundu authored
      
      Robust context attempts to perform a rendering that takes too long
      whether due to an infinite loop in a shader or even just a rendering
      operation that takes too long on the given hardware. This type of
      attempts can result into GPU faults. Robust context expect driver
      to replay IB instead skip IB and if it fails on replay context has
      to be invalidated.
      
      KGSL_CONTEXT_INVALIDATE_ON_FAULT flag allows draw context to execute
      only replay policy on GPU fault recovery instead of going to default
      recovery policy. User space has to set this flag during the context
      creation.
      
      Bug: 34887800
      Change-Id: If42dc5afc7d5ed1226b73ae5abfa2648d7acf2c3
      Signed-off-by: default avatarHareesh Gundu <hareeshg@codeaurora.org>
      6ddd277a
  6. Apr 20, 2017
  7. Apr 19, 2017
  8. Apr 17, 2017
  9. Apr 12, 2017
  10. Apr 11, 2017
  11. Apr 10, 2017
  12. Apr 07, 2017
    • Robert Baldyga's avatar
      UPSTREAM: usb: gadget: f_fs: add "no_disconnect" mode · 3e5882a9
      Robert Baldyga authored
      
      Since we can compose gadgets from many functions, there is the problem
      related to gadget breakage while FunctionFS daemon being closed. FFS
      function is userspace code so there is no way to know when it will close
      files (it doesn't matter what is the reason of this situation, it can
      be daemon logic, program breakage, process kill or any other). So when
      we have another function in gadget which, for example, sends some amount
      of data, does some software update or implements some real-time functionality,
      we may want to keep the gadget connected despite FFS function is no longer
      functional.
      
      We can't just remove one of functions from gadget since it has been
      enumerated, so the only way to keep entire gadget working is to make
      broken FFS function deactivated but still visible to host. For this
      purpose this patch introduces "no_disconnect" mode. It can be enabled
      by setting mount option "no_disconnect=1", and results with defering
      function disconnect to the moment of reopen ep0 file or filesystem
      unmount. After closing all endpoint files, FunctionFS is set to state
      FFS_DEACTIVATED.
      
      When ffs->state == FFS_DEACTIVATED:
      - function is still bound and visible to host,
      - setup requests are automatically stalled,
      - transfers on other endpoints are refused,
      - epfiles, except ep0, are deleted from the filesystem,
      - opening ep0 causes the function to be closed, and then FunctionFS
        is ready for descriptors and string write,
      - altsetting change causes the function to be closed - we want to keep
        function alive until another functions are potentialy used, altsetting
        change means that another configuration is being selected or USB cable
        was unplugged, which indicates that we don't need to stay longer in
        FFS_DEACTIVATED state
      - unmounting of the FunctionFS instance causes the function to be closed.
      
      Tested-by: default avatarDavid Cohen <david.a.cohen@linux.intel.com>
      Acked-by: default avatarMichal Nazarewicz <mina86@mina86.com>
      Signed-off-by: default avatarRobert Baldyga <r.baldyga@samsung.com>
      Signed-off-by: default avatarFelipe Balbi <balbi@ti.com>
      
      Bug: 36801389
      Bug: 34873000
      Change-Id: I950dc11f21048c34af640cb3ab81873d2a6730a9
      Signed-off-by: default avatarJerry Zhang <zhangjerry@google.com>
      3e5882a9
    • Joel Scherpelz's avatar
      net: ipv6: Add sysctl for minimum prefix len acceptable in RIOs. · e29230a9
      Joel Scherpelz authored
      
      This commit adds a new sysctl accept_ra_rt_info_min_plen that
      defines the minimum acceptable prefix length of Route Information
      Options. The new sysctl is intended to be used together with
      accept_ra_rt_info_max_plen to configure a range of acceptable
      prefix lengths. It is useful to prevent misconfigurations from
      unintentionally blackholing too much of the IPv6 address space
      (e.g., home routers announcing RIOs for fc00::/7, which is
      incorrect).
      
      Backport of net-next commit bbea124b ("net: ipv6: Add sysctl for minimum prefix len acceptable in RIOs.")
      
      [lorenzo@google.com: fixed conflicts in include/uapi/linux/ipv6.h]
      Bug: 33333670
      Test: net_test passes
      
      Signed-off-by: default avatarJoel Scherpelz <jscherpelz@google.com>
      Acked-by: default avatarLorenzo Colitti <lorenzo@google.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      e29230a9