* Lokesh Vutla lokeshvu...@ti.com [140709 23:00]:
Hi Tony,
On Wednesday 09 July 2014 09:14 PM, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [140626 03:28]:
* Sricharan R r.sricha...@ti.com [140626 01:36]:
Hi Tony,
On Thursday 26 June 2014 01:14 PM, Tony Lindgren wrote:
*
* Sebastian Andrzej Siewior bige...@linutronix.de [140709 10:52]:
While comparing the OMAP-serial and the 8250 part of this I noticed that
the the latter does not use runtime-pm. Here are the pieces. It is
basically a get before first register access and a last_busy + put after
last access.
On 07/10/2014 12:21 AM, Himangi Saraogi wrote:
This patch moves data allocated using clk_put and
snd_soc_register_component to the corresponding managed interfaces and
does away with the functions to free memory in the probe and remove
functions. The probe function is no longer required and is
* Sebastian Andrzej Siewior bige...@linutronix.de [140709 09:35]:
On 07/09/2014 05:12 PM, Tony Lindgren wrote:
And also please note that for runtime PM the wake-up events need
to be always enabled, so the device_may_wakeup() checks should
be only implemented for suspend and resume. I think
* Sebastian Andrzej Siewior bige...@linutronix.de [140709 10:52]:
v1…v2:
- added runtime PM. Could somebody could plese double check
this? I seems to be enabled and nothing explodes. However
serial_omap_get_context_loss_count() enable_wakeup() are
NULL pointer
On Tue, 2014-07-08 at 06:25 +, Gupta, Pekon wrote:
Do you plan to re-spin this patch with above comments, and mark it for stable?
It would be helpful for all OMAP3 users.
Thanks for the reminder. I'll respin the patchset this weekend.
-- Christoph
--
To unsubscribe from this list: send
On Thu, Jul 10, 2014 at 02:51:12AM +0530, Himangi Saraogi wrote:
This patch moves data allocated using clk_put and
snd_soc_register_component to the corresponding managed interfaces and
does away with the functions to free memory in the probe and remove
functions. The probe function is no
Hi,
This set is to enable audio (finally) on the omap5-uevm. We have been waiting
for the palmas 32K clock driver to make it to upstream, which it did and it is
already in linux-next.
With the three patch we can have audio working on omap5-uevm with linux-next.
Regards,
Peter
---
Peter Ujfalusi
clk32kg-audio clock is needed for twl6040 codec.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/omap5-uevm.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
index 1e1b05768cec..9166d479ac1b
The board uses twl6040 as audio codec. Move the corresponding pinctrl as
well under the node.
twl6040 needs 32k clock from palams.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/omap5-uevm.dts | 20 +++-
1 file changed, 19 insertions(+), 1 deletion(-)
The board uses twl6040 codec connected via McPDM link. McBSP1 and McBSP2 can
be used for FM/BT.
At the same time move the pinctrl handling to the correct place - under the
corresponding nodes.
Audio connectors on the board:
Headset in/out
Stereo Line out
Stereo Line in.
Signed-off-by: Peter
This driver has been flagged to drop class based instantiation. The removal
improves boot-up time and is unneeded for embedded controllers. Users have been
warned to switch for some time now, so we can actually do the removal. Keep the
DEPRECATED flag, so the core can inform users that the
Some drivers were flagged to remove class based instantiation soon to improve
boot-up time. Originally, I was planning for a longer deprecation time so users
could switch over to some other kind of instantiation. However, the demand for
the speed up is high enough and class based instantiation is
On Wed, Jul 09, 2014 at 03:52:59PM +0530, Keerthy wrote:
Add fixed_uV fields for dcdc5 and dcdc6.
Applied, but don't bury new patches into the middle of old threads -
it's a good way to get your patch ignored.
signature.asc
Description: Digital signature
Hi,
Wolfram Sang wrote:
Some drivers were flagged to remove class based instantiation soon to improve
boot-up time. Originally, I was planning for a longer deprecation time so
users
could switch over to some other kind of instantiation. However, the demand for
the speed up is high enough
On Thu, Jul 10, 2014 at 6:19 AM, Viresh Kumar viresh.ku...@linaro.org wrote:
On 9 July 2014 20:14, Santosh Shilimkar santosh.shilim...@ti.com wrote:
Assuming you are updating bidnings as suggested by Stephen,
patch looks good to me.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Why do
On Thursday 10 July 2014 05:42 PM, Mark Brown wrote:
On Wed, Jul 09, 2014 at 03:52:59PM +0530, Keerthy wrote:
Add fixed_uV fields for dcdc5 and dcdc6.
Applied, but don't bury new patches into the middle of old threads -
it's a good way to get your patch ignored.
Okay. I thought only one
+ /* Warn that the adapter lost class based instantiation */
+ if (adapter-class == I2C_CLASS_DEPRECATED) {
+ dev_dbg(adapter-dev,
+ This adapter dropped support for I2C classes and
+ won't auto-detect %s devices anymore. If you need
On Tue, Jul 08, 2014 at 08:53:32AM +0100, Lee Jones wrote:
On Tue, 08 Jul 2014, Maxime Coquelin wrote:
On 07/05/2014 08:25 AM, Peter Griffin wrote:
Signed-off-by: Peter Griffin peter.grif...@linaro.org
Acked-by: Maxime Coquelin maxime.coque...@st.com
Maxime,
Once Acked by Felipe, I
On Wednesday 09 July 2014 05:21 PM, Tony Lindgren wrote:
* Keerthy a0393...@ti.com [140709 04:03]:
On Wednesday 09 July 2014 02:01 PM, Tony Lindgren wrote:
* Keerthy j-keer...@ti.com [140708 22:40]:
The patch series adds the device tree nodes and the corresponding
documentation. The series
On Thursday 10 July 2014 08:39 AM, Nishanth Menon wrote:
On Thu, Jul 10, 2014 at 6:19 AM, Viresh Kumar viresh.ku...@linaro.org wrote:
On 9 July 2014 20:14, Santosh Shilimkar santosh.shilim...@ti.com wrote:
Assuming you are updating bidnings as suggested by Stephen,
patch looks good to me.
On 10 July 2014 19:01, Santosh Shilimkar santosh.shilim...@ti.com wrote:
Yep. Last time I blocked the series because all the DT conversions
were not done. Considering now the cpufreq-generic can work on non
DT platforms, I am ok to remove the omap-cpufreq.
Great.
--
To unsubscribe from this
On Thu, 10 Jul 2014, Felipe Balbi wrote:
On Tue, Jul 08, 2014 at 08:53:32AM +0100, Lee Jones wrote:
On Tue, 08 Jul 2014, Maxime Coquelin wrote:
On 07/05/2014 08:25 AM, Peter Griffin wrote:
Signed-off-by: Peter Griffin peter.grif...@linaro.org
Acked-by: Maxime Coquelin
On Thursday 10 July 2014 06:55 PM, Keerthy wrote:
On Wednesday 09 July 2014 05:21 PM, Tony Lindgren wrote:
* Keerthy a0393...@ti.com [140709 04:03]:
On Wednesday 09 July 2014 02:01 PM, Tony Lindgren wrote:
* Keerthy j-keer...@ti.com [140708 22:40]:
The patch series adds the device tree nodes
On Wed, Jul 9, 2014 at 7:49 PM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
+ * The lock assumption made here is none because runtime-pm suspend/resume
+ * callbacks should not be invoked there is any operation performed on the
port.
I think there's a missing if?
Best,
OG.
--
On Thu, Jul 10, 2014 at 06:40:39PM +0530, Keerthy wrote:
On Thursday 10 July 2014 05:42 PM, Mark Brown wrote:
Applied, but don't bury new patches into the middle of old threads -
it's a good way to get your patch ignored.
Okay. I thought only one patch had to be redone on top of the other
static inline void __stop_tx(struct uart_8250_port *p)
{
+ if (p-rs485.flags SER_RS485_ENABLED) {
+ int ret;
+
+ ret = (p-rs485.flags SER_RS485_RTS_AFTER_SEND) ? 1 : 0;
+ if (gpio_get_value(p-rts_gpio) != ret) {
+ if
On Wed, 9 Jul 2014 19:49:33 +0200
Sebastian Andrzej Siewior bige...@linutronix.de wrote:
The OMAP version of the 8250 can actually use 1:1 serial8250_startup().
However it needs to be extended by a wakeup irq which should to be
requested enabled at -startup() time and disabled at -shutdown()
On 07/09/2014 07:49 PM, Sebastian Andrzej Siewior wrote:
The OMAP version of the 8250 can actually use 1:1 serial8250_startup().
However it needs to be extended by a wakeup irq which should to be
requested enabled at -startup() time and disabled at -shutdown() time.
v1…v2: add shutdown
Hi Felipe,
Maxime,
Once Acked by Felipe, I think this should go in via your tree to
avoid conflicts with other ARM/STI ARCHITECTURE additions.
there are still many unresolved comments on patches 1 and 2.
Yes, sorry I've been a bit busy this week on other activities to send a V3.
I
On 07/10/2014 09:09 AM, Tony Lindgren wrote:
You can test this pretty easily on beagleboard xm for example
using v3.16-r4:
I tried this with am335x-evm, dra7-evm and beaglebone (omap5-uevm and
am335x-evmsk didn't want to boot a kernel and omap4-blaze didn't even
want to show MLO/U-boot) with
On 07/09/2014 09:01 PM, Lennart Sorensen wrote:
diff --git a/drivers/tty/serial/8250/8250_core.c
b/drivers/tty/serial/8250/8250_core.c
index c7c3bf7..bf06a4c 100644
--- a/drivers/tty/serial/8250/8250_core.c
+++ b/drivers/tty/serial/8250/8250_core.c
@@ -1281,10 +1283,34 @@ static void
On 07/10/2014 11:47 AM, Sebastian Andrzej Siewior wrote:
That core_pwrdm shows only up on dra7. However with both drivers (mine
and the current omap serial) the UART went down after three secs (as
expected) and didn't accept any characters while writing on the
console. If I wrote something on it
On Thu, Jul 10, 2014 at 08:54:18AM +0300, Ivaylo Dimitrov wrote:
On 9.07.2014 10:07, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [140708 11:40]:
Hi Peter,
On 07/08/2014 09:36 AM, Greg KH wrote:
On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
Hello,
Given the
On Thu, Jul 10, 2014 at 11:03 AM, Carlos Hernandez c...@ti.com wrote:
1) Append no_console_suspend to bootargs
Not needed. ideally with pinctrl wakeup capability, this should work.
if you do no_console_suspend, the module is not powered down.
--
To unsubscribe from this list: send the line
On Thu, Jul 10, 2014 at 12:11 PM, Greg KH gre...@linuxfoundation.org wrote:
On Thu, Jul 10, 2014 at 08:54:18AM +0300, Ivaylo Dimitrov wrote:
On 9.07.2014 10:07, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [140708 11:40]:
Hi Peter,
On 07/08/2014 09:36 AM, Greg KH wrote:
On
On Wed, Jul 09, 2014 at 08:35:52AM -0700, Tony Lindgren wrote:
The following changes since commit cd3de83f147601356395b57a8673e9c5ff1e59d1:
Linux 3.16-rc4 (2014-07-06 12:37:51 -0700)
are available in the git repository at:
Hello,
This series adds suspend/resume support for am335x. Version 3 of this
series can be found at [1]. I apologize for the large delay between this
and the previous revision. This code has been heavily refined
since the last version based on the various comments received for v3. The
major
From: Vaibhav Bedia vaibhav.be...@ti.com
OMAP timer code registers two timers - one as clocksource
and one as clockevent. Since AM33XX has only one usable timer
in the WKUP domain one of the timers needs suspend-resume
support to restore the configuration to pre-suspend state.
commit adc78e6
From: Daniel Mack zon...@gmail.com
This patch makes the edma driver resume correctly after suspend. Tested
on an AM33xx platform with cyclic audio streams and omap_hsmmc.
All information can be reconstructed by already known runtime
information.
As we now use some functions that were previously
Use pdata-quirks to reset the wkup_m3 during boot.
Signed-off-by: Dave Gerlach d-gerl...@ti.com
---
arch/arm/mach-omap2/pdata-quirks.c| 12
include/linux/platform_data/wkup_m3.h | 17 +
2 files changed, 29 insertions(+)
create mode 100644
OMAP4 and AM33XX share the same EMIF controller IP. Although there
are significant differences in the IP integration due to which
AM33XX can't reuse the EMIF driver DVFS similar to OMAP4,
it can definitely benefit by reusing the EMIF related macros
defined in drivers/memory/emif.h.
In the current
Add a remoteproc driver to load the firmware for and boot the wkup_m3
present on am33xx. The wkup_m3 is an integrated Cortex M3 that allows
the SoC to enter the lowest possible power state by taking control from
the MPU after it has gone into its own low power state and shutting off
any additional
Add the device tree bindings document for am3353 wkup_m3.
Signed-off-by: Dave Gerlach d-gerl...@ti.com
CC: Ohad Ben-Cohen o...@wizery.com
CC: Benoit Cousson bcous...@baylibre.com
---
.../bindings/remoteproc/wkup_m3_rproc.txt | 46 ++
1 file changed, 46 insertions(+)
Allow interrupt for wkup_m3 to be set from DT, add regs for
IPC regs to allow pm code to communicate with wkup_m3, and add data
needed for mailbox channel.
Signed-off-by: Dave Gerlach d-gerl...@ti.com
CC: Ohad Ben-Cohen o...@wizery.com
CC: Benoit Cousson bcous...@baylibre.com
---
From: Vaibhav Bedia vaibhav.be...@ti.com
SDRAM controller on AM33XX requires that a modification of certain
bit-fields in PWR_MGMT_CTRL register (ref. section 7.3.5.13 in
AM335x-Rev H) is followed by a dummy read access to SDRAM. This
scenario arises when entering a low power state like
AM335x supports various low power modes as documented
in section 8.1.4.3 of the AM335x Technical Reference Manual.
DeepSleep0 mode offers the lowest power mode with limited
wakeup sources without a system reboot and is mapped as
the suspend state in the kernel. In this state, MPU and
PER domains
With all the requisite changes in place we can now enable the basic
PM support for AM33xx. This patch updates the various OMAP files
to enable suspend-resume on AM33xx.
Because the suspend resume functionality is different on AM33xx
than other OMAP platforms due to the need for M3 firmware and an
In preparation for suspend-resume support for AM33XX, add
the assembly file with the code which is copied to internal
memory (OCMC RAM) during bootup and runs from there.
As part of the low power entry (DeepSleep0 mode in AM33XX TRM),
the code running from OCMC RAM does the following
1. Stores
This patch introduces the use of managed interfaces like devm_clk_get
and does away with the clk_puts in the probe and remove functions. A
label is also done away with.
Signed-off-by: Himangi Saraogi himangi...@gmail.com
---
This is a follow up to ASoC: omap-dmic: use managed interfaces which
50 matches
Mail list logo
