On Tue, Apr 23, 2013 at 02:45:45PM -0700, Tony Lindgren wrote:
>
> The following changes since commit 31880c37c11e28cb81c70757e38392b42e695dc6:
>
> Linux 3.9-rc6 (2013-04-07 20:49:54 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/
On Fri, Apr 26, 2013 at 03:03:07PM -0700, Kevin Hilman wrote:
> Hi Greg,
>
> Sourav Poddar writes:
>
> > Move "uart_console" definition to serial core header file, so that it can be
> > used by serial drivers.
> > Get rid of the uart_console defintion from mpc52xx_uart driver.
> >
> > Cc: Santos
On 04/26/2013 02:31 AM, Linus Walleij wrote:
> On Wed, Apr 17, 2013 at 2:41 AM, Javier Martinez Canillas
> wrote:
>
> So:
>
>> +static int omap_gpio_irq_domain_xlate(struct irq_domain *d,
>> + struct device_node *ctrlr,
>> +
On 04/26/2013 02:27 AM, Linus Walleij wrote:
> On Wed, Apr 17, 2013 at 5:41 PM, Stephen Warren wrote:
>> On 04/16/2013 05:14 PM, Jon Hunter wrote:
>
c) I have the feeling that hooking the of_xlate function for this is a
bit of an abuse of the function.
>>>
>>> I was wondering about tha
"no_console_suspend" is no longer handled in platform file,
Since the omap serial driver is now adapted to prevent
console UART idleing during suspend.
Cc: Santosh Shilimkar
Cc: Felipe Balbi
Cc: Rajendra nayak
Signed-off-by: Sourav Poddar
Reviewed-by: Felipe Balbi
---
arch/arm/mach-omap2/ser
Remove "no_idle_on_suspend" check, since respective
driver should be able to prevent idling of an
omap device whenever required.
Driver's can get same behavior by just returning -EBUSY
from their ->runtime_suspend only during suspend.
Cc: Santosh Shilimkar
Cc: Felipe Balbi
Cc: Rajendra nayak
C
The "ti,no_idle_on_suspend" property was required to keep ocmcram clocks
running during idle.
But commit 72bb6f9 (ARM: OMAP: omap_device: don't attempt late suspend
if no driver bound), added in v3.6 should prevent any automatic clock
gating for devices without drivers bound. Since there is no dr
This is a cleanup series done in response to the
serial driver fixes done for "no_console_suspend" case.
This cleanups mainly include getting
rid of using "omap_device_disable_idle_on_suspend" api for both dt and non dt
case
as the serial driver will be self sufficient to handle the "no_idle_on_s
On Saturday 27 April 2013 01:34 AM, Sourav Poddar wrote:
Hi,
This patch series contains fixes around the issue that
the console UART should not idled on suspend while using
"no_console_suspend" in bootargs.
The approach thought of is to modify the serial core/serial driver to bypass
runtime PM
Hi,
This patch series contains fixes around the issue that
the console UART should not idled on suspend while using
"no_console_suspend" in bootargs.
The approach thought of is to modify the serial core/serial driver to bypass
runtime PM if the UART in contention is a console and we are using
"
Move "uart_console" definition to serial core header file, so that it can be
used by serial drivers.
Get rid of the uart_console defintion from mpc52xx_uart driver.
Cc: Santosh Shilimkar
Cc: Felipe Balbi
Cc: Rajendra nayak
Signed-off-by: Sourav Poddar
Reviewed-by: Felipe Balbi
---
drivers/tt
The driver manages "no_console_suspend" by preventing runtime PM
during the suspend path, which forces the console UART to stay awake.
Signed-off-by: Sourav Poddar
Reviewed-by: Felipe Balbi
---
drivers/tty/serial/omap-serial.c | 34 +-
1 files changed, 33 inser
Hi,
This patch series contains fixes around the issue that
the console UART should not idled on suspend while using
"no_console_suspend" in bootargs.
The approach thought of is to modify the serial core/serial driver to bypass
runtime PM if the UART in contention is a console and we are using
"
Hi Kevin,
On Friday 26 April 2013 11:58 PM, Kevin Hilman wrote:
Sourav Poddar writes:
The driver manages "no_console_suspend" by preventing runtime PM
during the suspend path, which forces the console UART to stay awake.
Signed-off-by: Sourav Poddar
Reviewed-by: Felipe Balbi
---
drivers/tty
Sourav Poddar writes:
> The driver manages "no_console_suspend" by preventing runtime PM
> during the suspend path, which forces the console UART to stay awake.
>
> Signed-off-by: Sourav Poddar
> Reviewed-by: Felipe Balbi
> ---
> drivers/tty/serial/omap-serial.c | 28
Rajendra Nayak writes:
[...]
> OMAP UART IP needs manual idle modes based on functional state of the
> IP. Currently this is handled by the driver with function pointers
> implemented in platform code.
>
> This however breaks in case of device tree because of missing
> idle handling.
>
> The se
Rajendra Nayak writes:
> From: Santosh Shilimkar
>
> UART IP slave idle handling now taken care by runtime pm backend(hwmod layer)
> so remove the hackery from the driver.
>
> As discussed on the list, in future if dma mode needs to be brought
> back to this driver, UART sysc handling needs to b
Hi,
It seems that I have not been paying close attention to
actual voltage value seen on scope to map it back to verify the validity
of the voltage value. Even though I did verify[1] that voltage did scale to
values in DT entries, the values in the case of 3630 and 4460 were lower than
what the spe
commit d16fb25 (ARM: dts: OMAP4460: Add CPU OPP table)
introduced wrong OPP voltages per OPP by mistake. Sync the OPP
tables with existing OMAP4460 OPP data in
arch/arm/mach-omap2/opp4xxx_data.c
Signed-off-by: Nishanth Menon
---
arch/arm/boot/dts/omap4460.dtsi |6 +++---
1 file changed, 3 in
commit 3027e26 (ARM: dts: OMAP36xx: Add CPU OPP table)
introduced wrong OPP voltages per OPP by mistake. Sync the OPP
tables with existing OMAP36xx OPP data in
arch/arm/mach-omap2/opp3xxx_data.c
Signed-off-by: Nishanth Menon
---
arch/arm/boot/dts/omap36xx.dtsi |6 +++---
1 file changed, 3 in
* Luciano Coelho [130425 23:38]:
> On Thu, 2013-04-25 at 20:52 -0700, Tony Lindgren wrote:
> > Hi all,
>
> Hi Tony,
>
>
> > Here are some patches against linux next to make WLAN to work with
> > device tree. Note that we still are initializing wl12xx with pdata,
> > but so far it looks like onl
* Luciano Coelho [130426 06:29]:
> On Thu, 2013-04-25 at 20:52 -0700, Tony Lindgren wrote:
> > This is needed to get wl12xx working with device tree based
> > booting.
> >
> > Note that we claim the various GPIO inputs in the regulator
> > as the proper muxing is needed to enable and disable the
* Koen Kooi [130426 02:39]:
>
> Op 26 apr. 2013, om 05:52 heeft Tony Lindgren het volgende
> geschreven:
>
> > Without WLAN we cannot switch omap4 to use device tree
> > only booting. This patch can be reverted when the
> > binding for wl12xx is added.
>
> How much boards am I allowed to add
On 04/22/2013 03:54 AM, Andreas Fenkart wrote:
> When a gpio interrupt is masked, the gpio event will still be latched in
> the interrupt status register so when you unmask it later you may get an
> interrupt straight away. However, if the interrupt is disabled then gpio
> events occurring will no
On 04/26/2013 03:06 AM, Mats Liljegren wrote:
I would like to perform a customer demo running a benchmark
application in full nohz mode on TCI6638k2k target, which as far as I
understand it is a KeyStone II architecture.
Does anyone know what the best Linux source code is to perform the
nohz por
Hello.
On 26-04-2013 15:30, Mugunthan V N wrote:
With the commit id a11fbba
Please also specify that commit's summary line in parens.
from Sebastian Siewior, a kernel warning is
generated as below. This warning is generated as the irq_enabled is not
initialized for the primary interface
On Thu, 2013-04-25 at 20:52 -0700, Tony Lindgren wrote:
> This is needed to get wl12xx working with device tree based
> booting.
>
> Note that we claim the various GPIO inputs in the regulator
> as the proper muxing is needed to enable and disable the
> regulator.
>
> Also, we want to use non-rem
Just got this on my AM335x board.
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 3.9.0-rc8-00020-g6e8f1be-dirty
(mpfj@mpfj-nanobone) (gcc version 4.5.4 (Buildroot 2012.11) ) #210 Thu Apr 25
13:00:09 BST 2013
[0.00] CPU: ARMv7 Processor [413fc082] revision 2
Remove "no_idle_on_suspend" check, since respective
driver should be able to prevent idling of an
omap device whenever required.
Driver's can get same behavior by just returning -EBUSY
from their ->runtime_suspend only during suspend.
Cc: Santosh Shilimkar
Cc: Felipe Balbi
Cc: Rajendra nayak
C
The "ti,no_idle_on_suspend" property was required to keep ocmcram clocks
running during idle.
But commit 72bb6f9 (ARM: OMAP: omap_device: don't attempt late suspend
if no driver bound), added in v3.6 should prevent any automatic clock
gating for devices without drivers bound. Since there is no dr
The driver manages "no_console_suspend" by preventing runtime PM
during the suspend path, which forces the console UART to stay awake.
Signed-off-by: Sourav Poddar
Reviewed-by: Felipe Balbi
---
drivers/tty/serial/omap-serial.c | 28 +++-
1 files changed, 27 insertions(
Move "uart_console" definition to serial core header file, so that it can be
used by serial drivers.
Get rid of the uart_console defintion from mpc52xx_uart driver.
Cc: Santosh Shilimkar
Cc: Felipe Balbi
Cc: Rajendra nayak
Signed-off-by: Sourav Poddar
Reviewed-by: Felipe Balbi
---
drivers/tt
Hi,
This patch series contains fixes and cleanups around the issue that
the console UART should not idled on suspend while using "no_console_suspend"
in bootargs.
The approach thought of is to modify the serial core/serial driver to bypass
runtime PM if the UART in contention is a console and we
"no_console_suspend" is no longer handled in platform file,
Since the omap serial driver is now adapted to prevent
console UART idleing during suspend.
Cc: Santosh Shilimkar
Cc: Felipe Balbi
Cc: Rajendra nayak
Signed-off-by: Sourav Poddar
Reviewed-by: Felipe Balbi
---
arch/arm/mach-omap2/ser
On 04/26/2013 01:30 PM, Mugunthan V N wrote:
> diff --git a/drivers/net/ethernet/ti/cpsw.c b/drivers/net/ethernet/ti/cpsw.c
> index 4e2d224..59c4391 100644
> --- a/drivers/net/ethernet/ti/cpsw.c
> +++ b/drivers/net/ethernet/ti/cpsw.c
> @@ -1633,7 +1633,6 @@ static int cpsw_probe_dual_emac(struct pl
With the commit id a11fbba from Sebastian Siewior, a kernel warning is
generated as below. This warning is generated as the irq_enabled is not
initialized for the primary interface and in probe it is initialized for
the secondary interface. This patch moves irq_enabled initialization from
second in
On Fri, 2013-04-26 at 14:00 +0300, Luciano Coelho wrote:
> Hi Koen,
>
> On Fri, 2013-04-26 at 11:33 +0200, Koen Kooi wrote:
> > Op 26 apr. 2013, om 05:52 heeft Tony Lindgren het
> > volgende geschreven:
> >
> > > Without WLAN we cannot switch omap4 to use device tree
> > > only booting. This pa
Hi Koen,
On Fri, 2013-04-26 at 11:33 +0200, Koen Kooi wrote:
> Op 26 apr. 2013, om 05:52 heeft Tony Lindgren het volgende
> geschreven:
>
> > Without WLAN we cannot switch omap4 to use device tree
> > only booting. This patch can be reverted when the
> > binding for wl12xx is added.
>
> How mu
From: Santosh Shilimkar
UART IP slave idle handling now taken care by runtime pm backend(hwmod layer)
so remove the hackery from the driver.
As discussed on the list, in future if dma mode needs to be brought
back to this driver, UART sysc handling needs to be updated in
framework such a way tha
From: Santosh Shilimkar
UART IP idle handling now taken care by runtime pm backend(hwmod) indirectly
and OMAP serial driver is also cleaned up accordingly.
So remove the un-used slave idle platforms hooks now.
Tested-by: Vaibhav Bedia
Tested-by: Sourav Poddar
Signed-off-by: Rajendra nayak
Si
_enable_sysc() and _idle_sysc() handle the midle mode programming correctly
and program HWMOD_IDLEMODE_SMART or HWMOD_IDLEMODE_SMART_WKUP respectively
for supported IPs (The ones which support hardware controlled midle modes)
However the same programming logic is missing when it comes to sidle mod
From: Santosh Shilimkar
OMAP UART IP needs software control for slave idle modes based on functional
state of the IP. i.e The IP slave idle settings should be set to 'noidle' when
being used and then put back to 'smart_idle' when unused. Currently this is
handled by the driver with function point
From: Santosh Shilimkar
With the OMAP serial driver sysc cleanup patches in this series, we can
now remove the hwmod external apis for sysc fiddling.
While at this, also remove unused sysc auto idle api from hwmod code.
Tested-by: Vaibhav Bedia
Tested-by: Sourav Poddar
Signed-off-by: Rajendra
changes in v2:
---
1. Addressed the concerns from Paul Wamsley around cleanups in
_enable_wakeup()/_disable_wakeup(), and left them intact
2. Updates in changelogs in the serial patch about changes
needed when dma support is added back for serial
3. Dropped 1/8 from v1 since its already pulled in
Some IPs (like UART) need the sidle mode to be controlled in SW only
while they are active. Once they go inactive, they need the IP to be
put back in HW control so they are also wakeup capable.
The flag HWMOD_SWSUP_SIDLE takes care of IPs which need the sidle
mode to be *always* controlled in SWSU
Op 26 apr. 2013, om 05:52 heeft Tony Lindgren het volgende
geschreven:
> Without WLAN we cannot switch omap4 to use device tree
> only booting. This patch can be reverted when the
> binding for wl12xx is added.
How much boards am I allowed to add to this? I need to get the wl12xx wifi
expansi
On Thursday 25 April 2013 07:28 PM, Kevin Hilman wrote:
> Tony Lindgren writes:
>
>> * Santosh Shilimkar [130419 10:56]:
>>> On Friday 19 April 2013 11:14 PM, Tony Lindgren wrote:
* Santosh Shilimkar [130419 10:43]:
> On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote:
>> Hi all
From: Wei Yongjun
Add the missing iounmap() before return from omap1_system_dma_init()
in the error handling case.
Also removed platform_device_del() on add resources error case which
cause dup device delete.
Signed-off-by: Wei Yongjun
---
no compile test.
---
arch/arm/mach-omap1/dma.c | 8 +++
On Fri, Apr 19, 2013 at 9:20 PM, Andreas Fenkart
wrote:
> When a gpio interrupt is masked, the gpio event will still be latched in
> the interrupt status register so when you unmask it later you may get an
> interrupt straight away. However, if the interrupt is disabled then gpio
> events occurri
On Fri, Apr 19, 2013 at 2:49 AM, Jon Hunter wrote:
> From d02ef7b7dfcf8e13bf019aedfdecb38ca3c6749f Mon Sep 17 00:00:00 2001
> From: Jon Hunter
> Date: Mon, 15 Apr 2013 13:06:54 -0500
> Subject: [PATCH] gpio/omap: ensure gpio context is initialised
>
> Commit a2797be (gpio/omap: force restore if
On Wed, Apr 17, 2013 at 2:41 AM, Javier Martinez Canillas
wrote:
So:
> +static int omap_gpio_irq_domain_xlate(struct irq_domain *d,
> + struct device_node *ctrlr,
> + const u32 *intspec, unsigned int
> intsize,
> +
On Wed, Apr 17, 2013 at 5:41 PM, Stephen Warren wrote:
> On 04/16/2013 05:14 PM, Jon Hunter wrote:
>>> c) I have the feeling that hooking the of_xlate function for this is a
>>> bit of an abuse of the function.
>>
>> I was wondering about that. So I was grep'ing through the various xlate
>> imple
On Mon, Apr 15, 2013 at 11:40 PM, Jon Hunter wrote:
> I am still concerned about the case where a driver may have already
> called gpio_request() and then calls request_irq(). I think that the
> solution needs to handle cases where the driver may or may not call
> gpio_request() to allocate the g
On Tuesday 23 April 2013 01:49 PM, Paul Walmsley wrote:
> Hi Rajendra,
>
> On Thu, 18 Apr 2013, Rajendra Nayak wrote:
>
> _enable_wakeup() and _disable_wakeup() are expected to program the
> OCP_SYSCONFIG.ENAWAKEUP bit.
These functions were originally intended to take care of ev
I would like to perform a customer demo running a benchmark
application in full nohz mode on TCI6638k2k target, which as far as I
understand it is a KeyStone II architecture.
Does anyone know what the best Linux source code is to perform the
nohz port for this board? It should preferably be Linux
55 matches
Mail list logo
