> -Original Message-
> From: Paul Walmsley [mailto:p...@pwsan.com]
> Sent: Saturday, December 11, 2010 7:26 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> Rajendra Nayak; Benoit Cousson
> Subject: RE: [PATCH 01/11] OMAP4: PRCM: add OMAP4
Kevin,
> -Original Message-
> From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
> Sent: Saturday, December 11, 2010 6:14 AM
> To: Vishwanath Sripathy
> Cc: linux-omap@vger.kernel.org; Paul Walmsely
> Subject: Re: [PATCH/RFC 2/2] OMAP: PM: implement context loss count
> APIs
>
> Vishw
On Fri, Dec 10, 2010 at 8:08 PM, Felipe Balbi wrote:
> hi,
>
> On Fri, Dec 10, 2010 at 08:05:39PM +0530, Hema HK wrote:
>>
>> Calling runtime pm APIs pm_runtime_put_sync() and pm_runtime_get_sync()
>> for enabling/disabling the clocks, sysconfig settings.
>>
>> enable clock, configure no-idle/stan
* Jamie Iles [101209 09:29]:
> On Thu, Dec 09, 2010 at 07:11:28PM +0200, Aaro Koskinen wrote:
> >
> > Check the following commits in linux-omap tree:
> >
> > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=5403187f83c12c6f4c03547e0cc05bac0310be7b
> >
> > and
> >
From: Benoit Cousson
Mailbox hwmod data for omap4.
Signed-off-by: Benoit Cousson
Signed-off-by: Omar Ramirez Luna
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 68
1 files changed, 68 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_
From: Felipe Contreras
So that we can enable the main clock.
Signed-off-by: Felipe Contreras
Signed-off-by: Omar Ramirez Luna
---
arch/arm/mach-omap2/devices.c | 10 +-
arch/arm/mach-omap2/mailbox.c | 18 ++
2 files changed, 15 insertions(+), 13 deletions(-)
diff
From: Felipe Contreras
Remove static platform_device and resource data within
omap mailbox driver; use the one defined in the hwmod
database along with omap_device framework for device
build and registration.
Signed-off-by: Felipe Contreras
Signed-off-by: Omar Ramirez Luna
---
arch/arm/mach-o
Mailbox hwmod data for omap2430 and 2420.
Signed-off-by: Omar Ramirez Luna
---
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 73
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 72 +++
2 files changed, 145 insertions(+), 0 deletions(-)
diff -
Tested on 3430, based of pm-core branch. It may require rebase once
the mailbox git pull is made.
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg39719.html
** v3 **
- Taken mailbox hwmod as is from Benoit original branch.
- Put back numbers for irq, addresses instead of considering the
From: Felipe Contreras
Mailbox hwmod data for omap3.
Signed-off-by: Felipe Contreras
Signed-off-by: Omar Ramirez Luna
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 71
1 files changed, 71 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hw
On Wed, 8 Dec 2010, Santosh Shilimkar wrote:
> One more possible road block of removing the direct register access
> from PM code is DEVICE PRM module. Even with this clean-up for DEVCIE
> PRM related registers. I guess we still need to use the lowest level
> APIs.
To clarify my comments, I'm not
Tony Lindgren wrote on Saturday, December 11, 2010 7:21 AM:
> * Pedanekar, Hemant [101210 16:58]:
>> Tony Lindgren wrote on Monday, December 06, 2010 10:23 PM:
>>
>> [...]
Similarly, we will also need to add TI816X specific hwmods.
4) TI816X series shares similarity with OMAP4 to
* Pedanekar, Hemant [101210 16:58]:
> Tony Lindgren wrote on Monday, December 06, 2010 10:23 PM:
>
> [...]
> >> Similarly, we will also need to add TI816X specific hwmods.
> >>
> >> 4) TI816X series shares similarity with OMAP4 too - e.g., various IPs are
> >> same, CM module is closer to OMAP4
On Wed, 8 Dec 2010, Paul Walmsley wrote:
> On Wed, 8 Dec 2010, Kevin Hilman wrote:
>
> > Paul Walmsley writes:
> >
> > > - * _omap2_clkdm_set_hwsup - set the hwsup idle transition bit
> > > +/**
> > > + * _enable_hwsup - set the hwsup idle transition bit
> > > + * @clkdm: struct clockdomain *
>
Tony Lindgren wrote on Monday, December 06, 2010 10:23 PM:
[...]
>> Similarly, we will also need to add TI816X specific hwmods.
>>
>> 4) TI816X series shares similarity with OMAP4 too - e.g., various IPs are
>> same, CM module is closer to OMAP4 than OMAP3. Thus, regaring (1) above, I
>> could us
Vishwanath Sripathy writes:
> Kevin,
[...]
>> @@ -288,20 +290,19 @@ unsigned long omap_pm_cpu_get_freq(void)
>>
>> int omap_pm_get_dev_context_loss_count(struct device *dev)
>> {
>> +struct platform_device *pdev = to_platform_device(dev);
>> +int count;
>> +
>> if (!dev) {
>>
On Thu, 9 Dec 2010, Benoit Cousson wrote:
> From: Jonathan Bergsagel
>
> Add register address, mask and link to the clksel structure that
> were missing in the IVA DPLL mux clock node.
>
> Signed-off-by: Jonathan Bergsagel
> Signed-off-by: Benoit Cousson
This patch results in a checkpatch wa
Make the parameter received by omap_device_get_mpu_rt_va
consistent with the functions meant to be called by drivers.
Also move its header declaration to appear in the set of
functions to be used by drivers, as per the comment there.
Signed-off-by: Omar Ramirez Luna
Acked-by: Kevin Hilman
---
> I think the following list is the right list:
> https://gforge.ti.com/gf/project/omapandroid/mailman/?action=ListThreads&mailman_id=22
>
> Regards,
> Nishanth Menon
Thanks for the advice, discussion moved to omapandroid-discussion
Peter
--
To unsubscribe from this list: send the line "unsubscri
Hello.
Greg KH wrote:
Removed the board_data parameter being passed to musb_platform_init function
as board data can be extracted from device structure which is already member of
musb structure.
Signed-off-by: Hema HK
Cc: Felipe Balbi
Cc: Tony Lindgren
Cc: Kevin Hilman
Cc: Cousson, Benoi
Friday 10 December 2010 18:03:56 Russell King - ARM Linux napisał(a):
> On Fri, Dec 10, 2010 at 12:03:07PM +0100, Janusz Krzysztofik wrote:
> > void __init omap1_camera_init(void *info)
> > {
> > struct platform_device *dev = &omap1_camera_device;
> > + dma_addr_t paddr = omap1_camera_phys_
argon design had written, on 12/10/2010 02:34 PM, the following:
BACKGROUND
I am running the RLS25.INC2.6 Zoom release configured for board_overo
on a Overo Water Gumstix module (contains a 3530 chip).
[...]
Thanks (and many apologies if I haven't picked the right mailing list!),
I think the
BACKGROUND
I am running the RLS25.INC2.6 Zoom release configured for board_overo
on a Overo Water Gumstix module (contains a 3530 chip).
I have got the RLS25.12 binaries from TI's website
(https://gforge.ti.com/gf/project/openmax/frs/) and these work fine
for decoding video (via pvplayer_engine_te
On Fri, Dec 10, 2010 at 10:30:50PM +0300, Sergei Shtylyov wrote:
> Hello.
>
> Kevin Hilman wrote:
>
> >>Removed the board_data parameter being passed to musb_platform_init function
> >>as board data can be extracted from device structure which is already
> >>member of
> >>musb structure.
>
> >>
From: Jean Pihet
Provides documentation for the following:
- the new power trace API,
- the old (legacy) power trace API,
- the DEPRECATED Kconfig option usage..
Signed-off-by: Jean Pihet
---
Documentation/trace/events-power.txt | 90 ++
1 files changed, 90 in
From: Jean Pihet
Uses the machine_suspend trace point, called from the
generic kernel suspend_enter function.
Signed-off-by: Jean Pihet
CC: Thomas Renninger
---
kernel/power/suspend.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/kernel/power/suspend.c b/kernel/po
From: Jean Pihet
The patch adds the new power management trace points for
the OMAP architecture.
The trace points are for:
- default idle handler. Since the cpuidle framework is
instrumented in the generic way there is no need to
add trace points in the OMAP specific cpuidle handler;
- cpufr
From: Jean Pihet
Provides:
. calls to machine_suspend trace point,
. OMAP support,
. API Documentation
Applies on top of Thomas's 8 latest power trace API patches, cf.
http://marc.info/?l=linux-kernel&m=129130827309354&w=2
Jean Pihet (3):
perf: add calls to suspend trace point
perf: add OMA
Hello.
Kevin Hilman wrote:
Removed the board_data parameter being passed to musb_platform_init function
as board data can be extracted from device structure which is already member of
musb structure.
Signed-off-by: Hema HK
Cc: Felipe Balbi
Cc: Tony Lindgren
Cc: Kevin Hilman
Cc: Cousson,
* Janusz Krzysztofik [101210 08:03]:
> Saturday 04 December 2010 22:36:55 Tony Lindgren napisał(a):
> > Otherwise multi-omap1 configurations will fail.
>
> Tested on Amstrad Delta with omap1_defconfig.
>
> > Signed-off-by: Tony Lindgren
>
> Tested-by: Janusz Krzysztofik
Thanks, will merge th
On Thu, Dec 9, 2010 at 11:16 AM, Kevin Hilman
wrote:
> Omar Ramirez Luna writes:
>
>> Patch "OMAP: hwmod/device: add omap_{device, hwmod}_get_mpu_rt_va"[1],
>> introduces omap_device_get_rt_va which is meant to be called
>> by drivers to retrieve the _mpu_rt_va, however this function
>> receives
On Wed, Dec 8, 2010 at 5:49 PM, Greg KH wrote:
>> BTW, I don't expect this pushed through staging yet, I need to include
>> it to my branch first and then I'll send a pull request with the pile
>> of patches. Sorry for the misunderstanding and thanks for the review.
>
> Well, don't send me patches
This patch extends the smartreflex framework to support
OMAP4. The changes are minor like compiling smartreflex Kconfig
option for OMAP4 also, and a couple of OMAP4 checks in
the smartreflex framework.
The change in sr_device.c where new logic has to be introduced
for reading the efuse registers i
OMAP4 has three scalable voltage domains vdd_mpu, vdd_iva
and vdd_core. This patch adds the voltage tables and other
configurable voltage processor and voltage controller
settings to control these three scalable domains in OMAP4.
Signed-off-by: Thara Gopinath
---
This patch has 9 checkpatch.pl ab
From: Benoit Cousson
This patch adds the hwmod details for OMAP4 smartreflex modules.
Signed-off-by: Benoit Cousson
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 167
1 files changed, 167 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmo
TWL6030 is the power IC used along with OMAP4 in OMAP4 SDPs,
blaze boards and panda boards. This patch registers the OMAP4
PMIC specific information with the voltage layer.
This also involves implementing a different formula for
voltage to vsel and vsel to voltage calculations from
TWL4030.
Signed
This patch series adds support for OMAP4 support in the
smartreflex and voltage layer. The series involves extensions
to voltage layer and smartreflex layer for supporting OMAP4.
This series in based against kernel.org 2.6.37-rc3 and is
dependent on the "OMAP3: Adding Smartreflex and Voltage driv
By default the system boots up at nominal voltage for every
voltage domain in the system. This patch puts vdd_mpu, vdd_iva
and vdd_core to the correct boot up voltage as per the opp tables
specified. This patch implements this by matching the rate of
the main clock of the voltage domain with the op
Smartreflex Class3 implementation continuously monitors
silicon performance and instructs the Voltage Processors
to increase or decrease the voltage.
This patch adds smartreflex class 3 driver. This driver hooks
up with the generic smartreflex driver smartreflex.c to abstract
out class specific im
This patch adds support for device registration of various
smartreflex module present in the system. This patch introduces
the platform data for smartreflex devices which include
the efused n-target vaules, a parameter to indicate
whether smartreflex autocompensation needs to be
enabled on init or
This patch adds support in the twl4030 driver to enable smartreflex.
The smartreflex bit on twl4030 needs to be enabled by default irrespective
of whether smartreflex module is enabled on the OMAP side or not.
This is because without this bit enabled the voltage scaling through
vp forceupdate does
This patch registers the TWL4030 PMIC specific informtion
with the voltage driver. Failing this patch the voltage driver
is unware of the formula to use for vsel to voltage and vice versa
conversion and lot of other PMIC dependent parameters.
This file is based on the arch/arm/plat-omap opp_twl_tp
This patch adds voltage driver support for OMAP3. The driver
allows configuring the voltage controller and voltage
processors during init and exports APIs to enable/disable
voltage processors, scale voltage and reset voltage.
The driver maintains the global voltage table on a per
VDD basis which c
SmartReflex modules do adaptive voltage control for real-time
voltage adjustments. With Smartreflex the power supply voltage
can be adapted to the silicon performance(manufacturing process,
temperature induced performance, age induced performance etc).
There are differnet classes of smartreflex im
By default the system boots up at nominal voltage for every
voltage domain in the system. This patch puts VDD1 and VDD2
to the correct boot up voltage as per the opp tables specified.
This patch implements this by matching the rate of the main clock
of the voltage domain with the opp table and pick
This patch adds debug support to the voltage and smartreflex drivers.
This means a whole bunch of voltage processor and smartreflex
parameters are now visible through the pm debugfs.
The voltage parameters can be viewed at
/debug/voltage/vdd_/
and the smartreflex parameters can be viewed at
This patch series introduces smartreflex and voltage driver support
for OMAP3430 and OMAP3630. SmartReflex modules do adaptive voltage
control for real-time voltage adjustments.
Originally all the functionalities introduced in this patch
were present in arch/arm/mach-omap2/smartreflex.c file in Ke
This patch extends the device hwmod structure to contain
info about the voltage domain to which the device belongs to.
This is needed to support a device based DVFS where the
device knows which voltage domain it belongs to.
Signed-off-by: Thara Gopinath
---
arch/arm/plat-omap/include/plat/omap_h
This patch adds the smartreflex hwmod data for OMAP3430
and OMAP3630.
Signed-off-by: Thara Gopinath
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 174
1 files changed, 174 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
b/a
* Janusz Krzysztofik [101210 08:06]:
> Wednesday 08 December 2010 02:47:28 Tony Lindgren napisał(a):
> > Initialize asm_irq_flags in omap_init_irq and use it in
> > get_irqnr_and_base to detect between omap7xx and omap15xx/16xx.
> >
> > Note that both INT_1510_IH2_IRQ and INT_1510_IH2_IRQ are defi
* Janusz Krzysztofik [101210 08:05]:
> > We need to divide the 15xx/16xx offset by 2 for 7xx. Use bank->stride
> > for that. This allows us to get rid of the duplicate defines for the
> > MPUIO registers.
> >
> > Note that this will cause omap-keypad.c driver to not work on 7xx.
> > However, the r
On Fri, Dec 10, 2010 at 12:03:07PM +0100, Janusz Krzysztofik wrote:
> void __init omap1_camera_init(void *info)
> {
> struct platform_device *dev = &omap1_camera_device;
> + dma_addr_t paddr = omap1_camera_phys_mempool_base;
> + dma_addr_t size = omap1_camera_phys_mempool_size;
>
Hello.
Felipe Balbi wrote:
Index: linux-omap-pm/arch/arm/mach-davinci/usb.c
===
--- linux-omap-pm.orig/arch/arm/mach-davinci/usb.c
+++ linux-omap-pm/arch/arm/mach-davinci/usb.c
@@ -64,10 +64,12 @@ static struct resource usb_resourc
On Wed, Dec 8, 2010 at 2:10 AM, Andrew Morton wrote:
> Every time someone sends me a patch with text after the "---", I decide
> it was good changelog material and I promote it to above the "---".
> How's about you save us the effort :)
sure :)
>> +/**
>> + * BUG_ON_MAPPABLE_NULL() - BUG_ON(cond
Hi Mark and others!
Mark Brown wrote:
> On Tue, Dec 07, 2010 at 07:11:39PM +0100, Hans Verkuil wrote:
>
>> Ah, now I understand what you mean. Would 'activated' be better than
>> 'active'?
>
> Better, yes, though it still sounds a bit like something should be
> actively (IYSWIM) happening. In
On Fri, Dec 10, 2010 at 5:34 AM, Nishanth Menon wrote:
> Fernando Guzman Lugo wrote, on 12/09/2010 09:55 PM:
>>
>> * V2
>> - rebase to the latest
>> - remove patches no needed at this moment
>>
>> This set of patches fix some issues found in lastest tree.
>>
>> Fernando Guzman Lugo (4):
>> sta
Wednesday 08 December 2010 02:47:28 Tony Lindgren napisał(a):
> Initialize asm_irq_flags in omap_init_irq and use it in
> get_irqnr_and_base to detect between omap7xx and omap15xx/16xx.
>
> Note that both INT_1510_IH2_IRQ and INT_1510_IH2_IRQ are defined
> as 0, so use INT_1510_IH2_IRQ for both of
Wednesday 08 December 2010 00:23:16 Tony Lindgren napisał(a):
> * Tony Lindgren [101204 13:16]:
> > * Varadarajan, Charulatha [101202 06:08]:
> > > On Thu, Dec 2, 2010 at 15:28, Kevin Hilman
wrote:
> > > > Tony, you can also add
> > > >
> > > > Acked-by: Kevin Hilman
> >
> > OK, updated. Also
Saturday 04 December 2010 22:36:55 Tony Lindgren napisał(a):
> Otherwise multi-omap1 configurations will fail.
Tested on Amstrad Delta with omap1_defconfig.
> Signed-off-by: Tony Lindgren
Tested-by: Janusz Krzysztofik
> ---
> arch/arm/mach-omap1/board-ams-delta.c |3 +++
> arch/arm/mach-
On 12/10/2010 1:36 AM, Kevin Hilman wrote:
Benoit Cousson writes:
[...]
As with the other series, I tried to pull this into my pm-core for
testing with all the other PM stuff we have baking for 2.6.38.
Unfortunately, this series has conflicts with Paul's
pwrdm_prcm_[ab]_2.6.38 branches.
Co
hi,
On Fri, Dec 10, 2010 at 08:05:39PM +0530, Hema HK wrote:
Calling runtime pm APIs pm_runtime_put_sync() and pm_runtime_get_sync()
for enabling/disabling the clocks, sysconfig settings.
enable clock, configure no-idle/standby when active and configure force
idle/standby
and disable clock whe
Using omap_device_build API instead of platform_device_register for
OMAP2430,OMAP34xx and OMAP4430 musb device registration.
The device specific resources defined in centralized
database will be used.
Signed-off-by: Hema HK
Cc: Felipe Balbi
Cc: Tony Lindgren
Cc: Kevin Hilman
Cc: Cousson, Ben
Calling runtime pm APIs pm_runtime_put_sync() and pm_runtime_get_sync()
for enabling/disabling the clocks, sysconfig settings.
enable clock, configure no-idle/standby when active and configure force
idle/standby
and disable clock when idled. This is taken care by the runtime framework when
drive
OMAP2430 hwmod data structures are populated with base address, L3 and L4
interface clocks, IRQs and sysconfig register details.
As per OMAP USBOTG specification, need to configure the USBOTG
to smart idle/standby or no idle/standby during data transfer and
force idle/standby when not in use to su
OMAP3 hwmod data structures are populated for USBOTG with base address,
L3 and L4 interface clocks, IRQs and sysconfig register details.
As per OMAP USBOTG specification, need to configure the USBOTG
to smart idle/standby or no idle/standby during data transfer and
force idle/standby when not in u
From: Cousson, Benoit
OMAP4 hwmod data structures are populated with base address, L3 and L4
interface clocks, IRQs and sysconfig register details.
As per OMAP USBOTG specification, need to configure the USBOTG
to smart idle/standby or no idle/standby during data transfer and
force idle/standby
This patch series makes OMAP2PLUS musb module implemented
in HWMOD FW way. It also implements musb driver to
use the runtime pm apis.
As per the OMAP usbotg specification[1] musb sysconfig register
has to be set to force idle and force standby when not used
and set smart idle/standby or no idle/st
Hi,
On Fri, Dec 10, 2010 at 04:35:14PM +0300, Sergei Shtylyov wrote:
Index: linux-omap-pm/arch/arm/mach-davinci/usb.c
===
--- linux-omap-pm.orig/arch/arm/mach-davinci/usb.c
+++ linux-omap-pm/arch/arm/mach-davinci/usb.c
@@ -64,10 +64
Hello.
On 10-12-2010 16:20, Felipe Balbi wrote:
The resource data is getting automatically populated from a set of data
generated from TI's hardware database for the OMAP platform, While we
could hack in some exceptions to that tool to generate resources
in a specific order, it seems less fragi
On Fri, Dec 10, 2010 at 6:29 PM, Felipe Balbi wrote:
> Hi,
>
> On Fri, Dec 10, 2010 at 06:23:46PM +0530, Hema HK wrote:
>>
>> @@ -429,28 +392,29 @@ static int __init omap2430_probe(struct
>> pdev->num_resources);
>> if (ret) {
>> dev_err(&pdev->dev, "fa
Hello.
On 10-12-2010 15:40, Hema HK wrote:
Add the twl6030_usb transceiver file for compilation.
Signed-off-by: Hema HK
Cc: Felipe Balbi
Index: usb/drivers/usb/otg/Makefile
===
--- usb.orig/drivers/usb/otg/Makefile
+++ usb/dr
On Fri, Dec 10, 2010 at 6:32 PM, Felipe Balbi wrote:
> Hi,
>
> On Fri, Dec 10, 2010 at 06:23:10PM +0530, Hema HK wrote:
>>
>> @@ -212,8 +228,28 @@ void __init usb_musb_init(struct omap_mu
>> musb_plat.mode = board_data->mode;
>> musb_plat.extvbus = board_data->extvbus;
>>
>> -
Hello.
On 10-12-2010 15:38, Hema HK wrote:
Added the TWL6030-usb transceiver option in the Kconfig
Signed-off-by: Hema HK
Cc: Felipe Balbi
Cc: David Brownell
[...]
Index: usb/drivers/usb/otg/Kconfig
===
--- usb.orig/drivers/u
On Fri, Dec 10, 2010 at 03:56:27PM +0300, Sergei Shtylyov wrote:
Hello.
On 10-12-2010 7:46, Kalliguddi, Hema wrote:
The resource data is getting automatically populated from a set of data
generated from TI's hardware database for the OMAP platform, While we
could hack in some exceptions to tha
On Fri, Dec 10, 2010 at 6:26 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 10-12-2010 7:46, Kalliguddi, Hema wrote:
>
> The resource data is getting automatically populated from a set of data
> generated from TI's hardware database for the OMAP platform, While we
> could hack in some exce
On Fri, Dec 10, 2010 at 05:54:34PM +0530, Hema HK wrote:
This patch series has the support for TWL6030-usb
transceiver driver and changes in the musb driver to make it functional
with OMAP4430.
OMAP4 musb support UTMI and ULPI transceiver interfaces.
In UTMI mode, the transceiver functionality
Hi,
On Fri, Dec 10, 2010 at 06:23:10PM +0530, Hema HK wrote:
@@ -212,8 +228,28 @@ void __init usb_musb_init(struct omap_mu
musb_plat.mode = board_data->mode;
musb_plat.extvbus = board_data->extvbus;
- if (platform_device_register(&musb_device) < 0)
- printk(K
Hi,
On Fri, Dec 10, 2010 at 06:23:46PM +0530, Hema HK wrote:
@@ -429,28 +392,29 @@ static int __init omap2430_probe(struct
pdev->num_resources);
if (ret) {
dev_err(&pdev->dev, "failed to add resources\n");
- goto err4;
+
Hello.
On 10-12-2010 7:46, Kalliguddi, Hema wrote:
The resource data is getting automatically populated from a set of data
generated from TI's hardware database for the OMAP platform, While we
could hack in some exceptions to that tool to generate resources
in a specific order, it seems less fr
On Fri, Dec 10, 2010 at 02:51:34PM +0200, Felipe Balbi wrote:
On Fri, Dec 10, 2010 at 06:10:51PM +0530, Hema HK wrote:
@@ -214,9 +235,62 @@ static inline void omap2430_low_level_in
musb_writel(musb->mregs, OTG_FORCESTDBY, l);
}
+/* blocking notifier support */
+static int musb_otg_notif
Calling runtime pm APIs pm_runtime_put_sync() and pm_runtime_get_sync()
for enabling/disabling the clocks, sysconfig settings.
enable clock, configure no-idle/standby when active and configure force
idle/standby
and disable clock when idled. This is taken care by the runtime framework when
drive
Using omap_device_build API instead of platform_device_register for
OMAP2430,OMAP34xx and OMAP4430 musb device registration.
The device specific resources defined in centralized
database will be used.
Signed-off-by: Hema HK
Cc: Felipe Balbi
Cc: Tony Lindgren
Cc: Kevin Hilman
Cc: Cousson, Ben
From: Cousson, Benoit
OMAP4 hwmod data structures are populated with base address, L3 and L4
interface clocks, IRQs and sysconfig register details.
As per OMAP USBOTG specification, need to configure the USBOTG
to smart idle/standby or no idle/standby during data transfer and
force idle/standby
OMAP3 hwmod data structures are populated for USBOTG with base address,
L3 and L4 interface clocks, IRQs and sysconfig register details.
As per OMAP USBOTG specification, need to configure the USBOTG
to smart idle/standby or no idle/standby during data transfer and
force idle/standby when not in u
OMAP2430 hwmod data structures are populated with base address, L3 and L4
interface clocks, IRQs and sysconfig register details.
As per OMAP USBOTG specification, need to configure the USBOTG
to smart idle/standby or no idle/standby during data transfer and
force idle/standby when not in use to su
This patch series makes OMAP2PLUS musb module implemented
in HWMOD FW way. It also implements musb driver to
use the runtime pm apis.
As per the OMAP usbotg specification[1] musb sysconfig register
has to be set to force idle and force standby when not used
and set smart idle/standby or no idle/st
On Fri, Dec 10, 2010 at 06:10:51PM +0530, Hema HK wrote:
@@ -214,9 +235,62 @@ static inline void omap2430_low_level_in
musb_writel(musb->mregs, OTG_FORCESTDBY, l);
}
+/* blocking notifier support */
+static int musb_otg_notifications(struct notifier_block *nb,
+ unsigned lo
Enabling the musb OTG mode for SDP and PANDA boards.
Signed-off-by: Hema HK
Cc: Felipe Balbi
Cc: Tony Lindgren
---
arch/arm/mach-omap2/board-4430sdp.c|2 +-
arch/arm/mach-omap2/board-omap4panda.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Index: usb/arch/arm/mach-omap
OMAP4430 supports UTMI and ULPI types of transceiver interface.
In UTMI mode: The PHY is embedded within OMAP4430. The transceiver functionality
is split between the twl6030 PMIC chip and OMAP4430. The VBUS, ID pin
sensing and OTG SRP generation part is integrated in TWL6030 and UTMI PHY
function
Add the twl6030_usb transceiver file for compilation.
Signed-off-by: Hema HK
Cc: Felipe Balbi
Index: usb/drivers/usb/otg/Makefile
===
--- usb.orig/drivers/usb/otg/Makefile
+++ usb/drivers/usb/otg/Makefile
@@ -12,6 +12,7 @@ obj-$(CO
Registering the twl6030-usb transceiver device as a child to twl6030 core.
Removed the NOP transceiver init call from board file.
Populated twl4030_usb_data platform data structure with the function
pointers for OMAP4430 internal PHY operation to be used by twl630-usb driver.
Signed-off-by: Hema
Added the TWL6030-usb transceiver option in the Kconfig
Signed-off-by: Hema HK
Cc: Felipe Balbi
Cc: David Brownell
---
drivers/usb/otg/Kconfig | 12
1 file changed, 12 insertions(+)
Index: usb/drivers/usb/otg/Kconfig
=
Selecting the twl6030-usb for OMAP4430SDP and OMAP4PANDA boards and
adding OMAP4 internal phy code for compilation
Signed-off-by: Hema HK
Cc: Felipe Balbi
Cc: Tony Lindgren
---
arch/arm/mach-omap2/Makefile |6 --
drivers/usb/musb/Kconfig |1 +
2 files changed, 5 insertions(+),
Adding the twl6030-usb transceiver support for OMAP4 musb driver.
OMAP4 supports 2 types of transceiver interface.
1. UTMI: The PHY is embedded within OMAP4. The transceiver functionality
is split between the twl6030 PMIC chip and OMAP4430. The VBUS, ID pin
sensing and OTG SRP generation part is
With TWL6030-usb, VBUS SESS_VLD and SESS_END events are not generated
as expected. When these interrupts are enabled, charger VBUS detection
interrupt does not get generated. So USBOTG has to be dependent on charger
VBUS interrupts.
So added one bit for USBOTG and changed the handler to call the
U
This patch series has the support for TWL6030-usb
transceiver driver and changes in the musb driver to make it functional
with OMAP4430.
OMAP4 musb support UTMI and ULPI transceiver interfaces.
In UTMI mode, the transceiver functionality is split between
the TWL6030 PMIC chip and OMAP4 embedded P
On Fri, Dec 10, 2010 at 5:13 PM, Felipe Balbi wrote:
> On Fri, Dec 10, 2010 at 04:56:40PM +0530, Kalliguddi, Hema wrote:
>>
>> On Fri, Dec 10, 2010 at 2:11 PM, Felipe Balbi wrote:
>>>
>>> On Fri, Dec 10, 2010 at 12:34:35PM +0530, Hema HK wrote:
Added the TWL6030-usb transceiver option i
On Fri, Dec 10, 2010 at 04:56:40PM +0530, Kalliguddi, Hema wrote:
On Fri, Dec 10, 2010 at 2:11 PM, Felipe Balbi wrote:
On Fri, Dec 10, 2010 at 12:34:35PM +0530, Hema HK wrote:
Added the TWL6030-usb transceiver option in the Kconfig
Signed-off-by: Hema HK
Cc: Felipe Balbi
Cc: David Brownell
On Fri, Dec 10, 2010 at 4:00 PM, Felipe Balbi wrote:
> Hi,
>
> On Fri, Dec 10, 2010 at 12:34:50PM +0530, Hema HK wrote:
>>
>> Registering the twl6030-usb transceiver device as a child to twl6030 core.
>> Removed the NOP transceiver init call from board file.
>>
>> Populated twl4030_usb_data platfo
Fernando Guzman Lugo wrote, on 12/09/2010 09:55 PM:
* V2
- rebase to the latest
- remove patches no needed at this moment
This set of patches fix some issues found in lastest tree.
Fernando Guzman Lugo (4):
staging: tidspbridge - use GTP7 for DSP stack dump
staging: tidspbridge - fix
1 - 100 of 113 matches
Mail list logo
