> >I know, the sourceforge list is a bit of a pain.
As all sourceforge lists are.
> I don't even know
> >who the admin of that list is.
One of the Russian MontaVista crew created
that list, and presumably maintains it.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap
* Stephen Rothwell [100810 04:02]:
> Hi Jacob,
>
> On Mon, 9 Aug 2010 19:36:01 -0500 "Jacob Tanenbaum"
> wrote:
> >
> > I work for LogicPD and am trying to add new support for
> > there OMAP3 development boards to the kernel, I have a working version
> > of some of the base support
Hi,
On Tue, Aug 10, 2010 at 08:33:41AM +0200, ext Grant Likely wrote:
Now picked up into my test-spi branch. I'll add it to linux-next after
the merge window closes.
ok, thanks Grant
--
balbi
DefectiveByDesign.org
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
t
* Cory Maccarrone [100809 20:21]:
> On Mon, Aug 9, 2010 at 12:43 AM, Tony Lindgren wrote:
> > * Cory Maccarrone [100808 20:22]:
> >> On Wed, Aug 4, 2010 at 3:15 AM, Tony Lindgren wrote:
> >> > * Cory Maccarrone [100802 18:23]:
> >> >> This change adds in a bluetooth controld driver/rfkill
> >>
On Mon, Aug 09, 2010 at 01:36:18PM +0300, Felipe Balbi wrote:
> On Thu, Jun 03, 2010 at 01:09:01PM +0200, Balbi Felipe (Nokia-D/Helsinki)
> wrote:
> >From: Felipe Balbi
> >
> >dev_vdbg() is only compiled when VERBOSE is defined, so
> >there's no need to wrap dev_dbg() on #ifdef VERBOSE .. #endif
From: Vibhore Vardhan
This patch implements device wakeup latency constraint framework.
Using omap_pm_set_max_dev_wakeup_lat(), drivers can specify the
maximum amount of time for a device to become accessible after
its clocks are enabled. This is done by restricting the power
states that the pare
> -Original Message-
> From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
> Sent: Tuesday, August 10, 2010 5:29 AM
> To: Varadarajan, Charulatha
> Cc: linux-omap@vger.kernel.org; p...@pwsan.com; Cousson, Benoit; Nayak,
> Rajendra; Basak, Partha
> Subject: Re: [PATCH 09/13 v5] OMAP: G
Hi,
On Tue, Aug 10, 2010 at 07:27:43AM +0200, ext Grant Likely wrote:
I know, the sourceforge list is a bit of a pain. I don't even know
who the admin of that list is. It was set up before I started the SPI
maintainership. I've been thinking about creating a new spi list on
vger.kernel.org.
On Mon, Aug 9, 2010 at 11:21 PM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Aug 09, 2010 at 03:22:31PM +0200, ext Grant Likely wrote:
>>
>> It didn't get sent to the spi-devel-general list, so it didn't get
>> picked up by patchwork and wasn't there for me to pick up when I was
>> collecting stuff for
Hi,
On Mon, Aug 09, 2010 at 03:22:31PM +0200, ext Grant Likely wrote:
It didn't get sent to the spi-devel-general list, so it didn't get
picked up by patchwork and wasn't there for me to pick up when I was
collecting stuff for .36.
that's subscribers only ? I couldn't bother subscribing to a l
> -Original Message-
> From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
> Sent: Tuesday, August 10, 2010 4:30 AM
> To: Varadarajan, Charulatha
> Cc: linux-omap@vger.kernel.org; p...@pwsan.com; Cousson, Benoit; Nayak,
> Rajendra; Basak, Partha
> Subject: Re: [PATCH 13/13 v5] OMAP: G
> -Original Message-
> From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
> Sent: Tuesday, August 10, 2010 3:51 AM
> To: Varadarajan, Charulatha
> Cc: linux-omap@vger.kernel.org; p...@pwsan.com; Cousson, Benoit; Nayak,
> Rajendra; Basak, Partha
> Subject: Re: [PATCH 01/13 v5] OMAP: G
Hi,
>-Original Message-
>From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
>Sent: Tuesday, August 10, 2010 2:24 AM
>To: Kalliguddi, Hema
>Cc: linux-omap@vger.kernel.org; linux-...@vger.kernel.org;
>Felipe Balbi; Tony Lindgren
>Subject: Re: [PATCH 1/8] usb: musb: Adding names for I
Kevin,
> -Original Message-
> From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
> Sent: Monday, August 09, 2010 11:59 PM
> To: Sripathy, Vishwanath
> Cc: linux-omap@vger.kernel.org
> Subject: Re: [PATCH] OMAP PM: MPU/DMA Latency constraints
>
> Vishwanath Sripathy writes:
>
> > This
Hi,
>-Original Message-
>From: Cousson, Benoit
>Sent: Monday, August 09, 2010 5:22 PM
>To: Kalliguddi, Hema
>Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org;
>Felipe Balbi; Tony Lindgren; Kevin Hilman
>Subject: Re: [PATCH 4/8]usb: musb: HWMOD database structures
>fixes OMAP4
Hi,
>-Original Message-
>From: Cousson, Benoit
>Sent: Monday, August 09, 2010 7:37 PM
>To: Kalliguddi, Hema
>Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org;
>Basak, Partha; Felipe Balbi; Tony Lindgren; Kevin Hilman
>Subject: Re: [PATCH 8/8 ]usb : musb:Using runtime pm apis for
Hi,
>-Original Message-
>From: Cousson, Benoit
>Sent: Monday, August 09, 2010 6:15 PM
>To: Kalliguddi, Hema
>Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org;
>Felipe Balbi; Tony Lindgren; Kevin Hilman
>Subject: Re: [PATCH V2 4/8]usb : musb:Using omap_device_build
>for musb de
Hi,
>-Original Message-
>From: Cousson, Benoit
>Sent: Monday, August 09, 2010 6:02 PM
>To: Kalliguddi, Hema
>Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org;
>Felipe Balbi; Tony Lindgren; Kevin Hilman
>Subject: Re: [PATCH 0/8]usb: musb:USB driver changes to use
>hwmod+ omap-d
Cliff Brake wrote:
On Tue, Jun 22, 2010 at 11:11 AM, Kevin Hilman
wrote:
"Stanley.Miao" writes:
First, the subject needs to be more descriptive:
OMAP3: AM3505/3517 do not have IO wakeup capability
Functionally, what does this statement mean? The 3503 seems to have
the EN_IO [8] bi
Hi Jacob,
On Mon, 9 Aug 2010 19:36:01 -0500 "Jacob Tanenbaum"
wrote:
>
> I work for LogicPD and am trying to add new support for
> there OMAP3 development boards to the kernel, I have a working version
> of some of the base support and was wondering how to get that ready to
> be merg
Charulatha V writes:
> 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
> Signed-o
Charulatha V writes:
> This patch makes GPIO driver to use dev_pm_ops instead of
> sysdev_class. With this approach, gpio_bank_suspend & gpio_bank_resume
> are not part of sys_dev_class.
>
> According to this patch, a GPIO bank relinquishes the clock using
> PM runtime APIs when all the gpios in
Charulatha V writes:
> 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
> Signed-o
Charulatha V writes:
> @@ -650,21 +511,28 @@ static void _set_gpio_debounce(struct gpio_bank *bank,
> unsigned gpio,
> __raw_writel(debounce, reg);
>
> reg = bank->base;
> - if (cpu_is_omap44xx())
> + if (bank->method == METHOD_GPIO_44XX)
> reg += OMAP4_GPIO_D
Charulatha V writes:
> 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.
This patch should also remove the function from plat/gpio.c
Kevin
> Signed-off-by: Charulatha V
> Signed-o
Charulatha V writes:
> 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
> th
Charulatha V writes:
> @@ -1728,7 +1729,6 @@ static int __devinit omap_gpio_probe(struct
> platform_device *pdev)
> }
>
> pm_runtime_enable(bank->dev);
> - pm_runtime_get_sync(bank->dev);
Why do you remove this?
> omap_gpio_mod_init(bank, id);
This next call accesses G
On Tue, Jun 22, 2010 at 11:11 AM, Kevin Hilman
wrote:
> "Stanley.Miao" writes:
>
> First, the subject needs to be more descriptive:
>
> OMAP3: AM3505/3517 do not have IO wakeup capability
Functionally, what does this statement mean? The 3503 seems to have
the EN_IO [8] bit, but I've yet to figu
"Kalliguddi, Hema" writes:
[...]
>>>
>>> Changed the usb sysconfig settings as per the usbotg functional spec.
>>> When the device is not active, configure to force idle and
>>force standby mode.
>>> When it is being used, configure in smart standby and smart
>>idle mode.
>>> So while attempti
"Cousson, Benoit" writes:
> On 8/6/2010 5:54 PM, HEMA HK wrote:
>> From: Hema HK
>>
>> Series of patches to port musb driver to use hwmod and runtime pm
>> APIs for OMAP4 and OMAP3.These patches are tested on OMAP4430SDP and
>> OMAP3630-ZOOM3 boards.
>>
>> The patch 1 and 2 are are the prerequisi
Hema HK writes:
> From: Hema HK
>
> Modified the Omap,Blackfin and Davinci board files to add the name of the IRQs
> in the resource structures and musb driver to use the get_irq_byname() api to
> get the mc and dma irq numbers instead of using the index as the order of
> resource definition ne
Hi all,
Seems that, with current master branch
(commit ID: 842849896627701e4c07441f2c7519aeec771058),
and doing this change:
> diff --git a/drivers/net/smsc911x.h b/drivers/net/smsc911x.h
> index 016360c..2cd4f5a 100644
> --- a/drivers/net/smsc911x.h
> +++ b/drivers/net/smsc911x.h
> @@ -23,7 +23,
Hi,
> -Original Message-
> From: Elvis Dowson [mailto:elvis.dow...@mac.com]
> Sent: Monday, August 09, 2010 2:17 PM
> To: Aguirre, Sergio
> Cc: linux-omap@vger.kernel.org
> Subject: Re: Zoom3 not booting with omap3_defconfig
>
> Hi Sergio,
> I've seen the exact same t
This patch implements device wakeup latency constraint framework.
Using omap_pm_set_max_dev_wakeup_lat(), drivers can specify the
maximum amount of time for a device to become accessible after
its clocks are enabled. This is done by restricting the power
states that the parent powerdomain of a devi
From: Mike Turquette
mach-omap/voltage.c incorrectly called omap_get_mpuss_device and
omap_get_l3_device. The correct function names are
omap2_get_mpuss_device and omap2_get_l3_device respectively.
This fixes a compile break. Test on OMAP3430 SDP.
Signed-off-by: Mike Turquette
---
This patc
Govindraj writes:
> On Wed, Jul 7, 2010 at 5:32 PM, Tony Lindgren wrote:
>> * Govindraj [100608 09:24]:
>>> On Mon, Jun 7, 2010 at 9:45 PM, Luke-Jr wrote:
>>> > On Monday 07 June 2010 08:28:51 am Govindraj wrote:
>>> >> Link:
>>> >> http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-
Hi Sergio,
I've seen the exact same thing happen, when I used the
linux-omap v2.6.35 tag for a beagleboard based device. It gives me the same
kernel panic.
> [2.097320] Waiting for root device /dev/mmcblk0p2...
> [2.235595] mmc0: new SD card at address b874
> [2
Benoit Cousson writes:
> Hi Kevin & Paul,
>
> Here is the OMAP4430 ES1 & ES2 hwmod data v3 series.
>
> Please note that there is no difference between the ES1 & ES2 wrt hwmod.
>
> This series is re-organised in order to allow initial submission for upstream
> with minimal interconnect data set +
Hi,
I'm trying to boot from NFS with my Zoom3 board with current master branch
(commit ID: 842849896627701e4c07441f2c7519aeec771058)
But, I'm not successful so far. :(
Seems that it can't detect the eth0 device. (See attached log: bad.txt)
Now, If I take omap_zoom3_defconfig from just before co
Vishwanath Sripathy writes:
> This patch has implementation for OMAP MPU/DMA Latency constraints using PM
> QOS.
Changelog is missing description of the problem being solved and the
motivation for the solution.
In particular, a system-wide API is being changed here with no
description of the
Manjunatha GK writes:
> OMAP1610 build fails with following error on the branch pm-wip/hwmods-omap4.
>
> This patch fixes the build error.
> arch/arm/mach-omap1/pm_bus.c: In function 'platform_pm_runtime_suspend':
> arch/arm/mach-omap1/pm_bus.c:30: error: 'ret' undeclared (first use in this
> fu
Hi Michael and Sergio,
Michael Jones wrote:
> Aguirre, Sergio wrote:
>> Hi Michael,
>>
>>
>>> -Original Message- From: linux-omap-ow...@vger.kernel.org
>>> [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of Michael
>>> Jones Sent: Friday, August 06, 2010 8:48 AM To:
>>> linux-omap@v
On 8/9/2010 7:30 PM, Kevin Hilman wrote:
Benoit Cousson writes:
Since OMAP4 is using an absolute address, the current PRM accessors
are not useable.
OMAP4 adaptation for these API are currently ongoing, so define temp
version until the proper ones are defined.
Curious what we're waiting for
Benoit Cousson writes:
> Since OMAP4 is using an absolute address, the current PRM accessors
> are not useable.
> OMAP4 adaptation for these API are currently ongoing, so define temp
> version until the proper ones are defined.
Curious what we're waiting for for the final versions of these?
Kev
On Mon, Aug 9, 2010 at 12:43 AM, Tony Lindgren wrote:
> * Cory Maccarrone [100808 20:22]:
>> On Wed, Aug 4, 2010 at 3:15 AM, Tony Lindgren wrote:
>> > * Cory Maccarrone [100802 18:23]:
>> >> This change adds in a bluetooth controld driver/rfkill
>> >> interface to the serial bluetooth controlle
Hi Michael,
> -Original Message-
> From: Michael Jones [mailto:michael.jo...@matrix-vision.de]
> Sent: Monday, August 09, 2010 10:42 AM
> To: Aguirre, Sergio
> Cc: linux-omap@vger.kernel.org; sakari.ai...@maxwell.research.nokia.com
> Subject: Re: omap3camera and linux-omap
>
> Aguirre, Se
Hema,
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Hema HK
> Sent: Friday, August 06, 2010 10:57 PM
> To: linux-...@vger.kernel.org; linux-omap@vger.kernel.org
> Cc: Kalliguddi, Hema; Mankad, Maulik Ojas; Felipe Bal
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Shilimkar, Santosh
> Sent: Monday, August 09, 2010 9:43 PM
> To: Kevin Hilman
> Cc: Basak, Partha; Paul Walmsley; linux-omap@vger.kernel.org; Kalliguddi,
> Hema; Raja, Go
> -Original Message-
> From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
> Sent: Monday, August 09, 2010 9:25 PM
> To: Shilimkar, Santosh
> Cc: Basak, Partha; Paul Walmsley; linux-omap@vger.kernel.org; Kalliguddi,
> Hema; Raja, Govindraj; Varadarajan, Charulatha
> Subject: Re: Issues
"Shilimkar, Santosh" writes:
>> -Original Message-
>> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
>> ow...@vger.kernel.org] On Behalf Of Kevin Hilman
>> Sent: Monday, August 09, 2010 9:01 PM
>> To: Basak, Partha
>> Cc: Paul Walmsley; linux-omap@vger.kernel.org; Kalliguddi,
Aguirre, Sergio wrote:
> Hi Michael,
>
>
>> -Original Message-
>> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
>> ow...@vger.kernel.org] On Behalf Of Michael Jones
>> Sent: Friday, August 06, 2010 8:48 AM
>> To: linux-omap@vger.kernel.org
>> Cc: sakari.ai...@maxwell.research
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Kevin Hilman
> Sent: Monday, August 09, 2010 9:01 PM
> To: Basak, Partha
> Cc: Paul Walmsley; linux-omap@vger.kernel.org; Kalliguddi, Hema; Raja,
> Govindraj; Varadarajan,
"Basak, Partha" writes:
>> Finally, we have omap_sram_idle():
>>
>> > In particular, for USB, while executing SRAM_Idle, is we use pm_runtime
>> > functions, we see spurious IO-Pad interrupts.
>>
>> Your message doesn't specify what PM runtime functions you are executing.
>> But if those functi
On 8/9/2010 11:37 AM, Nayak, Rajendra wrote:
From: Paul Walmsley [mailto:p...@pwsan.com]
Sent: Monday, August 09, 2010 1:51 PM
(cc Benoît)
On Mon, 9 Aug 2010, Nayak, Rajendra wrote:
Does it make sense for the framework itself to enable wakeup
for all devices when the slave port is programm
This patch converts the i2c driver to use PM runtime apis for OMAP2+
and omap_device api's for OMAP1
Signed-off-by: Rajendra Nayak
Cc: Kevin Hilman
Cc: Paul Walmsley
---
drivers/i2c/busses/i2c-omap.c | 81 ++---
1 files changed, 35 insertions(+), 46 deleti
From: Paul Walmsley
Split the OMAP1 and OMAP2+ platform_device build and register code.
Convert the OMAP2+ variant to use omap_device.
This patch was developed in collaboration with Rajendra Nayak
.
Signed-off-by: Paul Walmsley
Signed-off-by: Rajendra Nayak
Cc: Kevin Hilman
---
arch/arm/pla
Add hwmod structures for I2C controllers on OMAP3430.
This patch was developed in collaboration with Paul Walmsley .
Signed-off-by: Rajendra Nayak
Signed-off-by: Paul Walmsley
Cc: Kevin Hilman
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 232
arch/arm/mach-om
The PM runtime core functions are implemented in pm_bus.c
which needs to be compiled for CONFIG_ARCH_OMAP4 for
runtime api's to work.
Signed-off-by: Rajendra Nayak
Cc: Kevin Hilman
---
arch/arm/mach-omap2/Makefile |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/ar
From: Paul Walmsley
Add hwmod structures for I2C controllers on OMAP2420/2430.
Signed-off-by: Paul Walmsley
Signed-off-by: Rajendra Nayak
Cc: Kevin Hilman
---
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 134 ++-
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 140
Hi,
This series makes I2C device registration use hwmod
and omap_device api's and converts the I2C driver to use
runtime PM api's.
Patches apply on the pm-wip/hwmods-omap4 branch from Kevin's tree.
Patches are tested on OMAP3 and OMAP4 SDP platforms.
regards,
Rajendra
Paul Walmsley (2):
OMAP
On 8/6/2010 7:29 PM, Hema HK wrote:
From: Hema HK
Calling runtime pm APIs pm_runtime_put_sync() and pm_runtime_get_sync()
for enabling/disabling the clocks,sysconfig settings.
used omap_hwmod_enable_wakeup& omap_hwmod_disable_wakeup apis to set/clear
the wakeup enable bit.
Also need to put the
Felipe,
Any comments on this patch?
Thanks a lot,
-Bryan
On 07/23/2010 10:36 PM, Bryan Wu wrote:
BugLink: http://bugs.launchpad.net/bugs/608312
v2:
fix the building error on latest 2.6.35-rc kernel, since v1 was generated in
2.6.33 kernel.
v1:
usb_add_hcd was only called when we insmod the
On Mon, Aug 9, 2010 at 4:36 AM, Felipe Balbi wrote:
> On Thu, Jun 03, 2010 at 01:09:01PM +0200, Balbi Felipe (Nokia-D/Helsinki)
> wrote:
>>
>> From: Felipe Balbi
>>
>> dev_vdbg() is only compiled when VERBOSE is defined, so
>> there's no need to wrap dev_dbg() on #ifdef VERBOSE .. #endif
>> as we
Hi,
>-Original Message-
>From: Cousson, Benoit
>Sent: Monday, August 09, 2010 6:31 PM
>To: Kalliguddi, Hema
>Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org;
>Mankad, Maulik Ojas; Felipe Balbi; Tony Lindgren; Kevin Hilman
>Subject: Re: [PATCH V2 6/8] usb: musb: Offmode fix for
On 8/6/2010 7:27 PM, Kalliguddi, Hema wrote:
From: Hema HK
With OMAP core-off support musb was not functional as context was getting
lost after wakeup from core-off. And also musb was blocking the core-off
after loading the gadget driver even with no cable connected sometimes.
Added the conext
> -Original Message-
> From: Tomi Valkeinen [mailto:tomi.valkei...@nokia.com]
> Sent: Tuesday, August 03, 2010 5:32 PM
> To: ext Grazvydas Ignotas
> Cc: linux-fb...@vger.kernel.org; linux-omap@vger.kernel.org; Hiremath,
> Vaibhav
> Subject: Re: [PATCH] OMAP: DSS2: OMAPFB: add support for FB
On 8/6/2010 5:57 PM, Kalliguddi, Hema wrote:
From: Hema HK
void __init usb_musb_init(struct omap_musb_board_data *board_data)
{
- if (cpu_is_omap243x()) {
- musb_resources[0].start = OMAP243X_HS_BASE;
- } else if (cpu_is_omap34xx()) {
- musb_resour
> -Original Message-
> From: Cousson, Benoit
> Sent: Friday, August 06, 2010 6:06 PM
> To: Varadarajan, Charulatha
> Cc: linux-omap@vger.kernel.org; p...@pwsan.com;
> khil...@deeprootsystems.com; Nayak, Rajendra; Basak, Partha
> Subject: Re: [PATCH] OMAP4: HWMOD: Do omap_hwmod_late_ini
On 8/6/2010 5:54 PM, HEMA HK wrote:
From: Hema HK
Series of patches to port musb driver to use hwmod and runtime pm
APIs for OMAP4 and OMAP3.These patches are tested on OMAP4430SDP and
OMAP3630-ZOOM3 boards.
The patch 1 and 2 are are the prerequisites for the hwmod changes.
Patch 6 is the OMAP3
On 8/6/2010 7:28 PM, Kalliguddi, Hema wrote:
From: Hema HK
Omap USBOTG modules has a requirement to set the auto idle bit only after
setting smart idle bit.
Is it a requirement or an errata? Could you provide more information
(i.e. TRM page or errata number / description)?
Modified the _sy
Hi Hema,
On 8/6/2010 5:57 PM, Kalliguddi, Hema wrote:
From: Hema HK
Fixed the missing sysc settings for OMAP4 and enabled the OMAP4
hwmod data structure.
Signed-off-by: Hema HK
Cc: Felipe Balbi
Cc: Tony Lindgren
Cc: Kevin Hilman
It is a good practice, if not mandatory, to CC the authors of t
> -Original Message-
> From: Premi, Sanjeev
> Sent: Tuesday, July 13, 2010 3:54 PM
> To: linux-omap@vger.kernel.org
> Cc: Premi, Sanjeev
> Subject: [PATCH] omap2: fix assorted compiler warnings
Tony,
I notice the same warnings today while building against:
commit 842849896627701e4c07441
On Thu, Jun 03, 2010 at 01:09:01PM +0200, Balbi Felipe (Nokia-D/Helsinki) wrote:
From: Felipe Balbi
dev_vdbg() is only compiled when VERBOSE is defined, so
there's no need to wrap dev_dbg() on #ifdef VERBOSE .. #endif
as we can use dev_vdbg() directly.
Signed-off-by: Felipe Balbi
---
ping,
> Finally, we have omap_sram_idle():
>
> > In particular, for USB, while executing SRAM_Idle, is we use pm_runtime
> > functions, we see spurious IO-Pad interrupts.
>
> Your message doesn't specify what PM runtime functions you are executing.
> But if those functions are calling mutex_lock(), the
> -Original Message-
> From: Paul Walmsley [mailto:p...@pwsan.com]
> Sent: Monday, August 09, 2010 1:51 PM
> To: Nayak, Rajendra
> Cc: Kalliguddi, Hema; linux-...@vger.kernel.org;
> linux-omap@vger.kernel.org; Basak, Partha; Felipe Balbi; Tony
> Lindgren; Cousson, Benoit; Kevin Hilman
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Shilimkar, Santosh
> Sent: Sunday, August 08, 2010 5:16 PM
> To: Russell King - ARM Linux
> Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org
> Subject:
(cc Benoît)
On Mon, 9 Aug 2010, Nayak, Rajendra wrote:
> Does it make sense for the framework itself to enable wakeup
> for all devices when the slave port is programmed to be in
> Smartidle
It seems to me that they are separate mechanisms? If a module is
programmed for slave smart-idle, then
Bootloader on Nokia N800 and N810 muxes I2C codec port pins for EAC block.
As there is no driver and use for EAC, mux those pins for McBSP instead
since N810 ASoC drivers can use it.
Signed-off-by: Jarkko Nikula
---
With this patch it is possible to use audio on Nokia N810 by enabling the
CONFIG_
Second i2c bus on Nokia N800 and N810 shares both common and hw specific
peripherals. Register now this bus and add board info with tlv320aic3x for
N810. Common peripherals may be added as an additional board info to
omap_register_i2c_bus(2, ...);
Signed-off-by: Jarkko Nikula
---
With this patch
- Move n8x0_i2c_board_info_1 out from #ifdef CONFIG_MENELAUS block,
register i2c1 in n8x0_init_machine and do a few clean-ups around these.
Code looks better if board infos are grouped together
- Mark n8x0_i2c_board_info_1 and n8x0_menelaus_platform_data with __initdata
Signed-off-by: Jarkko N
Hi
With this set and a fix [1] it is possible to get ALSA SoC on N810 working.
This set is generated against mainline commit e320cea but applies also to
linux-omap (board-n8x0.c has cbus patches in linux-omap).
--
Jarkko
1. http://marc.info/?l=linux-omap&m=128109830113485&w=2
--
To unsubscribe
On Sat, 7 Aug 2010, Basak, Partha wrote:
> > -Original Message-
> > From: Paul Walmsley [mailto:p...@pwsan.com]
> > Sent: Saturday, August 07, 2010 1:00 AM
> >
> > On Tue, 3 Aug 2010, Basak, Partha wrote:
> >
> > > I believe, it is not correct to call the pm_runtime APIs from interrupt
>
* Bryan Wu [100809 09:35]:
>
> I also did similar thing these days. And yes, with these 2 CONFIG_SMP related
> patches in omap3_defconfig, I can built a single for omap2/3/4 with
> CONFIG_SMP=y.
>
> But the kernel still doesn't boot on both omap3 beagle board and omap4 panda
> board on my side.
* Cory Maccarrone [100808 20:22]:
> On Wed, Aug 4, 2010 at 3:15 AM, Tony Lindgren wrote:
> > * Cory Maccarrone [100802 18:23]:
> >> This change adds in a bluetooth controld driver/rfkill
> >> interface to the serial bluetooth controller found on many
> >> HTC smartphones such as the HTC Herald a
* Jarkko Nikula [100808 19:57]:
>
> Tested on N810. Integrated eMMC on N810 started to work with this patch.
Ah great, good to hear! I've been wondering for a while how come only
the external MMC worked.
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of
85 matches
Mail list logo
