Home
last modified time | relevance | path

Searched hist:b63128e81214cc2db2995d690438055c26d213a5 (Results 1 – 4 of 4) sorted by relevance

/linux/arch/arm/mach-omap1/
H A Di2c.cdiff 9833eff3d7db76d2d04f28567ed8704d69e225ae Mon Feb 22 21:29:36 CET 2010 Jarkko Nikula <jhnikula@gmail.com> omap: i2c: Fix muxing for command line enabled bus

The commit b63128e81214cc2db2995d690438055c26d213a5 broke the pin muxing
for I2C busses that are enabled from the kernel command line.

Fix this by defining the board registration function omap_register_i2c_bus
in common platform code as it was before but keep the muxing in architecture
dependent files.

Signed-off-by: Jarkko Nikula <jhnikula@gmail.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
b63128e81214cc2db2995d690438055c26d213a5 Sat Dec 12 01:16:32 CET 2009 Tony Lindgren <tony@atomide.com> omap: Split i2c platform init for mach-omap1 and mach-omap2

Otherwise we cannot limit new mux code to mach-omap2.
The same signal names should eventually work for other
omaps under mach-omap2.

Note that these pins don't need to be OMAP_PIN_INPUT_PULLUP,
just OMAP_PIN_INPUT is enough.

Cc: Jarkko Nikula <jhnikula@gmail.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
H A DMakefilediff b63128e81214cc2db2995d690438055c26d213a5 Sat Dec 12 01:16:32 CET 2009 Tony Lindgren <tony@atomide.com> omap: Split i2c platform init for mach-omap1 and mach-omap2

Otherwise we cannot limit new mux code to mach-omap2.
The same signal names should eventually work for other
omaps under mach-omap2.

Note that these pins don't need to be OMAP_PIN_INPUT_PULLUP,
just OMAP_PIN_INPUT is enough.

Cc: Jarkko Nikula <jhnikula@gmail.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
/linux/arch/arm/mach-omap2/
H A Di2c.cdiff 9833eff3d7db76d2d04f28567ed8704d69e225ae Mon Feb 22 21:29:36 CET 2010 Jarkko Nikula <jhnikula@gmail.com> omap: i2c: Fix muxing for command line enabled bus

The commit b63128e81214cc2db2995d690438055c26d213a5 broke the pin muxing
for I2C busses that are enabled from the kernel command line.

Fix this by defining the board registration function omap_register_i2c_bus
in common platform code as it was before but keep the muxing in architecture
dependent files.

Signed-off-by: Jarkko Nikula <jhnikula@gmail.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
b63128e81214cc2db2995d690438055c26d213a5 Sat Dec 12 01:16:32 CET 2009 Tony Lindgren <tony@atomide.com> omap: Split i2c platform init for mach-omap1 and mach-omap2

Otherwise we cannot limit new mux code to mach-omap2.
The same signal names should eventually work for other
omaps under mach-omap2.

Note that these pins don't need to be OMAP_PIN_INPUT_PULLUP,
just OMAP_PIN_INPUT is enough.

Cc: Jarkko Nikula <jhnikula@gmail.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
H A DMakefilediff b63128e81214cc2db2995d690438055c26d213a5 Sat Dec 12 01:16:32 CET 2009 Tony Lindgren <tony@atomide.com> omap: Split i2c platform init for mach-omap1 and mach-omap2

Otherwise we cannot limit new mux code to mach-omap2.
The same signal names should eventually work for other
omaps under mach-omap2.

Note that these pins don't need to be OMAP_PIN_INPUT_PULLUP,
just OMAP_PIN_INPUT is enough.

Cc: Jarkko Nikula <jhnikula@gmail.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>