On Fri, May 11, 2012 at 00:38:49, Hiremath, Vaibhav wrote:
From: Afzal Mohammed af...@ti.com
This patch adds minimal support for AM335X machine init.
During last merge window, two separate patches supporting am33xx
machine init had been submitted,
1. Link to earlier Baseport patch
On Thu, May 10, 2012 at 14:23:01, Hiremath, Vaibhav wrote:
From: Afzal Mohammed af...@ti.com
Add support for low level debugging on AM335X EVM (AM33XX family).
Currently only support for UART1 console, which is used on AM335X EVM
is added.
Signed-off-by: Afzal Mohammed af...@ti.com
On Fri, May 11, 2012 at 18:17:45, Cousson, Benoit wrote:
Hi Tony,
Here are some remaining DT patches I was not able to push at 3.4 due to some
missing dependency.
It applies now fine on top of lo/dt branch.
Regards,
Benoit
The following changes since commit
On Fri, Mar 30, 2012 at 21:33:53, Hiremath, Vaibhav wrote:
In case of AM33XX device, XXX_RSTST register offset is not
consistent across PRM modules/instances,
PRM_XXXRSTST
=
PRM_PER_MOD: 0x04
PRM_WKUP_MOD: 0x0C
PRM_MPU_MOD: NA
Hi Tony,
This patch changes the sequence of how the host drivers set_ios
function gets called during probe.
Before:
1. mmc_power_off
2. mmc_power_up
Now:
1. mmc_power_up
My guess is then; the omap driver set_ios function requires that
mmc_power_off is called before a mmc_power_up.
Hopefully
Hi,
On Tue, May 29, 2012 at 02:52:34PM +0800, Ulf Hansson wrote:
Hi Tony,
This patch changes the sequence of how the host drivers set_ios
function gets called during probe.
Before:
1. mmc_power_off
2. mmc_power_up
Now:
1. mmc_power_up
My guess is then; the omap driver set_ios
On Fri, May 25, 2012 at 02:30:44PM +0200, Cousson Benoit wrote:
On 5/25/2012 10:25 AM, Eduardo Valentin wrote:
From: Kishon Vijay Abraham Ikis...@ti.com
Extracts the device data from hwmod database and create a platform device
using omap device build.
The device build is done during
Hi, Eduardo.
On 05/25/2012 12:26 PM, Eduardo Valentin wrote:
This patch add device tree entries on OMAP4 based boards
for System Control Module (SCM).
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
arch/arm/boot/dts/omap4.dtsi | 13 +
1 files changed, 13
This patch adds complete clockctree and hwmod data for the
AM33XX family of devices.
This patch-series is cleaned up further from Paul's cleanup
activity on AM33xx clocktree, where all leaf nodes have been
removed and now modules enable/disable is controlled only
using hwmod framework interface.
AM33XX PRCM architecture is different that any OMAP family
of devices, so it is required to have separate implementation
to handle AM33XX module enable/disable, reset assert/deassert
functionality.
This patch adds wrapper api's in omap_hwmod framework to
access prm/cm for AM33XX family of devices.
From: Paul Walmsley p...@pwsan.com
OMAP3, OMAP4 and AM33xx share some common data like, clksel_rate
oscillator clock input (Virtual clock nodes), required for
clock tree; so move common data to common data file so that it
can be reused.
Signed-off-by: Paul Walmsley p...@pwsan.com
AM33XX clock implementation is different than any existing OMAP
family of devices. Although DPLL module is similar to OMAP4
device, but the usage is very much different than OMAP4.
AM33XX has different peripheral set and each module gets
integrated to the clock framework differently than OMAP
Currently in the 1.153 errata handling, while waiting for transmitter
underflow, if NACK is got the XUDF(Transmit underflow) flag is also set.
Fix this by setting the XUDF(Transmit underflow) flag after wait for the
condition is over.
Cc: Alexander Shishkin virtu...@slind.org
Acked-by: Moiz
Currently in probe
pm_runtime_put(dev-dev);
...
/* i2c device drivers may be active on return from add_adapter() */
adap-nr = pdev-id;
r = i2c_add_numbered_adapter(adap);
if (r) {
dev_err(dev-dev, failure adding adapter\n);
goto
The section number in the recent errata document has changed.
Rename the erratum 1p153 to the unique id i462 instead, so that
it is easier to reference. Also change the function name and comments
to reflect the same.
Cc: Jon Hunter jon-hun...@ti.com
Reviewed-by: Kevin Hilman khil...@ti.com
Currently the i2c driver calls the pm_runtime_enable and never
the disable. This may cause a warning when pm_runtime_enable
checks for the count match.Fix the same by calling
pm_runtime_disable in the error and the remove path.
Cc: Rajendra Nayak rna...@ti.com
Acked-by: Kevin Hilman
If PM runtime get_sync fails return with the error
so that no further reads/writes goes through the interface.
This will avoid possible abort. Add a error message in case
of failure with the cause of the failure.
Reviewed-by: Kevin Hilman khil...@ti.com
Signed-off-by: Shubhrajyoti D
From: Tasslehoff Kjappfot tasskj...@gmail.com
i2c_probe set the dev-errata flag, but omap_i2c_init cleared the flag again.
Prevent the overwrite of the errata flags.Move the errata handling to a unified
place in probe to prevent such errors.
Reviewed-by: Kevin Hilman khil...@ti.com
On OMAP4 we were writing 1 to IRQENABLE_CLR which cleared only
the arbitration lost interrupt. The patch intends to fix the same by writing 0
to the IE register clearing all interrupts.
This is based on the work done by Vikram Pandita vikram.pand...@ti.com.
The changes from the original patch
By definition, wait_for_completion_timeout() returns an unsigned value and
therefore, it is not necessary to check if the return value is less than zero
as this is not possible.
This is based on a patch from Jon Hunter jon-hun...@ti.com
Changes from his patch
- Declare a long as the
In omap_i2c_remove we are accessing the I2C_CON register without
enabling the clocks. Fix the same by ensure device is accessible by calling
pm_runtime_get_sync before accessing the registers and calling
pm_runtime_put
after accessing.
This fixes the following crash.
[
From: Neil Brown ne...@suse.de
On a board with OMAP3 processor and TWL4030 Power management,
we need to talk to the TWL4030 during late suspend but cannot
because the I2C interrupt is disabled (as late suspend disables
interrupt).
e.g. I get messages like:
[ 62.161102] musb-omap2430
The functions omap_i2c_unidle/idle are called from omap_i2c_runtime_resume
and omap_i2c_runtime_suspend which is compiled for CONFIG_PM_RUNTIME.
This patch removes the omap_i2c_unidle/idle functions and folds them
into the runtime callbacks.
This fixes the below warn when CONFIG_PM_RUNTIME is not
The patch series does the following
- Warn fixes if CONFIG_PM_RUNTIME is not selected.
- In case of i2c remove register access was done without any
get_sync fix the same.
- Folds a patch from Tasslehoff to prevent any merge conflicts.
- Prevents the XDUF flag to be set if the underflow
Here are a few cleanups for the omap_udc.c driver.
Compile tested only with omap1_defconfig + enabling omap_udc.
There's still a bunch that needs to change on that driver,
but this is a start, at least.
Once -rc1 is tagged, I'll queue these patches for v3.6 merge
window together with Tony's
This patch is just a cleanup patch to make
checkpatch.pl a little happier with the
omap_udc.c driver.
No functional changes.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/omap_udc.c | 201 +
1 file changed, 121 insertions(+), 80
that print isn't needed at all. Remove it
and move the use_dma reinitialization to
probe() function.
Note that ideally we would drop all
cpu_is_* and machine_is_* checks from
this driver instead. Later patches will
come to get rid of those.
Signed-off-by: Felipe Balbi ba...@ti.com
---
this also helps removing a few lines of boilerplate
code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/omap_udc.c | 23 +++
1 file changed, 7 insertions(+), 16 deletions(-)
diff --git a/drivers/usb/gadget/omap_udc.c b/drivers/usb/gadget/omap_udc.c
index
when allocating a request, it's better programming
practice to make sure we return NULL if allocation
failed.
This will ensure that, if struct usb_request isn't
the first member on our structure, we don't cheat
the gadget driver into thinking allocating worked
because pointer isn't 0.
we don't need to check for _req because
kfree(NULL) is safe. Also, if someone
actually passes a NULL pointer to be freed
by usb_ep_free_request(), he deserves any
issue he faces.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/omap_udc.c |3 +--
1 file changed, 1
This patch makes use of the generic map/unmap
routines on the omap_udc driver. Removes
some useless and duplicated code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/omap_udc.c | 46 +++--
1 file changed, 7 insertions(+), 39 deletions(-)
Hi Paul,
On 5/25/2012 11:56 PM, Paul Walmsley wrote:
Kevin discovered that commit c8d82ff68fb6873691536cf33021977efbf5593c
(ARM: OMAP2/3: hwmod data: Add 32k-sync timer data to hwmod
database) broke CORE idle on OMAP3. This blocks device low power
states.
The root cause is that the 32K
* Felipe Balbi ba...@ti.com [120529 00:46]:
Can you enable debugging on menelaus so we see what the driver is doing ?
I believe that to change the VMMC's supply voltage you need to turn off
the regulator, meaning LDO_CTRL7[1:0] = 0b00.
Looks like it's some kind of race between the slots
Hi,
On Tue, May 29, 2012 at 05:47:32AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [120529 00:46]:
Can you enable debugging on menelaus so we see what the driver is doing ?
I believe that to change the VMMC's supply voltage you need to turn off
the regulator, meaning
On 5/28/2012 12:26 PM, Valentin, Eduardo wrote:
Hello Santosh,
On Mon, May 28, 2012 at 12:48 PM, Felipe Balbiba...@ti.com wrote:
Hi,
On Mon, May 28, 2012 at 03:03:26PM +0530, Shilimkar, Santosh wrote:
On Fri, May 25, 2012 at 1:56 PM, Eduardo Valentin
eduardo.valen...@ti.com wrote:
This
* Felipe Balbi ba...@ti.com [120529 05:56]:
Hi,
On Tue, May 29, 2012 at 05:47:32AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [120529 00:46]:
Can you enable debugging on menelaus so we see what the driver is doing ?
I believe that to change the VMMC's supply
On 5/28/2012 1:16 PM, Eduardo Valentin wrote:
Hello again,
On Fri, May 25, 2012 at 05:49:44PM +0200, Cousson Benoit wrote:
On 5/25/2012 10:25 AM, Eduardo Valentin wrote:
big cut
+
+static const struct omap_bandgap_data omap4460_data = {
+ .has_talert = true,
+ .has_tshut =
On 5/28/2012 1:35 PM, Eduardo Valentin wrote:
Hello,
On Fri, May 25, 2012 at 02:52:08PM +0200, Cousson Benoit wrote:
On 5/25/2012 10:25 AM, Eduardo Valentin wrote:
This patch introduces a MFD core device driver for
OMAP system control module.
The control module allows software control of
On 5/28/2012 3:15 PM, Shilimkar, Santosh wrote:
On Mon, May 28, 2012 at 5:12 PM, Eduardo Valentin
[...]
+/**
+ * omap_control_readl: Read a single omap control module register.
+ *
+ * @dev: device to read from.
+ * @reg: register to read.
+ * @val: output with register value.
+ *
+ *
Hi.
On 05/25/2012 12:25 PM, Eduardo Valentin wrote:
From: Kishon Vijay Abraham I kis...@ti.com
Extracts the device data from hwmod database and create a platform device
using omap device build.
The device build is done during postcore_initcall.
Signed-off-by: Kishon Vijay Abraham I
On 05/22/2012 10:09 AM, Tomi Valkeinen wrote:
Hi Florian,
Here are the OMAP DSS changes for 3.5.
Merged.
Thanks,
Florian Tobias Schandinat
I really tried this time to send the pull request early, but here I am
again, sending it when the merge window has already opened... A few
Hi Russell,
On Fri, Aug 12, 2011 at 9:35 PM, Gupta, Ramesh grgu...@ti.com wrote:
On Thu, Aug 11, 2011 at 5:29 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Thu, Aug 11, 2011 at 02:28:39PM -0500, Gupta, Ramesh wrote:
Hi Russel,
grr.
Sorry, typo.
On Thu, Apr 28, 2011 at
From ba09674260c0c6e7d7efe900bbd379195b7001e2 Mon Sep 17 00:00:00 2001
From: Ramesh Gupta G grgu...@ti.com
Date: Mon, 28 May 2012 20:00:15 +0530
Subject: [PATCH] ARM: new cache maintenance api for iommu mem flush
non-coherent IOMMUs need to make sure that the
data held in the caches need to be
Hi Xiao Jiang,
On 05/25/2012 05:42 AM, jgq...@gmail.com wrote:
From: Xiao Jiang jgq...@gmail.com
This series can be applied to dt branch of linux-omap tree.
Thanks for sending this!
Since omap24xx series has different wdt base addr (omap2420: 0x48022000 and
omap2430: 0x49016000) per
On 20120529-15:14, Cousson, Benoit wrote:
On 5/28/2012 1:16 PM, Eduardo Valentin wrote:
In fact I didn't touch the clk data on purpose and left the clock handling
as is. On my side I didn't know how the clock struct would look like with DT,
so, I didn't mess with it.
Do you have a reference
On 05/25/2012 05:42 AM, jgq...@gmail.com wrote:
From: Xiao Jiang jgq...@gmail.com
Add wdt node to support dt.
Signed-off-by: Xiao Jiang jgq...@gmail.com
---
arch/arm/boot/dts/omap3.dtsi |5 +
arch/arm/boot/dts/omap4.dtsi |5 +
2 files changed, 10 insertions(+), 0
On 05/25/2012 05:42 AM, jgq...@gmail.com wrote:
From: Xiao Jiang jgq...@gmail.com
If provided dt support, then skip add wdt platform device as usual.
Signed-off-by: Xiao Jiang jgq...@gmail.com
---
arch/arm/mach-omap2/devices.c |2 +-
1 files changed, 1 insertions(+), 1
On 05/25/2012 05:42 AM, jgq...@gmail.com wrote:
From: Xiao Jiang jgq...@gmail.com
Add device table for omap_wdt to support dt.
Signed-off-by: Xiao Jiang jgq...@gmail.com
---
drivers/watchdog/omap_wdt.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git
Tero Kristo t-kri...@ti.com writes:
On Wed, 2012-05-16 at 15:36 -0700, Kevin Hilman wrote:
+Jean for functional power states
Tero Kristo t-kri...@ti.com writes:
This patch adds device off support to OMAP4 device type.
Description is rather thin for a patch that is doing so much.
Jean Pihet jean.pi...@newoldbits.com writes:
Hi Tero, Kevin, Santosh,
On Mon, May 21, 2012 at 10:48 AM, Tero Kristo t-kri...@ti.com wrote:
On Wed, 2012-05-16 at 15:36 -0700, Kevin Hilman wrote:
+Jean for functional power states
Tero Kristo t-kri...@ti.com writes:
This patch adds device
On Mon, May 14, 2012 at 5:03 AM, Tero Kristo t-kri...@ti.com wrote:
[...]
+/**
* _enable - enable an omap_hwmod
* @oh: struct omap_hwmod *
*
@@ -1599,6 +1629,8 @@ static int _enable(struct omap_hwmod *oh)
_enable_clocks(oh);
_enable_module(oh);
+
On Thu, May 17, 2012 at 3:52 AM, Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
On Thu, May 17, 2012 at 12:34 PM, Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
On Thu, May 17, 2012 at 4:12 AM, Kevin Hilman khil...@ti.com wrote:
Tero Kristo t-kri...@ti.com writes:
[...]
- Rather than
On Mon, May 14, 2012 at 5:18 AM, Tero Kristo t-kri...@ti.com wrote:
Added similar PM errata flag support as omap3 has. A few errata flags
will be added in subsequent patches.
Considering that we might have erratas for future SoCs as well,
should'nt we just
set up a common errata flag for all
Tero Kristo t-kri...@ti.com writes:
On Wed, 2012-05-16 at 16:07 -0700, Kevin Hilman wrote:
On 05/16/2012 04:05 PM, Kevin Hilman wrote:
Tero Kristot-kri...@ti.com writes:
From: Santosh Shilimkarsantosh.shilim...@ti.com
The ROM BUG is when MPU Domain OFF wake up sequence that can
Tero Kristo t-kri...@ti.com writes:
On Wed, 2012-05-16 at 17:06 -0700, Kevin Hilman wrote:
+Benoit
Tero Kristo t-kri...@ti.com writes:
save_secure_all needs l3_main_3_ick and l4_secure_clkdm enabled,
otherwise the secure ROM code will crash.
Signed-off-by: Tero Kristo
Shilimkar, Santosh santosh.shilim...@ti.com writes:
Tero,
On Mon, May 21, 2012 at 3:51 PM, Tero Kristo t-kri...@ti.com wrote:
On Wed, 2012-05-16 at 17:31 -0700, Kevin Hilman wrote:
Tero Kristo t-kri...@ti.com writes:
If AUX_CORE_BOOT0 does not indicate wakeup request for cpu1, put it back
On Tue, May 29, 2012 at 3:15 PM, Kevin Hilman khil...@ti.com wrote:
Tero Kristo t-kri...@ti.com writes:
On Wed, 2012-05-16 at 17:06 -0700, Kevin Hilman wrote:
+Benoit
Tero Kristo t-kri...@ti.com writes:
save_secure_all needs l3_main_3_ick and l4_secure_clkdm enabled,
otherwise the
Jon Hunter jon-hun...@ti.com writes:
From: Jon Hunter jon-hun...@ti.com
This patch is based upon Ming Lei's patch to add runtime PM support for OMAP4
[1]. In Ming's original patch the CTI interrupts were being enabled during
runtime when the PMU was used but they were only configured once
Tarun Kanti DebBarma tarun.ka...@ti.com writes:
Timers in PER domain periodically report old time from TCRR in
posted mode if ick 4*fck. Therefore, set timer to non-posted
whenever ick 4*fck for all timers.
Is there an erratum assocaited with this?
Does this problem affect every SoC?
Tero Kristo t-kri...@ti.com writes:
Hi,
This set adds support for TPS62361 PMIC, which is used to power
MPU voltagedomain on OMAP4460 boards. These patches apply on top
of 3.4 + my voltagedomain fixes set to avoid adding redundant code.
Hmm... do you have an updated version of your
Hi Kevin,
On 05/29/2012 04:17 PM, Kevin Hilman wrote:
Jon Hunter jon-hun...@ti.com writes:
From: Jon Hunter jon-hun...@ti.com
This patch is based upon Ming Lei's patch to add runtime PM support for OMAP4
[1]. In Ming's original patch the CTI interrupts were being enabled during
runtime
Hi Kevin,
On 05/29/2012 05:07 PM, Jon Hunter wrote:
Hi Kevin,
On 05/29/2012 04:17 PM, Kevin Hilman wrote:
Jon Hunter jon-hun...@ti.com writes:
From: Jon Hunter jon-hun...@ti.com
This patch is based upon Ming Lei's patch to add runtime PM support for
OMAP4
[1]. In Ming's original patch
Jon Hunter wrote:
On 05/25/2012 05:42 AM, jgq...@gmail.com wrote:
From: Xiao Jiang jgq...@gmail.com
Add device table for omap_wdt to support dt.
Signed-off-by: Xiao Jiang jgq...@gmail.com
---
drivers/watchdog/omap_wdt.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
Jon Hunter wrote:
On 05/25/2012 05:42 AM, jgq...@gmail.com wrote:
From: Xiao Jiang jgq...@gmail.com
Add wdt node to support dt.
Signed-off-by: Xiao Jiang jgq...@gmail.com
---
arch/arm/boot/dts/omap3.dtsi |5 +
arch/arm/boot/dts/omap4.dtsi |5 +
2 files changed, 10
On 05/14/2012 06:42 AM, Rajendra Nayak wrote:
On Thursday 10 May 2012 03:32 PM, Daniel Lezcano wrote:
The current Makefile compiles the cpuidle34xx.c and cpuidle44xx.c files
even if the cpuidle option is not set in the kernel.
This patch fixes this by creating a section in the Makefile where
65 matches
Mail list logo
