On Wednesday 20 June 2012 05:09 PM, Tony Lindgren wrote:
* Rajendra Nayakrna...@ti.com [120606 22:33]:
Hi Tony,
On Tuesday 05 June 2012 12:12 PM, Tony Lindgren wrote:
* Rajendra Nayakrna...@ti.com [120601 05:13]:
The data is autogenerated using the OMAP autogeneration scripts (python
On Thu, Jun 21, 2012 at 8:46 AM, NeilBrown ne...@suse.de wrote:
On Thu, 14 Jun 2012 23:24:10 +0530 DebBarma, Tarun Kanti
tarun.ka...@ti.com wrote:
On Thu, Jun 14, 2012 at 5:45 AM, NeilBrown ne...@suse.de wrote:
On Fri, 11 May 2012 17:30:48 -0700 Kevin Hilman khil...@ti.com wrote:
Hi
Hi Jon,
On Thu, Jun 21, 2012 at 03:41:39, Hunter, Jon wrote:
Ok, I see your point. So today the _set_async_mode() is really doing two
things ...
1. It is calculating the timings
2. Programming the timings and setting async mode.
I think that it would be best if we were to make
On Wed, Jun 20, 2012 at 7:44 PM, Tony Lindgren t...@atomide.com wrote:
* Shubhrajyoti shubhrajy...@ti.com [120620 06:06]:
On Wednesday 20 June 2012 04:02 PM, Tony Lindgren wrote:
* Shubhrajyoti D shubhrajy...@ti.com [120618 07:35]:
From: Jon Hunter jon-hun...@ti.com
The OMAP3530 is based
* Rajendra Nayak rna...@ti.com [120620 23:33]:
On Wednesday 20 June 2012 05:09 PM, Tony Lindgren wrote:
* Rajendra Nayakrna...@ti.com [120606 22:33]:
Hi Tony,
On Tuesday 05 June 2012 12:12 PM, Tony Lindgren wrote:
* Rajendra Nayakrna...@ti.com [120601 05:13]:
The data is autogenerated
On Wednesday 20 June 2012 03:59 PM, Tony Lindgren wrote:
See the comments regarding driver specific resets in hwmod code.
you mean omap_hwmod.c
The way to set this up is to have a shared inline function in
i2c-omap.h that both the driver and hwmod code can use.
hwmod reset function uses oh
On Wed, Jun 20, 2012 at 7:53 PM, Kevin Hilman khil...@ti.com wrote:
Munegowda, Keshava keshava_mgo...@ti.com writes:
On Wed, Jun 20, 2012 at 11:53 AM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Tue, Jun 19, 2012 at 11:32 PM, Kevin Hilman khil...@ti.com wrote:
Munegowda, Keshava
* Shubhrajyoti shubhrajy...@ti.com [120621 00:08]:
On Wednesday 20 June 2012 03:59 PM, Tony Lindgren wrote:
See the comments regarding driver specific resets in hwmod code.
you mean omap_hwmod.c
The way to set this up is to have a shared inline function in
i2c-omap.h that both the driver
Hi Ricardo,
Thanks for the update.
On 6/21/2012 1:10 AM, Ricardo Neri wrote:
As per the OMAP4 documentation, audio over HDMI should be transmitted in
no-idle mode. This patch adds the HWMOD_SWSUP_SIDLE so that omap_hwmode uses
no-idle/force-idle settings instead of smart-idle mode.
This is
On Tue, Jun 19, 2012 at 3:56 PM, Tony Lindgren t...@atomide.com wrote:
Below is the pinctrl-single patch updated with hopefully all the Stephen's
comments addressed. The binding still needs to be looked at, see relevant
parts of the discussion below.
I am happy with the code and the way it
Hi Ricardo,
In fact the flags attribute was not located correctly with regard to the
template used by the scripts.
I updated the script, the patch, the subject and fix a typo in the changelog.
Please find below the updated version.
Regards,
Benoit
---
From
On Thursday 21 June 2012 12:50 PM, Tony Lindgren wrote:
* Shubhrajyoti shubhrajy...@ti.com [120621 00:08]:
On Wednesday 20 June 2012 03:59 PM, Tony Lindgren wrote:
See the comments regarding driver specific resets in hwmod code.
you mean omap_hwmod.c
The way to set this up is to have a shared
This is a fix for v3.4 stable kernel. Mainline commit is
3568f2a46f2a73bab18c914df06afd98a97e0e0e. As a clarification to the original
commit description below: when the bug happens the display does not show
anything.
There is a problem related to DSS FIFO thresholds and power management
on OMAP3.
Use INIT_COMPLETION instead of init_completion in transfer.
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index
Remove the definition of SYSS_RESETDONE_MASK and use the
one in omap_hwmod.h.
Also fixes the warning
CC drivers/i2c/busses/i2c-omap.o
drivers/i2c/busses/i2c-omap.c:163: warning: SYSS_RESETDONE_MASK redefined
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
Use SET_RUNTIME_PM_OPS macro to set runtime functions.
Acked-by: Felipe Balbi ba...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c |8 +---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c
From: Jon Hunter jon-hun...@ti.com
The OMAP3530 is based upon the same silicon as the OMAP3430 and so the I2C
revision is the same for 3430 and 3530. However, the OMAP3630 device has the
same I2C revision as OMAP4. Correct the revision definition to reflect this.
This patch is based on work done
The various devm_* functions allocate memory that is released when a driver
detaches. This patch uses devm_kzalloc, devm_request_and_ioremap for data
that is allocated in the probe function of a platform device and is only
freed in the remove function.
Signed-off-by: Shubhrajyoti D
The patch series does the following
- I2C register restore only if context if the context is lost
- Bus busy recovery mechanism.
- Adds a patch to use devm_* functions
- Adds a pdata function pointer to do context save restore
- Split the omap_i2c_isr to increase readability
- Make the i2c use
Currently i2c register restore is done always.
Adding conditional restore.
The i2c register restore is done only if the context is lost
or in case of error to be on the safe side.
Cc: Kevin Hilman khil...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
arch/arm/plat-omap/i2c.c
The omap_i2c_remove function may not be needed after
device exit so the memory could be freed.
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c
From: Vikram Pandita vikram.pand...@ti.com
In case a peripheral is driving SDA bus low (ie. a start condition), provide
a constant clock output using the test mode of the OMAP I2C controller to
try and clear the bus. Soft reset I2C controller after attempting the bus clear
to ensure that
A recent commit, [PATCH] Fix OMAP EHCI suspend/resume failure
(i693) '354ab856' causes ehci probe to fail on omap3xxx. This
exposed bugs in the ehci_hcd_omap_probe error path causing
an oops.
On the error path, call usb_remove_hcd if usb_add_hcd has been
called, and call usb_put_hcd if
[PATCH] Fix OMAP EHCI suspend/resume failure (i693) '354ab856' causes
an oops on boot for all omap3xxx platforms that use usbhs_omap for
EHCI. The actual oops comes from faulty ehci-omap cleanup, but the
failure caused by the change is evidenced here:
[3.655059] ehci-omap ehci-omap.0:
On Thu, Jun 21, 2012 at 10:12 AM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
I did the clone of this , But I am not seeing the branch 'tmp/test/usb-host'
I am seeing only the branch /wip/arm-nohz-cpusets other than master.
I didn't any usb-host branch here too:
Hi Arnd
Sorry for a delayed reply, we had to discuss this your idea internally
first before replying.
On Fri, 15 Jun 2012, Arnd Bergmann wrote:
On Friday 15 June 2012, Guennadi Liakhovetski wrote:
In the common case, you could have one device connected to the third
slave ID of the first
Hello.
On 21-06-2012 14:44, Russ Dill wrote:
A recent commit, [PATCH] Fix OMAP EHCI suspend/resume failure
(i693) '354ab856'
Usually commit ID follows the word commit, and then the commit summary.
causes ehci probe to fail on omap3xxx. This
exposed bugs in the ehci_hcd_omap_probe error
Hi,
Objective of this series is to make things easy for GPMC driver
conversion series by separating out more things from driver
conversion series.
This series,
1. Unifies NAND platform initialization functions
2. Prepares OneNAND platform code for gpmc driver migration
3. Handles additional
Helper function for updating nand platform data has been
added the capability to take timing structure arguement.
Usage of omap_nand_flash_init() has been replaced by modifed
one, omap_nand_flash_init was doing things similar to
board_nand_init except that NAND CS# were being acquired
based on
Configure busturnaround, cycle2cycledelay, waitmonitoringtime,
clkactivationtime in gpmc_cs_set_timings(). This is done so
that boards can configure these parameters of gpmc in Kernel
instead of relying on bootloader. Also configure bool type
timings like extradelay.
This needed change to two
Reorganize gpmc-onenand initialization so that changes
required for gpmc driver migration can be made smooth.
Ensuring sync read/write are disabled in onenand cannot
be expected to work properly unless GPMC is setup, this
has been removed.
Refactor set_async_mode set_sync_mode functions to
On Mon, Apr 30, 2012 at 10:26:45AM +0300, Peter Ujfalusi wrote:
On 04/29/2012 11:35 PM, Russell King - ARM Linux wrote:
Please can someone at TI take a current mainline kernel, build it, and
test out audio support on the 4430SDP - specifically output through the
headset jack into a line
On Thu, Jun 21, 2012 at 01:59:03PM +0100, Russell King - ARM Linux wrote:
On Mon, Apr 30, 2012 at 10:26:45AM +0300, Peter Ujfalusi wrote:
On 04/29/2012 11:35 PM, Russell King - ARM Linux wrote:
Please can someone at TI take a current mainline kernel, build it, and
test out audio support
On Thu, Jun 21, 2012 at 02:16:42PM +0100, Russell King - ARM Linux wrote:
On Thu, Jun 21, 2012 at 01:59:03PM +0100, Russell King - ARM Linux wrote:
On Mon, Apr 30, 2012 at 10:26:45AM +0300, Peter Ujfalusi wrote:
On 04/29/2012 11:35 PM, Russell King - ARM Linux wrote:
Please can someone
This commit 354ab8567ae3107a8cbe7228c3181990ba598aac titled
Fix OMAP EHCI suspend/resume failure (i693) is causing
the usb hub and device detection fails in beagle XM
causeing NFS not functional. This affects the core retention too.
The same commit logic needs to be revisted adhering to hwmod and
On Thu, Jun 21, 2012 at 7:12 PM, Keshava Munegowda
keshava_mgo...@ti.com wrote:
This commit 354ab8567ae3107a8cbe7228c3181990ba598aac titled
Fix OMAP EHCI suspend/resume failure (i693) is causing
the usb hub and device detection fails in beagle XM
causeing NFS not functional. This affects the
On 18.06.2012 10:15, Hiremath, Vaibhav wrote:
On Mon, Jun 11, 2012 at 19:21:21, Jason Kridner wrote:
From: Daniel Mack zon...@gmail.com
Hey,
can anybody give me a quick wrap-up about the current state of AM33xx
based SoCs in mainline? What are the next steps to get things merged?
There is
On Thursday 21 June 2012, Guennadi Liakhovetski wrote:
Indeed, this solution should be good enough, thanks! I'm not sure, whether
making this multiplexing available requires any additional code to the
generic DMA DT binding implementation. If it does - please, let's make
this a part of the
On Thu, 21 Jun 2012, Russ Dill wrote:
A recent commit, [PATCH] Fix OMAP EHCI suspend/resume failure
(i693) '354ab856' causes ehci probe to fail on omap3xxx. This
exposed bugs in the ehci_hcd_omap_probe error path causing
an oops.
On the error path, call usb_remove_hcd if usb_add_hcd has
Hi,
I have a custom dm3730 board, which is booting fines with 3.2.x kernel.
However it oopses very early in the boot process with 3.4.x kernel.
I have some trouble interpreting the oops so some help is welcome.
I think what makes this board quite different from other setup is the absence
of
The following changes since commit 485802a6c524e62b5924849dd727ddbb1497cc71:
Linux 3.5-rc3 (2012-06-16 17:25:17 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-fixes-for-v3.5-rc3
for you to fetch changes up to
The 5912OSK here no longer mounts NFS root:
http://www.pwsan.com/omap/bootlogs/20120620/omap_cleanup_a_3.6__07b3a13957aa250ff5b5409b8ed756b113544112/
This broke at some point between v3.4-rc2 and v3.5-rc3.
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the
N800 no longer mounts MMC on v3.5-rc3:
http://www.pwsan.com/omap/bootlogs/20120620/omap_cleanup_a_3.6__07b3a13957aa250ff5b5409b8ed756b113544112/n800_bootlog.txt
This broke at some point between v3.4-rc2 and v3.5-rc3.
- Paul
--
To unsubscribe from this list: send the line unsubscribe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tony
The following changes since commit 485802a6c524e62b5924849dd727ddbb1497cc71:
Linux 3.5-rc3 (2012-06-16 17:25:17 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git
Grazvydas Ignotas nota...@gmail.com writes:
On Thu, Jun 21, 2012 at 10:12 AM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
I did the clone of this , But I am not seeing the branch 'tmp/test/usb-host'
I am seeing only the branch /wip/arm-nohz-cpusets other than master.
I didn't any
Hi Russel,
On Thu, Jun 21, 2012 at 4:22 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
Okay, reverting back to v3.4-rc4 works.
As does reverting to v3.4, of course. So, it was broken during the last
merge window.
Strange...
I had no problem with the SDP4430/Blaze audio with
On Thu, Jun 21, 2012 at 09:36:12PM +0300, Ujfalusi, Peter wrote:
Hi Russel,
On Thu, Jun 21, 2012 at 4:22 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
Okay, reverting back to v3.4-rc4 works.
As does reverting to v3.4, of course. So, it was broken during the last
merge
Munegowda, Keshava keshava_mgo...@ti.com writes:
On Thu, Jun 21, 2012 at 7:12 PM, Keshava Munegowda
keshava_mgo...@ti.com wrote:
This commit 354ab8567ae3107a8cbe7228c3181990ba598aac titled
Fix OMAP EHCI suspend/resume failure (i693) is causing
the usb hub and device detection fails in beagle
On Thu, 21 Jun 2012, Paul Walmsley wrote:
N800 no longer mounts MMC on v3.5-rc3:
http://www.pwsan.com/omap/bootlogs/20120620/omap_cleanup_a_3.6__07b3a13957aa250ff5b5409b8ed756b113544112/n800_bootlog.txt
This broke at some point between v3.4-rc2 and v3.5-rc3.
Hmm looks like Tony has some
Hi all,
I am in the process of adding a device-tree binding for OMAP timers and
I have encountered a scenario where ideally it would be useful to remove
a device-tree node at runtime.
The scenario is this ...
1. OMAP3 devices may or may not have security features enabled. Security
enabled
On Thu, 21 Jun 2012, Paul Walmsley wrote:
The 5912OSK here no longer mounts NFS root:
http://www.pwsan.com/omap/bootlogs/20120620/omap_cleanup_a_3.6__07b3a13957aa250ff5b5409b8ed756b113544112/
This broke at some point between v3.4-rc2 and v3.5-rc3.
This one wass due to a bogus kernel
On Thu, 21 Jun 2012, Cousson, Benoit wrote:
Paul,
Will you take it as part of your fixes series for 3.5-rc?
Yes, I'll take your updated version.
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo
On Thu, 21 Jun 2012, Cousson, Benoit wrote:
Hi Ricardo,
In fact the flags attribute was not located correctly with regard to the
template used by the scripts.
I updated the script, the patch, the subject and fix a typo in the changelog.
Please find below the updated version.
Thanks,
Hello Sergei,
On Tue, 19 Jun 2012, Sergei Shtylyov wrote:
diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
index 6b0aedc..a428305 100644
--- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
+++
On 06/19/2012 07:56 AM, Tony Lindgren wrote:
Hi,
Below is the pinctrl-single patch updated with hopefully all the Stephen's
comments addressed. The binding still needs to be looked at, see relevant
parts of the discussion below.
...
From: Tony Lindgren t...@atomide.com
Date: Wed, 6 Jun
On 06/21/2012 02:15 PM, Jon Hunter wrote:
Hi all,
I am in the process of adding a device-tree binding for OMAP timers and
I have encountered a scenario where ideally it would be useful to remove
a device-tree node at runtime.
The scenario is this ...
1. OMAP3 devices may or may not
, and compiler warning fixes for 3.5-rc
-
Testing logs are at
http://www.pwsan.com/omap/bootlogs/20120621/omap_fixes_a_3.5rc__dc57aef503859dbf724f6126c58b2e1672e215f3/
N800 doesn't boot due to MMC problems; 3517 boards won't NFS-mount root
57 matches
Mail list logo
