lwn.git/arch/arm/mach-omap2/board-cm-t35.c, branch v4.4-rc3

ARM: OMAP2+: Remove legacy booting support for cm-t35

2015-05-04T17:53:48+00:00

We've been moving all omap2+ based systems to boot in device tree only mode for a few years now. Only omap3 has legacy booting support remaining. Most omap3 boards already have related arch/arm/boot/*.dts* files for booting with device tree. This board has support for device tree based booting, and we've been printing warnings about the legacy booting being deprecated for a few merge cycles now. Let's attempt to remove the legacy booting for it. The reason for removing the legacy booting support now rather than later is we can simply revert this patch if necessary if we run into some unexpected issues that are not trivial to fix for the device tree based booting. Cc: Dmitry Lifshitz Cc: Igor Grinberg Signed-off-by: Tony Lindgren

[media] omap3isp: Refactor device configuration structs for Device Tree

2015-04-02T19:41:01+00:00

Make omap3isp configuration data structures more suitable for consumption by the DT by separating the I2C bus information of all the sub-devices in a group and the ISP bus information from each other. The ISP bus information is made a pointer instead of being directly embedded in the struct. In the case of the DT only the sensor specific information on the ISP bus configuration is retained. The structs are renamed to reflect that. After this change the structs needed to describe device configuration can be allocated and accessed separately without those needed only in the case of platform data. The platform data related structs can be later removed once the support for platform data can be removed. Signed-off-by: Sakari Ailus Acked-by: Igor Grinberg (for cm-t35) Signed-off-by: Laurent Pinchart Signed-off-by: Mauro Carvalho Chehab

ARM: OMAP2+: Prepare to move GPMC to drivers by platform data header

2014-11-20T20:11:25+00:00

We still need to support platform data for omap3 until it's booting in device tree only mode. So let's add platform_data/omap-gpmc.h for that, and a minimal linux/omap-gpmc.h for the save and restore used by the PM code. Let's also keep a minimal mach-omap2/gpmc.h still around to avoid churn on the board-*.c files. Once omap3 boots in device tree only mode, we can drop mach-omap2/gpmc.h and we can make the data structures in platform_data/omap-gpmc.h private to the GPMC driver. Note that we can now also remove gpmc-nand.h and gpmc-onenand.h. Cc: Arnd Bergmann Acked-by: Roger Quadros Signed-off-by: Tony Lindgren

arm: omap: irq: drop omap3_intc_handle_irq()

2014-09-11T20:05:40+00:00

now that we're calling set_handle_irq() from init_irq(), we can safely drop all callers to omap3_intc_handle_irq() and its definition. Signed-off-by: Felipe Balbi Signed-off-by: Tony Lindgren

[media] ARM: omap2: cm-t35: Add regulators and clock for camera sensor

2014-02-24T16:10:14+00:00

The camera sensor will soon require regulators and clocks. Register fixed regulators for its VAA and VDD power supplies and a fixed rate clock for its master clock. Signed-off-by: Laurent Pinchart Acked-by: Igor Grinberg Acked-by: Tony Lindgren Signed-off-by: Mauro Carvalho Chehab

misc: (at24) move header to linux/platform_data/

2013-09-30T04:02:34+00:00

This patch moves the at24.h header from include/linux/i2c to include/linux/platform_data and updates existing support accordingly. It also fixes the following checkpatch warning: WARNING: please, no space before tabs #436: FILE: include/linux/platform_data/at24.h:31: + * ^Iu8 *mac_addr = ethernet_pdata->mac_addr;$ Signed-off-by: Vivien Didelot Signed-off-by: Wolfram Sang

ARM: OMAP: cm-t35: use new display drivers

2013-08-28T07:23:21+00:00

Use new display drivers for cm-t35 board. The new OMAP display drivers were merged for 3.11, and we can now change the board files to use the new ones and phase out the old ones. Signed-off-by: Tomi Valkeinen Acked-by: Tony Lindgren

ARM: OMAP: add vdds_dsi supply for omapdss_dpi.0

2013-06-12T13:59:40+00:00

DPI driver gets currently the vdds_dsi regulator via omapdss device. This is not correct, and we'll change the DPI driver to get the regulator directly via omapdss_dpi.0 device. This patch changes the relevant board files to add vdds_dsi supply for omapdss_dpi.0 device. Note that the vdds_dsi supply for omapdss device is still left there, as the current display driver uses it. When both the board files and the display driver has been changed, we can remove the unused supply. Signed-off-by: Tomi Valkeinen Signed-off-by: Tony Lindgren

ARM: OMAP: fix dsi regulator names

2013-06-12T13:59:39+00:00

board-cm-t35.c and board-ldp.c contain regulator supply entries for vdds_dsi. However, the given device name is wrong. This patch fixes the device name from omapdss_dsi1 to omapdss_dsi.0. Note that as far as I know, DSI driver is not used on these boards, so this should not have caused any problems. The DSI block can be used to generate clock for DPI, though, but that's not enabled for omap3 boards currently. Signed-off-by: Tomi Valkeinen Signed-off-by: Tony Lindgren

Merge branch 'late/clksrc' into late/cleanup

2013-05-06T21:43:45+00:00

There is no reason to keep the clksrc cleanups separate from the other cleanups, and this resolves some merge conflicts. Conflicts: arch/arm/mach-spear/spear13xx.c drivers/irqchip/Makefile