Hi,
echo'ing 'host' to the musb_hdrc/mode sysfs file triggers an oops on
BeagleBoard rev B4 with linux-omap HEAD. Passing along the trace with a
little extra debug to see if anyone happens to know what the problem is.
- Paul
r...@beagleboard:/sys# echo host > ./devices/platform/musb_hdrc/mo
This patch has been applied to the linux-omap
by youw fwiendly patch wobot.
Commit: c4df5a4d436bc3aea65cc665025d5ce62c8dfe09
PatchWorks
http://patchwork.kernel.org/patch/13863/
Git
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=c4df5a4d436bc3aea65cc665025d5ce62c8d
This patch has been applied to the linux-omap
by youw fwiendly patch wobot.
Commit: ac709382c70b02f84ba51b987fddafe3464a751b
PatchWorks
http://patchwork.kernel.org/patch/13959/
Git
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=ac709382c70b02f84ba51b987fddafe3464a
This patch has been applied to the linux-omap
by youw fwiendly patch wobot.
Commit: 7b2a455b3167755686e048c193911591c9966418
PatchWorks
http://patchwork.kernel.org/patch/14147/
Git
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=7b2a455b3167755686e048c193911591c996
On Tuesday 24 March 2009, Paul Walmsley wrote:
> MMC doesn't work after 3fe326511c66ab842ef0a09a1f4c564b1a8beecf unless
> CONFIG_REGULATOR, CONFIG_REGULATOR_TWL4030 are present in the .config.
> Add those in for all OMAP3 defconfigs. Tested on BeagleBoard, but this is
> presumably needed for a
This patch has been applied to the linux-omap
by youw fwiendly patch wobot.
Commit: 0268abf95f935c2fe45f778b2a223685e68c7823
PatchWorks
http://patchwork.kernel.org/patch/13958/
Git
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=0268abf95f935c2fe45f778b2a223685e68c
On Mon, Mar 23, 2009 at 9:47 PM, Tony Lindgren wrote:
> * ameya.pala...@nokia.com [090323 00:42]:
>> Hi Tony,
>>
>> I have collected latest patches for tidspbridge at:
>> git://gitorious.org/tidspbridge/mainline.git
>>
>> Branch is: tidspbridge
>>
>> It is based on your pm branch.
>> Can you pull
MMC doesn't work after 3fe326511c66ab842ef0a09a1f4c564b1a8beecf unless
CONFIG_REGULATOR, CONFIG_REGULATOR_TWL4030 are present in the .config.
Add those in for all OMAP3 defconfigs. Tested on BeagleBoard, but this is
presumably needed for anything with MMC and TWL4030.
Signed-off-by:
Hi,
On Tue, 24 Mar 2009, Paul Walmsley wrote:
> The BeagleBoard rev B4 here can't mount its root filesystem from MMC after
> 3fe326511c66ab842ef0a09a1f4c564b1a8beecf, "mmc-twl4030 uses regulator
> framework". This is with omap3_beagle_defconfig and rootwait in the
> kernel command line. Kern
Hi,
The BeagleBoard rev B4 here can't mount its root filesystem from MMC after
3fe326511c66ab842ef0a09a1f4c564b1a8beecf, "mmc-twl4030 uses regulator
framework". This is with omap3_beagle_defconfig and rootwait in the
kernel command line. Kernel hangs after:
Waiting for root device /dev/mmcb
On Tue, 2009-03-24 at 13:21 -0700, Kevin Hilman wrote:
> Peter Barada wrote:
> > On Tue, 2009-03-24 at 11:08 -0700, Kevin Hilman wrote:
> >> Peter Barada writes:
> >>
> >>> On Tue, 2009-03-17 at 22:21 -0700, Kevin Hilman wrote:
> FYI...
>
> The PM branch has now been rebased to tod
Peter Barada wrote:
On Tue, 2009-03-24 at 11:08 -0700, Kevin Hilman wrote:
Peter Barada writes:
On Tue, 2009-03-17 at 22:21 -0700, Kevin Hilman wrote:
FYI...
The PM branch has now been rebased to today's linux-omap HEAD which is
based on v2.6.29-rc8. The previous PM branch has been rename
On Tue, 2009-03-24 at 11:08 -0700, Kevin Hilman wrote:
> Peter Barada writes:
>
> > On Tue, 2009-03-17 at 22:21 -0700, Kevin Hilman wrote:
> >> FYI...
> >>
> >> The PM branch has now been rebased to today's linux-omap HEAD which is
> >> based on v2.6.29-rc8. The previous PM branch has been ren
This patch has been applied to the linux-omap
by youw fwiendly patch wobot.
Commit: ed39a47fbc83f2c0d82aaadca7dec9fe8f061f83
PatchWorks
http://patchwork.kernel.org/patch/13766/
Git
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=ed39a47fbc83f2c0d82aaadca7dec9fe8f06
On Tuesday 24 March 2009, Adrian Hunter wrote:
> >From 1a3f939d95122d8e58a3750cf5bce09247357203 Mon Sep 17 00:00:00 2001
> From: Adrian Hunter
>
> The MMC driver turns the power off before it turns it
> on. To avoid regulator warnings, vmmc_aux must only be
> disabled if it has previously been en
Peter Barada writes:
> On Tue, 2009-03-17 at 22:21 -0700, Kevin Hilman wrote:
>> FYI...
>>
>> The PM branch has now been rebased to today's linux-omap HEAD which is
>> based on v2.6.29-rc8. The previous PM branch has been renamed to
>> pm-2.6.28. Depending on when you look, Tony's linux-omap
On Tue, 2009-03-17 at 22:21 -0700, Kevin Hilman wrote:
> FYI...
>
> The PM branch has now been rebased to today's linux-omap HEAD which is
> based on v2.6.29-rc8. The previous PM branch has been renamed to
> pm-2.6.28. Depending on when you look, Tony's linux-omap tree may not
> (yet) have the
"Reddy, Teerth" writes:
> Resending the patches sent by Rajendra after fixing Kevin's comments and
> cleanup.
>
> This series fixes a set of defects/issues in Smartreflex driver. SR
> autocompensation is now functional and is validated with these patches on a
> ES3.1 based SDP with the N value
On Tue, Mar 24, 2009 at 05:14:58PM +0530, Aggarwal, Anuj wrote:
> I am seriously confused on how to fetch the struct device * in my
> consumer driver, for an already registered regulator. I am planning to
> use this consumer driver as a part of my CPU freq/CPU idle framework
> but I don't know wha
From 6d7a4c9322e70e83bdcf66d151c1ce56ba2f949f Mon Sep 17 00:00:00 2001
From: Adrian Hunter
Signed-off-by: Adrian Hunter
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 29 +++--
1 files changed, 26 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/board-rx
From 1a3f939d95122d8e58a3750cf5bce09247357203 Mon Sep 17 00:00:00 2001
From: Adrian Hunter
The MMC driver turns the power off before it turns it
on. To avoid regulator warnings, vmmc_aux must only be
disabled if it has previously been enabled.
Signed-off-by: Adrian Hunter
---
arch/arm/mach-om
Ameya,
> Is there any need to pass "HANDLE hPCtxt" to DRV_RemoveProcContext()
> function?
>
-- It should work even if you don't pass the hPCtxt. This function requires
some rework to avoid this confusion. Thanks for bringing up this question.
Thank you,
Best regards,
Hari
> -Original Messa
Hi Hari,
ext Kanigeri, Hari wrote:
> Hi Amey,
>
>> I am trying to understand this patch.
>> I see that pCtxtclosed is passed to DRV_RemoveProcContext() function
>> but it is not used anywhere inside it. I was expecting to see a
>> statement there which should free its memory.
>
> This pointer is
Hi Amey,
> I am trying to understand this patch.
> I see that pCtxtclosed is passed to DRV_RemoveProcContext() function
> but it is not used anywhere inside it. I was expecting to see a
> statement there which should free its memory.
This pointer is getting freed indirectly through the pCtxt2 poi
I am seriously confused on how to fetch the struct device * in my consumer
driver, for an already registered regulator. I am planning to use this consumer
driver as a part of my CPU freq/CPU idle framework but I don't know what to
pass in regulator_get.
Should I register my regulator device as
From: Teerth Reddy
This patch has some cleanup , replacing SR_PASS/FAIL,SR_TRUE/FALSE
with standard kernel values.
Signed-off-by: Teerth Reddy
---
arch/arm/mach-omap2/smartreflex.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
Index: linux-omap-pm/arch/arm/mach-o
From: Rajendra Nayak
This patch removes the local defines (PRCM_VDD1/2) in smartreflex
driver and uses the already existing global definitions (VDD1_OPP/VDD2_OPP)
from omap34xx.h file.
Signed-off-by: Rajendra Nayak
Signed-off-by: Tero Kristo
---
arch/arm/mach-omap2/resource34xx.c |6 +++-
From: Rajendra Nayak
This patch replaces all the printk(KERN_* with pr_* calls.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/smartreflex.c | 26 +-
1 files changed, 13 insertions(+), 13 deletions(-)
Index: linux-omap-pm/arch/arm/mach-omap2/smartreflex.c
===
From: Rajendra Nayak
This patch resets the voltage level for each OPP on SR disable.
Signed-off-by: Rajendra Nayak
Signed-off-by: Jouni Hogander
---
arch/arm/mach-omap2/smartreflex.c | 49 ++
1 files changed, 49 insertions(+)
Index: linux-omap-pm/arch/ar
From: Rajendra Nayak
This patch disables the Smartreflex auto compensation for
both VDD1 and VDD2 only during CORE transitions in idle path.
Signed-off-by: Rajendra Nayak
Signed-off-by: Jouni Hogander
---
arch/arm/mach-omap2/pm34xx.c | 12 ++--
1 files changed, 6 insertions(+), 6 de
From: Rajendra Nayak
This patch uses the sysclk to set the SR CLKLENGTH instead
of the OSC clock speed used earlier.
Signed-off-by: Rajendra Nayak
Signed-off-by: Jouni Hogander
---
arch/arm/mach-omap2/smartreflex.c | 14 +++---
1 files changed, 7 insertions(+), 7 deletions(-)
Inde
From: Rajendra Nayak
Currently vdd1 and vdd2 voltages are updated only after OMAP wakes up
from RET/OFF. This patch forces update according to boot OPP on boot.
Signed-off-by: Rajendra Nayak
Signed-off-by: Jouni Hogander
---
arch/arm/mach-omap2/smartreflex.c | 82 +--
From: Rajendra Nayak
This patch fixes a bug wherein the inital voltage was not set
correctly on a OPP change
Signed-off-by: Rajendra Nayak
Signed-off-by: Jouni Hogander
---
arch/arm/mach-omap2/smartreflex.c | 42 ++
1 files changed, 38 insertions(+), 4 d
Hi,
Resending the patches sent by Rajendra after fixing Kevin's comments and
cleanup.
This series fixes a set of defects/issues in Smartreflex driver. SR
autocompensation is now functional and is validated with these patches on a
ES3.1 based SDP with the N values in Efuse.
Patches apply on
From: Rajendra Nayak
This patch removes the local defines (PRCM_VDD1/2) in smartreflex
driver and uses the already existing global definitions (VDD1_OPP/VDD2_OPP)
from omap34xx.h file.
Signed-off-by: Rajendra Nayak
Signed-off-by: Tero Kristo
---
arch/arm/mach-omap2/resource34xx.c |6 +++--
From: Eero Nurkkala
If XSYNCERR or RSYNCERR interrupts are enabled, they are never
cleared causing the IRQ handler to be continuously called.
This patch clears the IRQs in question in the event they are
enabled and taken.
Signed-off-by: Eero Nurkkala
---
arch/arm/plat-omap/mcbsp.c | 30 +
Hi Hari,
On Mon, Mar 23, 2009 at 8:49 PM, Kanigeri, Hari wrote:
> DRV_RemoveProcContext((struct DRV_OBJECT *)hDrvObject,
> pCtxtclosed, (void *)pCtxtclosed->pid);
I am trying to understand this patch.
I see that pCtxtclosed is passed to DRV_Remo
On Tue, 24 Mar 2009, Gupta, Ramesh wrote:
> > -Original Message-
> > From: Paul Walmsley [mailto:p...@pwsan.com]
> >
> > DSPBridge and
> > other drivers needing clock notifiers should pass function pointers to
> > clk_notifier_{register,unregister}() in their struct
> > platform_data,
Paul,
> -Original Message-
> From: Paul Walmsley [mailto:p...@pwsan.com]
> Sent: Tuesday, March 24, 2009 2:58 PM
> To: Kevin Hilman
> Cc: Gupta, Ramesh; linux-omap@vger.kernel.org
> Subject: Re: [PATCH 1/1] Export notifier register functions
> for kernel module building
>
> Hello Kevin,
Hello Kevin, Ramesh,
On Thu, 12 Feb 2009, Kevin Hilman wrote:
> "Gupta, Ramesh" writes:
>
> > This Patch exports symbols clk_notifier_register/unregister
> > function for other kernel modules usage.
> >
> > Signed-off-by: Ramesh Gupta G
>
> Thanks, pushed to PM branch.
As an aside, this patc
On Mon, 23 Mar 2009, Paul Walmsley wrote:
> On Fri, 20 Mar 2009, Nayak, Rajendra wrote:
>
> > This patch set reverts some patches from Paul Walmsley to add the clock
> > notification infrastucture for OMAP3, and adds new patches from him on top,
> > which
> > have only been circulating internall
41 matches
Mail list logo
