Searched hist:"3 a8761c0272c961c707e5af2eb0179adf3ef7e14" (Results 1 – 8 of 8) sorted by relevance
| /openbmc/linux/arch/arm/mach-omap2/ |
| H A D | i2c.h | 3a8761c0272c961c707e5af2eb0179adf3ef7e14 Mon Oct 08 11:11:22 CDT 2012 Tony Lindgren <tony@atomide.com> ARM: OMAP: Split plat-omap/i2c.c into mach-omap1 and mach-omap2
There's no need to keep the device related things in the
common i2c.c as omap2+ is using hwmod. Split the code to
mach-omap1 and mach-omap2 parts and only leave common
code to plat-omap/i2c.c.
Note that as omap1 only has one i2c controller, we can
now remove the old device related macros.
Reviewed-by: Shubhrajyoti D <shubhrajyoti@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
|
| H A D | i2c.c | diff 3a8761c0272c961c707e5af2eb0179adf3ef7e14 Mon Oct 08 11:11:22 CDT 2012 Tony Lindgren <tony@atomide.com> ARM: OMAP: Split plat-omap/i2c.c into mach-omap1 and mach-omap2
There's no need to keep the device related things in the
common i2c.c as omap2+ is using hwmod. Split the code to
mach-omap1 and mach-omap2 parts and only leave common
code to plat-omap/i2c.c.
Note that as omap1 only has one i2c controller, we can
now remove the old device related macros.
Reviewed-by: Shubhrajyoti D <shubhrajyoti@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
|
| H A D | omap_hwmod_2420_data.c | diff 3a8761c0272c961c707e5af2eb0179adf3ef7e14 Mon Oct 08 11:11:22 CDT 2012 Tony Lindgren <tony@atomide.com> ARM: OMAP: Split plat-omap/i2c.c into mach-omap1 and mach-omap2
There's no need to keep the device related things in the
common i2c.c as omap2+ is using hwmod. Split the code to
mach-omap1 and mach-omap2 parts and only leave common
code to plat-omap/i2c.c.
Note that as omap1 only has one i2c controller, we can
now remove the old device related macros.
Reviewed-by: Shubhrajyoti D <shubhrajyoti@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
|
| H A D | omap_hwmod_2430_data.c | diff 3a8761c0272c961c707e5af2eb0179adf3ef7e14 Mon Oct 08 11:11:22 CDT 2012 Tony Lindgren <tony@atomide.com> ARM: OMAP: Split plat-omap/i2c.c into mach-omap1 and mach-omap2
There's no need to keep the device related things in the
common i2c.c as omap2+ is using hwmod. Split the code to
mach-omap1 and mach-omap2 parts and only leave common
code to plat-omap/i2c.c.
Note that as omap1 only has one i2c controller, we can
now remove the old device related macros.
Reviewed-by: Shubhrajyoti D <shubhrajyoti@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
|
| H A D | common.h | diff 3a8761c0272c961c707e5af2eb0179adf3ef7e14 Mon Oct 08 11:11:22 CDT 2012 Tony Lindgren <tony@atomide.com> ARM: OMAP: Split plat-omap/i2c.c into mach-omap1 and mach-omap2
There's no need to keep the device related things in the
common i2c.c as omap2+ is using hwmod. Split the code to
mach-omap1 and mach-omap2 parts and only leave common
code to plat-omap/i2c.c.
Note that as omap1 only has one i2c controller, we can
now remove the old device related macros.
Reviewed-by: Shubhrajyoti D <shubhrajyoti@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
|
| H A D | omap_hwmod_3xxx_data.c | diff 3a8761c0272c961c707e5af2eb0179adf3ef7e14 Mon Oct 08 11:11:22 CDT 2012 Tony Lindgren <tony@atomide.com> ARM: OMAP: Split plat-omap/i2c.c into mach-omap1 and mach-omap2
There's no need to keep the device related things in the
common i2c.c as omap2+ is using hwmod. Split the code to
mach-omap1 and mach-omap2 parts and only leave common
code to plat-omap/i2c.c.
Note that as omap1 only has one i2c controller, we can
now remove the old device related macros.
Reviewed-by: Shubhrajyoti D <shubhrajyoti@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
|
| /openbmc/linux/arch/arm/mach-omap1/ |
| H A D | i2c.c | diff 3a8761c0272c961c707e5af2eb0179adf3ef7e14 Mon Oct 08 11:11:22 CDT 2012 Tony Lindgren <tony@atomide.com> ARM: OMAP: Split plat-omap/i2c.c into mach-omap1 and mach-omap2
There's no need to keep the device related things in the
common i2c.c as omap2+ is using hwmod. Split the code to
mach-omap1 and mach-omap2 parts and only leave common
code to plat-omap/i2c.c.
Note that as omap1 only has one i2c controller, we can
now remove the old device related macros.
Reviewed-by: Shubhrajyoti D <shubhrajyoti@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
|
| H A D | common.h | diff 3a8761c0272c961c707e5af2eb0179adf3ef7e14 Mon Oct 08 11:11:22 CDT 2012 Tony Lindgren <tony@atomide.com> ARM: OMAP: Split plat-omap/i2c.c into mach-omap1 and mach-omap2
There's no need to keep the device related things in the
common i2c.c as omap2+ is using hwmod. Split the code to
mach-omap1 and mach-omap2 parts and only leave common
code to plat-omap/i2c.c.
Note that as omap1 only has one i2c controller, we can
now remove the old device related macros.
Reviewed-by: Shubhrajyoti D <shubhrajyoti@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
|