* Paul Walmsley p...@pwsan.com [120524 23:05]:
On Mon, 21 May 2012, Tony Lindgren wrote:
This series removes the old legacy fulls speed support for
omap2 as it's pretty much only used for omap1 only.
For omap2, only n8x0 seems to have active development, and
that has the external
* Paul Walmsley p...@pwsan.com [120523 17:55]:
On Tue, 22 May 2012, Tony Lindgren wrote:
Unfortunately for many of the older boards these values will probably
remain unknown.
So the better approach here is to just disable frequency scaling
for these cases. Otherwise we'll be
Hi,
* Woodruff, Richard r-woodru...@ti.com [120524 11:16]:
Hi Tony,
I am hoping to solicit an opinion from you for OMAP frameworks in general.
In some recent review there was some debate about how it was good practice to
form parameters in a way which didn't get misused. Nishanth was
On Thu, 2012-05-24 at 18:39 -0600, Paul Walmsley wrote:
cc Jean
Hello Tomi,
On Wed, 16 May 2012, Tomi Valkeinen wrote:
I also suspect that this could be just a plain DSS bug. The default FIFO
low/high thresholds are 960/1023 bytes (i.e. DSS starts refilling the
FIFO when there are
Hello Paul and Tony,
This is a series of patches adding a basic support for system control module,
on OMAP4+ context. It is a working in progress, but I wanted to share already
to get your feedback.
I've modeled the driver as an MFD. You will see in this series:
. A rework of the system control
This patch exposes the definitions under control.h to
drivers outside the machine code.
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
arch/arm/mach-omap2/am35xx-emac.c|2 +-
arch/arm/mach-omap2/board-3430sdp.c |2 +-
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 kis...@ti.com
Signed-off-by: Eduardo Valentin
This is a way to add an early device for system control module.
the code is also requesting for driver registration and probing.
Done at early_initcall because at that time, ioremapping is possible.
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
arch/arm/mach-omap2/devices.c | 29
This patch introduces a MFD core device driver for
OMAP system control module.
The control module allows software control of
various static modes supported by the device. It is
composed of two control submodules: general control
module and device (padconfiguration) control
module.
In this patch,
OMAP system control module can be probed early, then
omap_type is safe to use its APIs.
TODO: add support for other omap versions
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
arch/arm/mach-omap2/id.c | 16 +++-
1 files changed, 15 insertions(+), 1 deletions(-)
diff
Created a new platform driver for the platform device created by the
control module mfd core, wrt usb. This driver has API's to power on/off
the phy and the API's to write to musb mailbox.
(p.s. the mailbox for musb in omap4 is present in system control
module)
[kis...@ti.com: wrote the original
OMAP4460 specific temperature sensor register bit fields are added.
Existing OMAP4 entries are renamed to OMAP4430.
Signed-off-by: Keerthy j-keer...@ti.com
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
arch/arm/mach-omap2/include/mach/control.h | 116
This patch exposes OMAP4 thermal sensor as a thermal zone
named cpu. Only thermal creation is done here.
TODO:
- Add cooling bindings
- Add extrapolation rules
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
drivers/thermal/Kconfig | 12 ++
drivers/thermal/Makefile
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 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap4.dtsi
In the System Control Module, OMAP supplies a voltage reference
and a temperature sensor feature that are gathered in the band
gap voltage and temperature sensor (VBGAPTS) module. The band
gap provides current and voltage reference for its internal
circuits and other analog IP blocks. The
Hello again,
On Fri, May 25, 2012 at 11:25:50AM +0300, Eduardo Valentin wrote:
Hello Paul and Tony,
FYI, Forgot to mention that these patches are available here:
git://gitorious.org/omap-thermal/omap-thermal.git omap_scm_dev
This is a series of patches adding a basic support for system
On Thu, May 24, 2012 at 10:43 AM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Tue, 2012-05-22 at 22:54 +0300, Siarhei Siamashka wrote:
I ran my own fb perf test on omap3 overo board (perf test in
https://gitorious.org/linux-omap-dss2/omapfb-tests) :
vram_cache=n:
* Ryazantsev, Volodymyr v.riazant...@ti.com [120515 04:38]:
Hi Tony,
Could you please take this patch.
Its absence raises some issues like Errata maintenance.
This is already in mainline as commit 33ee0db53994a574b76e0261fc9a3daf71f4b0d7.
Regards,
Tony
--
To unsubscribe from this list:
* Mohammed, Afzal af...@ti.com [120514 03:37]:
Hi Tony,
I am planning to provide actual CS # used for NAND on above boards instead of
finding the value at runtime. Is there any reason that NAND CS# is found out
at runtime ? (hence remove necessity of omap_nand_flash_init()).
Yes makes
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 deletions(-)
diff --git a/arch/arm/mach-omap2/devices.c
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 deletions(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi
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 a/drivers/watchdog/omap_wdt.c b/drivers/watchdog/omap_wdt.c
* Sergio Aguirre sergio.a.agui...@gmail.com [120523 21:49]:
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
-
Hi Tony,
On Fri, May 25, 2012 at 12:56:59, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [120523 17:55]:
On Tue, 22 May 2012, Tony Lindgren wrote:
Unfortunately for many of the older boards these values will probably
remain unknown.
So the better approach here is to just
Hi.
On 05/25/2012 12:25 PM, Eduardo Valentin wrote:
Hello Paul and Tony,
This is a series of patches adding a basic support for system control module,
on OMAP4+ context. It is a working in progress, but I wanted to share already
to get your feedback.
I've modeled the driver as an MFD.
Konstantin,
On Fri, May 25, 2012 at 1:50 PM, Konstantin Baydarov
kbaida...@dev.rtsoft.ru wrote:
Hi.
On 05/25/2012 12:25 PM, Eduardo Valentin wrote:
Hello Paul and Tony,
This is a series of patches adding a basic support for system control module,
on OMAP4+ context. It is a working in
Hi , Eduardo.
On 05/25/2012 12:25 PM, Eduardo Valentin wrote:
This is a way to add an early device for system control module.
the code is also requesting for driver registration and probing.
Done at early_initcall because at that time, ioremapping is possible.
Signed-off-by: Eduardo
Hello,
On Fri, May 25, 2012 at 2:32 PM, Konstantin Baydarov
kbaida...@dev.rtsoft.ru wrote:
Hi , Eduardo.
On 05/25/2012 12:25 PM, Eduardo Valentin wrote:
This is a way to add an early device for system control module.
the code is also requesting for driver registration and probing.
Done at
Hi.
On 05/25/2012 12:25 PM, Eduardo Valentin wrote:
This is a way to add an early device for system control module.
the code is also requesting for driver registration and probing.
Done at early_initcall because at that time, ioremapping is possible.
Signed-off-by: Eduardo Valentin
Hi.
On 05/25/2012 03:11 PM, Valentin, Eduardo wrote:
Konstantin,
On Fri, May 25, 2012 at 1:50 PM, Konstantin Baydarov
kbaida...@dev.rtsoft.ru wrote:
Hi.
On 05/25/2012 12:25 PM, Eduardo Valentin wrote:
Hello Paul and Tony,
This is a series of patches adding a basic support for system
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 postcore_initcall.
Do you still need that since you are supporting only
On 5/25/2012 10:25 AM, Eduardo Valentin wrote:
This is a way to add an early device for system control module.
the code is also requesting for driver registration and probing.
Done at early_initcall because at that time, ioremapping is possible.
Signed-off-by: Eduardo
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
various static modes supported by the device. It is
composed of two control submodules: general control
module and device
Hi Eduardo,
On 5/25/2012 10:25 AM, Eduardo Valentin wrote:
OMAP system control module can be probed early, then
omap_type is safe to use its APIs.
TODO: add support for other omap versions
Signed-off-by: Eduardo Valentineduardo.valen...@ti.com
---
arch/arm/mach-omap2/id.c | 16
Hi Tomi, Paul!
On Fri, May 25, 2012 at 10:24 AM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Thu, 2012-05-24 at 18:39 -0600, Paul Walmsley wrote:
cc Jean
Hello Tomi,
On Wed, 16 May 2012, Tomi Valkeinen wrote:
I also suspect that this could be just a plain DSS bug. The default FIFO
Hi Edurardo,
A few doubts,
On Fri, May 25, 2012 at 1:55 PM, Eduardo Valentin
eduardo.valen...@ti.com wrote:
Created a new platform driver for the platform device created by the
control module mfd core, wrt usb. This driver has API's to power on/off
the phy and the API's to write to musb
On 5/25/2012 10:25 AM, Eduardo Valentin wrote:
Created a new platform driver for the platform device created by the
control module mfd core, wrt usb. This driver has API's to power on/off
the phy and the API's to write to musb mailbox.
(p.s. the mailbox for musb in omap4 is present in system
On 5/25/2012 10:25 AM, Eduardo Valentin wrote:
OMAP4460 specific temperature sensor register bit fields are added.
Existing OMAP4 entries are renamed to OMAP4430.
Signed-off-by: Keerthyj-keer...@ti.com
Signed-off-by: Eduardo Valentineduardo.valen...@ti.com
---
Hi everyone,
we're having some trouble getting useful results from Ftrace on OMAP3
(Gumstix Overo). As you can see in the example output below, function
duration can't be displayed with a precision higher than about 30.5 us,
which matches the frequency of the 32 kHz platform timer. For OMAP1,
Hi.
On 05/25/2012 12:25 PM, Eduardo Valentin wrote:
In the System Control Module, OMAP supplies a voltage reference
and a temperature sensor feature that are gathered in the band
gap voltage and temperature sensor (VBGAPTS) module. The band
gap provides current and voltage reference for its
Hi Wolfram,
Wolfram Sang w.s...@pengutronix.de writes:
On Wed, May 02, 2012 at 08:02:11PM +0530, Shubhrajyoti D wrote:
In omap_i2c_remove we are accessing the I2C_CON register without
enabling the clocks. Fix the same by enabling the clocks and disabling
it.
[...]
I'd really
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 sync timer IP block does not support
smart-idle mode[1], and
Shubhrajyoti D shubhrajy...@ti.com writes:
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.Attempting to fix the same by calling
pm_runtime_disable in the error and the remove path.
Looks
Shubhrajyoti D shubhrajy...@ti.com writes:
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.
Signed-off-by: Shubhrajyoti D
Shubhrajyoti D shubhrajy...@ti.com writes:
Currently in the 1.153 errata handling while waiting for transmitter
underflow if NACK is got the XUDF(Transmit underflow) flag is also set.
-EOVERFLOW
This sentence needs a rewrite and some punctuation. It does not read well.
The flag is set
Shubhrajyoti D shubhrajy...@ti.com writes:
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
Add the OMAP CPUFreq driver to the list of files in the OMAP Power
Management section.
I've already been maintaining this driver, this just makes it
official.
Signed-off-by: Kevin Hilman khil...@ti.com
---
MAINTAINERS |1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS
+Neil Brown
Shubhrajyoti D shubhrajy...@ti.com writes:
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.
Hi Santosh,
Santosh Shilimkar santosh.shilim...@ti.com writes:
Kevin,
Now Colin's v3 [1] is apearing in Len Brown's next branch, I have rebased
OMAP4 support against it. I need to pick up couple of fixes [2] posted on
top of v3 [1] version and arm-soc 'omap/cpuidle-cleanup' branch lined up
49 matches
Mail list logo
