RE: [PATCH] drm/bridge/sii902x: Fix EDID readback
Hello Peter, Thank you for your feedback! The changes you have suggested seem to be working just fine, I have tested them this morning. Thanks, Fab > Subject: Re: [PATCH] drm/bridge/sii902x: Fix EDID readback > > On 2018-11-02 13:13, Fabrizio Castro wrote: > > While adding SiI9022A support to the iwg23s board, it came > > up that when the HDMI transmitter is in pass through mode the > > device is not compliant with the I2C specification anymore, > > as it requires a far bigger tbuf, due to a delay the HDMI > > transmitter is adding when relaying the STOP condition on the > > monitor i2c side of things. > > > > When not providing an appropriate delay after the STOP condition > > the i2c bus would get stuck. Also, any other traffic on the bus > > while talking to the monitor may cause the transaction to fail > > or even cause issues with the i2c bus as well. > > > > I2c-gates seemed to reach consent as a possible way to address > > these issues, and as such this patch is implementing a solution > > based on that. Since others are clearly relying on the current > > implementation of the driver, this patch won't require any DT > > changes. > > > > Since we don't want any interference during the DDC Bus > > Request/Grant procedure and while talking to the monitor, we > > have to use the adapter locking primitives rather than the > > i2c-mux locking primitives. > > > > Signed-off-by: Fabrizio Castro > > --- > > RFC->PATCH: > > * Incorporated Linus Walleij, Peter Rosin, and Mark Brown comments > > > > Thank you guys > > > > drivers/gpu/drm/bridge/sii902x.c | 264 > > +-- > > 1 file changed, 196 insertions(+), 68 deletions(-) > > > > diff --git a/drivers/gpu/drm/bridge/sii902x.c > > b/drivers/gpu/drm/bridge/sii902x.c > > index e59a135..4f9d9c7 100644 > > --- a/drivers/gpu/drm/bridge/sii902x.c > > +++ b/drivers/gpu/drm/bridge/sii902x.c > > @@ -1,4 +1,6 @@ > > /* > > + * Copyright (C) 2018 Renesas Electronics > > + * > > * Copyright (C) 2016 Atmel > > * Bo Shen > > * > > @@ -21,6 +23,7 @@ > > */ > > > > #include > > +#include > > #include > > #include > > #include > > @@ -86,8 +89,68 @@ struct sii902x { > > struct drm_bridge bridge; > > struct drm_connector connector; > > struct gpio_desc *reset_gpio; > > +struct i2c_mux_core *i2cmux; > > }; > > > > +static int sii902x_read_unlocked(struct i2c_client *i2c, u8 reg, u8 *val) > > +{ > > +struct i2c_msg xfer[] = { > > +{ > > +.addr = i2c->addr, > > +.flags = 0, > > +.len = 1, > > +.buf = , > > +}, { > > +.addr = i2c->addr, > > +.flags = I2C_M_RD, > > +.len = 1, > > +.buf = val, > > +} > > +}; > > +unsigned char xfers = ARRAY_SIZE(xfer); > > +int ret, retries = 5; > > + > > +do { > > +ret = __i2c_transfer(i2c->adapter, xfer, xfers); > > +if (ret < 0) > > +return ret; > > +} while (ret != xfers && --retries); > > +return ret == xfers ? 0 : -1; > > New in 4.19 __i2c_smbus_xfer, and I think it helps here? (untested code) > > union i2c_smbus_data data; > int ret; > > ret = __i2c_smbus_xfer(i2c->adapter, i2c->addr, i2c->flags, >I2C_SMBUS_READ, reg, >I2C_SMBUS_BYTE_DATA, ); > > if (ret < 0) > return ret; > > *val = data.byte; > return 0; > > > +} > > + > > +static int sii902x_write_unlocked(struct i2c_client *i2c, u8 reg, u8 val) > > +{ > > +u8 data[2] = {reg, val}; > > +struct i2c_msg xfer = { > > +.addr = i2c->addr, > > +.flags = 0, > > +.len = sizeof(data), > > +.buf = data, > > +}; > > +int ret, retries = 5; > > + > > +do { > > +ret = __i2c_transfer(i2c->adapter, , 1); > > +if (ret < 0) > > +return ret; > > +} while (!ret && --retries); > > +return !ret ? -1 : 0; > > union i2c_smbus_data data; > > data.byte = val; > > return __i2c_smbus_xfer(i2c->adapter, i2c->addr, i2c->flags, > I2C_SMBUS_WRITE, reg, > I2C_SMBUS_BYTE_DATA, ); > > +} > > + > > +static int sii902x_update_bits_unlocked(struct i2c_client *i2c, u8 reg, u8 > > mask, > > +u8 val) > > +{ > > +int ret; > > +u8 status; > > + > > +ret = sii902x_read_unlocked(i2c, reg, ); > > +if (ret) > > +return ret; > > +status &= ~mask; > > +status |= val & mask; > > +return sii902x_wri
RE: [PATCH] drm/bridge/sii902x: Fix EDID readback
Hello Peter, Thank you for your feedback! > Subject: Re: [PATCH] drm/bridge/sii902x: Fix EDID readback > snip > > If the things you write about the bits are true (haven't looked closely), I > wouldn't > add any regmap coordination. But if I was the maintainer, I'd like a comment > about > this so that the next contributor has a better chance to understand the > subtlety. > > But I'm not the maintainer, so this is not my call, but by adding the comment > you > also clarify the situation for the maintainer, which is something that is > likely > to be appreciated. I'll add comments then. Cheers, Fab > > Cheers, > Peter Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
RE: [PATCH] drm/bridge/sii902x: Fix EDID readback
> > Here (and also in sii902x_i2c_bypass_deselect) you do a rmw access to the > > SII902X_SYS_CTRL_DATA register without coordinating with regmap. Regmap is > > also doing rmw accesses to that register in other parts of the driver. I > > think you need to either add comment as to why that is safe (maybe other > > things make it impossible for the two rmw accesses to cross?), or add the > > missing coordination. > > > > The other two places where SII902X_SYS_CTRL_DATA is being handled are > sii902x_bridge_disable and sii902x_bridge_enable, I didn’t think there is > any chance of the modes being probed while the bridge gets enabled/disabled, > but now that you make me think about it user space may trigger the readback > of the EDID at the most inconvenient times. Anyway, this is a good point, and > since I don't think I am supposed to access regmap's lock from outside the > APIs, > I could switch to the unlocked version of update_bits from within > sii902x_bridge_disable > and sii902x_bridge_enable, and manually grab the i2c adapter lock, what do > you think? > The bridge enable/disable callbacks deal with different bits of register SII902X_SYS_CTRL_DATA, and the value of register SII902X_SYS_CTRL_DATA after sii902x_i2c_bypass_deselect is the same as when sii902x_i2c_bypass_select gets triggered so basically even if we managed to get in the way of the regmap rmw (in the sense that for example sii902x_bridge_enable reads SII902X_SYS_CTRL_DATA and then we call into sii902x_i2c_bypass_select) by the time regmap_update_bits can perform the write operation the value of register SII902X_SYS_CTRL_DATA is the same as the one read by regmap, as "select xfer deselect" won't alter the final value of SII902X_SYS_CTRL_DATA and nobody can get in between. What do you think I should do? Do you think I can leave this alone and maybe add some comments or do you think I should explicitly protect access to SII902X_SYS_CTRL_DATA? Thanks, Fab Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] drm/bridge/sii902x: Fix EDID readback
On 2018-11-02 13:13, Fabrizio Castro wrote: > While adding SiI9022A support to the iwg23s board, it came > up that when the HDMI transmitter is in pass through mode the > device is not compliant with the I2C specification anymore, > as it requires a far bigger tbuf, due to a delay the HDMI > transmitter is adding when relaying the STOP condition on the > monitor i2c side of things. > > When not providing an appropriate delay after the STOP condition > the i2c bus would get stuck. Also, any other traffic on the bus > while talking to the monitor may cause the transaction to fail > or even cause issues with the i2c bus as well. > > I2c-gates seemed to reach consent as a possible way to address > these issues, and as such this patch is implementing a solution > based on that. Since others are clearly relying on the current > implementation of the driver, this patch won't require any DT > changes. > > Since we don't want any interference during the DDC Bus > Request/Grant procedure and while talking to the monitor, we > have to use the adapter locking primitives rather than the > i2c-mux locking primitives. > > Signed-off-by: Fabrizio Castro > --- > RFC->PATCH: > * Incorporated Linus Walleij, Peter Rosin, and Mark Brown comments > > Thank you guys > > drivers/gpu/drm/bridge/sii902x.c | 264 > +-- > 1 file changed, 196 insertions(+), 68 deletions(-) > > diff --git a/drivers/gpu/drm/bridge/sii902x.c > b/drivers/gpu/drm/bridge/sii902x.c > index e59a135..4f9d9c7 100644 > --- a/drivers/gpu/drm/bridge/sii902x.c > +++ b/drivers/gpu/drm/bridge/sii902x.c > @@ -1,4 +1,6 @@ > /* > + * Copyright (C) 2018 Renesas Electronics > + * > * Copyright (C) 2016 Atmel > * Bo Shen > * > @@ -21,6 +23,7 @@ > */ > > #include > +#include > #include > #include > #include > @@ -86,8 +89,68 @@ struct sii902x { > struct drm_bridge bridge; > struct drm_connector connector; > struct gpio_desc *reset_gpio; > + struct i2c_mux_core *i2cmux; > }; > > +static int sii902x_read_unlocked(struct i2c_client *i2c, u8 reg, u8 *val) > +{ > + struct i2c_msg xfer[] = { > + { > + .addr = i2c->addr, > + .flags = 0, > + .len = 1, > + .buf = , > + }, { > + .addr = i2c->addr, > + .flags = I2C_M_RD, > + .len = 1, > + .buf = val, > + } > + }; > + unsigned char xfers = ARRAY_SIZE(xfer); > + int ret, retries = 5; > + > + do { > + ret = __i2c_transfer(i2c->adapter, xfer, xfers); > + if (ret < 0) > + return ret; > + } while (ret != xfers && --retries); > + return ret == xfers ? 0 : -1; New in 4.19 __i2c_smbus_xfer, and I think it helps here? (untested code) union i2c_smbus_data data; int ret; ret = __i2c_smbus_xfer(i2c->adapter, i2c->addr, i2c->flags, I2C_SMBUS_READ, reg, I2C_SMBUS_BYTE_DATA, ); if (ret < 0) return ret; *val = data.byte; return 0; > +} > + > +static int sii902x_write_unlocked(struct i2c_client *i2c, u8 reg, u8 val) > +{ > + u8 data[2] = {reg, val}; > + struct i2c_msg xfer = { > + .addr = i2c->addr, > + .flags = 0, > + .len = sizeof(data), > + .buf = data, > + }; > + int ret, retries = 5; > + > + do { > + ret = __i2c_transfer(i2c->adapter, , 1); > + if (ret < 0) > + return ret; > + } while (!ret && --retries); > + return !ret ? -1 : 0; union i2c_smbus_data data; data.byte = val; return __i2c_smbus_xfer(i2c->adapter, i2c->addr, i2c->flags, I2C_SMBUS_WRITE, reg, I2C_SMBUS_BYTE_DATA, ); > +} > + > +static int sii902x_update_bits_unlocked(struct i2c_client *i2c, u8 reg, u8 > mask, > + u8 val) > +{ > + int ret; > + u8 status; > + > + ret = sii902x_read_unlocked(i2c, reg, ); > + if (ret) > + return ret; > + status &= ~mask; > + status |= val & mask; > + return sii902x_write_unlocked(i2c, reg, status); > +} > + > static inline struct sii902x *bridge_to_sii902x(struct drm_bridge *bridge) > { > return container_of(bridge, struct sii902x, bridge); > @@ -135,41 +198,11 @@ static const struct drm_connector_funcs > sii902x_connector_funcs = { > static int sii902x_get_modes(struct drm_connector *connector) > { > struct sii902x *sii902x = connector_to_sii902x(connector); > - struct regmap *regmap = sii902x->regmap; > u32 bus_format = MEDIA_BUS_FMT_RGB888_1X24; > - struct device *dev = >i2c->dev; > - unsigned long timeout; > - unsigned int
Re: [PATCH] drm/bridge/sii902x: Fix EDID readback
On 2018-11-02 17:16, Fabrizio Castro wrote: >>> Here (and also in sii902x_i2c_bypass_deselect) you do a rmw access to the >>> SII902X_SYS_CTRL_DATA register without coordinating with regmap. Regmap is >>> also doing rmw accesses to that register in other parts of the driver. I >>> think you need to either add comment as to why that is safe (maybe other >>> things make it impossible for the two rmw accesses to cross?), or add the >>> missing coordination. >>> >> >> The other two places where SII902X_SYS_CTRL_DATA is being handled are >> sii902x_bridge_disable and sii902x_bridge_enable, I didn’t think there is >> any chance of the modes being probed while the bridge gets enabled/disabled, >> but now that you make me think about it user space may trigger the readback >> of the EDID at the most inconvenient times. Anyway, this is a good point, and >> since I don't think I am supposed to access regmap's lock from outside the >> APIs, >> I could switch to the unlocked version of update_bits from within >> sii902x_bridge_disable >> and sii902x_bridge_enable, and manually grab the i2c adapter lock, what do >> you think? >> > > The bridge enable/disable callbacks deal with different bits of register > SII902X_SYS_CTRL_DATA, and the value of register SII902X_SYS_CTRL_DATA after > sii902x_i2c_bypass_deselect is the same as when sii902x_i2c_bypass_select > gets triggered > so basically even if we managed to get in the way of the regmap rmw (in the > sense that > for example sii902x_bridge_enable reads SII902X_SYS_CTRL_DATA and then we call > into sii902x_i2c_bypass_select) by the time regmap_update_bits can perform the > write operation the value of register SII902X_SYS_CTRL_DATA is the same as > the one > read by regmap, as "select xfer deselect" won't alter the final value of > SII902X_SYS_CTRL_DATA > and nobody can get in between. > What do you think I should do? Do you think I can leave this alone and maybe > add some > comments or do you think I should explicitly protect access to > SII902X_SYS_CTRL_DATA? If the things you write about the bits are true (haven't looked closely), I wouldn't add any regmap coordination. But if I was the maintainer, I'd like a comment about this so that the next contributor has a better chance to understand the subtlety. But I'm not the maintainer, so this is not my call, but by adding the comment you also clarify the situation for the maintainer, which is something that is likely to be appreciated. Cheers, Peter ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] drm/bridge/sii902x: Fix EDID readback
On 2018-11-02 13:13, Fabrizio Castro wrote: > While adding SiI9022A support to the iwg23s board, it came > up that when the HDMI transmitter is in pass through mode the > device is not compliant with the I2C specification anymore, > as it requires a far bigger tbuf, due to a delay the HDMI > transmitter is adding when relaying the STOP condition on the > monitor i2c side of things. > > When not providing an appropriate delay after the STOP condition > the i2c bus would get stuck. Also, any other traffic on the bus > while talking to the monitor may cause the transaction to fail > or even cause issues with the i2c bus as well. > > I2c-gates seemed to reach consent as a possible way to address > these issues, and as such this patch is implementing a solution > based on that. Since others are clearly relying on the current > implementation of the driver, this patch won't require any DT > changes. > > Since we don't want any interference during the DDC Bus > Request/Grant procedure and while talking to the monitor, we > have to use the adapter locking primitives rather than the > i2c-mux locking primitives. > > Signed-off-by: Fabrizio Castro > --- > RFC->PATCH: > * Incorporated Linus Walleij, Peter Rosin, and Mark Brown comments > > Thank you guys > > drivers/gpu/drm/bridge/sii902x.c | 264 > +-- > 1 file changed, 196 insertions(+), 68 deletions(-) > > diff --git a/drivers/gpu/drm/bridge/sii902x.c > b/drivers/gpu/drm/bridge/sii902x.c > index e59a135..4f9d9c7 100644 > --- a/drivers/gpu/drm/bridge/sii902x.c > +++ b/drivers/gpu/drm/bridge/sii902x.c > @@ -1,4 +1,6 @@ > /* > + * Copyright (C) 2018 Renesas Electronics > + * > * Copyright (C) 2016 Atmel > * Bo Shen > * > @@ -21,6 +23,7 @@ > */ > > #include > +#include > #include > #include > #include > @@ -86,8 +89,68 @@ struct sii902x { > struct drm_bridge bridge; > struct drm_connector connector; > struct gpio_desc *reset_gpio; > + struct i2c_mux_core *i2cmux; > }; > > +static int sii902x_read_unlocked(struct i2c_client *i2c, u8 reg, u8 *val) > +{ > + struct i2c_msg xfer[] = { > + { > + .addr = i2c->addr, > + .flags = 0, > + .len = 1, > + .buf = , > + }, { > + .addr = i2c->addr, > + .flags = I2C_M_RD, > + .len = 1, > + .buf = val, > + } > + }; > + unsigned char xfers = ARRAY_SIZE(xfer); > + int ret, retries = 5; > + > + do { > + ret = __i2c_transfer(i2c->adapter, xfer, xfers); > + if (ret < 0) > + return ret; > + } while (ret != xfers && --retries); > + return ret == xfers ? 0 : -1; > +} > + > +static int sii902x_write_unlocked(struct i2c_client *i2c, u8 reg, u8 val) > +{ > + u8 data[2] = {reg, val}; > + struct i2c_msg xfer = { > + .addr = i2c->addr, > + .flags = 0, > + .len = sizeof(data), > + .buf = data, > + }; > + int ret, retries = 5; > + > + do { > + ret = __i2c_transfer(i2c->adapter, , 1); > + if (ret < 0) > + return ret; > + } while (!ret && --retries); > + return !ret ? -1 : 0; > +} > + > +static int sii902x_update_bits_unlocked(struct i2c_client *i2c, u8 reg, u8 > mask, > + u8 val) > +{ > + int ret; > + u8 status; > + > + ret = sii902x_read_unlocked(i2c, reg, ); > + if (ret) > + return ret; > + status &= ~mask; > + status |= val & mask; > + return sii902x_write_unlocked(i2c, reg, status); > +} > + > static inline struct sii902x *bridge_to_sii902x(struct drm_bridge *bridge) > { > return container_of(bridge, struct sii902x, bridge); > @@ -135,41 +198,11 @@ static const struct drm_connector_funcs > sii902x_connector_funcs = { > static int sii902x_get_modes(struct drm_connector *connector) > { > struct sii902x *sii902x = connector_to_sii902x(connector); > - struct regmap *regmap = sii902x->regmap; > u32 bus_format = MEDIA_BUS_FMT_RGB888_1X24; > - struct device *dev = >i2c->dev; > - unsigned long timeout; > - unsigned int retries; > - unsigned int status; > struct edid *edid; > - int num = 0; > - int ret; > - > - ret = regmap_update_bits(regmap, SII902X_SYS_CTRL_DATA, > - SII902X_SYS_CTRL_DDC_BUS_REQ, > - SII902X_SYS_CTRL_DDC_BUS_REQ); > - if (ret) > - return ret; > - > - timeout = jiffies + > - msecs_to_jiffies(SII902X_I2C_BUS_ACQUISITION_TIMEOUT_MS); > - do { > - ret = regmap_read(regmap, SII902X_SYS_CTRL_DATA, ); > - if (ret) > - return ret; > - } while (!(status &
RE: [PATCH] drm/bridge/sii902x: Fix EDID readback
Hello Peter, Thank you for your feedback! > > +static int sii902x_i2c_bypass_select(struct i2c_mux_core *mux, u32 chan_id) > > +{ > > +struct sii902x *sii902x = i2c_mux_priv(mux); > > +struct device *dev = >i2c->dev; > > +unsigned long timeout; > > +u8 status; > > +int ret; > > + > > +ret = sii902x_update_bits_unlocked(sii902x->i2c, SII902X_SYS_CTRL_DATA, > > + SII902X_SYS_CTRL_DDC_BUS_REQ, > > + SII902X_SYS_CTRL_DDC_BUS_REQ); > > Here (and also in sii902x_i2c_bypass_deselect) you do a rmw access to the > SII902X_SYS_CTRL_DATA register without coordinating with regmap. Regmap is > also doing rmw accesses to that register in other parts of the driver. I > think you need to either add comment as to why that is safe (maybe other > things make it impossible for the two rmw accesses to cross?), or add the > missing coordination. > The other two places where SII902X_SYS_CTRL_DATA is being handled are sii902x_bridge_disable and sii902x_bridge_enable, I didn’t think there is any chance of the modes being probed while the bridge gets enabled/disabled, but now that you make me think about it user space may trigger the readback of the EDID at the most inconvenient times. Anyway, this is a good point, and since I don't think I am supposed to access regmap's lock from outside the APIs, I could switch to the unlocked version of update_bits from within sii902x_bridge_disable and sii902x_bridge_enable, and manually grab the i2c adapter lock, what do you think? Fab Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] drm/bridge/sii902x: Fix EDID readback
While adding SiI9022A support to the iwg23s board, it came up that when the HDMI transmitter is in pass through mode the device is not compliant with the I2C specification anymore, as it requires a far bigger tbuf, due to a delay the HDMI transmitter is adding when relaying the STOP condition on the monitor i2c side of things. When not providing an appropriate delay after the STOP condition the i2c bus would get stuck. Also, any other traffic on the bus while talking to the monitor may cause the transaction to fail or even cause issues with the i2c bus as well. I2c-gates seemed to reach consent as a possible way to address these issues, and as such this patch is implementing a solution based on that. Since others are clearly relying on the current implementation of the driver, this patch won't require any DT changes. Since we don't want any interference during the DDC Bus Request/Grant procedure and while talking to the monitor, we have to use the adapter locking primitives rather than the i2c-mux locking primitives. Signed-off-by: Fabrizio Castro --- RFC->PATCH: * Incorporated Linus Walleij, Peter Rosin, and Mark Brown comments Thank you guys drivers/gpu/drm/bridge/sii902x.c | 264 +-- 1 file changed, 196 insertions(+), 68 deletions(-) diff --git a/drivers/gpu/drm/bridge/sii902x.c b/drivers/gpu/drm/bridge/sii902x.c index e59a135..4f9d9c7 100644 --- a/drivers/gpu/drm/bridge/sii902x.c +++ b/drivers/gpu/drm/bridge/sii902x.c @@ -1,4 +1,6 @@ /* + * Copyright (C) 2018 Renesas Electronics + * * Copyright (C) 2016 Atmel * Bo Shen * @@ -21,6 +23,7 @@ */ #include +#include #include #include #include @@ -86,8 +89,68 @@ struct sii902x { struct drm_bridge bridge; struct drm_connector connector; struct gpio_desc *reset_gpio; + struct i2c_mux_core *i2cmux; }; +static int sii902x_read_unlocked(struct i2c_client *i2c, u8 reg, u8 *val) +{ + struct i2c_msg xfer[] = { + { + .addr = i2c->addr, + .flags = 0, + .len = 1, + .buf = , + }, { + .addr = i2c->addr, + .flags = I2C_M_RD, + .len = 1, + .buf = val, + } + }; + unsigned char xfers = ARRAY_SIZE(xfer); + int ret, retries = 5; + + do { + ret = __i2c_transfer(i2c->adapter, xfer, xfers); + if (ret < 0) + return ret; + } while (ret != xfers && --retries); + return ret == xfers ? 0 : -1; +} + +static int sii902x_write_unlocked(struct i2c_client *i2c, u8 reg, u8 val) +{ + u8 data[2] = {reg, val}; + struct i2c_msg xfer = { + .addr = i2c->addr, + .flags = 0, + .len = sizeof(data), + .buf = data, + }; + int ret, retries = 5; + + do { + ret = __i2c_transfer(i2c->adapter, , 1); + if (ret < 0) + return ret; + } while (!ret && --retries); + return !ret ? -1 : 0; +} + +static int sii902x_update_bits_unlocked(struct i2c_client *i2c, u8 reg, u8 mask, + u8 val) +{ + int ret; + u8 status; + + ret = sii902x_read_unlocked(i2c, reg, ); + if (ret) + return ret; + status &= ~mask; + status |= val & mask; + return sii902x_write_unlocked(i2c, reg, status); +} + static inline struct sii902x *bridge_to_sii902x(struct drm_bridge *bridge) { return container_of(bridge, struct sii902x, bridge); @@ -135,41 +198,11 @@ static const struct drm_connector_funcs sii902x_connector_funcs = { static int sii902x_get_modes(struct drm_connector *connector) { struct sii902x *sii902x = connector_to_sii902x(connector); - struct regmap *regmap = sii902x->regmap; u32 bus_format = MEDIA_BUS_FMT_RGB888_1X24; - struct device *dev = >i2c->dev; - unsigned long timeout; - unsigned int retries; - unsigned int status; struct edid *edid; - int num = 0; - int ret; - - ret = regmap_update_bits(regmap, SII902X_SYS_CTRL_DATA, -SII902X_SYS_CTRL_DDC_BUS_REQ, -SII902X_SYS_CTRL_DDC_BUS_REQ); - if (ret) - return ret; - - timeout = jiffies + - msecs_to_jiffies(SII902X_I2C_BUS_ACQUISITION_TIMEOUT_MS); - do { - ret = regmap_read(regmap, SII902X_SYS_CTRL_DATA, ); - if (ret) - return ret; - } while (!(status & SII902X_SYS_CTRL_DDC_BUS_GRTD) && -time_before(jiffies, timeout)); - - if (!(status & SII902X_SYS_CTRL_DDC_BUS_GRTD)) { - dev_err(dev, "failed to acquire the i2c bus\n"); - return