- 08 Apr, 2013 21 commits
-
-
Florian Vaussard authored
Add device-tree support for the GPMC controller on the OMAP3. Signed-off-by:
Florian Vaussard <florian.vaussard@epfl.ch> Signed-off-by:
Benoit Cousson <benoit.cousson@linaro.org>
-
Sourav Poddar authored
Add mcspi node and pinmux data for omap5 mcspi controller. Tested on omap5430 evm with 3.8-rc6 custom kernel. Signed-off-by:
Sourav Poddar <sourav.poddar@ti.com> Signed-off-by:
-
Felipe Balbi authored
Add all 4 mcspi instances to omap5.dtsi file. Signed-off-by:
Felipe Balbi <balbi@ti.com> Signed-off-by:
-
Sourav Poddar authored
Booting 3.8-rc6 on omap4 panda results in the following error [ 0.444427] omap_i2c 48070000.i2c: did not get pins for i2c error: -19 [ 0.445770] omap_i2c 48070000.i2c: bus 0 rev0.11 at 400 kHz [ 0.473937] omap_i2c 48072000.i2c: did not get pins for i2c error: -19 [ 0.474670] omap_i2c 48072000.i2c: bus 1 rev0.11 at 400 kHz [ 0.474822] omap_i2c 48060000.i2c: did not get pins for i2c error: -19 [ 0.476379] omap_i2c 48060000.i2c: bus 2 rev0.11 at 100 kHz [ 0.477294] omap_i2c 48350000.i2c: did not get pins for i2c error: -19 [ 0.477996] omap_i2c 48350000.i2c: bus 3 rev0.11 at 400 kHz [ 0.483398] Switching to clocksource 32k_counter This happens because omap4 panda dts file is not adapted to use i2c through pinctrl framework. Populating i2c pinctrl data to get rid of the error. Tested on omap4460 panda with 3.8-rc6 kernel. Signed-off-by:
Luciano Coelho <coelho@ti.com> Signed-off-by:
-
Sourav Poddar authored
Booting 3.8-rc6 on omap 5430evm results in the following error omap_i2c 48070000.i2c: did not get pins for i2c error: -19 [ 1.024261] omap_i2c 48070000.i2c: bus 0 rev0.12 at 100 kHz [ 1.030181] omap_i2c 48072000.i2c: did not get pins for i2c error: -19 [ 1.037384] omap_i2c 48072000.i2c: bus 1 rev0.12 at 400 kHz [ 1.043762] omap_i2c 48060000.i2c: did not get pins for i2c error: -19 [ 1.050964] omap_i2c 48060000.i2c: bus 2 rev0.12 at 100 kHz [ 1.056823] omap_i2c 4807a000.i2c: did not get pins for i2c error: -19 [ 1.064025] omap_i2c 4807a000.i2c: bus 3 rev0.12 at 400 kHz This happens because omap5 dts file is not adapted to use i2c through pinctrl framework. Populating i2c pinctrl data to get rid of the error. Tested on omap5430 evm with 3.8-rc6 kernel. Signed-off-by:
-
Florian Vaussard authored
Add the needed sections to enable audio support on Overo. Signed-off-by:
-
Sourav Poddar authored
Booting 3.8-rc6 on omap 4430sdp results in the following error omap_i2c 48070000.i2c: did not get pins for i2c error: -19 [ 1.024261] omap_i2c 48070000.i2c: bus 0 rev0.12 at 100 kHz [ 1.030181] omap_i2c 48072000.i2c: did not get pins for i2c error: -19 [ 1.037384] omap_i2c 48072000.i2c: bus 1 rev0.12 at 400 kHz [ 1.043762] omap_i2c 48060000.i2c: did not get pins for i2c error: -19 [ 1.050964] omap_i2c 48060000.i2c: bus 2 rev0.12 at 100 kHz [ 1.056823] omap_i2c 4807a000.i2c: did not get pins for i2c error: -19 [ 1.064025] omap_i2c 4807a000.i2c: bus 3 rev0.12 at 400 kHz This happens because omap4 dts file is not adapted to use i2c through pinctrl framework. Populating i2c pinctrl data to get rid of the error. Tested on omap4430 sdp with 3.8-rc6 kernel. Signed-off-by:
Santosh Shilimkar <santosh.shilimkar@ti.com> Signed-off-by:
-
Florian Vaussard authored
Convert the on-board LED connected to the TWL4030 (LEDB) to use pwm-leds. Signed-off-by:
-
Peter Ujfalusi authored
Section to describe the backlight for the LCD panels. Signed-off-by:
Peter Ujfalusi <peter.ujfalusi@ti.com> Signed-off-by:
-
Peter Ujfalusi authored
Sections to describe the pwm-leds in the system. Signed-off-by:
-
Peter Ujfalusi authored
We have proper driver stack to handle the pmu_stat LED which is connected PWMB of twl4030. Signed-off-by:
-
Peter Ujfalusi authored
Enable support for the PWMs and LED as PWM drivers. Signed-off-by:
-
Peter Ujfalusi authored
Enable support for the PWMs and LEDs as PWM drivers. Signed-off-by:
-
AnilKumar Ch authored
Add a new address space/memory resource to d_can device tree node. D_CAN RAM initialization is achieved through RAMINIT register which is part of AM33XX control module address space. D_CAN RAM init or de-init should be done by writing instance corresponding value to control module register. Till we have a separate control module driver to write to control module, d_can driver will handle the register writes to control module by itself. So a new address space to represent this control module register is added to d_can driver. Signed-off-by:
AnilKumar Ch <anilkumar@ti.com> Acked-by:
Marc Kleine-Budde <mkl@pengutronix.de> Signed-off-by:
-
AnilKumar Ch authored
Add d_can instances to aliases node to get the D_CAN instance number from the driver. To initialize D_CAN message RAM, corresponding instance number is required. To initialize instance 0 message RAM then 0x1 should be written and for instance 1 message RAM, 0x2 should be written to control module register. With device-tree framework ip instance number is "-1" by default for all instances. To get device id/instance number then modules should be added to DT "aliases" node. of_alias_get_id() gives the device id number based on number of alias nodes present in "aliases node". Signed-off-by:
-
Matthias Brugger authored
This is a follow-up to Javier Martinez effort adding initial device tree support to IGEP technology devices [1]. It adds uart1 and uart2 bindings to the generic dtsi for the IGEP boards. [1] http://www.spinics.net/lists/linux-omap/msg83409.htmlSigned-off-by:
Matthias Brugger <matthias.bgg@gmail.com> Signed-off-by:
-
Javier Martinez Canillas authored
ISEE IGEP COM Module is an TI OMAP3 SoC computer on module. This patch adds an initial device tree support to boot an IGEP COM Module from the MMC/SD. Signed-off-by:
Javier Martinez Canillas <javier.martinez@collabora.co.uk> Tested-by:
Enric Balletbo i Serra <eballetbo@gmail.com> [b-cousson@ti.com: Update the Makefile for 3.8-rc2] Signed-off-by:
-
Javier Martinez Canillas authored
ISEE IGEPv2 is an TI OMAP3 SoC based embedded board. This patch adds an initial device tree support to boot an IGEPv2 from the MMC/SD. Currently is working everything that is supported by DT on OMAP3 SoCs (MMC/SD, GPIO LEDs, EEPROM, TWL4030 audio). Signed-off-by:
-
Javier Martinez Canillas authored
Add a generic .dtsi device tree source file for the common characteristics across IGEP Technology devices. Signed-off-by:
-
AnilKumar Ch authored
Rename I2C and GPIO nodes according to AM33XX TRM. According to AM33XX TRM device instances are starting from "0" like i2c0, i2c1 and i2c3. Signed-off-by:
Pantelis Antoniou <panto@antoniou-consulting.com> [panto@antoniou-consulting.com: initial patch by pantelis's] Signed-off-by:
-
Benoit Cousson authored
Merge tag 'omap-devel-b-for-3.10' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into for_3.10/dts_merged
-
- 02 Apr, 2013 19 commits
-
-
Roger Quadros authored
Provide RESET and Power regulators for the USB PHY, the USB Host port mode and the PHY device. Also provide pin multiplexer information for USB host pins. CC: Benoît Cousson <b-cousson@ti.com> Signed-off-by:
Roger Quadros <rogerq@ti.com> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
Roger Quadros authored
Adds device nodes for HS USB Host module, TLL module, OHCI and EHCI controllers. CC: Benoît Cousson <b-cousson@ti.com> Signed-off-by:
-
Roger Quadros authored
Adds device nodes for HS USB Host module, TLL module, OHCI and EHCI controllers. CC: Benoît Cousson <b-cousson@ti.com> Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's RESET regulator and the NOP PHY device. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's RESET regulator and the NOP PHY device. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's RESET regulator and the NOP PHY device. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's RESET regulator and the NOP PHY device. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's RESET regulator and NOP PHY device. VAUX2 supplies the PHY's VCC. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's RESET regulator and the NOP PHY device. VAUX2 supplies the PHY's VCC. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's RESET regulators and the NOP PHY devices. Signed-off-by:
-
Roger Quadros authored
Remove deprecated USBHS platform data. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's RESET regulators and the NOP PHY devices. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's RESET regulators and the NOP PHY devices. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's RESET regulators and the NOP PHY device. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's VCC and RESET regulators and the NOP PHY device. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's RESET regulators and the NOP PHY devices. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's RESET regulators and the NOP PHY devices. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's VCC and RESET regulators and the NOP PHY device. Signed-off-by:
-
Roger Quadros authored
Use usbhs_init_phys() to register the PHY's VCC and RESET regulators and the NOP PHY device. Get rid of managing the PHY clock as it will be done by the PHY driver. For that to work we create a clock alias that links the PHY clock name to the PHY device name. Signed-off-by:
-
