Re: tHigh tLow discussion (was [pacth] I2C bug fixes for L-O and L-Z)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Feb 23, 2009 at 8:27 PM,  <ext-Eero.Nurkkala@xxxxxxxxx> wrote:
>
>
>> ;) Aye Aye.... I wonder if the equation you provided is based on
>> emperical measurement? if so would it vary based on electrical
>> characteristics of a platform? I mean beagleboard Vs Zoom Vs SDP
>> atleast have variances of i2c trace lengths and number of devices per
>> i2c bus.. wont the equation change based on board configuration?
>
> Nothing empirical. It's just for one board.
>
> They say it differs from board to board. I haven't had time to spend with different boards.
> They call it the "load on scl line", that makes the numbers different on other
> boards. (I'm not so sure about that, but agreed it may vary little)
>
So, it might be worth considering my following proposition?"
Now, from a s/w perspective, If we would like to have it so that we can
configure tHigh and tLow based on devices, electrical characteristics on
a bus, not just speed of the bus, the current implementation would
probably need to change(I think).
"
maybe take tHigh, tLow as a platform data input to the driver? that
could allow scaling for all boards I wonder?

Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux