>> >
>> > +struct mxs_i2c_speed_config {
>> > + uint32_t timing0;
>> > + uint32_t timing1;
>> > + uint32_t timing2;
>> > +};
>> > +
>> > +const struct mxs_i2c_speed_config mxs_i2c_95kHz_config = {
>>
>> You are using 95k?
>
> Yes
>
>> Didnt understand this.
>
> What exactly, it's running (according to the datasheet) at 95kHz.
Did you intend 100k?
and approximating due to clock ... or some other limitaion?
That is what I was trying to understand.
>
>> > + .timing0 = 0x00780030,
>> > + .timing1 = 0x00800030,
>> > + .timing2 = 0x0015000d,
>> > +};
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
