Searched hist:fa5e2845a867a3715240ff221aaec2825b5c73df (Results 1 – 3 of 3) sorted by relevance
| /rk3399_rockchip-uboot/arch/arm/include/asm/arch-mxs/ |
| H A D | clock.h | fa5e2845a867a3715240ff221aaec2825b5c73df Fri Nov 30 18:17:07 UTC 2012 Marek Vasut <marex@denx.de> mxs: i2c: Implement algorithm to set up arbitrary i2c speed
This algorithm computes the values of TIMING{0,1,2} registers for the
MX28 I2C block. This algorithm was derived by using a scope, but the
result seems correct.
The resulting values programmed into the registers do not correlate
with the contents in datasheet. When using the values from the datasheet,
the I2C clock were completely wrong.
Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Stefano Babic <sbabic@denx.de>
Cc: Fabio Estevam <fabio.estevam@freescale.com>
Cc: Wolfgang Denk <wd@denx.de>
|
| /rk3399_rockchip-uboot/arch/arm/cpu/arm926ejs/mxs/ |
| H A D | clock.c | fa5e2845a867a3715240ff221aaec2825b5c73df Fri Nov 30 18:17:07 UTC 2012 Marek Vasut <marex@denx.de> mxs: i2c: Implement algorithm to set up arbitrary i2c speed
This algorithm computes the values of TIMING{0,1,2} registers for the
MX28 I2C block. This algorithm was derived by using a scope, but the
result seems correct.
The resulting values programmed into the registers do not correlate
with the contents in datasheet. When using the values from the datasheet,
the I2C clock were completely wrong.
Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Stefano Babic <sbabic@denx.de>
Cc: Fabio Estevam <fabio.estevam@freescale.com>
Cc: Wolfgang Denk <wd@denx.de>
|
| /rk3399_rockchip-uboot/drivers/i2c/ |
| H A D | mxs_i2c.c | fa5e2845a867a3715240ff221aaec2825b5c73df Fri Nov 30 18:17:07 UTC 2012 Marek Vasut <marex@denx.de> mxs: i2c: Implement algorithm to set up arbitrary i2c speed
This algorithm computes the values of TIMING{0,1,2} registers for the
MX28 I2C block. This algorithm was derived by using a scope, but the
result seems correct.
The resulting values programmed into the registers do not correlate
with the contents in datasheet. When using the values from the datasheet,
the I2C clock were completely wrong.
Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Stefano Babic <sbabic@denx.de>
Cc: Fabio Estevam <fabio.estevam@freescale.com>
Cc: Wolfgang Denk <wd@denx.de>
|