user space client interface driver
Subsystems (2)
PATCH 1/3 bus: mhi: core: Add helper API to return number of free TREs
In reply to Hemant KumarIntroduce mhi_get_no_free_descriptors() API to return number of TREs available to queue buffer. MHI clients can use this API to know before hand if ring is full without calling queue API.
--- drivers/bus/mhi/core/main.c | 12 ++++++++++++ include/linux/mhi.h | 9 +++++++++ 2 files changed, 21 insertions(+)
drivers/bus/mhi/core/main.c +12 -0
@@ -294,6 +294,18 @@ int mhi_destroy_device(struct device *dev, void *data)return 0 ; } +int mhi_get_no_free_descriptors (struct mhi_device *mhi_dev, +enum dma_data_direction dir) +{ +struct mhi_controller *mhi_cntrl = mhi_dev->mhi_cntrl; +struct mhi_chan *mhi_chan = (dir ==DMA_TO_DEVICE ) ? + mhi_dev->ul_chan : mhi_dev->dl_chan; +struct mhi_ring *tre_ring = &mhi_chan->tre_ring; + +return get_nr_avail_ring_elements (mhi_cntrl, tre_ring); +} +EXPORT_SYMBOL_GPL (mhi_get_no_free_descriptors); +void mhi_notify (struct mhi_device *mhi_dev,enum mhi_callback cb_reason) {struct mhi_driver *mhi_drv;
include/linux/mhi.h +9 -0
@@ -620,6 +620,15 @@ void mhi_set_mhi_state(struct mhi_controller *mhi_cntrl,void mhi_notify (struct mhi_device *mhi_dev,enum mhi_callback cb_reason);/** +* mhi_get_no_free_descriptors - Get transfer ring length +* Get # of TD available to queue buffers +* @mhi_dev: Device associated with the channels +* @dir: Direction of the channel +*/ +int mhi_get_no_free_descriptors (struct mhi_device *mhi_dev, +enum dma_data_direction dir); + +/** * mhi_prepare_for_power_up - Do pre-initialization before power up. * This is optional, call this before power up if * the controller does not want bus framework to
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
PATCH 2/3 bus: mhi: core: Move MHI_MAX_MTU to external header file
In reply to Hemant KumarCurrently this macro is defined in internal MHI header as a TRE length mask. Moving it to external header allows MHI client drivers to set this upper bound for the transmit buffer size.
--- drivers/bus/mhi/core/internal.h | 1 - include/linux/mhi.h | 3 +++ 2 files changed, 3 insertions(+), 1 deletion(-)
drivers/bus/mhi/core/internal.h +0 -1
@@ -490,7 +490,6 @@ enum mhi_pm_state {#define PRIMARY_CMD_RING 0#define MHI_BW_SCALE_CHAN_DB 126#define MHI_DEV_WAKE_DB 127 -#define MHI_MAX_MTU 0xffff#define MHI_RANDOM_U32_NONZERO (bmsk) (prandom_u32_max(bmsk) + 1)#define MHI_BW_SCALE_SETUP (er_index) (((MHI_BW_SCALE_CHAN_DB << \
include/linux/mhi.h +3 -0
@@ -16,6 +16,9 @@#include <linux/wait.h> #include <linux/workqueue.h> +/* MHI client drivers to set this upper bound for tx buffer */ +#define MHI_MAX_MTU 0xffff +#define MHI_VOTE_BUS BIT(0)/* do not disable the mhi bus */ #define MHI_VOTE_DEVICE BIT(1)/* prevent mhi device from entering lpm */
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
cover user space client interface driver
MHI based uci driver is for transferring data between host and device using standard file operations from user space. Open, read, write, and close operations are supported by this driver. Currently LOOPBACK channel is supported.
Hemant Kumar (3):
bus: mhi: core: Add helper API to return number of free TREs
bus: mhi: core: Move MHI_MAX_MTU to external header file
bus: mhi: clients: Add user space client interface driver
drivers/bus/mhi/Kconfig | 2 + drivers/bus/mhi/Makefile | 1 + drivers/bus/mhi/clients/Kconfig | 16 + drivers/bus/mhi/clients/Makefile | 3 + drivers/bus/mhi/clients/uci.c | 653 +++++++++++++++++++++++++++++++++++++++ drivers/bus/mhi/core/internal.h | 1 - drivers/bus/mhi/core/main.c | 12 + include/linux/mhi.h | 12 + 8 files changed, 699 insertions(+), 1 deletion(-) create mode 100644 drivers/bus/mhi/clients/Kconfig create mode 100644 drivers/bus/mhi/clients/Makefile create mode 100644 drivers/bus/mhi/clients/uci.c
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
PATCH 3/3 bus: mhi: clients: Add user space client interface driver
This MHI client driver allows user space clients to transfer data between MHI device and host using standard file operations. Device file node is created with format
/dev/mhi_<controller_name>_<mhi_device_name>
Currently it supports loopback client.
--- drivers/bus/mhi/Kconfig | 2 + drivers/bus/mhi/Makefile | 1 + drivers/bus/mhi/clients/Kconfig | 16 + drivers/bus/mhi/clients/Makefile | 3 + drivers/bus/mhi/clients/uci.c | 653 +++++++++++++++++++++++++++++++++++++++ 5 files changed, 675 insertions(+) create mode 100644 drivers/bus/mhi/clients/Kconfig create mode 100644 drivers/bus/mhi/clients/Makefile create mode 100644 drivers/bus/mhi/clients/uci.c
drivers/bus/mhi/Kconfig +2 -0
@@ -20,3 +20,5 @@ config MHI_BUS_DEBUG Enable debugfs support for use with the MHI transport. Allows reading and/or modifying some values within the MHI controller for debug and test purposes. + +source "drivers/bus/mhi/clients/Kconfig"
drivers/bus/mhi/Makefile +1 -0
@@ -1,2 +1,3 @@ # core layer obj-y += core/ +obj-y += clients/
drivers/bus/mhi/clients/Kconfig new file +16 -0
@@ -0,0 +1,16 @@ +# SPDX-License-Identifier: GPL-2.0-only + +menu "MHI clients support" + depends on MHI_BUS + +config MHI_UCI + tristate "MHI UCI" + depends on MHI_BUS + help + MHI based userspace client interface driver is for transferring + data between host and device using standard file operations from + user space. Open, read, write, and close operations are supported + by this driver. Please check mhi_uci_match_table for all supported + channels that are exposed to userspace. + +endmenu
drivers/bus/mhi/clients/Makefile new file +3 -0
@@ -0,0 +1,3 @@ +# SPDX-License-Identifier: GPL-2.0-only + +obj-$(CONFIG_MHI_UCI) +=uci.o
drivers/bus/mhi/clients/uci.c new file +653 -0
653 lines not on this page · raw message
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
Re: [PATCH v1 3/3] bus: mhi: clients: Add user space client interface driver
Quoted 58 lines · Hemant Kumar
drivers/bus/mhi/clients/uci.c new file +58
-0+static ssize_t mhi_uci_read (struct file *file, +char __user *buf, +size_t count, +loff_t *ppos) +{ +struct uci_dev *uci_dev = file->private_data; +struct mhi_device *mhi_dev = uci_dev->mhi_dev; +struct uci_chan *uci_chan = &uci_dev->dl_chan; +struct device *dev = &mhi_dev->dev; +struct uci_buf *uci_buf; +char *ptr; +size_t to_copy; +int ret =0 ; + +if (!buf) +return -EINVAL ; + +dev_dbg (dev,"Client provided buf len:%lu\n" , count); + +/* confirm channel is active */ +spin_lock_bh (&uci_chan->lock); +if (!uci_dev->enabled) { +spin_unlock_bh (&uci_chan->lock); +return -ERESTARTSYS ; + } + +/* No data available to read, wait */ +if (!uci_chan->cur_buf &&list_empty (&uci_chan->pending)) { +dev_dbg (dev,"No data available to read waiting\n" ); + +spin_unlock_bh (&uci_chan->lock); + ret =wait_event_interruptible (uci_chan->wq, + (!uci_dev->enabled || + !list_empty (&uci_chan->pending))); +if (ret == -ERESTARTSYS ) { +dev_dbg (dev,"Exit signal caught for node\n" ); +return -ERESTARTSYS ; + } + +spin_lock_bh (&uci_chan->lock); +if (!uci_dev->enabled) { +dev_dbg (dev,"node is disabled\n" ); + ret = -ERESTARTSYS ; + goto read_error; + } + } + +/* new read, get the next descriptor from the list */ +if (!uci_chan->cur_buf) { + uci_buf =list_first_entry_or_null (&uci_chan->pending, + struct uci_buf, node); +if (unlikely (!uci_buf)) { + ret = -EIO ; + goto read_error; + } + +list_del (&uci_buf->node); + uci_chan->cur_buf = uci_buf;
drivers/bus/mhi/clients/uci.c line 331
Quoted 10 lines
drivers/bus/mhi/clients/uci.c new file +10
-0+ uci_chan->rx_size = uci_buf->len; +dev_dbg (dev,"Got pkt of size:%zu\n" , uci_chan->rx_size); + } + + uci_buf = uci_chan->cur_buf; + +/* Copy the buffer to user space */ + to_copy =min_t (size_t, count, uci_chan->rx_size); + ptr = uci_buf->data + (uci_buf->len - uci_chan->rx_size); +spin_unlock_bh (&uci_chan->lock);
This presents a race condition. Imagine if you will, two processes are in read() at the same time. They will be contending for the lock. One will win, and enter the above critical section. As soon as the winner gets here and unlocks the lock, the loser will get the lock and enter the critical section. There is a possibility that both processes get to this point at roughly the same time, and thus both have a cached version of the identical cur_buf pointer. At this point, bad things can happen.
If both processes consume the entire buffer, they will then both re-queue the buffer to MHI. You then can cause memory corruption, and a kernel crash if the buffer is consumed, then freed, then the memory is allocated to somewhere else in the kernel, then MHI consumed the buffer again (memory corruption). If the buffer gets freed again, slub may trigger a BUG_ON if the allocation for elsewhere is completely different in structure.
I think you need a mutex covering the entire read() operation to serialize it.
Quoted 46 lines
drivers/bus/mhi/clients/uci.c new file +46
-0+ + ret =copy_to_user (buf, ptr, to_copy); +if (ret) +return ret; + +spin_lock_bh (&uci_chan->lock); + +/* Buffer already queued from diff thread while we dropped lock */ +if (to_copy && !uci_chan->rx_size) { +dev_dbg (dev,"Bailout as buffer already queued (%lu %lu)\n" , + to_copy, uci_chan->rx_size); + goto read_error; + } + +dev_dbg (dev,"Copied %lu of %lu bytes\n" , to_copy, uci_chan->rx_size); + uci_chan->rx_size -= to_copy; + +/* we finished with this buffer, queue it back to hardware */ +if (!uci_chan->rx_size) { + uci_chan->cur_buf =NULL ; + +if (uci_dev->enabled) + ret =mhi_queue_buf (mhi_dev,DMA_FROM_DEVICE , + uci_buf->data, + uci_dev->actual_mtu,MHI_EOT ); +else + ret = -ERESTARTSYS ; + +if (ret) { +dev_err (dev,"Failed to recycle element\n" ); +kfree (uci_buf->data); + goto read_error; + } + } +spin_unlock_bh (&uci_chan->lock); + +dev_dbg (dev,"Returning %lu bytes\n" , to_copy); + +return to_copy; + +read_error: +spin_unlock_bh (&uci_chan->lock); + +return ret; +} +
Signature · 3 lines
Jeffrey Hugo Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.