[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141203111518.GB1039@katana>
Date: Wed, 3 Dec 2014 12:15:18 +0100
From: Wolfram Sang <wsa@...-dreams.de>
To: Addy Ke <addy.ke@...k-chips.com>
Cc: max.schwarz@...ine.de, heiko@...ech.de, olof@...om.net,
dianders@...omium.org, robh+dt@...nel.org, pawel.moll@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, cf@...k-chips.com,
xjq@...k-chips.com, huangtao@...k-chips.com, zyw@...k-chips.com,
yzq@...k-chips.com, hj@...k-chips.com, kever.yang@...k-chips.com,
hl@...k-chips.com, caesar.wang@...k-chips.com,
zhengsq@...k-chips.com
Subject: Re: [PATCH v2] i2c: rk3x: fix bug that cause measured high_ns
doesn't meet I2C spec
> + - rise-ns : Number of nanoseconds the signal takes to rise (t(r) in i2c spec).
> + If not specified this is assumed to be the max the spec allows
> + (1000 ns for standard mode, 300 ns for fast mode) which might
> + cause slightly slower communication.
> + - fall-ns : Number of nanoseconds the signal takes to fall (t(f) in the i2c0
> + spec). If not specified this is assumed to be the max the spec
> + allows (300 ns) which might cause slightly slower communication.
We already have those bindings from the designware driver:
- i2c-sda-hold-time-ns : should contain the SDA hold time in nanoseconds.
- i2c-scl-falling-time : should contain the SCL falling time in nanoseconds.
- i2c-sda-falling-time : should contain the SDA falling time in nanoseconds.
Can you reuse them? Or do you really need a specific rise-time property?
If so, please matche the style of the bindings above.
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists