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: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Peter Rosin <peda@axentia.se>

diff --git a/drivers/i2c/muxes/i2c-demux-pinctrl.c b/drivers/i2c/muxes/i2c-demux-pinctrl.c
index 428de4c97fb2848c2bed71775a4f846d84f048b4..035032e203276e96b27dd57770f47af98ee5146f 100644 (file)
--- a/drivers/i2c/muxes/i2c-demux-pinctrl.c
+++ b/drivers/i2c/muxes/i2c-demux-pinctrl.c
@@ -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.algo = &priv->algo;
        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.retries = adap->retries;
        priv->cur_adap.timeout = adap->timeout;