- 13 2月, 2016 4 次提交
-
-
由 Adam Ford 提交于
This patch defines the pin muxing to configure the hsusb0 through the twl4030 PMIC, because we can't always assume the bootloader will do it correctly. Signed-off-by: NAdam Ford <aford173@gmail.com> Signed-off-by: NTony Lindgren <tony@atomide.com>
-
由 Adam Ford 提交于
The devkit has an AT25 EEPROM on MCSPI1. Enable this with default parameters. Signed-off-by: NAdam Ford <aford173@gmail.com> Signed-off-by: NTony Lindgren <tony@atomide.com>
-
由 Adam Ford 提交于
Setup regulator and fix pin muxing to allow Panel to sleep and wake from sleep for some low power improvements. Signed-off-by: NAdam Ford <aford173@gmail.com> Signed-off-by: NTony Lindgren <tony@atomide.com>
-
由 Adam Ford 提交于
The Logic PD Torpedo standard kits come with a SOM populated to us an 8-bit parallel camera interface. This patch pin muxes the omap3-isp pins, sets the MT9P031 clicks, and configures the i2c2 bus to communicate with the mt9p031 on address 0x48. I have not done a lot of testing, but when modprobing mt9p031, then omap3-isp, the board responds with MT9P031 detected at address 0x48. Signed-off-by: NAdam Ford <aford173@gmail.com> Signed-off-by: NTony Lindgren <tony@atomide.com>
-
- 22 12月, 2015 1 次提交
-
-
由 Adam Ford 提交于
The development kit uses a TSC2004 chip attached to I2C3. Signed-off-by: NAdam Ford <aford173@gmail.com> Signed-off-by: NTony Lindgren <tony@atomide.com>
-
- 18 12月, 2015 3 次提交
-
-
由 Adam Ford 提交于
Revert 6f0f6c40b66 ("ARM: dts: Set VAUX1 and VAUX4 on Logic PD Torpedo") because it It was already done and it's just a duplicate. See: 2d11961f ("ARM: dts: Set VAUX1 and VAUX4 to 3.0V and 1.8V respectively") Signed-off-by: NAdam Ford <aford173@gmail.com> Signed-off-by: NTony Lindgren <tony@atomide.com>
-
由 Adam Ford 提交于
Add basic support for Logic PD type 15 display for older development kits. This uses GPIO for the backlight. Signed-off-by: NAdam Ford <aford173@gmail.com> Signed-off-by: NTony Lindgren <tony@atomide.com>
-
由 Sudeep Holla 提交于
Though the keyboard and other driver will continue to support the legacy "gpio-key,wakeup", "linux,wakeup" boolean property to enable the wakeup source, "wakeup-source" is the new standard binding. This patch replaces all the legacy wakeup properties with the unified "wakeup-source" property in order to avoid any futher copy-paste duplication. Cc: "Benoît Cousson" <bcousson@baylibre.com> Cc: Tony Lindgren <tony@atomide.com> Cc: linux-omap@vger.kernel.org Signed-off-by: NSudeep Holla <sudeep.holla@arm.com> Signed-off-by: NTony Lindgren <tony@atomide.com>
-
- 01 12月, 2015 3 次提交
-
-
由 Adam Ford 提交于
The schematic expects VAUX1 to be 3.0V attached to the debug port. The schematic expects VAUX4 to be 1.8V. VAUX4 powers VDDS_CSI2 on processor. Signed-off-by: NAdam Ford <adam.ford@logicpd.com> Signed-off-by: NTony Lindgren <tony@atomide.com>
-
由 Adam Ford 提交于
The development kit schematic expects VAUX1 to be 3.0V. Most users use the development kit as a reference. The development kit schematic expects VAUX4 to be 1.8V. VAUX4 powers VDDS_CSI2 on processor. If the voltage is too high it could damage the processor. If it's too low, it won't work. Signed-off-by: NTony Lindgren <tony@atomide.com>
-
由 Adam Ford 提交于
Use the TWL4030 Codec with mcbsp2 on Torpedo. Signed-off-by: NAdam Ford <adam.ford@logicpd.com> Signed-off-by: NTony Lindgren <tony@atomide.com>
-
- 19 10月, 2015 1 次提交
-
-
由 Tony Lindgren 提交于
Some omaps are producing imprecise external aborts because we are wrongly trying to init SRAM for device tree based booting. Only omap3 is still using the legacy SRAM code, so we need to make it omap3 specific. Otherwise we can get errors like this on at least dm814x: Unhandled fault: imprecise external abort (0xc06) at 0xc08b156c ... (omap_rev) from [<c08b12e0>] (omap_sram_init+0xf8/0x3e0) (omap_sram_init) from [<c08aca0c>] (omap_sdrc_init+0x10/0xb0) (omap_sdrc_init) from [<c08b581c>] (pdata_quirks_init+0x18/0x44) (pdata_quirks_init) from [<c08b5478>] (omap_generic_init+0x10/0x1c) (omap_generic_init) from [<c08a57e0>] (customize_machine+0x1c/0x40) (customize_machine) from [<c00098a4>] (do_one_initcall+0x80/0x1dc) (do_one_initcall) from [<c08a2ec4>] (kernel_init_freeable+0x218/0x2e8) (kernel_init_freeable) from [<c063a554>] (kernel_init+0x8/0xec) (kernel_init) from [<c000f890>] (ret_from_fork+0x14/0x24) Let's fix the issue by making sure omap_sdrc_init only gets called for omap3. To do that, we need to have compatible "ti,omap3" in the dts files. And let's also use "ti,omap3630" instead of "ti,omap36xx" like we're supposed to. Signed-off-by: NTony Lindgren <tony@atomide.com>
-
- 21 5月, 2015 1 次提交
-
-
由 Tony Lindgren 提交于
The LogicPD Torpedo DM3730 devkit consists of a base board and two processor boards. One of the processor boards has a WLAN and the other one does not. Let's set up basic dts file so we can move to device tree only based booting over next few merge windows. So far I've tested that UARTs, MMC1, USB OTG, smsc911x, and basic PM support works. Note that the wireless support in kernel for wl1283 seems to be broken, it tries to load wl127x-nvs.bin instead of wl128x-nvs.bin with firmware. Cc: Tim Nordell <tim.nordell@logicpd.com> Signed-off-by: NTony Lindgren <tony@atomide.com>
-