> -Original Message-
> From: Cousson, Benoit
> Sent: Tuesday, June 15, 2010 10:53 PM
> To: Varadarajan, Charulatha
> Cc: davi...@pacbell.net; broo...@opensource.wolfsonmicro.com; a...@linux-
> foundation.org; linux-omap@vger.kernel.org; p...@pwsan.com; Nayak, Rajendra;
> khil...@deeproots
> -Original Message-
> From: Cousson, Benoit
> Sent: Tuesday, June 15, 2010 10:10 PM
> To: Varadarajan, Charulatha
> Cc: davi...@pacbell.net; broo...@opensource.wolfsonmicro.com; a...@linux-
> foundation.org; linux-omap@vger.kernel.org; p...@pwsan.com; Nayak, Rajendra;
> khil...@deeproots
Han Wang wrote:
Hi,
I am testing the 2.6.35-rc1 pm branch code on Overo. The system
boots ok. (I can provide booting log if that is necessary) However,
when I use "echo mem > /sys/power/state" to send overo to sleep and
wake it up by enter a key into serial console. I got garbage
characters in
Hi Ohad,
From: ext Ohad Ben-Cohen
Subject: Re: [PATCH v3 4/4] omap: mailbox: convert block api to kfifo
Date: Wed, 16 Jun 2010 07:09:13 +0200
> On Tue, Jun 15, 2010 at 3:04 AM, Hiroshi DOYU wrote:
>> Fair enough.
>
> Thanks, I'll prepare them and resubmit
You can use the following branch whic
On Tue, Jun 15, 2010 at 3:04 AM, Hiroshi DOYU wrote:
> Fair enough.
Thanks, I'll prepare them and resubmit
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.h
Hi,
I am testing the 2.6.35-rc1 pm branch code on Overo. The system
boots ok. (I can provide booting log if that is necessary) However,
when I use "echo mem > /sys/power/state" to send overo to sleep and
wake it up by enter a key into serial console. I got garbage
characters in the serial consol
On Tue, 2010-06-15 at 14:55 -0700, David Brownell wrote:
> > > > When going from PREEMPT_VOLUNTARY to PREEMPT_NONE
> > the problem goes away.
>
> Have you found whether this is a problem
> with the OMAP HSMMC driver
> versus the MMC/SD framework code
>
Not yet - I'm in the code, investigating.
> > > When going from PREEMPT_VOLUNTARY to PREEMPT_NONE
> the problem goes away.
Have you found whether this is a problem
with the OMAP HSMMC driver
versus the MMC/SD framework code
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vge
On Tue, 2010-06-15 at 20:58 +0530, Venkatraman S wrote:
> Mathieu Poirier wrote:
> > HW: Beagleboard rev. C2 and C4
> > Processor: OMAP3
> > Kernel: 2.6.35-rc2
> > Driver: mmci-omap-hs
> >
> > I am faced with an SDHC card problem on a beagleboard. Some cards
> > cannot be initialized on startup w
On 6/15/2010 5:05 PM, Varadarajan, Charulatha wrote:
From: Charulatha V
This patch adds support for handling GPIO as a HWMOD FW adapted
platform device for OMAP2PLUS chips.
gpio_init needs to be done before machine_init functions access gpio APIs.
Hence gpio_init is made as a postcore_initcall.
Hi Charu,
On 6/15/2010 5:05 PM, Varadarajan, Charulatha wrote:
From: Charulatha V
This patch adds gpio_dev_attr to OMAP4 gpio hwmod structure. This patch
also corrects the gpio .main_clk and .clk fields in gpio hwmod structures.
Signed-off-by: Charulatha V
---
arch/arm/mach-omap2/omap_hwmod_
Mathieu Poirier wrote:
> HW: Beagleboard rev. C2 and C4
> Processor: OMAP3
> Kernel: 2.6.35-rc2
> Driver: mmci-omap-hs
>
> I am faced with an SDHC card problem on a beagleboard. Some cards
> cannot be initialized on startup while others work perfectly. I tracked
> the issue down to one single k
From: Charulatha V
This patch series makes OMAP2PLUS specific GPIO implemented in HWMOD
FW way. This is done by implementing GPIO module in platform device model.
This patch series is generated on "origin/pm-wip/hwmods-omap4".
This patch series is created on top of the following two patches:
-
From: Charulatha V
This patch adds support for handling OMAP15xx specific gpio_init
by providing platform device data and doing device registration.
Signed-off-by: Charulatha V
---
arch/arm/mach-omap1/gpio15xx.c | 102
1 files changed, 102 insertions(+
From: Charulatha V
Add hwmod structures for GPIO module on OMAP243X
Signed-off-by: Charulatha V
---
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 279
1 files changed, 279 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_2430_data.c
b/arc
From: Charulatha V
This patch populates omap24xx.h, omap34xx.h and omap44xx.h files
with SoC specific GPIO base addresses. This would be later used
while creating GPIO hwmod structures.
---
arch/arm/plat-omap/include/plat/omap24xx.h | 12
arch/arm/plat-omap/include/plat/omap34xx.h
From: Charulatha V
This patch introduces platform_data structure for GPIO
so that GPIO module can be implemented in platform device model.
Signed-off-by: Charulatha V
---
arch/arm/plat-omap/include/plat/gpio.h | 21 +
1 files changed, 21 insertions(+), 0 deletions(-)
dif
From: Charulatha V
This is in prepartion for implementing GPIO as a platform device.
gpio bank's base addresses are moved from gpio.c to plat/gpio.h.
This patch also modifies omap_gpio_init() to make use of
omap_gpio_chip_init() and omap_gpio_mod_init(). omap_gpio_mod_init() does
the module init
From: Charulatha V
Add hwmod structures for GPIO module on OMAP242X
Signed-off-by: Charulatha V
---
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 228
1 files changed, 228 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_2420_data.c
b/arc
From: Charulatha V
This patch adds support for handling OMAP7xx specific gpio_init
by providing platform device data and doing device registration.
Signed-off-by: Charulatha V
---
arch/arm/mach-omap1/gpio7xx.c | 274 +
1 files changed, 274 insertions(+)
From: Charulatha V
This patch adds gpio_dev_attr to OMAP4 gpio hwmod structure. This patch
also corrects the gpio .main_clk and .clk fields in gpio hwmod structures.
Signed-off-by: Charulatha V
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 37 +++-
1 files changed,
From: Charulatha V
This patch adds support for handling GPIO as a HWMOD FW adapted
platform device for OMAP2PLUS chips.
gpio_init needs to be done before machine_init functions access gpio APIs.
Hence gpio_init is made as a postcore_initcall.
Signed-off-by: Charulatha V
---
arch/arm/mach-omap
From: Charulatha V
This patch adds support for handling OMAP16xx specific gpio_init
by providing platform device data and doing device registration.
Signed-off-by: Charulatha V
---
arch/arm/mach-omap1/gpio16xx.c | 208
1 files changed, 208 insertions(+
From: Charulatha V
This patch removes the usage of omap_gpio_init() from all
omap board files since omap_gpio_init() does nothing, after gpio
is implemented as a platform device.
Signed-off-by: Charulatha V
---
arch/arm/mach-omap1/board-ams-delta.c |1 -
arch/arm/mach-omap1/board-fsam
From: Charulatha V
This patch implements GPIO as a platform device. Also it
implements OMAP2PLUS specific GPIO as HWMOD FW adapted device.
OMAP2PLUS GPIO uses runtime APIs.
GPIO APIs are used in machine_init functions. Hence it is
required to complete GPIO probe before machine_init. Therefore
GP
From: Charulatha V
Add hwmod structures for GPIO module on OMAP3
Signed-off-by: Charulatha V
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 366
1 files changed, 366 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/o
HW: Beagleboard rev. C2 and C4
Processor: OMAP3
Kernel: 2.6.35-rc2
Driver: mmci-omap-hs
I am faced with an SDHC card problem on a beagleboard. Some cards
cannot be initialized on startup while others work perfectly. I tracked
the issue down to one single kernel config: PREEMPT_VOLUNTARY.
When
Adding board configuration for the tmp105
temperature sensor. The interface to the sensor
is I2C.
Signed-off-by: Shubhrajyoti D
---
arch/arm/mach-omap2/board-4430sdp.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
mode change 100644 => 100755 arch/arm/mach-omap2/board-4430sd
Tony,
> -Original Message-
> From: Vimal Singh [mailto:vimal.neww...@gmail.com]
> Sent: Tuesday, June 08, 2010 10:43 PM
> To: Ghorai, Sukumar
> Cc: linux-omap@vger.kernel.org; linux-...@lists.infradead.org;
> t...@atomide.com; m...@compulab.co.il
> Subject: Re: [PATCH v5 0/3] omap3 nand: c
I have a urgent message to share with you get back to me for details...
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Tomi,
> -Original Message-
> From: Guruswamy, Senthilvadivu
> Sent: Thursday, June 10, 2010 4:54 PM
> To: linux-omap@vger.kernel.org; linux-fb...@vger.kernel.org;
> t...@atomide.com; tomi.valkei...@nokia.com; Hiremath, Vaibhav
> Cc: Guruswamy, Senthilvadivu
> Subject: [PATCH v3 3/3] DSS
From: Kishore Kadiyala
This patch improves low speeds for SD cards.
OMAP-MMC controller's can support maximum bus width of '8'.
when bus width is mentioned as "8" in controller data,the SD
stack will check whether bus width is "4" and if not it will
set bus width to "1" and there by degrading per
Hi Ohad,
From: ext Ohad Ben-Cohen
Subject: Re: [PATCH v3 4/4] omap: mailbox: convert block api to kfifo
Date: Tue, 15 Jun 2010 06:43:21 +0200
> Hi Hiroshi,
>
> On Mon, Jun 14, 2010 at 3:58 AM, Hiroshi DOYU wrote:
>> Does dspbridge really need its own defered work for sending mailbox
>> message
Sorry its Line wrapped and please drop this, Will be reposting the same.
Regards,
Kishore
On Mon, Jun 14, 2010 at 9:40 PM, kishore kadiyala
wrote:
> This patch improves low speeds for SD cards.
> OMAP-MMC controller's can support maximum bus width of '8'.
> when bus width is mentioned as "8" in
From: "ext C.A, Subramaniam"
Subject: RE: [PATCH v3 4/4] omap: mailbox: convert block api to kfifo
Date: Mon, 14 Jun 2010 17:56:35 +0200
> Hi Ohad/Hiroshi,
>
> Good to see the new mailbox requirements. While we are at it can we add some
> more :)?
>
> * Make the mailbox as a generic driver.
>
35 matches
Mail list logo
