Hi,
On Friday 29 March 2013 12:01 AM, David Miller wrote:
You really need to CC: net...@vger.kernel.org rather than me explicitly
on this patch set.
I was CC'ing whatever get_maintainer shows. I'll make sure to CC
net...@vger.kernel.org though there's nothing related to network in this
Hi Felipe,
On Tue, Apr 2, 2013 at 1:59 PM, Felipe Balbi ba...@ti.com wrote:
On Mon, Apr 01, 2013 at 07:24:01PM +0530, Vivek Gautam wrote:
The current code in the dwc3 probe effectively disables runtime pm
from ever working because it calls a get() that was never put() until
device removal.
Hi Kishon,
On Wed, Apr 3, 2013 at 10:38 AM, Kishon Vijay Abraham I kis...@ti.com wrote:
Hi,
On Monday 01 April 2013 07:24 PM, Vivek Gautam wrote:
Adding APIs to handle runtime power management on PHY
devices. PHY consumers may need to wake-up/suspend PHYs
when they work across
From: Kishon Vijay Abraham I kis...@ti.com
Date: Wed, 3 Apr 2013 11:29:53 +0530
Hi,
On Friday 29 March 2013 12:01 AM, David Miller wrote:
You really need to CC: net...@vger.kernel.org rather than me
explicitly
on this patch set.
I was CC'ing whatever get_maintainer shows. I'll make
Hi,
On Wednesday 03 April 2013 12:01 PM, David Miller wrote:
From: Kishon Vijay Abraham I kis...@ti.com
Date: Wed, 3 Apr 2013 11:29:53 +0530
Hi,
On Friday 29 March 2013 12:01 AM, David Miller wrote:
You really need to CC: net...@vger.kernel.org rather than me
explicitly
on this patch set.
Hi,
On Wed, Apr 03, 2013 at 11:48:39AM +0530, Vivek Gautam wrote:
Adding APIs to handle runtime power management on PHY
devices. PHY consumers may need to wake-up/suspend PHYs
when they work across autosuspend.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
Hi,
On Wed, Apr 03, 2013 at 11:35:43AM +0530, Vivek Gautam wrote:
The current code in the dwc3 probe effectively disables runtime pm
from ever working because it calls a get() that was never put() until
device removal. Change the runtime pm code to match the standard
formula and allow
Hi,
On 2013-03-28 14:48, Tomi Valkeinen wrote:
So here are the DSS related board file changes for 3.10.
First there are a bunch of patches adding the Kconfig options so that only one
display device is created for a single video bus. Only Overo had more than two
displays on the same bus, but
cyclic DMA is only used by audio which needs DMA to be started without a
delay.
If the DMA for audio is started using the tasklet we experience random
channel switch (to be more precise: channel shift).
Reported-by: Peter Meerwald pme...@pmeerw.net
Signed-off-by: Peter Ujfalusi
On Wednesday 03 April 2013 04:47 PM, Peter Ujfalusi wrote:
cyclic DMA is only used by audio which needs DMA to be started without a
delay.
If the DMA for audio is started using the tasklet we experience random
channel switch (to be more precise: channel shift).
Reported-by: Peter Meerwald
Hi Matt,
On 3/6/2013 9:45 PM, Matt Porter wrote:
This series adds DMA Engine support for AM33xx, which uses
an EDMA DMAC. The EDMA DMAC has been previously supported by only
a private API implementation (much like the situation with OMAP
DMA) found on the DaVinci family of SoCs.
Matt
Hi Vaibhav,
On Mon, Dec 31, 2012 at 2:07 PM, Vaibhav Bedia vaibhav.be...@ti.com wrote:
AM335x supports various low power modes as documented
in section 8.1.4.3 of the AM335x TRM which is available
@ http://www.ti.com/litv/pdf/spruh73f
May I ask about the plans for this series? Will you be
On 04/03/2013 01:24 PM, Santosh Shilimkar wrote:
On Wednesday 03 April 2013 04:47 PM, Peter Ujfalusi wrote:
cyclic DMA is only used by audio which needs DMA to be started without a
delay.
If the DMA for audio is started using the tasklet we experience random
channel switch (to be more
On Wednesday 03 April 2013 05:22 PM, Peter Ujfalusi wrote:
On 04/03/2013 01:24 PM, Santosh Shilimkar wrote:
On Wednesday 03 April 2013 04:47 PM, Peter Ujfalusi wrote:
cyclic DMA is only used by audio which needs DMA to be started without a
delay.
If the DMA for audio is started using the
From: Matthias Brugger matthias@gmail.com
This patch adds a generic power script configuration.
When rebooting an OMAP3530 at 125 MHz, the reboot hangs.
With the generic power script, TWL4030 will be reset
when a warm reset occures. This way the OMAP3530 does not
hang on reboot.
On 19.03.2013 14:27, Peter Korsgaard wrote:
Daniel == Daniel Mack zon...@gmail.com writes:
Hi,
I know this patch reintroduces bits that have been intentionally
removed before, in particular by 032ec49f53 (usb: musb: drop
useless board_mode usage), but I don't know how this usb
On 2013-02-14 15:51, Igor Grinberg wrote:
On 02/14/13 14:52, Tomi Valkeinen wrote:
On 2013-02-14 14:37, Igor Grinberg wrote:
On 02/14/13 12:59, Tomi Valkeinen wrote:
On 2013-02-14 11:43, Igor Grinberg wrote:
True, it's generic, but does it work reliably? The panel hardware is now
partly
Hi,
(sorry, being really busy lately)
On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote:
I know this patch reintroduces bits that have been intentionally
removed before, in particular by 032ec49f53 (usb: musb: drop
useless board_mode usage), but I don't know how this usb
Hi Felipe,
On 03.04.2013 14:04, Felipe Balbi wrote:
(sorry, being really busy lately)
On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote:
I know this patch reintroduces bits that have been intentionally
removed before, in particular by 032ec49f53 (usb: musb: drop
useless
Whata...
On 04/03/2013 01:59 PM, Peter Ujfalusi wrote:
From: Matthias Brugger matthias@gmail.com
This patch adds a generic power script configuration.
When rebooting an OMAP3530 at 125 MHz, the reboot hangs.
With the generic power script, TWL4030 will be reset
when a warm reset
Hi Tony,
On 2013-02-13 18:46, Tony Lindgren wrote:
* Archit Taneja arc...@ti.com [130213 06:26]:
init functions in omap board files request panel specific gpios, and provide
functions which omapdss panel drivers call to enable or disable them.
Instead of the board files requesting these
From: Matthias Brugger matthias@gmail.com
This patch adds a generic power script configuration.
When rebooting an OMAP3530 at 125 MHz, the reboot hangs.
With the generic power script, TWL4030 will be reset
when a warm reset occures. This way the OMAP3530 does not
hang on reboot.
On 03.04.2013 14:04, Felipe Balbi wrote:
On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote:
Felipe, could you explain the background on how the dsps driver is
supposed to work in host mode at boot time with the rework of the driver
you did for 3.7? It might just be me not
Used the generic PHY framework API to create the PHY. omap_usb2_suspend
is split into omap_usb_suspend and omap_usb_resume in order to align
with the new framework.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined with PHY and moving to the new
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. To obtain a reference to the PHY without
using phandle, the platform specfic intialization code (say from board file)
Added a generic PHY framework that provides a set of APIs for the PHY drivers
to create/destroy a PHY and APIs for the PHY users to obtain a reference to
the PHY with or without using phandle. To obtain a reference to the PHY
without using phandle, the platform specfic intialization code (say from
In order for controllers to get PHY in case of non dt boot, the phy
binding information should be added in the platform specific
initialization code using phy_bind.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/mach-omap2/usb-musb.c |7 ++-
1 file changed, 6
Use the generic PHY framework API to get the PHY. The usb_phy_set_suspend
and usb_phy_set_resume is replaced with phy_suspend and phy_resume to
align with the new PHY framework.
musb-xceiv can't be removed as of now because musb core uses xceiv.state and
xceiv.otg. Once there is a separate state
Used the generic PHY framework API to create the PHY. twl4030_usb_suspend
and twl4030_usb_resume is added to phy_ops in order to align
with the new framework.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined with PHY and moving to the new
framework
Updated the usb_otg_hs dt data to include the *phy* and *phy-names*
binding in order for the driver to use the new generic PHY framework.
Also updated the Documentation to include the binding information.
The PHY binding information can be found at
Hi,
On Wed, Apr 03, 2013 at 02:43:00PM +0200, Daniel Mack wrote:
On 03.04.2013 14:04, Felipe Balbi wrote:
On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote:
Felipe, could you explain the background on how the dsps driver is
supposed to work in host mode at boot time with the
Op 3 apr. 2013, om 15:09 heeft Felipe Balbi ba...@ti.com het volgende
geschreven:
Hi,
On Wed, Apr 03, 2013 at 02:43:00PM +0200, Daniel Mack wrote:
On 03.04.2013 14:04, Felipe Balbi wrote:
On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote:
Felipe, could you explain the
Hi Felipe,
On Wed, Apr 3, 2013 at 1:45 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Wed, Apr 03, 2013 at 11:48:39AM +0530, Vivek Gautam wrote:
Adding APIs to handle runtime power management on PHY
devices. PHY consumers may need to wake-up/suspend PHYs
when they work across autosuspend.
On 03.04.2013 15:12, Koen Kooi wrote:
Op 3 apr. 2013, om 15:09 heeft Felipe Balbi ba...@ti.com het
volgende geschreven:
Hi,
On Wed, Apr 03, 2013 at 02:43:00PM +0200, Daniel Mack wrote:
On 03.04.2013 14:04, Felipe Balbi wrote:
On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote:
On Wed, Apr 03, 2013 at 06:23:49PM +0530, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. To obtain a reference to the PHY without
using
Hi,
On Wed, Apr 03, 2013 at 03:12:11PM +0200, Koen Kooi wrote:
On Wed, Apr 03, 2013 at 02:43:00PM +0200, Daniel Mack wrote:
On 03.04.2013 14:04, Felipe Balbi wrote:
On Wed, Apr 03, 2013 at 02:00:23PM +0200, Daniel Mack wrote:
Felipe, could you explain the background on how the dsps
Hi,
On Wed, Apr 03, 2013 at 03:16:05PM +0200, Daniel Mack wrote:
On 03.04.2013 15:12, Koen Kooi wrote:
Op 3 apr. 2013, om 15:09 heeft Felipe Balbi ba...@ti.com het
volgende geschreven:
Hi,
On Wed, Apr 03, 2013 at 02:43:00PM +0200, Daniel Mack wrote:
On 03.04.2013 14:04, Felipe
On Wed, Apr 03, 2013 at 06:23:50PM +0530, Kishon Vijay Abraham I wrote:
Used the generic PHY framework API to create the PHY. omap_usb2_suspend
is split into omap_usb_suspend and omap_usb_resume in order to align
with the new framework.
However using the old USB PHY library cannot be
HI,
On Wed, Apr 03, 2013 at 06:42:48PM +0530, Vivek Gautam wrote:
Adding APIs to handle runtime power management on PHY
devices. PHY consumers may need to wake-up/suspend PHYs
when they work across autosuspend.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
Hi,
On Wed, Apr 03, 2013 at 04:54:14PM +0300, Felipe Balbi wrote:
+static inline void usb_phy_autopm_enable(struct usb_phy *x)
+{
+ if (!x || !x-dev) {
+ dev_err(x-dev, no PHY or attached device
available\n);
+ return;
+
Hi,
On Wed, Apr 3, 2013 at 7:26 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Wed, Apr 03, 2013 at 04:54:14PM +0300, Felipe Balbi wrote:
+static inline void usb_phy_autopm_enable(struct usb_phy *x)
+{
+ if (!x || !x-dev) {
+ dev_err(x-dev, no PHY or attached
Hi,
On Wed, Apr 03, 2013 at 07:40:44PM +0530, Vivek Gautam wrote:
+static inline void usb_phy_autopm_enable(struct usb_phy *x)
+{
+ if (!x || !x-dev) {
+ dev_err(x-dev, no PHY or attached device
available\n);
+ return;
+
Hi,
On Wednesday 03 April 2013 07:12 PM, Felipe Balbi wrote:
On Wed, Apr 03, 2013 at 06:23:49PM +0530, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without
hi,
On Wed, Apr 03, 2013 at 07:48:42PM +0530, Kishon Vijay Abraham I wrote:
+struct phy *of_phy_xlate(struct phy *phy, struct of_phandle_args *args)
+{
+ return phy;
+}
+EXPORT_SYMBOL_GPL(of_phy_xlate);
so you get a PHY and just return it ? What gives ?? (maybe I skipped
some of the
Hi,
On Wednesday 03 April 2013 07:57 PM, Felipe Balbi wrote:
hi,
On Wed, Apr 03, 2013 at 07:48:42PM +0530, Kishon Vijay Abraham I wrote:
+struct phy *of_phy_xlate(struct phy *phy, struct of_phandle_args *args)
+{
+ return phy;
+}
+EXPORT_SYMBOL_GPL(of_phy_xlate);
so you get a PHY and
On Wed, Apr 3, 2013 at 7:48 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Wed, Apr 03, 2013 at 07:40:44PM +0530, Vivek Gautam wrote:
+static inline void usb_phy_autopm_enable(struct usb_phy *x)
+{
+ if (!x || !x-dev) {
+ dev_err(x-dev, no PHY or attached
On 04/02/2013 08:21 PM, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [130320 09:24]:
On Wed, Mar 20, 2013 at 09:13:24AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [130320 09:00]:
On Wed, Mar 20, 2013 at 05:44:40PM +0200, Roger Quadros wrote:
Add clk_rate parameter to platform
On Wednesday 03 April 2013, Felipe Balbi wrote:
const ? Maybe provide a:
#define DEFINE_PHY_OPS(name)\
const struct phy_ops #name_phy_ops = {
macro ? This will force people to add the const keyword :-)
Forcing people to use const structures is good, but I think it would be
better
* Peter Ujfalusi peter.ujfal...@ti.com [130403 05:36]:
From: Matthias Brugger matthias@gmail.com
This patch adds a generic power script configuration.
When rebooting an OMAP3530 at 125 MHz, the reboot hangs.
With the generic power script, TWL4030 will be reset
when a warm reset occures.
* Tomi Valkeinen tomi.valkei...@ti.com [130403 05:32]:
Hi Tony,
On 2013-02-13 18:46, Tony Lindgren wrote:
* Archit Taneja arc...@ti.com [130213 06:26]:
init functions in omap board files request panel specific gpios, and
provide
functions which omapdss panel drivers call to enable or
Hi,
On Wed, Apr 03, 2013 at 08:02:52PM +0530, Kishon Vijay Abraham I wrote:
+ ret = -EINVAL;
+ goto err0;
+ }
+
+ if (!phy_class)
+ phy_core_init();
why don't you setup the class on module_init ? Then this would be a
terrible error condition here :-)
This is
Hi,
On Wed, Apr 03, 2013 at 02:55:47PM +, Arnd Bergmann wrote:
On Wednesday 03 April 2013, Felipe Balbi wrote:
const ? Maybe provide a:
#define DEFINE_PHY_OPS(name)\
const struct phy_ops #name_phy_ops = {
macro ? This will force people to add the const keyword :-)
Paul,
Should I start a new email chain with that patch or add it here?
On Wed, Apr 3, 2013 at 12:19 AM, Alexey Pelykh alexey.pel...@gmail.com wrote:
Hi Paul,
No problem, I'll prepare patch in next 24 hours and will send in ASAP.
But, since we've found the issue, I suggest that we should
From: Kishon Vijay Abraham I kis...@ti.com
Date: Wed, 3 Apr 2013 12:05:30 +0530
This patch series is about drivers/phy which will be used for now by
usb, sata and maybe some video PHY's. Network itself has a
comprehensive PHY in drivers/net/phy which we'd like to merge it with
drivers/phy so
On Tue, Mar 26, 2013 at 11:22:00PM +, Russell King - ARM Linux wrote:
On Mon, Mar 25, 2013 at 02:31:26PM -0500, Jon Hunter wrote:
Hi Russell,
On 03/19/2013 12:59 PM, Tony Lindgren wrote:
Hi Russell,
Can we use your commit 71856843 (ARM: OMAP: use consistent error checking)
Question: Do you still need this patch for 3.10?
http://marc.info/?l=linux-usbm=136057666911621w=2
Does this patchset build on top of that?
I'm really behind on my patches for 3.10, sorry.
Sarah Sharp
On Mon, Apr 01, 2013 at 07:23:59PM +0530, Vivek Gautam wrote:
This patch-series enables
Nishanth Menon n...@ti.com writes:
The following version 3 of the series arose from trying to use BeagleBoard-XM
(OMAP3 variant) for doing CPU DVFS using cpufreq-cpu0. This series enables the
generic cpufreq-cpu0 driver to be used in device tree enabled boot while
maintaining support of the
Sourav Poddar sourav.pod...@ti.com writes:
Hi Kevin,
On Wednesday 20 March 2013 05:36 PM, Sourav Poddar wrote:
Realised the list to whom the patch was send got dropped. Ccing
them all..
On Wednesday 20 March 2013 05:18 PM, Sourav Poddar wrote:
Hi Kevin,
On Tuesday 19 March 2013 12:24 AM,
* Russell King - ARM Linux li...@arm.linux.org.uk [130403 09:58]:
On Tue, Mar 26, 2013 at 11:22:00PM +, Russell King - ARM Linux wrote:
On Mon, Mar 25, 2013 at 02:31:26PM -0500, Jon Hunter wrote:
Hi Russell,
On 03/19/2013 12:59 PM, Tony Lindgren wrote:
Hi Russell,
Can
* Jon Hunter jon-hun...@ti.com [130401 19:14]:
The following changes since commit 2d61aecee8f32259920cdf90a452fa26ffc64e9f:
Merge commit '6bb27d7349db51b50c40534710fe164ca0d58902' into
omap-timer-for-v3.10 (2013-04-01 13:47:29 -0500)
are available in the git repository at:
On Wed, 3 Apr 2013, Felipe Balbi wrote:
Lets suppose DWC3 enables runtime_pm on USB 2 type phy,
it will try to go into suspend state and thereby call runtime_suspend(), if
any.
And PHY will come to active state only when its consumer wakes it up,
and this consumer is operational
only
On 10:47-20130403, Kevin Hilman wrote:
Nishanth Menon n...@ti.com writes:
[...]
Test coverage:
test script: http://pastebin.com/zrr8ptge
Platforms verified:
beaglebone(rev A6a) - AM33xx compatible - http://pastebin.com/GVP2wDVr
beagleboard (rev C1D) - OMAP3430 compatible
From: Alexey Pelykh alexey.pel...@gmail.com
Partially reverts 1776fd059c40907297d6c26c51876575d63fd9e2
that introduced regression reported by Paul Walmsley.
This commit restores setting granularity in SCR register
and adds note about comments below being inconsistent with
actual code.
Nishanth Menon n...@ti.com writes:
With OMAP3+ and AM33xx supported SoC having defined CPU device tree
entries with operating-points defined, we can now use the SoC
generic cpufreq-cpu0 driver by registering appropriate device.
As part of this change, add dummy clock node to use
I've submitted patch that should remove this regression
On Wed, Apr 3, 2013 at 6:55 PM, Alexey Pelykh alexey.pel...@gmail.com wrote:
Paul,
Should I start a new email chain with that patch or add it here?
On Wed, Apr 3, 2013 at 12:19 AM, Alexey Pelykh alexey.pel...@gmail.com
wrote:
Hi
Hi Santosh
On Wed, 3 Apr 2013, Santosh Shilimkar wrote:
Thes patchset has already missed last couple of merge windows and its the
biggest bottleneck in getting OMAP5 booting from mainline. So I request
you to please have a look it quickly so that Tony can line that up for
3.10.
Looks like
Hi Santosh,
Santosh Shilimkar santosh.shilim...@ti.com writes:
OMAP5 and future OMAP based SOCs has backward compatible MPUSS
IP block with OMAP4. It's programming model is mostly similar.
Hence consolidate the OMAP MPUSS code so that it can be re-used
on OMAP5 and future SOCs.
No
Quoting Nishanth Menon (2013-04-02 19:00:02)
On 20:35-20130402, Andrii Tseglytskyi wrote:
On 04/02/2013 08:16 PM, Mike Turquette wrote:
Quoting Nishanth Menon (2013-04-01 20:35:45)
On 17:05-20130401, Mike Turquette wrote:
OK, so we're in agreement on what The Future looks like. What does
cc Kevin
Hi
On Wed, 20 Mar 2013, Santosh Shilimkar wrote:
Benoit Cousson (7):
ARM: OMAP5: PRM: Add OMAP54XX register and bitfield files
So it looks like this patch never made it to the mailing list. Was it too
big? If so, please try splitting it into two or more pieces. Looking at
Hi,
On Fri, 18 Jan 2013, Santosh Shilimkar wrote:
Series contains the hwmod, clock and prm data files for OMAP54xx SOCs.
This data was kept out of tree to be validated on es2.0 silicon version
and also to avoid the es1.0/es2.0 differences which are many.
Benoit Cousson, Rajendra Nayak,
Hi Greg, Alexey,
On Wed, 3 Apr 2013, Alexey Pelykh wrote:
From: Alexey Pelykh alexey.pel...@gmail.com
Partially reverts 1776fd059c40907297d6c26c51876575d63fd9e2
that introduced regression reported by Paul Walmsley.
This commit restores setting granularity in SCR register
and adds note
On Wed, 3 Apr 2013, Alexey Pelykh wrote:
I've submitted patch that should remove this regression
Thanks, indeed it does. So the revert patch that I sent at the beginning
of this thread is now mooted.
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of
Santosh Shilimkar santosh.shilim...@ti.com writes:
OMAP5 has backward compatible PRCM block and it's programming
model is mostly similar to OMAP4. Same is going to be maintained
for future OMAP4 based SOCs. Hence consolidate the OMAP4 power
management code so that it can be re-used on OMAP5
Hi,
On Wed, 3 Apr 2013, Alexey Pelykh wrote:
But, since we've found the issue, I suggest that we should look at it
closer, especially since at this moment only you can reproduce it. As
far as I understand, but I may be wrong,
this comment is wrong, since if to specify
On Wed, Apr 03, 2013 at 08:16:18PM +, Paul Walmsley wrote:
Hi Greg, Alexey,
On Wed, 3 Apr 2013, Alexey Pelykh wrote:
From: Alexey Pelykh alexey.pel...@gmail.com
Partially reverts 1776fd059c40907297d6c26c51876575d63fd9e2
that introduced regression reported by Paul Walmsley.
Santosh Shilimkar santosh.shilim...@ti.com writes:
Enables MPUSS ES2 power management mode using ES2_PM_MODE in
AMBA_IF_MODE register.
0x0: ES1 behavior, CPU cores would enter and exit OFF mode together. Broken
What is broken?
0x1: ES2 behavior, CPU cores are allowed to enter/exit OFF mode
Santosh Shilimkar santosh.shilim...@ti.com writes:
In addition to the standard power-management technique, the OMAP5
MPU subsystem also employs an SR3-APG (mercury) power management
technology to reduce leakage.
It allows for full logic and memories retention on MPU_C0 and MPU_C1 and
is
Santosh Shilimkar santosh.shilim...@ti.com writes:
With consolidated code, now we can add the .init_late hook for
OMAP5 to enable power management and mux initialization.
Acked-by: Nishanth Menon n...@ti.com
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
Hi
On Wed, Apr 3, 2013 at 11:21 PM, Paul Walmsley p...@pwsan.com wrote:
Hi,
On Wed, 3 Apr 2013, Alexey Pelykh wrote:
But, since we've found the issue, I suggest that we should look at it
closer, especially since at this moment only you can reproduce it. As
far as I understand, but I may be
Hi,
On Wed, Apr 3, 2013 at 12:19 AM, Alexey Pelykh alexey.pel...@gmail.com wrote:
But, since we've found the issue, I suggest that we should look at it
closer, especially since at this moment only you can reproduce it. As
FWIW I was also affected by it, maybe because my console is on UART3
Santosh Shilimkar santosh.shilim...@ti.com writes:
Add power management code to handle the CPU off mode to enable CPUP hotplug
mode for OMAP5 devices. Separate suspend finisher is used for
OMAP5(Cortex-A15)
because it doesn't use SCU power status register and external PL310 L2 cache
which
Santosh Shilimkar santosh.shilim...@ti.com writes:
While waking up CPU from off state using clock domain force wakeup, restore
the CPU power state to ON state before putting CPU clock domain under
hardware control. Otherwise CPU wakeup might fail. The change is recommended
for all OMAP4+
Hi Alexey,
On Wed, 3 Apr 2013, Alexey Pelykh wrote:
But, since we've found the issue, I suggest that we should look at it
closer, especially since at this moment only you can reproduce it.
Well probably no one else is testing it :-)
As far as I understand, but I may be wrong, this comment
Santosh Shilimkar santosh.shilim...@ti.com writes:
When the entire MPUSS cluster is powered down in device off state, L2 cache
memory looses it's content and hence while targetting such a state,
l2 cache needs to be flushed to main memory.
Add the necessary low power code support for the
Santosh Shilimkar santosh.shilim...@ti.com writes:
OMAP4 CPUidle driver registration call is under a loop which leads
to calling cpuidle_register_driver twice which is not intended.
Fix it by moving the driver registration outside the loop.
Reported-by: Nishanth Menon n...@ti.com
Acked-by:
Santosh Shilimkar santosh.shilim...@ti.com writes:
If the CPUidle device registration fails for some reason, we should
unregister the driver on error path.
Fix the code accordingly. Also when at it, check of the driver registration
failure too.
Acked-by: Nishanth Menon n...@ti.com
Santosh Shilimkar santosh.shilim...@ti.com writes:
It is useful to know the CPU power state along with MPUSS power state
in a supported C-state. Since the data is available via sysfs, one can
avoid scrolling the source code for precise construction of C-state.
Reported-by: Nishanth Menon
Hi Paul,
Is it possible to check behavior on 3.0-3.2 kernels?
On Wed, Apr 3, 2013 at 11:57 PM, Paul Walmsley p...@pwsan.com wrote:
Hi Alexey,
On Wed, 3 Apr 2013, Alexey Pelykh wrote:
But, since we've found the issue, I suggest that we should look at it
closer, especially since at this
Santosh Shilimkar santosh.shilim...@ti.com writes:
The OMAP5 idle driver can re-use most of OMAP4 CPUidle driver
implementation. Also the next derivative SOCs are going to re-use
the MPUSS so, same driver with minor updates can be re-used.
Prepare the code so that its easier to add CPUidle
Santosh Shilimkar santosh.shilim...@ti.com writes:
The OMAP5 idle driver can re-use OMAP4 CPUidle driver implementation thanks
to compatible MPUSS design.
Though unlike OMAP4, on OMAP5 devices, MPUSS CSWR (Close Switch
Retention) power states can be achieved with respective power states
on
Santosh Shilimkar santosh.shilim...@ti.com writes:
Current OMAP4 CPUIdle driver is using omap4_mpuss_read_prev_context_state()
function to check whether the MPU cluster lost context or not. Thanks to
couple CPUIdle, cluster low power entry is almost guaranteed and hence
the programmed cluster
* Jon Hunter jon-hun...@ti.com [130402 10:00]:
The following changes since commit dca3a783400a18e2bf4503b1d4a85c4d0ca1a7e4:
Merge commit '31d9adca82ce65e5c99d045b5fd917c702b6fce3' into tmp
(2013-04-01 14:33:50 -0500)
are available in the git repository at:
On 04/03/2013 02:53 PM, Kishon Vijay Abraham I wrote:
--- /dev/null
+++ b/Documentation/devicetree/bindings/phy/phy-bindings.txt
@@ -0,0 +1,67 @@
+This document explains only the dt data binding. For general information about
s/dt data/device tree ?
+PHY subsystem refer Documentation/phy.txt
Hi Laurent,
On Tue, Mar 26, 2013 at 12:07:01AM +0100, Laurent Pinchart wrote:
On Sunday 24 March 2013 23:46:01 Sakari Ailus wrote:
Pali Rohár wrote:
On Thursday 07 March 2013 23:18:27 Sakari Ailus wrote:
On Wed, Mar 06, 2013 at 10:44:41PM +0100, Sebastian Reichel wrote:
On Wed, Mar
Hi Santosh,
Santosh Shilimkar santosh.shilim...@ti.com writes:
Here is the refreshed version(v2) of the OMAP5 PM suspport which was posted
earlier (March 1st 2013). Patch-set incorporates comments from Nishant
Menon (Thanks for review NM) and his acked-by tags. I would like to get this
Hi,
* Roger Quadros rog...@ti.com [130319 07:31]:
Register a device tree clock provider for AUX clocks
on the OMAP4 SoC. Also provide the binding information.
Signed-off-by: Roger Quadros rog...@ti.com
---
.../devicetree/bindings/clock/omap4-clock.txt | 32 ++
On 04/03/2013 06:53 AM, Kishon Vijay Abraham I wrote:
Added a generic PHY framework that provides a set of APIs for the PHY drivers
to create/destroy a PHY and APIs for the PHY users to obtain a reference to
the PHY with or without using phandle. To obtain a reference to the PHY
without using
On 04/03/2013 06:53 AM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. To obtain a reference to the PHY without
using phandle, the
On 04/03/2013 04:40 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130402 10:00]:
The following changes since commit dca3a783400a18e2bf4503b1d4a85c4d0ca1a7e4:
Merge commit '31d9adca82ce65e5c99d045b5fd917c702b6fce3' into tmp
(2013-04-01 14:33:50 -0500)
are available in the git
(( Attempting to re-post this since Yahoo! shipped the previous one as HTML...
))
All,
My team is presently seeing *extremely poor* (on the order of single-digit
Mbps) Ethernet performance out of an AM3517-based COM (Technexion's TAM-3517 in
this case) when it _transmits TCP_. Receiving TCP
1 - 100 of 106 matches
Mail list logo
