Dear Sascha Hauer,
> On Sat, Jun 09, 2012 at 12:34:47PM +0200, Marek Vasut wrote:
> > Dear Shubhrajyoti Datta,
> >
> > > Didnt understand this.
> >
> > What exactly, it's running (according to the datasheet) at 95kHz.
> >
> > > > + .timing0 = 0x00780030,
> > > > + .timing1 = 0x00800030,
> > > > + .timing2 = 0x0015000d,
> > > > +};
> > > > +
> > > > +const struct mxs_i2c_speed_config mxs_i2c_400kHz_config = {
> > > > + .timing0 = 0x000f0007,
> > > > + .timing1 = 0x001f000f,
> > > > + .timing2 = 0x0015000d,
> > > > +};
> > > > +
> > >
> > > How are these values calculated?
> >
> > They're not calculated, they're presented in the datasheet. There's no
> > formula, even though I believe one could be derived given enough effort.
>
> Don't these values depend on the input clock of this unit? I don't know,
> just asking.
Isn't the i2c block supplied from 24MHz clock source in the mx28?
> Sascha
Best regards,
Marek Vasut
--
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
