From: Thierry Reding <tred...@nvidia.com>
Similarly to what can be done for device drivers, allow driver-specific
data to be attached to a master. This is necessary for masters whose
device is already bound to by a different driver and therefore cannot be
used to store the driver-specific data.
Signed-off-by: Thierry Reding <tred...@nvidia.com>
---
Note that I'd like to merge this patch through the Tegra DRM tree so
that the Tegra DRM changes later in this patch can be merged at the same
time to avoid them being delayed for another release cycle.
In particular I'm looking for an Acked-by from Greg and Russell.
drivers/base/component.c | 13 +++++++++++++
include/linux/component.h | 3 +++
2 files changed, 16 insertions(+)
diff --git a/drivers/base/component.c b/drivers/base/component.c
index c4778995cd72..fb4510707281 100644
--- a/drivers/base/component.c
+++ b/drivers/base/component.c
@@ -25,6 +25,8 @@ struct master {
const struct component_master_ops *ops;
struct device *dev;
+
+ void *drvdata;
};
struct component {
@@ -53,6 +55,17 @@ static struct master *__master_find(struct device *dev,
return NULL;
}
+void master_set_drvdata(struct master *master, void *data)
+{
+ if (master)
+ master->drvdata = data;
+}
+
+void *master_get_drvdata(struct master *master)
+{
+ return master ? master->drvdata : NULL;
+}
+
/* Attach an unattached component to a master. */
static void component_attach_master(struct master *master, struct component *c)
{
diff --git a/include/linux/component.h b/include/linux/component.h
index 68870182ca1e..f130b34b1575 100644
--- a/include/linux/component.h
+++ b/include/linux/component.h
@@ -26,6 +26,9 @@ int component_master_add(struct device *, const struct
component_master_ops *);
void component_master_del(struct device *,
const struct component_master_ops *);
+void master_set_drvdata(struct master *, void *);
+void *master_get_drvdata(struct master *);
+
int component_master_add_child(struct master *master,
int (*compare)(struct device *, void *), void *compare_data);
--
1.9.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
