1. 04 Jun, 2015 17 commits
  2. 03 Jun, 2015 20 commits
    • Dave Airlie's avatar
      Merge branch 'virtio-gpu-drm-next' of git://git.kraxel.org/linux into drm-next · 63e14561
      Dave Airlie authored
      Yay, thanks to Gerd for pull this together.
      
      * 'virtio-gpu-drm-next' of git://git.kraxel.org/linux:
        Add MAINTAINERS entry for virtio-gpu.
        Add virtio gpu driver.
        drm_vblank_get: don't WARN_ON in case vblanks are not initialized
        break kconfig dependency loop
      63e14561
    • Dave Airlie's avatar
      Merge branch 'linux-4.1.0-rc5-tilcdc-refactor' of https://github.com/jsarha/linux into drm-next · 6aa62725
      Dave Airlie authored
      Please pull the contents of "Use DRM component API in tilcdc to
      connect to tda998x" patch series.
      
      * 'linux-4.1.0-rc5-tilcdc-refactor' of https://github.com/jsarha/linux:
        drm/tilcdc: Force building of DRM_TILCDC_SLAVE_COMPAT
        drm/tilcdc: Add DRM_TILCDC_SLAVE_COMPAT for ti,tilcdc,slave binding support
        drm/tilcdc: use pm_runtime_irq_safe()
        drm/tilcdc: Add support for external tda998x encoder
        drm/tilcdc: Remove tilcdc slave support for tda998x driver
        drm/tilcdc: Fix module unloading
      6aa62725
    • Dave Airlie's avatar
      Merge tag 'v4.1-rc6' into drm-next · a8a50fce
      Dave Airlie authored
      Linux 4.1-rc6
      
      backmerge 4.1-rc6 as some of the later pull reqs are based on newer bases
      and I'd prefer to do the fixup myself.
      a8a50fce
    • Maarten Lankhorst's avatar
      drm/atomic: Clear crtc_state->active in drm_atomic_helper_set_config. · 9b5edbf7
      Maarten Lankhorst authored
      This fixes some regressions in i915 when converting to atomic.
      set_config failed with -EINVAL, and I received the following warning
      in dmesg:
      
      [drm:drm_atomic_crtc_check] [CRTC:20] active without enabled
      
      Solve this by clearing active when a crtc is disabled.
      
      Because crtc_state->enable implies that connectors are active the
      change from disabled->enabled can only happen for the crtc that's
      being set_config'd, and checking for !crtc_state->enable is sufficient
      here.
      
      Cc: dri-devel@lists.freedesktop.org
      Reviewed-by: default avatarRob Clark <robdclark@gmail.com>
      Signed-off-by: default avatarMaarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      9b5edbf7
    • Dave Airlie's avatar
      Merge tag 'topic/drm-misc-2015-05-27' of git://anongit.freedesktop.org/drm-intel into drm-next · 531e63e1
      Dave Airlie authored
      One more round of drm-misc, again mostly atomic. Big thing is the
      userspace blob code from Daniel Stone, with support for the mode_id blob
      now added to the atomic ioctl. Finally we can do atomic modesets!
      
      Note that the atomic ioctl is still behind the module knob since the
      weston patches aren't quite ready yet imo - they lack TEST_ONLY support,
      which is a fairly crucial bit of the atomic api. But besides that I think
      it's all good to go. That's also why we didn't bother to hide the new blob
      ioctls behind the knob, that part won't need to change. And if weston
      patches get in shape in time we could throw the "atomic by default patch"
      on top for 4.2.
      
      * tag 'topic/drm-misc-2015-05-27' of git://anongit.freedesktop.org/drm-intel:
        drm: Fix off-by-one in vblank hardware counter wraparound handling
        drm/atomic: fix out of bounds read in for_each_*_in_state helpers
        drm/atomic: Add MODE_ID property
        drm/atomic: Add current-mode blob to CRTC state
        drm: Add drm_atomic_set_mode_for_crtc
        drm: check for garbage in unused addfb2 fields
        drm: Retain reference to blob properties in lookup
        drm/mode: Add user blob-creation ioctl
        drm: Return error value from blob creation
        drm: Allow creating blob properties without copy
        drm/mode: Unstatic kernel-userspace mode conversion
        drm/mode: Validate modes inside drm_crtc_convert_umode
        drm/crtc_helper: Replace open-coded CRTC state helpers
        drm: kerneldoc fixes for blob properties
        drm/DocBook: Add more drm_bridge documentation
        drm: bridge: Allow daisy chaining of bridges
        drm/atomic: add all affected planes in drm_atomic_helper_check_modeset
        drm/atomic: add drm_atomic_add_affected_planes
        drm/atomic: add commit_planes_on_crtc helper
      531e63e1
    • Dave Airlie's avatar
      Merge tag 'drm-amdkfd-next-2015-06-03' of git://people.freedesktop.org/~gabbayo/linux into drm-next · cb2d47a4
      Dave Airlie authored
      drm-amdkfd-next-2015-06-03:
      
      - Add the H/W debugger support module, including new IOCTLs to:
        - register/unregister a process as a debugged process
        - Set address watch-point in the debugged process's GPU kernel
        - Do a wave control operation in the debugged process's waves
        See the commit messages for more details on the available operations.
      
        The debugged process can only perform debug operation on itself. It is
        blocked by the amdkfd+H/W from performing operations on other processes's
        waves or GPU kernels. The blocking is done by setting the VMID and PASID of
        the debugged process in the packets that are sent to the CP with the debug
        instructions.
      
      - Add support for static user-mode queues. These queues are regular queues,
        but because they belong to the debugged process, we need to make sure the CP
        doesn't preempt them during a debug operation. Therefore, we mark them as
        static for the CP ignore them during preemption.
      
      - Support killing all the waves when a process is terminated. This is needed
        in case a process is terminated but we can't UNMAP its queues (can occur due
        to several reasons). In that case, the CP could be stuck unless we kill all
        its waves. This function is *very* important as it provides the kernel a high
        level of control over the GPU. The reason we didn't upstream this function
        so far, is because it is implemented using the H/W debugger module functions,
        so we had to wait until we can upstream the H/W debugger module.
      
      - Replace declaration of bitmap from unsigned long to standard DECLARE_BITMAP
      
      * tag 'drm-amdkfd-next-2015-06-03' of git://people.freedesktop.org/~gabbayo/linux:
        drm/amdkfd: Enforce kill all waves on process termination
        drm/radeon: Add ATC VMID<-->PASID functions to kfd->kgd
        drm/amdkfd: Implement address watch debugger IOCTL
        drm/amdkfd: Implement wave control debugger IOCTL
        drm/amdkfd: Implement (un)register debugger IOCTLs
        drm/amdkfd: Add address watch operation to debugger
        drm/amdkfd: Add wave control operation to debugger
        drm/amdkfd: Add skeleton H/W debugger module support
        drm/amdkfd: Add static user-mode queues support
        drm/amdkfd: add H/W debugger IOCTL set definitions
        drm/radeon: Add H/W debugger kfd->kgd functions
        drm/amdkfd: Use DECLARE_BITMAP
      cb2d47a4
    • Gerd Hoffmann's avatar
      Add MAINTAINERS entry for virtio-gpu. · 4ad6ee91
      Gerd Hoffmann authored
      Signed-off-by: default avatarGerd Hoffmann <kraxel@redhat.com>
      4ad6ee91
    • Dave Airlie's avatar
      Add virtio gpu driver. · dc5698e8
      Dave Airlie authored
      This patch adds a kms driver for the virtio gpu.  The xorg modesetting
      driver can handle the device just fine, the framebuffer for fbcon is
      there too.
      
      Qemu patches for the host side are under review currently.
      
      The pci version of the device comes in two variants: with and without
      vga compatibility.  The former has a extra memory bar for the vga
      framebuffer, the later is a pure virtio device.  The only concern for
      this driver is that in the virtio-vga case we have to kick out the
      firmware framebuffer.
      
      Initial revision has only 2d support, 3d (virgl) support requires
      some more work on the qemu side and will be added later.
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      Signed-off-by: default avatarGerd Hoffmann <kraxel@redhat.com>
      Acked-by: default avatarMichael S. Tsirkin <mst@redhat.com>
      dc5698e8
    • Ben Goz's avatar
      drm/amdkfd: Enforce kill all waves on process termination · c3447e81
      Ben Goz authored
      This commit makes sure that on process termination, after
      we're destroying all the active queues, we're killing all the
      existing wave front of the current process.
      
      By doing this we're making sure that if any of the CUs were blocked
      by infinite loop we're enforcing it to end the shader explicitly.
      Signed-off-by: default avatarBen Goz <ben.goz@amd.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      c3447e81
    • Alexey Skidanov's avatar
      drm/radeon: Add ATC VMID<-->PASID functions to kfd->kgd · edad4023
      Alexey Skidanov authored
      This patch adds three new interfaces to kfd2kgd interface file of radeon.
      
      The interfaces are:
      
      - Check if a specific VMID has a valid PASID mapping
      - Retrieve the PASID which is mapped to a specific VMID
      - Issue a VMID invalidation request to the ATC
      Signed-off-by: default avatarAlexey Skidanov <Alexey.Skidanov@amd.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      edad4023
    • Yair Shachar's avatar
      drm/amdkfd: Implement address watch debugger IOCTL · f8bd1333
      Yair Shachar authored
      v2:
      
      - rename get_dbgmgr_mutex to kfd_get_dbgmgr_mutex to namespace it
      - change void* to uint64_t inside ioctl arguments
      - use kmalloc instead of kzalloc because we use copy_from_user
        immediately after it
      Signed-off-by: default avatarYair Shachar <yair.shachar@amd.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      f8bd1333
    • Yair Shachar's avatar
      drm/amdkfd: Implement wave control debugger IOCTL · 94484589
      Yair Shachar authored
      v2:
      
      - rename get_dbgmgr_mutex to kfd_get_dbgmgr_mutex to namespace it
      - change void* to uint64_t inside ioctl arguments
      - use kmalloc instead of kzalloc because we use copy_from_user
        immediately after it
      Signed-off-by: default avatarYair Shachar <yair.shachar@amd.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      94484589
    • Yair Shachar's avatar
      drm/amdkfd: Implement (un)register debugger IOCTLs · 037ed9a2
      Yair Shachar authored
      v2: rename get_dbgmgr_mutex to kfd_get_dbgmgr_mutex to namespace it
      Signed-off-by: default avatarYair Shachar <yair.shachar@amd.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      037ed9a2
    • Yair Shachar's avatar
      drm/amdkfd: Add address watch operation to debugger · e2e9afc4
      Yair Shachar authored
      The address watch operation gives the ability to specify watch points
      which will generate a shader breakpoint, based on a specified single
      address or range of addresses.
      
      There is support for read/write/any access modes.
      Signed-off-by: default avatarYair Shachar <yair.shachar@amd.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      e2e9afc4
    • Yair Shachar's avatar
      drm/amdkfd: Add wave control operation to debugger · 788bf83d
      Yair Shachar authored
      The wave control operation supports several command types executed upon
      existing wave fronts that belong to the currently debugged process.
      
      The available commands are:
      
      HALT   - Freeze wave front(s) execution
      RESUME - Resume freezed wave front(s) execution
      KILL   - Kill existing wave front(s)
      Signed-off-by: default avatarYair Shachar <yair.shachar@amd.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      788bf83d
    • Yair Shachar's avatar
      drm/amdkfd: Add skeleton H/W debugger module support · fbeb661b
      Yair Shachar authored
      This patch adds the skeleton H/W debugger module support. This code
      enables registration and unregistration of a single HSA process at a
      time.
      
      The module saves the process's pasid and use it to verify that only the
      registered process is allowed to execute debugger operations through the
      kernel driver.
      
      v2: rename get_dbgmgr_mutex to kfd_get_dbgmgr_mutex to namespace it
      Signed-off-by: default avatarYair Shachar <yair.shachar@amd.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      fbeb661b
    • Yair Shachar's avatar
      drm/amdkfd: Add static user-mode queues support · 992839ad
      Yair Shachar authored
      This patch adds support for static user-mode queues in QCM.
      Queues which are designated as static can NOT be preempted by
      the CP microcode when it is executing its scheduling algorithm.
      
      This is needed for supporting the debugger feature, because we
      can't allow the CP to preempt queues which are currently being debugged.
      
      The number of queues that can be designated as static is limited by the
      number of HQDs (Hardware Queue Descriptors).
      Signed-off-by: default avatarYair Shachar <yair.shachar@amd.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      992839ad
    • Yair Shachar's avatar
      drm/amdkfd: add H/W debugger IOCTL set definitions · aef11009
      Yair Shachar authored
      This patch adds four new IOCTLs to amdkfd. These IOCTLs expose a H/W
      debugger functionality to the userspace.
      
      The IOCTLs are:
      
      - AMDKFD_IOC_DBG_REGISTER:
      
      The purpose of this IOCTL is to notify amdkfd that a process wants to use
      GPU debugging facilities on itself only.
      It is expected that this IOCTL would be called before any other H/W
      debugger requests are sent to amdkfd and for each GPU where the H/W
      debugging needs to be enabled. The use of this IOCTL ensures that only
      one instance of a debugger is active in the system.
      
      - AMDKFD_IOC_DBG_UNREGISTER:
      
      This IOCTL detaches the debugger/debugged process from the H/W
      Debug which was established by the AMDKFD_IOC_DBG_REGISTER IOCTL.
      
      - AMDKFD_IOC_DBG_ADDRESS_WATCH:
      
      This IOCTL allows to set different watchpoints with various conditions as
      indicated by the IOCTL's arguments. The available number of watchpoints
      is retrieved from topology. This operation is confined to the current
      debugged process, which was registered through AMDKFD_IOC_DBG_REGISTER.
      
      - AMDKFD_IOC_DBG_WAVE_CONTROL:
      
      This IOCTL allows to control a wavefront as indicated by the IOCTL's
      arguments. For example, you can halt/resume or kill either a
      single wavefront or a set of wavefronts. This operation is confined to
      the current debugged process, which was registered through
      AMDKFD_IOC_DBG_REGISTER.
      
      Because the arguments for the address watch IOCTL and wave control IOCTL
      are dynamic, meaning that they could vary in size, the userspace passes a
      pointer to a structure (in userspace) that contains the value of the
      arguments. The kernel driver is responsible to parse this structure and
      validate its contents.
      
      v2: change void* to uint64_t inside ioctl arguments
      Signed-off-by: default avatarYair Shachar <yair.shachar@amd.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      aef11009
    • Yair Shachar's avatar
      drm/radeon: Add H/W debugger kfd->kgd functions · a6186f4d
      Yair Shachar authored
      This patch adds new interface functions to the kfd2kgd interface file. The
      new functions allow to perform H/W debugger operations by writing to GPU
      registers.
      Signed-off-by: default avatarYair Shachar <yair.shachar@amd.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      a6186f4d
    • Joe Perches's avatar
      drm/amdkfd: Use DECLARE_BITMAP · f761d8bd
      Joe Perches authored
      Use the generic mechanism to declare a bitmap instead of unsigned long.
      
      It seems that "struct kfd_process.allocated_queue_bitmap" is unused.
      Maybe it could be deleted instead.
      Signed-off-by: default avatarJoe Perches <joe@perches.com>
      Signed-off-by: default avatarOded Gabbay <oded.gabbay@gmail.com>
      f761d8bd
  3. 02 Jun, 2015 3 commits
    • Gerd Hoffmann's avatar
    • Gerd Hoffmann's avatar
      break kconfig dependency loop · 06b718c0
      Gerd Hoffmann authored
      After adding virtio-gpu I get this funky kconfig dependency loop.
      
      scripts/kconfig/conf --oldconfig Kconfig
      drivers/video/fbdev/Kconfig:5:error: recursive dependency detected!
      drivers/video/fbdev/Kconfig:5:  symbol FB is selected by DRM_KMS_FB_HELPER
      drivers/gpu/drm/Kconfig:34:     symbol DRM_KMS_FB_HELPER is selected by DRM_VIRTIO_GPU
      drivers/gpu/drm/virtio/Kconfig:1:       symbol DRM_VIRTIO_GPU depends on VIRTIO
      drivers/virtio/Kconfig:1:       symbol VIRTIO is selected by REMOTEPROC
      drivers/remoteproc/Kconfig:4:   symbol REMOTEPROC is selected by OMAP_REMOTEPROC
      drivers/remoteproc/Kconfig:12:  symbol OMAP_REMOTEPROC depends on OMAP_IOMMU
      drivers/iommu/Kconfig:141:      symbol OMAP_IOMMU is selected by VIDEO_OMAP3
      drivers/media/platform/Kconfig:96:      symbol VIDEO_OMAP3 depends on VIDEO_V4L2
      drivers/media/v4l2-core/Kconfig:6:      symbol VIDEO_V4L2 depends on I2C
      drivers/i2c/Kconfig:7:  symbol I2C is selected by FB_DDC
      drivers/video/fbdev/Kconfig:59: symbol FB_DDC is selected by FB_CYBER2000_DDC
      drivers/video/fbdev/Kconfig:374:        symbol FB_CYBER2000_DDC depends on FB_CYBER2000
      drivers/video/fbdev/Kconfig:362:        symbol FB_CYBER2000 depends on FB
      
      Making VIDEO_OMAP3 depend on OMAP_IOMMU instead of selecting it breaks the
      loop, which looks like the best way to handle it to me.  Updated OMAP_IOMMU
      help text accordingly.
      Signed-off-by: default avatarGerd Hoffmann <kraxel@redhat.com>
      Acked-by: default avatarMauro Carvalho Chehab <mchehab@osg.samsung.com>
      06b718c0
    • Dave Airlie's avatar
      Merge tag 'drm-intel-next-fixes-2015-05-29' of... · 3e8d222f
      Dave Airlie authored
      Merge tag 'drm-intel-next-fixes-2015-05-29' of git://anongit.freedesktop.org/drm-intel into drm-next
      
      Fixes for 4.2. Nothing too serious (given that it's still pre merge
      window). With that it's off for 2 weeks of vacation for me and taking care
      of 4.2 fixes for Jani.
      
      * tag 'drm-intel-next-fixes-2015-05-29' of git://anongit.freedesktop.org/drm-intel:
        drm/i915: limit PPGTT size to 2GB in 32-bit platforms
        drm/i915: Another fbdev hack to avoid PSR on fbcon.
        drm/i915: Return the frontbuffer flip to enable intel_crtc_enable_planes.
        drm/i915: disable IPS while getting the sink CRCs
        drm/i915: Disable 12bpc hdmi for now
        drm/i915: Adjust sideband locking a bit for CHV/VLV
        drm/i915: s/dpio_lock/sb_lock/
        drm/i915: Kill intel_flush_primary_plane()
        drm/i915: Throw out WIP CHV power well definitions
        drm/i915: Use the default 600ns LDO programming sequence delay
        drm/i915: Remove unnecessary null check in execlists_context_unqueue
        drm/i915: Use spinlocks for checking when to waitboost
        drm/i915: Fix the confusing comment about the ioctl limits
        Revert "drm/i915: Force clean compilation with -Werror"
      3e8d222f