| Message ID | 20190403124019.8947-10-wsa+renesas@sang-engineering.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | i2c: core: introduce atomic transfers | expand |
On Wed, Apr 03, 2019 at 02:40:16PM +0200, Wolfram Sang wrote: > The driver already has the routine in place, tie it to the new callback. > > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com> > Cc: Andrew Lunn <andrew@lunn.ch> The polling function was not really designed with the intention to be used in atomic context. But it does appear to be safe to use in that context. So Reviewed-by: Andrew Lunn <andrew@lunn.ch> Andrew
diff --git a/drivers/i2c/busses/i2c-ocores.c b/drivers/i2c/busses/i2c-ocores.c index 1b99f467aae0..c3dabee0aa35 100644 --- a/drivers/i2c/busses/i2c-ocores.c +++ b/drivers/i2c/busses/i2c-ocores.c @@ -442,6 +442,7 @@ static u32 ocores_func(struct i2c_adapter *adap) static struct i2c_algorithm ocores_algorithm = { .master_xfer = ocores_xfer, + .master_xfer_atomic = ocores_xfer_polling, .functionality = ocores_func, };
The driver already has the routine in place, tie it to the new callback. Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Cc: Andrew Lunn <andrew@lunn.ch> --- drivers/i2c/busses/i2c-ocores.c | 1 + 1 file changed, 1 insertion(+)