Dear Shubhrajyoti Datta,
> >> > +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?
I intended to stick with the datasheet, if you manage to find explanation for
why they chose 95kHz, I'd be interested to hear it ... btw. 24MHz/95kHz gives
pretty weird divider, which is quite suspicious.
> and approximating due to clock ... or some other limitaion?
Doesn't seem to be the case, see "btw" part above.
> That is what I was trying to understand.
>
> >> > + .timing0 = 0x00780030,
> >> > + .timing1 = 0x00800030,
> >> > + .timing2 = 0x0015000d,
> >> > +};
Best regards,
Marek Vasut
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
