On 2019-10-21 22:24, Jae Hyun Yoo wrote: > Append a binding to support hardware timeout feature. > > Signed-off-by: Jae Hyun Yoo <jae.hyun.yoo@xxxxxxxxxxxxxxx> > --- > Documentation/devicetree/bindings/i2c/i2c-aspeed.txt | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/Documentation/devicetree/bindings/i2c/i2c-aspeed.txt b/Documentation/devicetree/bindings/i2c/i2c-aspeed.txt > index b47f6ccb196a..133bfedf4cdd 100644 > --- a/Documentation/devicetree/bindings/i2c/i2c-aspeed.txt > +++ b/Documentation/devicetree/bindings/i2c/i2c-aspeed.txt > @@ -17,6 +17,8 @@ Optional Properties: > - bus-frequency : frequency of the bus clock in Hz defaults to 100 kHz when not > specified > - multi-master : states that there is another master active on this bus. > +- aspeed,hw-timeout-ms : Hardware timeout in milliseconds. If it's not > + specified, the H/W timeout feature will be disabled. > > Example: > > Some SMBus clients support a smbus-timeout-disable binding for disabling timeouts like this, for cases where the I2C adapter in question on occasion is unable to keep the pace. Adding that property thus avoids undesired timeouts when the client is SMBus conformant without it. Your new binding is the reverse situation, where you want to add a timeout where one is otherwise missing. Anyway, since I2C does not have a specified lowest possible frequency, this feels like something that is more in the SMBus arena. Should the property perhaps be a generic property named smbus-timeout-ms, or something like that? If the above is not wanted or appropriate, then I would personally prefer aspeed,bus-timeout-ms over aspeed,hw-timeout-ms. To me, hw-timeout-ms sounds like a (more serious) timeout between the CPU and the I2C peripheral unit or something like that. But I don't care deeply... Cheers, Peter
