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.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
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
