Trent Piepho wrote:
Seems like it should keep the clock registers at what u-boot set them too.
Or we could have U-Boot put the i2c clock frequency into the I2C node, and let
the driver program the hardware again. That would keep the ugliness in U-Boot.
--
Timur Tabi
Linux kernel developer at
Timur Tabi wrote:
Trent Piepho wrote:
Seems like it should keep the clock registers at what u-boot set them too.
Or we could have U-Boot put the i2c clock frequency into the I2C node, and let
the driver program the hardware again. That would keep the ugliness in U-Boot.
André Schwarz wrote:
Wouldn't it be easier to omit frequency re-programming at all ?
Maybe configurable for non U-Boot users ...
Well, the real problem is that Linux is ignoring what the boot loader has done.
This is bad, regardless as to which boot loader you're using.
The question is, do
On Mon, 1 Dec 2008, Andr? Schwarz wrote:
Timur Tabi wrote:
Trent Piepho wrote:
Seems like it should keep the clock registers at what u-boot set them
too.
Or we could have U-Boot put the i2c clock frequency into the I2C node, and
let
the driver program the hardware again.
On Mon, 1 Dec 2008, Scott Wood wrote:
Trent Piepho wrote:
U-boot could pass in bus-frequency to let software know the speed of the
I2C bus from Linux. Seems like a standard property for bus nodes.
clock-frequency is standard, though it should probably be the input frequency
rather than
Trent Piepho wrote:
For a bus device like an i2c controller, you really have two clocks. The
input clock the controller runs from and the speed it runs the bus at. One
could say that one clock is for the device node and the other clock is for
the device's sub-nodes.
We could add a property
Trent Piepho wrote:
The Linux code could use current-speed to know if it should program the
registers. I.e., if current-speed is present and non-zero, then leave the
frequency registers alone. Otherwise u-boot or whatever might not have
programmed the I2C controller and the driver can do what
On Thu, 27 Nov 2008, Andre Schwarz wrote:
Timur Tabi schrieb:
On Thu, Nov 27, 2008 at 9:00 AM, Andre Schwarz
[EMAIL PROTECTED] wrote:
All,
is anybody working on some improvements regarding configurable I2C
frequency inside the i2c-mpc driver ?
If not - would anybody be intersted in
On Thu, Nov 27, 2008 at 9:00 AM, Andre Schwarz
[EMAIL PROTECTED] wrote:
All,
is anybody working on some improvements regarding configurable I2C
frequency inside the i2c-mpc driver ?
If not - would anybody be intersted in getting this done, i.e.
configurable via device tree ?
Maybe I'm
Timur Tabi schrieb:
On Thu, Nov 27, 2008 at 9:00 AM, Andre Schwarz
[EMAIL PROTECTED] wrote:
All,
is anybody working on some improvements regarding configurable I2C
frequency inside the i2c-mpc driver ?
If not - would anybody be intersted in getting this done, i.e.
configurable via
Timur Tabi wrote:
On Thu, Nov 27, 2008 at 9:00 AM, Andre Schwarz
[EMAIL PROTECTED] wrote:
All,
is anybody working on some improvements regarding configurable I2C
frequency inside the i2c-mpc driver ?
If not - would anybody be intersted in getting this done, i.e.
configurable via device
11 matches
Mail list logo
