提交 5a9dcd81 编写于 作者: W Wolfram Sang 提交者: Peter Rosin

i2c: mux: demux-pinctrl: use proper parent device for demux adapter

Due to a typo, the wrong parent device was assigned to the newly created
demuxing adapter device. It got connected to the demuxing platform
device but not to the selected parent I2C adapter device. Fix it to get
a proper parent-child relationship of the demuxed busses.
Signed-off-by: NWolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: NSimon Horman <horms+renesas@verge.net.au>
Signed-off-by: NPeter Rosin <peda@axentia.se>
上级 f657c9fe
...@@ -106,7 +106,7 @@ static int i2c_demux_activate_master(struct i2c_demux_pinctrl_priv *priv, u32 ne ...@@ -106,7 +106,7 @@ static int i2c_demux_activate_master(struct i2c_demux_pinctrl_priv *priv, u32 ne
priv->cur_adap.owner = THIS_MODULE; priv->cur_adap.owner = THIS_MODULE;
priv->cur_adap.algo = &priv->algo; priv->cur_adap.algo = &priv->algo;
priv->cur_adap.algo_data = priv; priv->cur_adap.algo_data = priv;
priv->cur_adap.dev.parent = priv->dev; priv->cur_adap.dev.parent = &adap->dev;
priv->cur_adap.class = adap->class; priv->cur_adap.class = adap->class;
priv->cur_adap.retries = adap->retries; priv->cur_adap.retries = adap->retries;
priv->cur_adap.timeout = adap->timeout; priv->cur_adap.timeout = adap->timeout;
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册