On Wed, 2011-02-09 at 12:23 +0530, G, Manjunath Kondaiah wrote:
> On Wed, Feb 9, 2011 at 1:13 AM, Ricardo Salveti de Araujo
> wrote:
> > Function beagle_twl_gpio_setup is called after beagle_display_init, what
> > lets reset_gpio with an invalid value at the time it request
ymore.
Tested with Beagle-xM and C4.
Signed-off-by: Ricardo Salveti de Araujo
---
arch/arm/mach-omap2/board-omap3beagle.c | 22 +++---
1 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap3beagle.c
b/arch/arm/mach-omap2/board-omap3bea
Mathieu Poirier
Signed-off-by: Leann Ogasawara
Signed-off-by: Ricardo Salveti de Araujo
---
arch/arm/mach-omap2/board-omap3beagle.c | 11 ++-
1 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap3beagle.c
b/arch/arm/mach-omap2/board-omap3beagle.
for vdds_sdi.
Ricardo Salveti de Araujo (1):
omap3: beaglexm: fix DVI initialization
arch/arm/mach-omap2/board-omap3beagle.c | 33 ---
1 files changed, 17 insertions(+), 16 deletions(-)
--
1.7.2.3
--
To unsubscribe from this list: send the line "unsubs
In case in user has a OMAP3630 < ES1.2 the kernel should warn the user
about the ERRATUM, but using pr_warn instead of WARN_ON is already
enough, as there is nothing else the user can do besides changing the
board.
Signed-off-by: Ricardo Salveti de Araujo
---
v1->v2:
* Use pr_warn inst
In case in user has a OMAP3630 < ES1.2 the kernel should warn the user
about the ERRATUM, but using printk instead of WARN_ON is already
enough, as there is nothing else the user can do besides changing the
board.
Signed-off-by: Ricardo Salveti de Araujo
---
arch/arm/mach-omap2/cpuidle34x
ssary anymore.
Tested with Beagle-xM and C4.
Signed-off-by: Ricardo Salveti de Araujo
---
arch/arm/mach-omap2/board-omap3beagle.c | 17 ++---
1 files changed, 6 insertions(+), 11 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap3beagle.c
b/arch/arm/mach-omap2/board-omap3bea
Hello,
These 2 patches are basically bugfixing to make DVI work again on beagle.
Tested with Beagle-xM and C4.
Mathieu J. Poirier (1):
omap3: beagle: adding regulator supply for vdds_sdi.
Ricardo Salveti de Araujo (1):
omap3: beaglexm: fix DVI initialization
arch/arm/mach-omap2/board
From: Mathieu J. Poirier
The omapfb driver couldn't locate its display sink because of
an initialisation error in the DSS subsystem. This error was
caused by a missing 'sdi' entry in the board power regulator list.
BugLink: https://bugs.launchpad.net/bugs/597904
Signed-off-by: Mathieu J. Poiri
TQ0Ni00ZmFlLTlhODgtN2QzNjUwMzBkNDI2&hl=en
> In the mean time I will try with yours!
I'm unable to boot with your x-loader at my ES2.0 (6 and 8 layers),
however I'm able to boot it with ES1. Are you sure you're testing it
at an ES2 board?
This is what I get, it just hangs:
Tex
efconfig also ok omap4.
>>
>> Which Panda version are you using during your tests? I tried
>> omap_4430sdp_defconfig using omap4-for-tony branch at my ES2.0 and I'm
>> unable to detect the MMC.
>>
>> Do I need any other patch to make the MMC
I applied
>> > your series to current l-o master, and it works.
>> >
>> Cool!!
>
> [Ghorai] I have tested MMC/SD boot using omap3_defconfig on ZOOM3, 4430 ES2.0
> SDP, Blaze and Panda and all booting fine.
>
> And omap_4430sdp_defconfig also ok omap4.
Which Pand
At Pandaboard we have 2 status leds, so adding them with similar usage as
we have for Beagleboard (heartbeat and mmc0). The patch basically adds the
platform data required by leds-gpio driver.
Signed-off-by: Ricardo Salveti de Araujo
---
arch/arm/mach-omap2/board-omap4panda.c | 32
13 matches
Mail list logo