mailbox: Allow attaching private data for mbox_chan
Sometimes mbox controllers wants to store private data in mbox_chan so that it can be used at a later point of time. Adding support for hooking private data. Reviewed-by: Tom Rini <trini@konsulko.com> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
This commit is contained in:
parent
694b052401
commit
600e46b08c
1 changed files with 3 additions and 4 deletions
|
@ -44,6 +44,7 @@ struct udevice;
|
||||||
*
|
*
|
||||||
* @dev: The device which implements the mailbox.
|
* @dev: The device which implements the mailbox.
|
||||||
* @id: The mailbox channel ID within the provider.
|
* @id: The mailbox channel ID within the provider.
|
||||||
|
* @con_priv: Hook for controller driver to attach private data
|
||||||
*
|
*
|
||||||
* Currently, the mailbox API assumes that a single integer ID is enough to
|
* Currently, the mailbox API assumes that a single integer ID is enough to
|
||||||
* identify and configure any mailbox channel for any mailbox provider. If this
|
* identify and configure any mailbox channel for any mailbox provider. If this
|
||||||
|
@ -56,11 +57,9 @@ struct udevice;
|
||||||
*/
|
*/
|
||||||
struct mbox_chan {
|
struct mbox_chan {
|
||||||
struct udevice *dev;
|
struct udevice *dev;
|
||||||
/*
|
/* Written by of_xlate.*/
|
||||||
* Written by of_xlate. We assume a single id is enough for now. In the
|
|
||||||
* future, we might add more fields here.
|
|
||||||
*/
|
|
||||||
unsigned long id;
|
unsigned long id;
|
||||||
|
void *con_priv;
|
||||||
};
|
};
|
||||||
|
|
||||||
/**
|
/**
|
||||||
|
|
Loading…
Reference in a new issue