Hi Doug,
在 2016/5/6 7:02, Doug Anderson 写道:
David,
On Wed, May 4, 2016 at 7:37 AM, David Wu <david.wu@xxxxxxxxxxxxxx> wrote:
Signed-off-by: David Wu <david.wu@xxxxxxxxxxxxxx>
---
drivers/i2c/busses/i2c-rk3x.c | 21 +++++++++++++++++----
1 file changed, 17 insertions(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2c-rk3x.c b/drivers/i2c/busses/i2c-rk3x.c
index 47368c4..c66cc39 100644
--- a/drivers/i2c/busses/i2c-rk3x.c
+++ b/drivers/i2c/busses/i2c-rk3x.c
@@ -124,6 +124,17 @@ static const struct i2c_spec_values fast_mode_spec = {
.min_hold_buffer_ns = 1300,
};
+static const struct i2c_spec_values fast_mode_plus_spec = {
+ .min_hold_start_ns = 260,
+ .min_low_ns = 500,
+ .min_high_ns = 260,
+ .min_setup_start_ns = 260,
+ .max_data_hold_ns = 400,
I'm curious where you got the data_hold_ns. I can't quite remember
what this parameter does / how the timing function works anymore, but
the doc I have (search for UM10204 and click the first link) shows
values for Standard-mode and Fast-mode but not Fast-mode Plus. It
seems to imply that this is a bit of a bogus number anyway because it
only matters if we don't stretch the tLOW to go along with the longer
data hold.
As I have said in the previous patch, how all this stuff works has
totally left my brain, so if you understand it that's probably good
enough. If you feel like I should try to re-understand this again so
I can review it more deeply, let me know.
Yes, I could not get the description of fast-mode plus data_hold_ns, but
I saw that the maximum tHD;DAT must be less than the maximum of
tVD;DATor tVD;ACKby for Standard-mode and Fast-mode.
So I think the maximum tHD;DAT for Fast-mode Plus should be less than
the maximum of tVD;DATor tVD;ACKby too, the maximum of tVD;DATor
tVD;ACKby is 450ns, and 400ns is my taking a conservative value.
Description form UM10204
[4] The maximum tHD;DATcould be 3.45μs and 0.9μs for Standard-mode and
Fast-mode, but must be less than the maximum of tVD;DATor tVD;ACKby a
transition time. This maximum must only be met if the device does not
stretch the LOW period (tLOW) of the SCL signal. If the clock stretches
the SCL, the data must be valid by the set-up time before it releases
the clock.
Since I assume that you had some sane reason to include max_data_hold_ns:
Reviewed-by: Douglas Anderson <dianders@xxxxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
