On Sat, Jun 13, 2009 at 4:13 AM, Kevin
Hilman wrote:
> Ulrik Bech Hald writes:
>
>> This patch contains two bugfixes:
>>
>> 1)In omap_wdt_probe() the watchdog is reset and disabled. This
>> requires register access and the clks needs to be enabled temporarily
>>
>> 2)In omap_wdt_open() the timer r
On Sat, Jun 13, 2009 at 3:40 AM, Madhusudhan wrote:
> Hugo,
>
> Your CLK and CMD line mux does not look correct to me.
>
> Try the below settings.
>
> MUX_CFG_34XX("AF10_3430_MMC3_CLK", 0x5d8,
> OMAP34XX_MUX_MODE2 | OMAP34XX_PIN_INPUT_PULLUP)
> MUX_CFG_34XX("AC3_3430_MMC3_CMD", 0x1d
Thanks for that. These don't help specifically with my problem, but
are none-the-less valuable, and seem to make MMC more reliable when
the system is heavily loaded.
On Fri, Jun 12, 2009 at 7:25 PM, Adrian Hunter wrote:
> We have fixed a few bugs in omap_hsmmc.c that we have not had time
> to sen
This fixes the positioning of " in MODULE_AUTHOR, which is currently
causing a build failure on latest git with CONFIG_OMAP_MBOX_FWK=m; the
original breakage appears to date from the end of last year in
a5abbbe52b7e89a7633319c5417bd4331f7ac8ed
Signed-Off-By: Jonathan McDowell
-
diff --git a/
On Fri, Jun 12, 2009 at 10:01 PM, Felipe Balbi wrote:
> On Fri, Jun 12, 2009 at 04:50:09PM +0200, ext Pandita, Vikram wrote:
>>
>>
>> >-Original Message-
>> >From: Menon, Nishanth
>> >Sent: Friday, June 12, 2009 9:46 AM
>> >To: felipe.ba...@nokia.com
>> >Cc: Pandita, Vikram; linux-omap@vger
Update defconfig for Zoom2 to include
TWL4030 core
TWL4030 drivers (bci, gpio, keypad, usb, mmc)
Also sync the defconfig after issuing a menuconfig
Signed-off-by: Vikram Pandita
---
arch/arm/configs/omap_zoom2_defconfig | 484 +++-
1 files changed, 408 insertions(+)
Add TWL4030 CORE and TWL4030 drivers to Zoom2 board file
TWL drivers enabled are:
bci
madc
usb
keypad
mmc
Signed-off-by: Vikram Pandita
---
arch/arm/mach-omap2/board-zoom2.c | 208 +++--
1 files changed, 197 insertions(+),
For OMAP3 add MMC1 MMC2 and MMC3 pin mux
Signed-off-by: Chikkature Rajashekar
Signed-off-by: Vikram Pandita
---
arch/arm/mach-omap2/devices.c | 33 ++
arch/arm/mach-omap2/mux.c | 49 +
arch/arm/plat-omap/include/mach/mu
Ulrik Bech Hald writes:
> The functionality of omap_type() is needed for eg. watchdog
> device registration to distinguish different device types.
>
> Signed-off-by: Ulrik Bech Hald
Collision. :) I have an add-back of this in my fixes queue which I
just posted as well.
Kevin
> ---
> arch/arm
The omap_type() function is added and returns the DEVICETYPE field of
the CONTROL_STATUS register. The result can be used for conditional
code based on whether device is GP, EMU or HS.
Signed-off-by: Kevin Hilman
---
arch/arm/mach-omap2/id.c | 22 ++
1 files changed, 22 in
From: Kalle Jokiniemi
This patch enables MStandby smart-idle mode, autoidle smartidle mode,
and the autoidle bit for DMA4_OCP_SYSCONFIG.
Signed-off-by: Kalle Jokiniemi
Signed-off-by: Tony Lindgren
Signed-off-by: Kevin Hilman
---
arch/arm/plat-omap/dma.c | 13 +
arc
Here's a couple patches to add-back some feature dropped in the
mainline sync. These are needed for the PM branch among other things.
Applies to linux-omap master.
Kevin
Kalle Jokiniemi (1): OMAP3: DMA: Enable idlemodes for DMA OCP
Kevin Hilman (1):
OMAP2/3: SoC IDs: add omap_type() for dete
Deos any one have any comments on by-passing the get_user_pages function for
the buffers that meets the following condition ? If not, this code will be
merged into dspbridge tree.
if ((vma->vm_flags & VM_IO) | ((vma->vm_flags & VM_RESERVED) &&
+ (~pgprot_val(vma->vm_page_prot) &
This patch contains two bugfixes:
1)In omap_wdt_probe() the watchdog is reset and disabled. This
requires register access and the clks needs to be enabled temporarily
2)In omap_wdt_open() the timer register needs to be reloaded
to trigger a new timer value (the default of 60s)
Tested on OMAP34xx
The functionality of omap_type() is needed for eg. watchdog
device registration to distinguish different device types.
Signed-off-by: Ulrik Bech Hald
---
arch/arm/mach-omap2/id.c | 21 +
1 files changed, 21 insertions(+), 0 deletions(-)
mode change 100644 => 100755 arch/ar
On Fri, 12 Jun 2009 12:32:51 -0500
Vikram Pandita wrote:
> There is currently no provision for passing IRQ trigger flags for
> serial IRQs with triggering requirements (such as GPIO IRQs.)
>
> This patch adds UPF_IRQ_TRIG_* flags which map on to IRQF_TRIGGER_*
> flags.
>
> Signed-off-by: Vikram
>-Original Message-
>From: Felipe Balbi [mailto:felipe.ba...@nokia.com]
>Sent: Friday, June 12, 2009 2:02 PM
>To: Pandita, Vikram
>Cc: Menon, Nishanth; Balbi Felipe (Nokia-D/Helsinki);
>linux-omap@vger.kernel.org
>Subject: Re: [PATCH 1/2] Serial: Define IRQ flags for 8250 driver
>
>On Fr
On Fri, Jun 12, 2009 at 04:50:09PM +0200, ext Pandita, Vikram wrote:
>
>
> >-Original Message-
> >From: Menon, Nishanth
> >Sent: Friday, June 12, 2009 9:46 AM
> >To: felipe.ba...@nokia.com
> >Cc: Pandita, Vikram; linux-omap@vger.kernel.org
> >Subject: RE: [PATCH 1/2] Serial: Define IRQ fl
There is currently no provision for passing IRQ trigger flags for
serial IRQs with triggering requirements (such as GPIO IRQs.)
This patch adds UPF_IRQ_TRIG_* flags which map on to IRQF_TRIGGER_*
flags.
Signed-off-by: Vikram Pandita
Acked-by: Kevin Hilman
---
drivers/serial/8250.c | 10
On Thu, 11 Jun 2009 19:53:50 -0500
Vikram Pandita wrote:
> Boards with serial irq High/Low/Rising/Falling IRQ requirement
> do not work today
>
> 8250 serial driver does not have provision to pass on IRQ flags
> from platform_device
>
> This is requred for OMAP Zoom2 board for which Serial IRQ
Vikram Pandita writes:
> Boards with serial irq High/Low/Rising/Falling IRQ requirement
> do not work today
>
> 8250 serial driver does not have provision to pass on IRQ flags
> from platform_device
>
> This is requred for OMAP Zoom2 board for which Serial IRQ trigger
> is IRQF_TRIGGER_HIGH
>
> S
Ulrik Bech Hald writes:
> This patch contains two bugfixes:
>
> 1)In omap_wdt_probe() the watchdog is reset and disabled. This
> requires register access and the clks needs to be enabled temporarily
>
> 2)In omap_wdt_open() the timer register needs to be reloaded
> to trigger a new timer value (t
This patch contains two bugfixes:
1)In omap_wdt_probe() the watchdog is reset and disabled. This
requires register access and the clks needs to be enabled temporarily
2)In omap_wdt_open() the timer register needs to be reloaded
to trigger a new timer value (the default of 60s)
Signed-off-by: Ulr
Hi Doyu-san,
Thanks for providing your comments.
Please see my below comments.
> I agree that it's necessary to build up mbox instances with those IDs
> dynamically.
>
> We may want to add one more argument "struct omap_mbox" in
> omap_mbox_set() as below:
>
> arch/arm/mach-omap2/mailbox.c:
>
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Adrian Hunter
Sent: Friday, June 12, 2009 2:26 AM
To: Hugo Vincent
Cc: Grazvydas Ignotas; Pandita, Vikram; linux-omap; General mailing list for
gumstix users.
Subject: Re: OMAP
Regards,
Nishanth Menon
> -Original Message-
> From: Pandita, Vikram
> Sent: Friday, June 12, 2009 9:50 AM
> To: Menon, Nishanth; felipe.ba...@nokia.com
> Cc: linux-omap@vger.kernel.org
> Subject: RE: [PATCH 1/2] Serial: Define IRQ flags for 8250 driver
>
>
>
> >-Original Message-
>-Original Message-
>From: Menon, Nishanth
>Sent: Friday, June 12, 2009 9:46 AM
>To: felipe.ba...@nokia.com
>Cc: Pandita, Vikram; linux-omap@vger.kernel.org
>Subject: RE: [PATCH 1/2] Serial: Define IRQ flags for 8250 driver
>
>> -Original Message-
>> From: Felipe Balbi [mailto:fel
> -Original Message-
> From: Felipe Balbi [mailto:felipe.ba...@nokia.com]
> Sent: Friday, June 12, 2009 1:38 AM
> To: Menon, Nishanth
> Cc: Pandita, Vikram; linux-omap@vger.kernel.org
> Subject: Re: [PATCH 1/2] Serial: Define IRQ flags for 8250 driver
>
> On Fri, Jun 12, 2009 at 03:46:37AM
And yesterday, I commited the core arch support for the da830/omap-L137
SoC to DaVinci git.
http://git.kernel.org/?p=linux/kernel/git/khilman/linux-davinci.git
This part is OMAP in name and marketing spin only. This is very much
in the davinci family of SoCs, so I expect more confusion on th
From: Eero Nurkkala
When data is read through DMA, the last element must be read separately
through the RX register. It cannot be transferred by the DMA. For further
details see e.g. OMAP3430 TRM.
Without the fix the driver causes extra clocks to be clocked to the
bus after DMA RX operations. Th
From 2766ff4a4087bae99463813b4a018ef9ebe498fc Mon Sep 17 00:00:00 2001
From: Adrian Hunter
Date: Fri, 12 Jun 2009 14:39:22 +0300
Subject: [PATCH] OMAP: gpmc-onenand: correct use of async timings
Use async timings when sync timings are not requested.
Also ensure that OneNAND is in async mode wh
From aea78b09cac91d51d31ef61a2554f3470b498cfd Mon Sep 17 00:00:00 2001
From: Adrian Hunter
Date: Fri, 12 Jun 2009 14:41:14 +0300
Subject: [PATCH] OMAP: RX51: use OneNAND sync read / write
Signed-off-by: Adrian Hunter
---
arch/arm/mach-omap2/board-rx51-peripherals.c |1 +
1 files changed, 1
Thanks a lot.
Stanley.
Syed Mohammed, Khasim wrote:
Hi,
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Tony
Lindgren
Sent: Friday, June 12, 2009 4:02 PM
To: stanley.miao; Kevin Hilman
Cc: linux-omap@vger.kernel.org
Hi Dmitry,
Thursday 11 June 2009 08:18:56 Dmitry Torokhov napisał(a):
> Hi Janusz,
>
> On Fri, Jun 05, 2009 at 12:39:39AM +0200, Janusz Krzysztofik wrote:
> > This patch adds support for exporting status of GPIO switches, configured
> > as gpio-keys buttons that generate events of type EV_SW, over
Hi,
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org
> [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Tony
> Lindgren
> Sent: Friday, June 12, 2009 4:02 PM
> To: stanley.miao; Kevin Hilman
> Cc: linux-omap@vger.kernel.org
> Subject: Re: Which directory should OMAP-L13
* stanley.miao [090612 02:53]:
> I am developing on the board OMAP-L137/L138, which is similar with
> Davinci series board. Should I put its platform file in the directory
> arch/arm/mach-davinci ? or create a new direcory arch/arch/mach-L1xx for
> it ?
>
> Any suggestions ?
If it uses DaV
I am developing on the board OMAP-L137/L138, which is similar with
Davinci series board. Should I put its platform file in the directory
arch/arm/mach-davinci ? or create a new direcory arch/arch/mach-L1xx for
it ?
Any suggestions ?
Thanks
Stanley.
--
To unsubscribe from this list: send the
Hugo Vincent wrote:
On 11/06/2009, at 9:29 PM, Grazvydas Ignotas wrote:
On Thu, Jun 11, 2009 at 10:43 AM, Hugo
Vincent wrote:
On 11/06/2009, at 6:08 PM, Peter Barada wrote:
On Thu, 2009-06-11 at 15:35 +1200, Hugo Vincent wrote:
On Thu, Jun 11, 2009 at 2:39 PM, Pandita, Vikram
Hugo
-Or
38 matches
Mail list logo
