Jean,
On Monday 21 May 2012 07:55 PM, Shilimkar, Santosh wrote:
Jean,
On Mon, May 21, 2012 at 7:23 PM, Jean Pihet jean.pi...@newoldbits.com wrote:
Hi Santosh,
On Thu, May 17, 2012 at 12:04 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
[...]
What do you think?
I like the idea
On Mon, May 21, 2012 at 08:20:05PM +0300, Ohad Ben-Cohen wrote:
Sometimes a single IOMMU user may have to deal with several
different IOMMU devices (e.g. remoteproc).
When an IOMMU fault happens, such users have to regain their
context in order to deal with the fault.
Users can't use the
On Wed, Apr 25, 2012 at 21:06:43, Paul Walmsley wrote:
On Wed, 25 Apr 2012, Cousson, Benoit wrote:
Please take care of changing the hwmod main_clk as well. But maybe
that's not part of that series.
It's not part of the series yet.
Vaibhav, could you take care of changing the main_clk
Hi Ludovic,
On Tue, May 22, 2012 at 3:51 PM, frq09524 ludovic.ba...@stericsson.com wrote:
In my previous patch, to find the correct subdevice that match with physical
memory, I used pa member of rproc_mem_entry.
I'm not sure we want to find these subdevices using the physical
memory of the
On Wed, May 9, 2012 at 1:29 PM, Kevin Hilman khil...@ti.com wrote:
Woodruff, Richard r-woodru...@ti.com writes:
From: Hilman, Kevin
Sent: Tuesday, May 08, 2012 5:17 PM
A basic OMAP AVS driver has been in mainline for a long time, yet we
have not seen support submitted for all of these
On Tue, 22 May 2012, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [120521 23:51]:
Next, I'd suggest implementing the code to allow GPMC timing configuration
from raw register data (the second method above). This is hackish but for
some boards, this is all we'll have. This
Hi Vaibhav
On Wed, 23 May 2012, Hiremath, Vaibhav wrote:
I used your cleaned version of clocktree data, where you have removed all
leaf-nodes and merged multiple clocks nodes into one; but it did not work. I
attempted to review the cleanup and tried to debug, but found it bit hard to
come
On Wed, May 23, 2012 at 20:38:27, Paul Walmsley wrote:
Hi Vaibhav
On Wed, 23 May 2012, Hiremath, Vaibhav wrote:
I used your cleaned version of clocktree data, where you have removed all
leaf-nodes and merged multiple clocks nodes into one; but it did not work.
I
attempted to
On Fri, Nov 18, 2011 at 04:47:17PM +0530, Rajendra Nayak wrote:
+ xyzreg: regulator@0 {
+ regulator-min-microvolt = 100;
+ regulator-max-microvolt = 250;
+ regulator-always-on;
+ vin-supply = vin;
+ };
Just noticed this, but
On Monday 21 May 2012 09:08:40 Tony Lindgren wrote:
Hi Pali,
* Tony Lindgren t...@atomide.com [120508 17:12]:
* Pali Rohár pali.ro...@gmail.com [120504 08:41]:
Hi!
Upstream linux kernel has already driver for lis3lv02d
accelerometer in drivers/misc/lis3lv02d. So now can be
Register OMAP DRM/KMS platform device. DMM is split into a
separate device using hwmod.
Signed-off-by: Andy Gross andy.gr...@ti.com
---
arch/arm/mach-omap2/Makefile |4 ++
arch/arm/mach-omap2/drm.c | 61
Hi Tony, Benoit,
On 1 May 2012 12:47, Omar Ramirez Luna omar.l...@linaro.org wrote:
To allow mailbox driver to function with device tree.
Tested in OMAP4 and OMAP3. OMAP2 untested.
Omar Ramirez Luna (2):
OMAP: mailbox: add device tree support
arm/dts: OMAP2+: Add mailbox nodes
Govindraj.R govindraj.r...@ti.com writes:
From: Govindraj.R govindraj.r...@ti.com
The commit (bce492c0 ARM: OMAP2+: UART: Fix incorrect population of
default uart pads) removed default uart pads that where getting populated
and which was making rx pin wakeup capable. If uart pads were used
Hi Keshava,
Using current l-o master, I noticed that CORE was not hitting retention
in idle on my 3530/Overo. CORE hits retention on suspend just fine.
Debugging this, I found that usbtll_fck was still enabled during idle,
thus preventing CORE from hitting retention.
To test, I disabled USB
On 05/23/2012 05:01 PM, Kevin Hilman wrote:
Hi Keshava,
Using current l-o master, I noticed that CORE was not hitting retention
in idle on my 3530/Overo. CORE hits retention on suspend just fine.
Debugging this, I found that usbtll_fck was still enabled during idle,
thus preventing CORE from
Hi Tony,
On Tue, May 8, 2012 at 6:46 PM, Tony Lindgren t...@atomide.com wrote:
* Sergio Aguirre saagui...@ti.com [120502 08:21]:
This adds support for camera interface with the support for
following sensors:
- OV5640
- OV5650
It seems that at this point we should initialize new things
16 matches
Mail list logo
