2018-05-31 20:11:03 +03:00
// SPDX-License-Identifier: GPL-2.0
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
/*
* Copyright ( c ) 2016 , Linaro Ltd .
* Copyright ( c ) 2012 , Michal Simek < monstr @ monstr . eu >
* Copyright ( c ) 2012 , PetaLogix
* Copyright ( c ) 2011 , Texas Instruments , Inc .
* Copyright ( c ) 2011 , Google , Inc .
*
* Based on rpmsg performance statistics driver by Michal Simek , which in turn
* was based on TI & Google OMX rpmsg driver .
*/
2021-11-08 16:59:45 +03:00
# define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
# include <linux/cdev.h>
# include <linux/device.h>
# include <linux/fs.h>
# include <linux/idr.h>
# include <linux/kernel.h>
# include <linux/module.h>
# include <linux/poll.h>
# include <linux/rpmsg.h>
# include <linux/skbuff.h>
# include <linux/slab.h>
# include <linux/uaccess.h>
# include <uapi/linux/rpmsg.h>
# define RPMSG_DEV_MAX (MINORMASK + 1)
static dev_t rpmsg_major ;
static struct class * rpmsg_class ;
static DEFINE_IDA ( rpmsg_ctrl_ida ) ;
static DEFINE_IDA ( rpmsg_ept_ida ) ;
static DEFINE_IDA ( rpmsg_minor_ida ) ;
# define dev_to_eptdev(dev) container_of(dev, struct rpmsg_eptdev, dev)
# define cdev_to_eptdev(i_cdev) container_of(i_cdev, struct rpmsg_eptdev, cdev)
# define dev_to_ctrldev(dev) container_of(dev, struct rpmsg_ctrldev, dev)
# define cdev_to_ctrldev(i_cdev) container_of(i_cdev, struct rpmsg_ctrldev, cdev)
/**
* struct rpmsg_ctrldev - control device for instantiating endpoint devices
* @ rpdev : underlaying rpmsg device
* @ cdev : cdev for the ctrl device
* @ dev : device for the ctrl device
*/
struct rpmsg_ctrldev {
struct rpmsg_device * rpdev ;
struct cdev cdev ;
struct device dev ;
} ;
/**
* struct rpmsg_eptdev - endpoint device context
* @ dev : endpoint device
* @ cdev : cdev for the endpoint device
* @ rpdev : underlaying rpmsg device
* @ chinfo : info used to open the endpoint
* @ ept_lock : synchronization of @ ept modifications
* @ ept : rpmsg endpoint reference , when open
* @ queue_lock : synchronization of @ queue operations
* @ queue : incoming message queue
* @ readq : wait object for incoming queue
*/
struct rpmsg_eptdev {
struct device dev ;
struct cdev cdev ;
struct rpmsg_device * rpdev ;
struct rpmsg_channel_info chinfo ;
struct mutex ept_lock ;
struct rpmsg_endpoint * ept ;
spinlock_t queue_lock ;
struct sk_buff_head queue ;
wait_queue_head_t readq ;
} ;
static int rpmsg_eptdev_destroy ( struct device * dev , void * data )
{
struct rpmsg_eptdev * eptdev = dev_to_eptdev ( dev ) ;
mutex_lock ( & eptdev - > ept_lock ) ;
if ( eptdev - > ept ) {
rpmsg_destroy_ept ( eptdev - > ept ) ;
eptdev - > ept = NULL ;
}
mutex_unlock ( & eptdev - > ept_lock ) ;
/* wake up any blocked readers */
wake_up_interruptible ( & eptdev - > readq ) ;
device_del ( & eptdev - > dev ) ;
put_device ( & eptdev - > dev ) ;
return 0 ;
}
static int rpmsg_ept_cb ( struct rpmsg_device * rpdev , void * buf , int len ,
void * priv , u32 addr )
{
struct rpmsg_eptdev * eptdev = priv ;
struct sk_buff * skb ;
skb = alloc_skb ( len , GFP_ATOMIC ) ;
if ( ! skb )
return - ENOMEM ;
networking: introduce and use skb_put_data()
A common pattern with skb_put() is to just want to memcpy()
some data into the new space, introduce skb_put_data() for
this.
An spatch similar to the one for skb_put_zero() converts many
of the places using it:
@@
identifier p, p2;
expression len, skb, data;
type t, t2;
@@
(
-p = skb_put(skb, len);
+p = skb_put_data(skb, data, len);
|
-p = (t)skb_put(skb, len);
+p = skb_put_data(skb, data, len);
)
(
p2 = (t2)p;
-memcpy(p2, data, len);
|
-memcpy(p, data, len);
)
@@
type t, t2;
identifier p, p2;
expression skb, data;
@@
t *p;
...
(
-p = skb_put(skb, sizeof(t));
+p = skb_put_data(skb, data, sizeof(t));
|
-p = (t *)skb_put(skb, sizeof(t));
+p = skb_put_data(skb, data, sizeof(t));
)
(
p2 = (t2)p;
-memcpy(p2, data, sizeof(*p));
|
-memcpy(p, data, sizeof(*p));
)
@@
expression skb, len, data;
@@
-memcpy(skb_put(skb, len), data, len);
+skb_put_data(skb, data, len);
(again, manually post-processed to retain some comments)
Reviewed-by: Stephen Hemminger <stephen@networkplumber.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-06-16 15:29:20 +03:00
skb_put_data ( skb , buf , len ) ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
spin_lock ( & eptdev - > queue_lock ) ;
skb_queue_tail ( & eptdev - > queue , skb ) ;
spin_unlock ( & eptdev - > queue_lock ) ;
/* wake up any blocking processes, waiting for new data */
wake_up_interruptible ( & eptdev - > readq ) ;
return 0 ;
}
static int rpmsg_eptdev_open ( struct inode * inode , struct file * filp )
{
struct rpmsg_eptdev * eptdev = cdev_to_eptdev ( inode - > i_cdev ) ;
struct rpmsg_endpoint * ept ;
struct rpmsg_device * rpdev = eptdev - > rpdev ;
struct device * dev = & eptdev - > dev ;
2021-03-11 17:04:13 +03:00
if ( eptdev - > ept )
return - EBUSY ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
get_device ( dev ) ;
ept = rpmsg_create_ept ( rpdev , rpmsg_ept_cb , eptdev , eptdev - > chinfo ) ;
if ( ! ept ) {
dev_err ( dev , " failed to open %s \n " , eptdev - > chinfo . name ) ;
put_device ( dev ) ;
return - EINVAL ;
}
eptdev - > ept = ept ;
filp - > private_data = eptdev ;
return 0 ;
}
static int rpmsg_eptdev_release ( struct inode * inode , struct file * filp )
{
struct rpmsg_eptdev * eptdev = cdev_to_eptdev ( inode - > i_cdev ) ;
struct device * dev = & eptdev - > dev ;
/* Close the endpoint, if it's not already destroyed by the parent */
mutex_lock ( & eptdev - > ept_lock ) ;
if ( eptdev - > ept ) {
rpmsg_destroy_ept ( eptdev - > ept ) ;
eptdev - > ept = NULL ;
}
mutex_unlock ( & eptdev - > ept_lock ) ;
/* Discard all SKBs */
2019-10-29 09:09:14 +03:00
skb_queue_purge ( & eptdev - > queue ) ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
put_device ( dev ) ;
return 0 ;
}
2018-08-07 10:14:24 +03:00
static ssize_t rpmsg_eptdev_read_iter ( struct kiocb * iocb , struct iov_iter * to )
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
{
2018-08-07 10:14:24 +03:00
struct file * filp = iocb - > ki_filp ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
struct rpmsg_eptdev * eptdev = filp - > private_data ;
unsigned long flags ;
struct sk_buff * skb ;
int use ;
if ( ! eptdev - > ept )
return - EPIPE ;
spin_lock_irqsave ( & eptdev - > queue_lock , flags ) ;
/* Wait for data in the queue */
if ( skb_queue_empty ( & eptdev - > queue ) ) {
spin_unlock_irqrestore ( & eptdev - > queue_lock , flags ) ;
if ( filp - > f_flags & O_NONBLOCK )
return - EAGAIN ;
/* Wait until we get data or the endpoint goes away */
if ( wait_event_interruptible ( eptdev - > readq ,
! skb_queue_empty ( & eptdev - > queue ) | |
! eptdev - > ept ) )
return - ERESTARTSYS ;
/* We lost the endpoint while waiting */
if ( ! eptdev - > ept )
return - EPIPE ;
spin_lock_irqsave ( & eptdev - > queue_lock , flags ) ;
}
skb = skb_dequeue ( & eptdev - > queue ) ;
2017-01-21 07:53:40 +03:00
spin_unlock_irqrestore ( & eptdev - > queue_lock , flags ) ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
if ( ! skb )
return - EFAULT ;
2018-08-07 10:14:24 +03:00
use = min_t ( size_t , iov_iter_count ( to ) , skb - > len ) ;
if ( copy_to_iter ( skb - > data , use , to ) ! = use )
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
use = - EFAULT ;
kfree_skb ( skb ) ;
return use ;
}
2018-08-07 10:14:24 +03:00
static ssize_t rpmsg_eptdev_write_iter ( struct kiocb * iocb ,
struct iov_iter * from )
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
{
2018-08-07 10:14:24 +03:00
struct file * filp = iocb - > ki_filp ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
struct rpmsg_eptdev * eptdev = filp - > private_data ;
2018-08-07 10:14:24 +03:00
size_t len = iov_iter_count ( from ) ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
void * kbuf ;
int ret ;
2018-08-07 10:14:24 +03:00
kbuf = kzalloc ( len , GFP_KERNEL ) ;
if ( ! kbuf )
return - ENOMEM ;
2019-09-17 06:31:23 +03:00
if ( ! copy_from_iter_full ( kbuf , len , from ) ) {
ret = - EFAULT ;
goto free_kbuf ;
}
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
if ( mutex_lock_interruptible ( & eptdev - > ept_lock ) ) {
ret = - ERESTARTSYS ;
goto free_kbuf ;
}
if ( ! eptdev - > ept ) {
ret = - EPIPE ;
goto unlock_eptdev ;
}
if ( filp - > f_flags & O_NONBLOCK )
2021-03-11 17:04:11 +03:00
ret = rpmsg_trysendto ( eptdev - > ept , kbuf , len , eptdev - > chinfo . dst ) ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
else
2021-03-11 17:04:11 +03:00
ret = rpmsg_sendto ( eptdev - > ept , kbuf , len , eptdev - > chinfo . dst ) ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
unlock_eptdev :
mutex_unlock ( & eptdev - > ept_lock ) ;
free_kbuf :
kfree ( kbuf ) ;
return ret < 0 ? ret : len ;
}
2017-07-03 13:39:46 +03:00
static __poll_t rpmsg_eptdev_poll ( struct file * filp , poll_table * wait )
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
{
struct rpmsg_eptdev * eptdev = filp - > private_data ;
2017-07-03 13:39:46 +03:00
__poll_t mask = 0 ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
if ( ! eptdev - > ept )
2018-02-12 01:34:03 +03:00
return EPOLLERR ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
poll_wait ( filp , & eptdev - > readq , wait ) ;
if ( ! skb_queue_empty ( & eptdev - > queue ) )
2018-02-12 01:34:03 +03:00
mask | = EPOLLIN | EPOLLRDNORM ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
mask | = rpmsg_poll ( eptdev - > ept , filp , wait ) ;
return mask ;
}
static long rpmsg_eptdev_ioctl ( struct file * fp , unsigned int cmd ,
unsigned long arg )
{
struct rpmsg_eptdev * eptdev = fp - > private_data ;
if ( cmd ! = RPMSG_DESTROY_EPT_IOCTL )
return - EINVAL ;
return rpmsg_eptdev_destroy ( & eptdev - > dev , NULL ) ;
}
static const struct file_operations rpmsg_eptdev_fops = {
. owner = THIS_MODULE ,
. open = rpmsg_eptdev_open ,
. release = rpmsg_eptdev_release ,
2018-08-07 10:14:24 +03:00
. read_iter = rpmsg_eptdev_read_iter ,
. write_iter = rpmsg_eptdev_write_iter ,
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
. poll = rpmsg_eptdev_poll ,
. unlocked_ioctl = rpmsg_eptdev_ioctl ,
2018-09-11 22:59:08 +03:00
. compat_ioctl = compat_ptr_ioctl ,
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
} ;
static ssize_t name_show ( struct device * dev , struct device_attribute * attr ,
char * buf )
{
struct rpmsg_eptdev * eptdev = dev_get_drvdata ( dev ) ;
return sprintf ( buf , " %s \n " , eptdev - > chinfo . name ) ;
}
static DEVICE_ATTR_RO ( name ) ;
static ssize_t src_show ( struct device * dev , struct device_attribute * attr ,
char * buf )
{
struct rpmsg_eptdev * eptdev = dev_get_drvdata ( dev ) ;
return sprintf ( buf , " %d \n " , eptdev - > chinfo . src ) ;
}
static DEVICE_ATTR_RO ( src ) ;
static ssize_t dst_show ( struct device * dev , struct device_attribute * attr ,
char * buf )
{
struct rpmsg_eptdev * eptdev = dev_get_drvdata ( dev ) ;
return sprintf ( buf , " %d \n " , eptdev - > chinfo . dst ) ;
}
static DEVICE_ATTR_RO ( dst ) ;
static struct attribute * rpmsg_eptdev_attrs [ ] = {
& dev_attr_name . attr ,
& dev_attr_src . attr ,
& dev_attr_dst . attr ,
NULL
} ;
ATTRIBUTE_GROUPS ( rpmsg_eptdev ) ;
static void rpmsg_eptdev_release_device ( struct device * dev )
{
struct rpmsg_eptdev * eptdev = dev_to_eptdev ( dev ) ;
ida_simple_remove ( & rpmsg_ept_ida , dev - > id ) ;
ida_simple_remove ( & rpmsg_minor_ida , MINOR ( eptdev - > dev . devt ) ) ;
cdev_del ( & eptdev - > cdev ) ;
kfree ( eptdev ) ;
}
static int rpmsg_eptdev_create ( struct rpmsg_ctrldev * ctrldev ,
struct rpmsg_channel_info chinfo )
{
struct rpmsg_device * rpdev = ctrldev - > rpdev ;
struct rpmsg_eptdev * eptdev ;
struct device * dev ;
int ret ;
eptdev = kzalloc ( sizeof ( * eptdev ) , GFP_KERNEL ) ;
if ( ! eptdev )
return - ENOMEM ;
dev = & eptdev - > dev ;
eptdev - > rpdev = rpdev ;
eptdev - > chinfo = chinfo ;
mutex_init ( & eptdev - > ept_lock ) ;
spin_lock_init ( & eptdev - > queue_lock ) ;
skb_queue_head_init ( & eptdev - > queue ) ;
init_waitqueue_head ( & eptdev - > readq ) ;
device_initialize ( dev ) ;
dev - > class = rpmsg_class ;
dev - > parent = & ctrldev - > dev ;
dev - > groups = rpmsg_eptdev_groups ;
dev_set_drvdata ( dev , eptdev ) ;
cdev_init ( & eptdev - > cdev , & rpmsg_eptdev_fops ) ;
eptdev - > cdev . owner = THIS_MODULE ;
ret = ida_simple_get ( & rpmsg_minor_ida , 0 , RPMSG_DEV_MAX , GFP_KERNEL ) ;
if ( ret < 0 )
goto free_eptdev ;
dev - > devt = MKDEV ( MAJOR ( rpmsg_major ) , ret ) ;
ret = ida_simple_get ( & rpmsg_ept_ida , 0 , 0 , GFP_KERNEL ) ;
if ( ret < 0 )
goto free_minor_ida ;
dev - > id = ret ;
dev_set_name ( dev , " rpmsg%d " , ret ) ;
ret = cdev_add ( & eptdev - > cdev , dev - > devt , 1 ) ;
if ( ret )
goto free_ept_ida ;
/* We can now rely on the release function for cleanup */
dev - > release = rpmsg_eptdev_release_device ;
ret = device_add ( dev ) ;
if ( ret ) {
2017-06-02 14:36:04 +03:00
dev_err ( dev , " device_add failed: %d \n " , ret ) ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
put_device ( dev ) ;
}
return ret ;
free_ept_ida :
ida_simple_remove ( & rpmsg_ept_ida , dev - > id ) ;
free_minor_ida :
ida_simple_remove ( & rpmsg_minor_ida , MINOR ( dev - > devt ) ) ;
free_eptdev :
put_device ( dev ) ;
kfree ( eptdev ) ;
return ret ;
}
static int rpmsg_ctrldev_open ( struct inode * inode , struct file * filp )
{
struct rpmsg_ctrldev * ctrldev = cdev_to_ctrldev ( inode - > i_cdev ) ;
get_device ( & ctrldev - > dev ) ;
filp - > private_data = ctrldev ;
return 0 ;
}
static int rpmsg_ctrldev_release ( struct inode * inode , struct file * filp )
{
struct rpmsg_ctrldev * ctrldev = cdev_to_ctrldev ( inode - > i_cdev ) ;
put_device ( & ctrldev - > dev ) ;
return 0 ;
}
static long rpmsg_ctrldev_ioctl ( struct file * fp , unsigned int cmd ,
unsigned long arg )
{
struct rpmsg_ctrldev * ctrldev = fp - > private_data ;
void __user * argp = ( void __user * ) arg ;
struct rpmsg_endpoint_info eptinfo ;
struct rpmsg_channel_info chinfo ;
if ( cmd ! = RPMSG_CREATE_EPT_IOCTL )
return - EINVAL ;
if ( copy_from_user ( & eptinfo , argp , sizeof ( eptinfo ) ) )
return - EFAULT ;
memcpy ( chinfo . name , eptinfo . name , RPMSG_NAME_SIZE ) ;
chinfo . name [ RPMSG_NAME_SIZE - 1 ] = ' \0 ' ;
chinfo . src = eptinfo . src ;
chinfo . dst = eptinfo . dst ;
return rpmsg_eptdev_create ( ctrldev , chinfo ) ;
} ;
static const struct file_operations rpmsg_ctrldev_fops = {
. owner = THIS_MODULE ,
. open = rpmsg_ctrldev_open ,
. release = rpmsg_ctrldev_release ,
. unlocked_ioctl = rpmsg_ctrldev_ioctl ,
2018-09-11 22:59:08 +03:00
. compat_ioctl = compat_ptr_ioctl ,
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
} ;
static void rpmsg_ctrldev_release_device ( struct device * dev )
{
struct rpmsg_ctrldev * ctrldev = dev_to_ctrldev ( dev ) ;
ida_simple_remove ( & rpmsg_ctrl_ida , dev - > id ) ;
ida_simple_remove ( & rpmsg_minor_ida , MINOR ( dev - > devt ) ) ;
kfree ( ctrldev ) ;
}
static int rpmsg_chrdev_probe ( struct rpmsg_device * rpdev )
{
struct rpmsg_ctrldev * ctrldev ;
struct device * dev ;
int ret ;
ctrldev = kzalloc ( sizeof ( * ctrldev ) , GFP_KERNEL ) ;
if ( ! ctrldev )
return - ENOMEM ;
ctrldev - > rpdev = rpdev ;
dev = & ctrldev - > dev ;
device_initialize ( dev ) ;
dev - > parent = & rpdev - > dev ;
dev - > class = rpmsg_class ;
cdev_init ( & ctrldev - > cdev , & rpmsg_ctrldev_fops ) ;
ctrldev - > cdev . owner = THIS_MODULE ;
ret = ida_simple_get ( & rpmsg_minor_ida , 0 , RPMSG_DEV_MAX , GFP_KERNEL ) ;
if ( ret < 0 )
goto free_ctrldev ;
dev - > devt = MKDEV ( MAJOR ( rpmsg_major ) , ret ) ;
ret = ida_simple_get ( & rpmsg_ctrl_ida , 0 , 0 , GFP_KERNEL ) ;
if ( ret < 0 )
goto free_minor_ida ;
dev - > id = ret ;
dev_set_name ( & ctrldev - > dev , " rpmsg_ctrl%d " , ret ) ;
2022-01-10 21:47:36 +03:00
ret = cdev_device_add ( & ctrldev - > cdev , & ctrldev - > dev ) ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
if ( ret )
goto free_ctrl_ida ;
/* We can now rely on the release function for cleanup */
dev - > release = rpmsg_ctrldev_release_device ;
dev_set_drvdata ( & rpdev - > dev , ctrldev ) ;
return ret ;
free_ctrl_ida :
ida_simple_remove ( & rpmsg_ctrl_ida , dev - > id ) ;
free_minor_ida :
ida_simple_remove ( & rpmsg_minor_ida , MINOR ( dev - > devt ) ) ;
free_ctrldev :
put_device ( dev ) ;
kfree ( ctrldev ) ;
return ret ;
}
static void rpmsg_chrdev_remove ( struct rpmsg_device * rpdev )
{
struct rpmsg_ctrldev * ctrldev = dev_get_drvdata ( & rpdev - > dev ) ;
int ret ;
/* Destroy all endpoints */
ret = device_for_each_child ( & ctrldev - > dev , NULL , rpmsg_eptdev_destroy ) ;
if ( ret )
dev_warn ( & rpdev - > dev , " failed to nuke endpoints: %d \n " , ret ) ;
2022-01-10 21:47:36 +03:00
cdev_device_del ( & ctrldev - > cdev , & ctrldev - > dev ) ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
put_device ( & ctrldev - > dev ) ;
}
static struct rpmsg_driver rpmsg_chrdev_driver = {
. probe = rpmsg_chrdev_probe ,
. remove = rpmsg_chrdev_remove ,
. drv = {
. name = " rpmsg_chrdev " ,
} ,
} ;
2021-03-11 17:04:08 +03:00
static int rpmsg_chrdev_init ( void )
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
{
int ret ;
ret = alloc_chrdev_region ( & rpmsg_major , 0 , RPMSG_DEV_MAX , " rpmsg " ) ;
if ( ret < 0 ) {
2021-11-08 16:59:45 +03:00
pr_err ( " failed to allocate char dev region \n " ) ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
return ret ;
}
rpmsg_class = class_create ( THIS_MODULE , " rpmsg " ) ;
if ( IS_ERR ( rpmsg_class ) ) {
pr_err ( " failed to create rpmsg class \n " ) ;
unregister_chrdev_region ( rpmsg_major , RPMSG_DEV_MAX ) ;
return PTR_ERR ( rpmsg_class ) ;
}
ret = register_rpmsg_driver ( & rpmsg_chrdev_driver ) ;
if ( ret < 0 ) {
2021-11-08 16:59:45 +03:00
pr_err ( " failed to register rpmsg driver \n " ) ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
class_destroy ( rpmsg_class ) ;
unregister_chrdev_region ( rpmsg_major , RPMSG_DEV_MAX ) ;
}
return ret ;
}
2021-03-11 17:04:08 +03:00
postcore_initcall ( rpmsg_chrdev_init ) ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
static void rpmsg_chrdev_exit ( void )
{
unregister_rpmsg_driver ( & rpmsg_chrdev_driver ) ;
class_destroy ( rpmsg_class ) ;
unregister_chrdev_region ( rpmsg_major , RPMSG_DEV_MAX ) ;
}
module_exit ( rpmsg_chrdev_exit ) ;
2018-03-23 07:09:12 +03:00
MODULE_ALIAS ( " rpmsg:rpmsg_chrdev " ) ;
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
2017-01-11 17:35:12 +03:00
MODULE_LICENSE ( " GPL v2 " ) ;