summaryrefslogtreecommitdiff
path: root/drivers/dma/Makefile
diff options
context:
space:
mode:
authorDave Jiang <dave.jiang@intel.com>2021-07-15 21:44:35 +0300
committerVinod Koul <vkoul@kernel.org>2021-07-21 07:39:16 +0300
commit448c3de8ac8353fc4447738ae3c56c4eb6c2131d (patch)
tree1e22d8ca26055024fc5204a85e85875c49136eed /drivers/dma/Makefile
parent0cda4f6986a3824cac500f66326ff267bf37110f (diff)
downloadlinux-448c3de8ac8353fc4447738ae3c56c4eb6c2131d.tar.xz
dmaengine: idxd: create user driver for wq 'device'
The original architecture of /sys/bus/dsa invented a scheme whereby a single entry in the list of bus drivers, /sys/bus/drivers/dsa, handled all device types and internally routed them to different drivers. Those internal drivers were invisible to userspace. Now, as /sys/bus/dsa wants to grow support for alternate drivers for a given device, for example vfio-mdev instead of kernel-internal-dmaengine, a proper bus device-driver model is needed. The first step in that process is separating the existing omnibus/implicit "dsa" driver into proper individual drivers registered on /sys/bus/dsa. Establish the idxd_user_drv driver that controls the enabling and disabling of the wq and also register and unregister a char device to allow user space to mmap the descriptor submission portal. The cdev related bits are moved to the cdev driver probe/remove and out of the drv_enabe/disable_wq() calls. These bits are exclusive to the cdev operation and not part of the generic enable/disable of the wq device. Reviewed-by: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Dave Jiang <dave.jiang@intel.com> Link: https://lore.kernel.org/r/162637467578.744545.10203997610072341376.stgit@djiang5-desk3.ch.intel.com Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'drivers/dma/Makefile')
0 files changed, 0 insertions, 0 deletions