On Monday 17 June 2013 11:16 AM, J Keerthy wrote:
Remove code which is not necessary for a device tree boot.
Boot tested on OMAP5-UEVM board.
Signed-off-by: J Keerthy
Looks good to me.
Acked-by: Laxman Dewangan
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
t
On Fri, May 31, 2013 at 5:59 PM, Arnd Bergmann wrote:
> The bug fix 352a2d5bf "gpio/omap: ensure gpio context is initialised"
> has caused a new warning for omap1_defconfig:
>
> drivers/gpio/gpio-omap.c:1465:13: warning: 'omap_gpio_init_context' defined
> but not used [-Wunused-function]
> stat
Hi Benoit,
> -Original Message-
> From: J, KEERTHY
> Sent: Thursday, June 13, 2013 10:19 PM
> To: Cousson, Benoit
> Cc: linux-omap@vger.kernel.org; linux-ker...@vger.kernel.org;
> ldewan...@nvidia.com; grant.lik...@secretlab.ca; swar...@wwwdotorg.org;
> swar...@nvidia.com; sa...@linux.inte
* Felipe Balbi [130615 08:12]:
>
> fair enough, then let's just add those interrupts to hwmod which will,
> eventually, let us drop all of that data from hwmod.
Nope, we're already dropping the duplicate data from hwmod for
am33xx and omap4. See omap-for-v3.11/cleanup branch.
Regards,
Tony
--
On Mon, Jun 17, 2013 at 11:16:02AM +0530, J Keerthy wrote:
> Remove code which is not necessary for a device tree boot.
>
> Boot tested on OMAP5-UEVM board.
>
> Signed-off-by: J Keerthy
This looks good to me!
Acked-by: Graeme Gregory
> ---
> drivers/mfd/palmas.c | 106
> --
Remove code which is not necessary for a device tree boot.
Boot tested on OMAP5-UEVM board.
Signed-off-by: J Keerthy
---
drivers/mfd/palmas.c | 106 --
1 files changed, 0 insertions(+), 106 deletions(-)
diff --git a/drivers/mfd/palmas.c b/driver
Here are some basic OMAP test results for Linux v3.10-rc6.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.10-rc6/20130616211951/
Test summary
Build: uImage:
Pass (16/16): am33xx_only, n800_multi_omap2xxx, n800_only_a,
omap1_defconfi
On Monday 17 June 2013 10:38 AM, Hiremath, Vaibhav wrote:
>
>> -Original Message-
>> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
>> ow...@vger.kernel.org] On Behalf Of Kevin Hilman
>> Sent: Friday, June 14, 2013 7:31 PM
>> To: Paul Walmsley
>> Cc: Nayak, Rajendra; Hiremath,
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Kevin Hilman
> Sent: Friday, June 14, 2013 7:31 PM
> To: Paul Walmsley
> Cc: Nayak, Rajendra; Hiremath, Vaibhav; linux-omap@vger.kernel.org;
> linux-arm-ker...@lists.infr
On Mon, 17 Jun 2013, Jonghwan Choi wrote:
> This patch looks like it should be in the 3.9-stable tree, should we apply
> it?
Please do.
- Paul
>
> --
>
> From: "Jean-Philippe Francois "
>
> commit a93d8a1cea0899982993e9a93404c6f78b123697 upstream
>
> omap36xx_pwrdn_clk_enab
On Fri, 14 Jun 2013, Lokesh Vutla wrote:
> On Monday 10 June 2013 12:52 PM, Paul Walmsley wrote:
>
> > * 3730 Beagle XM, am335xbone, CM-T3517: uart4_rx.uart4_rx mux failure
> >- Cause unknown
> I am able to reproduce this issue on 37xx EVM using non-dt boot (dt boot
> doesn't throw this error
On Mon, 10 Jun 2013, Lokesh Vutla wrote:
> On Monday 10 June 2013 12:52 PM, Paul Walmsley wrote:
>
> > * 3730 Beagle XM, am335xbone, CM-T3517: uart4_rx.uart4_rx mux failure
> Just booted up my BeagleBone. I didn't see any error for uart4_rx in my boot
> log.
> Since I don't have other boards, I wa
On 06/14/2013 10:10 PM, Kishon Vijay Abraham I wrote:
> Modified dwc3-omap to receive connect and disconnect notification using
> extcon framework. Also did the necessary cleanups required after
> adapting to extcon framework.
>
> Signed-off-by: Kishon Vijay Abraham I
> Acked-by: Felipe Balbi
>
On Sat, 15 Jun 2013, Jarkko Nikula wrote:
> Last remaining DMA channel definitions in arch/arm/mach-omap2/dma.h
> are used only by omap_hwmod_2xxx_3xxx_ipblock_data.c and
> omap_hwmod_3xxx_data.c. Remove them by using directly DMA channel number in
> hwmod data and drop definitions with a followin
Hi Tan,
On 06/14/2013 04:32 AM, LF.Tan wrote:
>
> Hi Suman
>
> Thanks for your reply.
> I have took a look the patches you've mentioned in [1]. It is totally
> new framework from what is located in linux-next git tree now.
Yes, that is correct. The framework is different, but functionality
wise
Hi Felipe
On 06/15/2013 06:06 PM, Felipe Balbi wrote:
> On Sat, Jun 15, 2013 at 11:31:04AM +0300, Jarkko Nikula wrote:
>> Last remaining DMA channel definitions in arch/arm/mach-omap2/dma.h
>> are used only by omap_hwmod_2xxx_3xxx_ipblock_data.c and
>> omap_hwmod_3xxx_data.c. Remove them by using
Move omap_usb_config to platform data, so that OTG driver can include it.
Signed-off-by: Aaro Koskinen
---
arch/arm/mach-omap1/include/mach/usb.h | 38 +---
include/linux/platform_data/usb-omap1.h | 51 +
2 files changed, 52 insertions(+), 37
Transceivers need to manage OTG controller state on OMAP1 to enable
switching between peripheral and host modes. Provide a driver for that.
Signed-off-by: Aaro Koskinen
---
drivers/usb/phy/Kconfig| 10 +++
drivers/usb/phy/Makefile | 1 +
drivers/usb/phy/phy-omap-otg.c | 171
Add extcon field to platform data.
Signed-off-by: Aaro Koskinen
---
include/linux/platform_data/usb-omap1.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/platform_data/usb-omap1.h
b/include/linux/platform_data/usb-omap1.h
index 8c7764d..43b5ce1 100644
--- a/include/linux/p
Add platform data for Tahvo.
Signed-off-by: Aaro Koskinen
---
arch/arm/mach-omap1/board-nokia770.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/mach-omap1/board-nokia770.c
b/arch/arm/mach-omap1/board-nokia770.c
index 62a15e2..85089d8 100644
--- a/arch/arm/mach-omap1
Add Tahvo USB transceiver driver.
Based on old code from linux-omap tree. The original driver was written
by Juha Yrjölä, Tony Lindgren, and Timo Teräs.
Signed-off-by: Aaro Koskinen
---
drivers/usb/phy/Kconfig | 14 ++
drivers/usb/phy/Makefile| 1 +
drivers/usb/phy/phy-tahvo.c | 448
Hi,
These patches add support for Tahvo USB transceiver and allow using both
host and peripheral modes on Nokia 770.
Tested (peripheral mode, host mode, vbus detection) with 3.10-rc6.
History:
v2: Use extcon framework to trigger OTG driver mode changes.
v1: http://marc.info/?l=li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/13/13 19:01, Tomi Valkeinen wrote:
> On 13/06/13 18:51, Igor Grinberg wrote:
>> Hi Tomi,
>>
>> On 06/04/13 10:40, Tomi Valkeinen wrote:
>>> Hi guys,
>>
>>> I've made some big changes on the omapdss device model, which involves
>>> converting al
23 matches
Mail list logo
