Techwizz/kernel-fxtec-pro1x
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

rpmsg: Introduce a driver override mechanism

Browse source 
Similar to other subsystems it's useful to provide a mechanism to force
a specific driver match on a device, so introduce this.

Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
This commit is contained in:
Bjorn Andersson 2016-10-07 21:23:12 -07:00
parent 66dca399e6
commit e950604782
2 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
drivers/rpmsg/rpmsg_core.c
View file

@ -315,6 +315,9 @@ static int rpmsg_dev_match(struct device *dev, struct device_driver *drv)
const struct rpmsg_device_id *ids = rpdrv->id_table; const struct rpmsg_device_id *ids = rpdrv->id_table;
unsigned int i; unsigned int i;
if (rpdev->driver_override)
return !strcmp(rpdev->driver_override, drv->name);
if (ids) if (ids)
for (i = 0; ids[i].name[0]; i++) for (i = 0; ids[i].name[0]; i++)
if (rpmsg_id_match(rpdev, &ids[i])) if (rpmsg_id_match(rpdev, &ids[i]))

2
include/linux/rpmsg.h
View file

@ -64,6 +64,7 @@ struct rpmsg_channel_info {
* rpmsg_device - device that belong to the rpmsg bus * rpmsg_device - device that belong to the rpmsg bus
* @dev: the device struct * @dev: the device struct
* @id: device id (used to match between rpmsg drivers and devices) * @id: device id (used to match between rpmsg drivers and devices)
* @driver_override: driver name to force a match
* @src: local address * @src: local address
* @dst: destination address * @dst: destination address
* @ept: the rpmsg endpoint of this channel * @ept: the rpmsg endpoint of this channel
@ -72,6 +73,7 @@ struct rpmsg_channel_info {
struct rpmsg_device { struct rpmsg_device {
struct device dev; struct device dev;
struct rpmsg_device_id id; struct rpmsg_device_id id;
char *driver_override;
u32 src; u32 src;
u32 dst; u32 dst;
struct rpmsg_endpoint *ept; struct rpmsg_endpoint *ept;