On Tue, Sep 18, 2012 at 3:09 AM, Tony Lindgren t...@atomide.com wrote:
* Tony Lindgren t...@atomide.com [120917 14:39]:
* Benoit Cousson b-cous...@ti.com [120913 01:57]:
Enable Cortex A15 generic timer support for OMAP5 based SOCs.
The CPU local timers run on the free running real
On Tue, Sep 18, 2012 at 2:08 AM, Tony Lindgren t...@atomide.com wrote:
* Sebastian Reichel s...@debian.org [120913 14:58]:
Hi,
Are there plans to add crypto acceleration support to OMAP4? Has
this hardware component been removed from OMAP4? I tried to load the
code written for OMAP3 on
On Tue, Sep 18, 2012 at 11:30 AM, Axel Lin axel@gmail.com wrote:
This fixes below build error when CONFIG_LEDS_CLASS is not set.
LD init/built-in.o
arch/arm/plat-omap/built-in.o: In function `fpga_probe':
arch/arm/plat-omap/debug-leds.c:113: undefined reference to
2012/9/18 Bryan Wu bryan...@canonical.com:
On Tue, Sep 18, 2012 at 11:30 AM, Axel Lin axel@gmail.com wrote:
This fixes below build error when CONFIG_LEDS_CLASS is not set.
LD init/built-in.o
arch/arm/plat-omap/built-in.o: In function `fpga_probe':
Hi Linus,
The following changes since commit 55d512e245bc7699a8800e23df1a24195dd08217:
Linux 3.6-rc5 (2012-09-08 16:43:45 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ohad/hwspinlock.git
tags/hwspinlock-3.6-fix
for you to fetch changes up to
Hi Linus,
The following changes since commit 55d512e245bc7699a8800e23df1a24195dd08217:
Linux 3.6-rc5 (2012-09-08 16:43:45 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ohad/rpmsg.git
tags/rpmsg-3.6-fix
for you to fetch changes up to
Hi all,
I have been convinced that my patch for disabling the message
Uncompressing linux... on kernel start was not all that good an idea.
As the problem still remains an issue for me and I'd like to find a fix
for everyone I'd like to ask for pointers where or how to fix this.
To sum up my
Hi Andrew,
On Tue, Sep 18, 2012 at 04:05:59, Andrew Morton wrote:
On Mon, 17 Sep 2012 12:53:22 +0530
AnilKumar Ch anilku...@ti.com wrote:
Add lis331dlh device tree data to am335x-evm.dts. In AM335x EVM
lis331dlh accelerometer is connected to I2C2 bus. So this patch
change the status of
Add temperature sensor DT data to am335x-evm.dts. In AM335x EVM
tmp275 temperature sensor is connected to I2C2 bus. So this patch
adds child node inside i2c2 node with i2c slave address. This patch
is tested on AM335x EVM.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
On Tue, Sep 18, 2012 at 2:49 PM, Axel Lin axel@gmail.com wrote:
2012/9/18 Bryan Wu bryan...@canonical.com:
On Tue, Sep 18, 2012 at 11:30 AM, Axel Lin axel@gmail.com wrote:
This fixes below build error when CONFIG_LEDS_CLASS is not set.
LD init/built-in.o
On Mon, Sep 17, 2012 at 08:43:57AM +0530, Vinod Koul wrote:
On Fri, 2012-09-14 at 15:05 +0300, Peter Ujfalusi wrote:
- /* FIXME: not supported by platform private API */
- return -EINVAL;
+ /* Pause/Resume only allowed with cyclic mode */
+ if (!c-cyclic)
+
On Mon, Sep 17, 2012 at 11:01:23AM +0200, Linus Walleij wrote:
On Thu, Sep 13, 2012 at 3:37 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
Change the parameter list of device_prep_dma_cyclic() so the DMA drivers
can receive the no_wakeup request coming from client drivers.
This feature
When a PM QoS device latency constraint is requested or removed the
constraint is stored in the constraints list of the corresponding power
domain, then the aggregated constraint value is applied by programming
the next functional power state using pwrdm_set_fpwrst.
The per-device PM QoS locking
. Implement the devices wake-up latency constraints using the global
device PM QoS notification handler which applies the constraints to the
underlying layer,
. Implement the low level code which controls the power domains next
functional power states, through the hwmod and pwrdm layers,
.
Update the data from the measurements performed at HW and SW levels.
Cf. http://www.omappedia.org/wiki/Power_Management_Device_Latencies_Measurement
for a detailed explanation on where are the numbers coming from.
ToDo:
- Measure the wake-up latencies for all power domains for OMAP3
- Correct
Figures are added to the power domains structs for RET and OFF modes.
Note: the latency figures for MPU, PER, CORE, NEON have been obtained
from actual measurements.
The latency figures for the other power domains are preliminary and
shall be added.
Cf.
Implement the devices wake-up latency constraints using the global
device PM QoS notification handler which applies the constraints to the
underlying layer by calling the corresponding function at hwmod level.
Reworked after Paul's suggestions.
Tested on OMAP3 Beagleboard and OMAP4 Pandaboard in
Convert the driver from the outdated omap_pm_set_max_mpu_wakeup_lat
API to the new PM QoS API.
Since the constraint is on the MPU subsystem, use the PM_QOS_CPU_DMA_LATENCY
class of PM QoS. The resulting MPU constraints are used by cpuidle to
decide the next power state of the MPU subsystem.
The
Remove the following functions from the OMAP PM API:
omap_pm_set_max_mpu_wakeup_lat
omap_pm_set_max_dev_wakeup_lat
omap_pm_set_max_sdma_lat
and updated the kernel Documentation accordingly.
The generic per-device PM QoS functions shall be used instead of the
OMAP PM API, cf.
The OMAP PM code implements a handler for the per-device PM QoS framework.
The handler queries the omap_hwmod layer in order to manage the power domains
wake-up latency constraints. Hwmod retrieves the correct power domain
and if it exists it calls the corresponding power domain function.
Tested
Hi,
On Tue, Sep 18, 2012 at 08:39:53AM +0200, Maximilian Schwerin wrote:
I have been convinced that my patch for disabling the message
Uncompressing linux... on kernel start was not all that good an idea.
As the problem still remains an issue for me and I'd like to find a fix
for everyone I'd
Hi,
On Tue, Sep 18, 2012 at 10:52:11AM +0200, Jean Pihet wrote:
Convert the driver from the outdated omap_pm_set_max_mpu_wakeup_lat
API to the new PM QoS API.
Since the constraint is on the MPU subsystem, use the PM_QOS_CPU_DMA_LATENCY
class of PM QoS. The resulting MPU constraints are used
On Tue, 2012-09-18 at 09:31 +0100, Russell King - ARM Linux wrote:
On Mon, Sep 17, 2012 at 11:01:23AM +0200, Linus Walleij wrote:
On Thu, Sep 13, 2012 at 3:37 PM, Peter Ujfalusi peter.ujfal...@ti.com
wrote:
Change the parameter list of device_prep_dma_cyclic() so the DMA drivers
can
-Ursprüngliche Nachricht-
Von: Felipe Balbi [mailto:ba...@ti.com]
Gesendet: Dienstag, 18. September 2012 10:50
An: Maximilian Schwerin
Cc: linux-omap@vger.kernel.org
Betreff: Re: How to disable message Uncompressing linux...
on kernel start? (PGP: Plain, Unable to verify
Hello,
I am wondering if an OMAP3 (say dm3730) can generate the hsusb0_clk (musb)
for ULPI by itself? (and if so, how?)
is hsusb0_clk strictly an input depending on an external clock source?
looking at the DM3730 TRM I am not entirely sure
thanks, regards, p.
--
Peter Meerwald
Hi Arnd,
On 09/12/2012 08:20 PM, Arnd Bergmann wrote:
On Tuesday 11 September 2012, Peter Ujfalusi wrote:
OMAP McBSP has nothing to do with a dsp.
A better name would be: ti-mcbsp.h (or leave it as mcbsp.h)
McBSP stands for: Multichannel Buffered Serial Port and it is used for audio
On Thu, Sep 13, 2012 at 5:14 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Mon, Aug 13, 2012 at 8:23 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Mon, Aug 13, 2012 at 7:39 PM, Felipe Balbi ba...@ti.com wrote:
On Mon, Aug 13, 2012 at 06:52:13PM +0530, Munegowda, Keshava
Hi Fernando,
On Thu, Aug 30, 2012 at 9:26 PM, Fernando Guzman Lugo
fernando.l...@ti.com wrote:
These set of patches make possible the remoteproc recover after a crash.
This is a hard recovery, that means the remoteproc is reset and it will
start from the beginning. When a crash happen all the
On 18 September 2012 12:09, Maximilian Schwerin
maximilian.schwe...@tigris.de wrote:
Hi all,
I have been convinced that my patch for disabling the message
Uncompressing linux... on kernel start was not all that good an idea.
As the problem still remains an issue for me and I'd like to find a
On 18 September 2012 15:37, Jassi Brar jaswinder.si...@linaro.org wrote:
On 18 September 2012 12:09, Maximilian Schwerin
maximilian.schwe...@tigris.de wrote:
Hi all,
I have been convinced that my patch for disabling the message
Uncompressing linux... on kernel start was not all that good an
I'm using a BeagleBone, and the linux kernel from Koen Kooi
(https://github.com/koenkooi/linux.git).
I have noticed there is a 0.5sec delay between OMAP UART0 being initialised and
the console being
enabled.
I'll dig a bit deeper, but can anyone shed light on what the delay is ?
Can this
With LPAE, When either the start address or end address
or physical address to be mapped is unaligned,
alloc_init_section creates page granularity mappings.
alloc_init_section calls alloc_init_pte which populates
one pmd entry and sets up the ptes. But if the size is
greater than what can be
On 18/09/12 11:40, Mark Jackson wrote:
I'm using a BeagleBone, and the linux kernel from Koen Kooi
(https://github.com/koenkooi/linux.git).
I have noticed there is a 0.5sec delay between OMAP UART0 being initialised
and the console being
enabled.
It is, of course, when the printk()
Drop the check for up being valid on suspend/resume callbacks.
It should be valid always. Get rid of the pdata check also as
serial_omap_get_context_loss_count() checks for it.
Tested on omap4 panda and 3630 based Beagle board.
Signed-off-by: Sourav Poddar sourav.pod...@ti.com
---
-Ursprüngliche Nachricht-
Von: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] Im Auftrag von Jassi Brar
Gesendet: Dienstag, 18. September 2012 12:23
An: Maximilian Schwerin
Cc: linux-omap@vger.kernel.org
Betreff: Re: How to disable message Uncompressing
On Tue, Sep 18, 2012 at 05:05:54PM +0530, Sourav Poddar wrote:
Drop the check for up being valid on suspend/resume callbacks.
It should be valid always. Get rid of the pdata check also as
serial_omap_get_context_loss_count() checks for it.
Tested on omap4 panda and 3630 based Beagle board.
2012/9/18 Mark Jackson mpfj-l...@mimc.co.uk:
I'm using a BeagleBone, and the linux kernel from Koen Kooi
(https://github.com/koenkooi/linux.git).
I have noticed there is a 0.5sec delay between OMAP UART0 being initialised
and the console being
enabled.
I'll dig a bit deeper, but can
Hi Felipe,
On Tue, Sep 18, 2012 at 5:04 PM, Felipe Balbi ba...@ti.com wrote:
On Tue, Sep 18, 2012 at 05:05:54PM +0530, Sourav Poddar wrote:
Drop the check for up being valid on suspend/resume callbacks.
It should be valid always. Get rid of the pdata check also as
On 18 September 2012 12:09, Maximilian Schwerin
maximilian.schwe...@tigris.de wrote:
Hi all,
I have been convinced that my patch for disabling the message
Uncompressing linux... on kernel start was not all that
good an idea.
As the problem still remains an issue for me and I'd like
Adds pinctrl support to support OMAP platforms that boot from DT
and rely on pinctrl support to set pinmuxes.
Signed-off-by: Matt Porter mpor...@ti.com
---
drivers/spi/spi-omap2-mcspi.c |8
1 file changed, 8 insertions(+)
diff --git a/drivers/spi/spi-omap2-mcspi.c
On Tue, Sep 18, 2012 at 10:57:26AM +0530, Shubhrajyoti wrote:
On Monday 17 September 2012 10:52 PM, Matt Porter wrote:
Adds pinctrl support to support OMAP platforms that boot from DT
and rely on pinctrl support to set pinmuxes.
Signed-off-by: Matt Porter mpor...@ti.com
---
looks good
On Tuesday 18 September 2012 05:31 PM, Matt Porter wrote:
Adds pinctrl support to support OMAP platforms that boot from DT
and rely on pinctrl support to set pinmuxes.
looks good
Acked-by: Shubhrajyoti D shubhrajy...@ti.com
Signed-off-by: Matt Porter mpor...@ti.com
---
On Mon, Sep 17, 2012 at 7:22 PM, Matt Porter mpor...@ti.com wrote:
Enable pinctrl dummy states for all OMAP platforms that don't
populate DT. This allows drivers to be converted to pinctrl
and not generate new warnings on platforms that do not provide
pinctrl data. These platforms already
-Ursprüngliche Nachricht-
Von: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] Im Auftrag von Jassi Brar
Gesendet: Dienstag, 18. September 2012 13:54
An: Maximilian Schwerin
Cc: linux-omap@vger.kernel.org
Betreff: Re: How to disable message Uncompressing
On Tue, Sep 18, 2012 at 11:00 AM, Vinod Koul vinod.k...@linux.intel.com wrote:
On Tue, 2012-09-18 at 09:31 +0100, Russell King - ARM Linux wrote:
On Mon, Sep 17, 2012 at 11:01:23AM +0200, Linus Walleij wrote:
On Thu, Sep 13, 2012 at 3:37 PM, Peter Ujfalusi peter.ujfal...@ti.com
wrote:
Greg's tty-next is not booting on 2420 based N800. The failure is
observed at serial init itself. The reason might be that n800 tries to
resume even though it is not suspended before.
Reported-by: Paul Walmsley p...@pwsan.com
Signed-off-by: Sourav Poddar sourav.pod...@ti.com
---
This patch is
On Monday 17 September 2012, David Brown wrote:
There is also a lot of similarity between the mmci hardware and the
msm_sdcc hardware. Enough so, that it is probably better for us to
make the mmci driver work with our hardware, rather than trying to
keep msm_sdcc going.
There is also an
On Tue, Sep 18, 2012 at 08:43:55AM +0530, Vinod Koul wrote:
On Mon, 2012-09-17 at 23:36 +0100, Russell King - ARM Linux wrote:
I believe that Jon is on vacation this week, so if this is the only issue
holding up the merge, maybe you can change this in his patch directly, or
I can
On Tue, Sep 18, 2012 at 06:10:50PM +0530, Sourav Poddar wrote:
Greg's tty-next is not booting on 2420 based N800. The failure is
observed at serial init itself. The reason might be that n800 tries to
resume even though it is not suspended before.
Reported-by: Paul Walmsley p...@pwsan.com
On Tuesday 18 September 2012, Matt Porter wrote:
On Tue, Sep 18, 2012 at 08:43:55AM +0530, Vinod Koul wrote:
Now would it make sense to NOT merge these changes for 3.7 and postpone
to 3.8. I can host these patches on a topic branch and merge them when
we are ready. I plan to spend some
This patch series provides an update of a previous posting:
http://www.spinics.net/lists/arm-kernel/msg194946.html
v2 updates:
- Dropped v7 dcache level patch
- Refactor the set to make it work on all processors with MULTI_CACHE
and !MULTI_CACHE
- Factor out label redefinition in
ARM v7 architecture introduced the concept of cache levels and related
control registers. New processors like A7 and A15 embed an L2 unified cache
controller that becomes part of the cache level hierarchy. Some operations in
the kernel like cpu_suspend and __cpu_disable do not require a flush of
This patch renames jump labels in v7_flush_dcache_all in order to define
a specific flush cache levels entry point.
TODO: factor out the level flushing loop if considered worthwhile and
define the input registers requirements.
Signed-off-by: Lorenzo Pieralisi lorenzo.pieral...@arm.com
---
In processors like A15/A7 L2 cache is unified and integrated within the
processor cache hierarchy, so that it is not considered an outer cache
anymore. For processors like A15/A7 flush_cache_all() ends up cleaning
all cache levels up to Level of Coherency (LoC) that includes
the L2 unified cache.
From: Santosh Shilimkar santosh.shilim...@ti.com
The ARMv7 processor setup function __v7_setup() cleans and invalidates the
CPU cache before enabling MMU to start the CPU with a clean CPU local cache.
But on ARMv7 architectures like Cortex-[A15/A8], this code will end
up flushing the L2
When a CPU is hotplugged out caches that reside in its power domain
lose their contents and so must be cleaned to the next memory level.
Currently, __cpu_disable calls flush_cache_all() that for new generation
processor like A15/A7 ends up cleaning and invalidating all cache levels
up to Level of
Found by http://coccinelle.lip6.fr/
Signed-off-by: Peter Senna Tschudin peter.se...@gmail.com
---
arch/arm/mach-omap2/board-flash.c | 2 +-
arch/arm/mach-omap2/clkt_clksel.c | 2 +-
arch/arm/mach-omap2/mux.c | 2 +-
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c |
Found by http://coccinelle.lip6.fr/
Signed-off-by: Peter Senna Tschudin peter.se...@gmail.com
---
arch/arm/plat-omap/omap-pm-noop.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/plat-omap/omap-pm-noop.c
b/arch/arm/plat-omap/omap-pm-noop.c
index
Found by http://coccinelle.lip6.fr/
Signed-off-by: Peter Senna Tschudin peter.se...@gmail.com
---
arch/arm/mach-omap1/devices.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap1/devices.c b/arch/arm/mach-omap1/devices.c
index fa1fa4d..688b23a 100644
---
Hello all,
I have been moving from the ti 2.6.37 BSP to the 3.x kernel with quite a bit of
success, the main issue I have at the moment is trying to get the frame buffer
and any displays I have initialised.
[2.805358] omapfb omapfb: no driver for display: lcd
[2.810729] omapfb omapfb:
Hi Paul,
On Thu, Sep 13, 2012 at 9:04 AM, Jean Pihet jean.pi...@newoldbits.com wrote:
On Thu, Sep 13, 2012 at 2:34 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Jean Pihet jean.pi...@newoldbits.com writes:
Here is a re-spin after some comments and suggestions after review
and
Here are some basic OMAP boot and power management test results for
v3.6-rc6:
http://www.pwsan.com/omap/testlogs/test_v3.6-rc6/20120918101040/
Some observations:
Boot tests:
* CM-T3517: L3 in-band error with USB OTG during boot
- Cause unknown; longstanding issue; does not occur on the
* Shubhrajyoti shubhrajy...@ti.com [120918 05:09]:
On Tuesday 18 September 2012 05:31 PM, Matt Porter wrote:
Adds pinctrl support to support OMAP platforms that boot from DT
and rely on pinctrl support to set pinmuxes.
looks good
Acked-by: Shubhrajyoti D shubhrajy...@ti.com
Acked-by:
* Shilimkar, Santosh santosh.shilim...@ti.com [120917 23:07]:
On Tue, Sep 18, 2012 at 3:09 AM, Tony Lindgren t...@atomide.com wrote:
* Tony Lindgren t...@atomide.com [120917 14:39]:
* Benoit Cousson b-cous...@ti.com [120913 01:57]:
Enable Cortex A15 generic timer support for
* Omar Ramirez Luna omar.l...@linaro.org [120912 12:47]:
--- a/arch/arm/plat-omap/include/plat/iommu.h
+++ b/arch/arm/plat-omap/include/plat/iommu.h
@@ -27,6 +27,13 @@ struct iotlb_entry {
};
};
+/* context registers */
+struct iommu_regs {
+ u32 irqen;
+ u32 cntl;
+
When using pinctrl-single to handle i2c initialization, it has
to be done early.
On the beaglebone the regulator is connected to the i2c0 bus,
and for sure that's the case for many other am33xx boards.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
Pinctrl-fy the OMAP I2C driver.
Due to the requirement of early usage of I2C for
regulators and such, earlier initialization of pinctrl
is required.
This patch series is against
git://gitorious.org/linus-tree/linus-tree.git for_3.7/i2c/big_cleanups
Note that the I2C DT bindings are against the
The message spit out when the i2c-omap driver load is printing
the platform device's id as a bus number. However when booting
from OF id is -1, which is not so nice.
Fix it by printing the adapter number.
[0.210467] omap_i2c 44e0b000.i2c: bus -1 rev2.4.0 at 400 kHz
vs
[0.210467]
Add DT I2C bindings for am33xx platforms, as well as rename the
instances to what is used in the TRM.
The patch series is against linux-omap-dt for_3.7/dts_part2
Pantelis Antoniou (2):
arm/dts: AM33XX: I2C DT bindings for the bone.
am33xx: DT convert I2C from OMAP to am33xx names
Add I2C DT bindings for the beaglebone.
This includes bindings for the EEPROMs on both I2C busses.
Note that this requires a pinmux node in am33xx.dtsi,
introduced from 47acae37fa0d11dd8fba58f8825ac3a2baeab903
arm/dts: AM33XX: Add basic pinctrl device tree data
Signed-off-by: Pantelis Antoniou
On Tue, 18 Sep 2012, Lorenzo Pieralisi wrote:
ARM v7 architecture introduced the concept of cache levels and related
control registers. New processors like A7 and A15 embed an L2 unified cache
controller that becomes part of the cache level hierarchy. Some operations in
the kernel like
On OMAP the TRM names I2C instances as i2c1, i2c2, etc.
On the am33xx's it is i2c0, i2c1, etc.
Use am33xx naming everywhere; the only exception is the hwmod names,
which we don't want to mess with right now.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
Add support for pinctrl mux settings in the OMAP I2C driver.
If no such pinctl bindings are found a warning message is printed.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
drivers/i2c/busses/i2c-omap.c | 7 +++
1 file changed, 7 insertions(+)
diff --git
On Tue, 18 Sep 2012, Lorenzo Pieralisi wrote:
This patch renames jump labels in v7_flush_dcache_all in order to define
a specific flush cache levels entry point.
TODO: factor out the level flushing loop if considered worthwhile and
define the input registers requirements.
On Tue, 18 Sep 2012, Lorenzo Pieralisi wrote:
In processors like A15/A7 L2 cache is unified and integrated within the
processor cache hierarchy, so that it is not considered an outer cache
anymore. For processors like A15/A7 flush_cache_all() ends up cleaning
all cache levels up to Level of
On Tue, 18 Sep 2012, Lorenzo Pieralisi wrote:
When a CPU is hotplugged out caches that reside in its power domain
lose their contents and so must be cleaned to the next memory level.
Currently, __cpu_disable calls flush_cache_all() that for new generation
processor like A15/A7 ends up
On Tue, 18 Sep 2012, Lorenzo Pieralisi wrote:
From: Santosh Shilimkar santosh.shilim...@ti.com
The ARMv7 processor setup function __v7_setup() cleans and invalidates the
CPU cache before enabling MMU to start the CPU with a clean CPU local cache.
But on ARMv7 architectures like
Hi,
* Pantelis Antoniou pa...@antoniou-consulting.com [120918 11:13]:
When using pinctrl-single to handle i2c initialization, it has
to be done early.
On the beaglebone the regulator is connected to the i2c0 bus,
and for sure that's the case for many other am33xx boards.
Usually it's better
* Pantelis Antoniou pa...@antoniou-consulting.com [120918 11:13]:
Add support for pinctrl mux settings in the OMAP I2C driver.
If no such pinctl bindings are found a warning message is printed.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
* Pantelis Antoniou pa...@antoniou-consulting.com [120918 11:13]:
The message spit out when the i2c-omap driver load is printing
the platform device's id as a bus number. However when booting
from OF id is -1, which is not so nice.
Fix it by printing the adapter number.
[0.210467]
Hi Ohad,
On Tue, Sep 18, 2012 at 4:59 AM, Ohad Ben-Cohen o...@wizery.com wrote:
Hi Fernando,
On Thu, Aug 30, 2012 at 9:26 PM, Fernando Guzman Lugo
fernando.l...@ti.com wrote:
These set of patches make possible the remoteproc recover after a crash.
This is a hard recovery, that means the
On Tuesday, September 18, 2012, Axel Lin wrote:
omap_device_get_by_hwmod_name() returns ERR_PTR on error.
Signed-off-by: Axel Lin axel@gmail.com
Kevin, should I take this?
Rafael
---
drivers/cpufreq/omap-cpufreq.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
Hi Tony,
On Sep 18, 2012, at 9:21 PM, Tony Lindgren wrote:
Hi,
* Pantelis Antoniou pa...@antoniou-consulting.com [120918 11:13]:
When using pinctrl-single to handle i2c initialization, it has
to be done early.
On the beaglebone the regulator is connected to the i2c0 bus,
and for sure
Hi Panto,
That patch is good, but a similar one was already posted by Florian.
https://patchwork.kernel.org/patch/1392671/
Checking the email thread it seems that Wolfram pulled it.
Regards,
Benoit
On 9/19/2012 11:07 AM, Pantelis Antoniou wrote:
The message spit out when the i2c-omap driver
Hi Tony,
On Sep 18, 2012, at 9:23 PM, Tony Lindgren wrote:
* Pantelis Antoniou pa...@antoniou-consulting.com [120918 11:13]:
Add support for pinctrl mux settings in the OMAP I2C driver.
If no such pinctl bindings are found a warning message is printed.
Signed-off-by: Pantelis Antoniou
Hi Samuel,
El Mon, Sep 17, 2012 at 01:09:36AM +0200 Samuel Ortiz ha dit:
On Thu, Aug 09, 2012 at 10:42:31PM +0200, Matthias Kaehlcke wrote:
The TPS65217 chip contains a boost converter and current sinks which can be
used to drive LEDs for use as backlights. Expose this functionality via the
The decision was made a few months ago to weaken the clockdomain
requirements for hwmods and clocks. Convert some of these
warnings into debug messages. In other cases, don't return an
error when a clockdomain isn't specified. And while here,
appropriately mark some OMAP4 hwmods that don't have
Some struct omap_hwmod records belonging to PRCM IP blocks are missing
HWMOD_NO_IDLEST flags; add them.
Signed-off-by: Paul Walmsley p...@pwsan.com
Cc: Benoît Cousson b-cous...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c |3 +++
1 file changed, 3 insertions(+)
diff --git
The decision was made a few months ago to allow struct omap_hwmod
records and struct clk records to omit clockdomain information if the
clockdomain is not software-controllable. See for example commit
868c157df9721675c19729eed2c96bac6c3f1d01 (ARM: OMAP2+: hwmod: remove
prm_clkdm, cm_clkdm; allow
We're no longer requiring struct omap_hwmod records to contain a
clockdomain. So we shouldn't return -EINVAL any more from
_omap4_wait_target_disable() or _omap4_wait_target_ready() if there's
no clockdomain defined, since that just gets passed back to the
caller. This can result in pointless
Hi Paul,
On 9/18/2012 4:12 PM, Paul Walmsley wrote:
The decision was made a few months ago to allow struct omap_hwmod
records and struct clk records to omit clockdomain information if the
clockdomain is not software-controllable. See for example commit
868c157df9721675c19729eed2c96bac6c3f1d01
On 9/18/2012 4:42 AM, Arnd Bergmann wrote:
On Saturday 15 September 2012, Russell King - ARM Linux wrote:
On Fri, Sep 14, 2012 at 05:41:56PM -0500, Jon Hunter wrote:
3. Supporting legacy devices not using DMA Engine
These devices present a problem, as there may not be a uniform way to
Hi Tero,
just looking at the usecounting series to see what is mergeable and
noticed this:
On Fri, 13 Jul 2012, Tero Kristo wrote:
Secondly, there are multiple erratas for omap3, which say that the
wakedeps should be enabled for the PER domain, see e.g. errata i582 for
omap3630.
Erratum
On Wed, Sep 19, 2012 at 06:19:06AM +0800, Mitch Bradley wrote:
Is there ever a point when old architectures leave the Linux tree, or
will people have to see grep hits from them until the end of time?
That depends on use and the burden of keeping them in the tree. I'm
not aware of much activity
On Tue, 18 Sep 2012, Paul Walmsley wrote:
What do you think about the following patch to handle part of the i582
workaround?
That patch was an older version; here's one that builds and boots - sorry
about that. It passed the basic PM tests here on 3730ES1.0 Beagle XM and
3730ES1.2 EVM.
On Tue, 18 Sep 2012, Felipe Balbi wrote:
On Tue, Sep 18, 2012 at 06:10:50PM +0530, Sourav Poddar wrote:
Greg's tty-next is not booting on 2420 based N800. The failure is
observed at serial init itself. The reason might be that n800 tries to
resume even though it is not suspended before.
Hi Peter,
On Mon, Sep 10, 2012 at 01:46:18PM +0300, Peter Ujfalusi wrote:
Hello,
Generated on top of:
git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git topic/omap
I applied the first 8 patches, but I'd like to get Mark's ACK for the rest of
the serie.
Unless you're expecting Mark to
Hi Tony,
On 18 September 2012 13:04, Tony Lindgren t...@atomide.com wrote:
* Omar Ramirez Luna omar.l...@linaro.org [120912 12:47]:
--- a/arch/arm/plat-omap/include/plat/iommu.h
+++ b/arch/arm/plat-omap/include/plat/iommu.h
@@ -27,6 +27,13 @@ struct iotlb_entry {
};
};
+/* context
Hi
On Mon, 27 Aug 2012, Paul Walmsley wrote:
Add integration data for the hardware random number generator IP block
on some OMAP SoCs. This appears to be present on OMAP2xxx and OMAP3xxx
SoCs, although it is not so easy to tell. It may also be present on
other OMAP2+ SoCs.
Hi
On Fri, 14 Sep 2012, Maximilian Schwerin wrote:
we've designed two beagle board clones (two different layouts) for a
customer. After quite some time without any problems they are now seeing
USB problems on some of the boards. I have so far not been able to
reproduce the problem...
1 - 100 of 103 matches
Mail list logo
