On Wed, 27 Aug 2014, Nishanth Menon wrote:
> On Mon, Jul 28, 2014 at 12:34 AM, Lokesh Vutla wrote:
> > On Monday 28 July 2014 10:59 AM, Paul Walmsley wrote:
> >> On Mon, 28 Jul 2014, Lokesh Vutla wrote:
> >>
> >>> From: Rajendra Nayak
> >>>
> >>> Use the corresponding compatibles to identify the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tony,
The following changes since commit 52addcf9d6669fa439387610bc65c92fa0980cef:
Linux 3.17-rc2 (2014-08-25 15:36:20 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git
tags/fo
Hi,
On Wed, Aug 27, 2014 at 04:28:07PM -0700, Tony Lindgren wrote:
> It's not being used any longer.
>
> Signed-off-by: Tony Lindgren
> ---
> drivers/phy/phy-twl4030-usb.c | 2 --
> drivers/usb/phy/phy-twl6030-usb.c | 2 --
> 2 files changed, 4 deletions(-)
>
> diff --git a/drivers/phy/phy
We can now let the interrupt and delayed work do all that's
needed with runtime PM.
Signed-off-by: Tony Lindgren
---
drivers/phy/phy-twl4030-usb.c | 20 +++-
1 file changed, 3 insertions(+), 17 deletions(-)
diff --git a/drivers/phy/phy-twl4030-usb.c b/drivers/phy/phy-twl4030-usb
It's not being used any longer.
Signed-off-by: Tony Lindgren
---
drivers/phy/phy-twl4030-usb.c | 2 --
drivers/usb/phy/phy-twl6030-usb.c | 2 --
2 files changed, 4 deletions(-)
diff --git a/drivers/phy/phy-twl4030-usb.c b/drivers/phy/phy-twl4030-usb.c
index 9cd33a4..bc28ecc 100644
--- a/dri
There's no longer need for tracking the phy state in the driver
with asleep, we can now rely on runtime PM.
Signed-off-by: Tony Lindgren
---
drivers/phy/phy-twl4030-usb.c | 14 +-
1 file changed, 5 insertions(+), 9 deletions(-)
diff --git a/drivers/phy/phy-twl4030-usb.c b/drivers/ph
We're using threaded irq on a I2C bus and we're sleeping in
twl4030_usb_irq() as it calls twl4030_usb_linkstat() which
calls the i2c functions. If we ever need to lock for longer
I2C transaction sequences a mutex will allow us to do that
easily.
Signed-off-by: Tony Lindgren
---
drivers/phy/phy-t
We don't need twl4030_phy_power() any longer now that we have
the runtime PM calls. Let's get rid of it as it's confusing.
No functional changes, just move the code and use res instead
of ret as we are not returning that value.
Signed-off-by: Tony Lindgren
---
drivers/phy/phy-twl4030-usb.c | 72
Hi,
Here are few more patches for v3.18 to clean up twl4030-usb.
These are based on the two regression fixes I sent earlier:
[PATCH] usb: phy: twl4030-usb: Fix regressions to runtime PM on omaps
[PATCH] usb: phy: twl4030-usb: Fix lost interrupts after ID pin goes down
For testing with v3.17-rc2
On Tue, Aug 26, 2014 at 03:14:13PM -0700, Tony Lindgren wrote:
> The following changes since commit 52addcf9d6669fa439387610bc65c92fa0980cef:
>
> Linux 3.17-rc2 (2014-08-25 15:36:20 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/li
Nishanth Menon writes:
> powerdomain configuration in OMAP is done using PWRSTCTRL register for
> each power domain. However, PRCM lets us write any value we'd like to
> the logic and power domain target states, however the SoC integration
> tends to actually function only at a few discrete state
* Sebastian Andrzej Siewior [140827 12:54]:
> On 08/21/2014 08:44 PM, Tony Lindgren wrote:
> >>> Also, with DMA enabled, looks like omap deeper idle states are
> >>> blocked as the DMA stays reserved. After I commented out the
> >>> DMA info for my console UART, PM started working.
> >>
> >> Hmm.
Santosh Shilimkar writes:
> On Wednesday 27 August 2014 03:35 PM, Nishanth Menon wrote:
>> On Wed, Aug 27, 2014 at 2:13 PM, Kevin Hilman
>> wrote:
>>> + Daniel (cpuidle maintainer)
>> [...]
+static int omap_enter_idle_smp(struct cpuidle_device *dev,
+struct
On 08/21/2014 08:44 PM, Tony Lindgren wrote:
>>> Also, with DMA enabled, looks like omap deeper idle states are
>>> blocked as the DMA stays reserved. After I commented out the
>>> DMA info for my console UART, PM started working.
>>
>> Hmm. This would explain something. This would mean that I shou
On 08/27/2014 02:43 PM, Santosh Shilimkar wrote:
> On Wednesday 27 August 2014 03:41 PM, Tony Lindgren wrote:
>> * Nishanth Menon [140827 12:05]:
>>> On 08/27/2014 01:58 PM, Kevin Hilman wrote:
Nishanth Menon writes:
> From: Rajendra Nayak
>
> On OMAP5 / DRA7, prevent a CPU
On Wednesday 27 August 2014 03:41 PM, Tony Lindgren wrote:
> * Nishanth Menon [140827 12:05]:
>> On 08/27/2014 01:58 PM, Kevin Hilman wrote:
>>> Nishanth Menon writes:
>>>
From: Rajendra Nayak
On OMAP5 / DRA7, prevent a CPU powerdomain OFF and resulting MPU OSWR
and instead a
* Nishanth Menon [140827 12:05]:
> On 08/27/2014 01:58 PM, Kevin Hilman wrote:
> > Nishanth Menon writes:
> >
> >> From: Rajendra Nayak
> >>
> >> On OMAP5 / DRA7, prevent a CPU powerdomain OFF and resulting MPU OSWR
> >> and instead attempt a CPU RET and side effect, MPU RET in suspend.
> >>
>
On Wednesday 27 August 2014 03:35 PM, Nishanth Menon wrote:
> On Wed, Aug 27, 2014 at 2:13 PM, Kevin Hilman
> wrote:
>> + Daniel (cpuidle maintainer)
> [...]
>>> +static int omap_enter_idle_smp(struct cpuidle_device *dev,
>>> +struct cpuidle_driver *drv,
>>> +
On Wed, Aug 27, 2014 at 2:13 PM, Kevin Hilman
wrote:
> + Daniel (cpuidle maintainer)
[...]
>> +static int omap_enter_idle_smp(struct cpuidle_device *dev,
>> +struct cpuidle_driver *drv,
>> +int index)
>> +{
>> + struct idle_statedata *cx
Nishanth Menon writes:
> The following series are various fixes and improvements for
> supporting suspend-to-ram. This depends on the following for basic
> functionality:
> series 1/6 where powerdomain fixes were involved.
I had a look through this series, and it looks good overall. I think Da
+ Daniel (cpuidle maintainer)
Nishanth Menon writes:
> From: Santosh Shilimkar
>
> Add OMAP5/DRA74/72 CPUIDLE support.
>
> This patch adds MPUSS low power states in cpuidle.
>
> C1 - CPU0 WFI + CPU1 WFI + MPU ON
> C2 - CPU0 RET + CPU1 RET + MPU CSWR
>
> Tested on DRA74/72-EVM fo
On 08/27/2014 01:58 PM, Kevin Hilman wrote:
> Nishanth Menon writes:
>
>> From: Rajendra Nayak
>>
>> On OMAP5 / DRA7, prevent a CPU powerdomain OFF and resulting MPU OSWR
>> and instead attempt a CPU RET and side effect, MPU RET in suspend.
>>
>> Signed-off-by: Rajendra Nayak
>> [n...@ti.com: u
Nishanth Menon writes:
> From: Rajendra Nayak
>
> On OMAP5 / DRA7, prevent a CPU powerdomain OFF and resulting MPU OSWR
> and instead attempt a CPU RET and side effect, MPU RET in suspend.
>
> Signed-off-by: Rajendra Nayak
> [n...@ti.com: update to do save_state only on DRA7]
> Signed-off-by: N
powerdomain configuration in OMAP is done using PWRSTCTRL register for
each power domain. However, PRCM lets us write any value we'd like to
the logic and power domain target states, however the SoC integration
tends to actually function only at a few discrete states. These valid
states are already
Nishanth Menon writes:
> From: Santosh Shilimkar
>
> With EMIF clock-domain put under hardware supervised control, memory
> corruption and untraceable crashes are observed on OMAP5. Further
> investigation revealed that there is a weakness in the PRCM on this
> specific dynamic depedency.
hmm,
On Friday 22 August 2014 09:51 AM, Nishanth Menon wrote:
> The following series are various fixes and improvements for
> PRM for I/O Daisy chain support in OMAP4+ with device tree.
>
> This is part 2/6 series which eventually enables framework for
> suspend-to-ram and cpuidle for OMAP5 and DRA7
>
On Wed, Aug 27, 2014 at 11:35 AM, Nishanth Menon wrote:
> On Wed, Aug 27, 2014 at 1:27 PM, Kevin Hilman
> wrote:
>> Nishanth Menon writes:
>>
>>> powerdomain configuration in OMAP is done using PWRSTCTRL register for
>>> each power domain. However, PRCM lets us write any value we'd like to
>>> t
On Friday 22 August 2014 09:49 AM, Nishanth Menon wrote:
> Hi,
>
> The following series are various fixes and improvements for
> powerdomain support in OMAP4+.
>
> This is part 1/6 series which eventually enables framework for
> suspend-to-ram and cpuidle for OMAP5 and DRA7
>
> Each of series is
On Wed, Aug 27, 2014 at 1:27 PM, Kevin Hilman
wrote:
> Nishanth Menon writes:
>
>> powerdomain configuration in OMAP is done using PWRSTCTRL register for
>> each power domain. However, PRCM lets us write any value we'd like to
>> the logic and power domain target states, however the SoC integrati
Nishanth Menon writes:
> The following series are various fixes and improvements for
> powerdomain support in OMAP4+.
Ah, here I see "fixes and improvements" since I was about to nipick that
the series contains more than just fixes.
Anyways, the series looks good to me. After fixing up the BUG
Nishanth Menon writes:
> powerdomain configuration in OMAP is done using PWRSTCTRL register for
> each power domain. However, PRCM lets us write any value we'd like to
> the logic and power domain target states, however the SoC integration
> tends to actually function only at a few discrete state
On Tue, Aug 26, 2014 at 11:03:36AM +0100, Marc Zyngier wrote:
> Use the new handle_domain_irq method to handle interrupts.
>
> Signed-off-by: Marc Zyngier
This (and the other two openrisc related patches in this series) works fine
in my setup at least.
Acked-by: Stefan Kristiansson
--
To unsub
On Mon, Jul 28, 2014 at 12:34 AM, Lokesh Vutla wrote:
> On Monday 28 July 2014 10:59 AM, Paul Walmsley wrote:
>> On Mon, 28 Jul 2014, Lokesh Vutla wrote:
>>
>>> From: Rajendra Nayak
>>>
>>> Use the corresponding compatibles to identify the devices.
>>>
>>> Signed-off-by: Rajendra Nayak
>>> Signe
* Paul Walmsley [140827 09:38]:
> On Mon, 25 Aug 2014, Tony Lindgren wrote:
>
> > Looks like MUSB cable removal can cause wake-up interrupts to
> > stop working for device tree based booting at least for UART3
> > even as nothing is dynamically remuxed. This can be fixed by
> > calling reconfigur
Here are some basic OMAP test results for Linux v3.17-rc1.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.17-rc1/20140821122707/
Test summary
Build: zImage:
Pass (16/16): multi_v7_defconfig, omap2plus_defconfig,
omap2plus_defconfig_
Here are some basic OMAP test results for Linux v3.17-rc2.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.17-rc2/20140825183438/
Test summary
Build: uImage+dtb:
Pass (10/10): omap2plus_defconfig_am33xx_only/am335x-bone,
omap2plus_de
On Mon, 25 Aug 2014, Tony Lindgren wrote:
> Looks like MUSB cable removal can cause wake-up interrupts to
> stop working for device tree based booting at least for UART3
> even as nothing is dynamically remuxed. This can be fixed by
> calling reconfigure_io_chain() for device tree based booting
>
Hi,
I am trying to get both CSI2 interfaces up and running through the ISS
on the v3.16 kernel for the TI OMAP4 Blaze platform (omap4430 ES 2.3
revision).
Trough a omap_device_build() call (using the "iss" omap_hwmod) I call the
iss_probe function. It devm_clk_get's both the iss_ctrlclk and th
On 08/21/2014 04:49 PM, Tero Kristo wrote:
Previously, the TI clock driver initialized all the clocks hierarchically
under each separate clock provider node. Now, each clock that requires
IO access will instead check their parent node to find out which IO range
to use.
This patch allows the TI c
On 26/08/14 19:58, Laurent Pinchart wrote:
> Hi Tomi,
>
> On Monday 16 December 2013 16:56:34 Tomi Valkeinen wrote:
>> Signed-off-by: Tomi Valkeinen
>> ---
>> .../video/omap2/displays-new/connector-analog-tv.c | 66 ++-
>> 1 file changed, 65 insertions(+), 1 deletion(-)
>>
>> dif
Hi Thomas,
On Tue, Aug 26 2014 at 10:34:51 pm BST, Thomas Gleixner
wrote:
> On Tue, 26 Aug 2014, Marc Zyngier wrote:
>
>> A number of irqchip drivers are directly calling irq_find_mapping,
>> which may use a rcu_read_lock call when walking the radix tree.
>>
>> Turns out that if you hit that po
Hi Andreas,
On 08/24/2014 07:46 PM, Andreas Fenkart wrote:
> Hi Florian
>
> 2014-08-24 10:26 GMT+02:00 Florian Vaussard :
>> Hi Andreas,
>>
>> On 05/29/2014 10:28 AM, Andreas Fenkart wrote:
>>> There have been various patches floating around for enabling
>>> the SDIO IRQ for hsmmc, but none of th
Hi Tony, Andreas,
On 08/24/2014 08:41 PM, Tony Lindgren wrote:
> * Florian Vaussard [140824 01:29]:
>> --- a/arch/arm/boot/dts/omap3-overo-base.dtsi
>> +++ b/arch/arm/boot/dts/omap3-overo-base.dtsi
>> @@ -119,7 +119,7 @@
>> OMAP3_CORE1_IOPAD(0x2158, PIN_INPUT_PULLUP | MUX_MOD
43 matches
Mail list logo
