With more overlays and overlay managers on OMAP4, and more coming in future
OMAPs, the current way of defining the DISPC overlay and manager register
offsets through macros isn't scalable. Introduce a new dispc.h header which
contains Macros for common DISPC registers and inline functions for
Move all DISPC register definitions to a new header dispc.h. There are
separate register offset definitions for GFX, VID1 and VID2 pipeline share
register definitions by using an argument. The introduction of VID3 pipeline
on OMAP4 will not let us use the above method since VID3 pipe register
Represent manager/channel specific DISPC registers as inline functions returning
the required dispc_reg struct. This is done since the current method is not
scalable as the number of overlay managers increase in number.
Signed-off-by: Archit Taneja arc...@ti.com
---
struct dispc_reg was originally used while migrating from old omapfb to
catch cases where the arguments to dispc_read_reg/dispc_write_reg were in
wrong order, since old omapfb had the arguments in reverse order.
Remove this struct and use u16 instead
Signed-off-by: Archit Taneja arc...@ti.com
* Tony Lindgren t...@atomide.com [110505 08:56]:
So the problem is patches 1 8 in this series. The rest is just fine
as it's the necessary omap hardware specific implementation.
Sorry, patches 1 7 I mean.
Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the
Hi,
* Adrian Hunter adrian.hun...@nokia.com [110505 14:48]:
From: Venkatraman S svenk...@ti.com
Add sDMA driver support for descriptor autoloading feature.
Descriptor autoloading is OMAP sDMA v5 hardware capability that can be
exploited for scatter gather
scenarios, currently available
* Oleg Drokin gr...@linuxhacker.ru [110504 08:59]:
Hello!
On May 4, 2011, at 9:27 AM, Mike Rapoport wrote:
Commits 5e6a64b36ce346b7a2d481ef9fa315290eb28e5e (omap: move detection of
NAND CS to common-board-devices) and
96974a249b0cf3537f49115a59be67e2c54f315c
(omap: consolidate touch
On Fri, May 6, 2011 at 12:18 AM, Artem Bityutskiy dedeki...@gmail.com wrote:
On Mon, 2011-05-02 at 16:40 +0530, Kishore Kadiyala wrote:
For prefetch engine, read and write got broken in commit '2c01946c'.
We never hit a scenario of not getting 'gpmc_prefetch_enable'
call success.
When
On Fri, May 6, 2011 at 6:08 AM, Cousson, Benoit b-cous...@ti.com wrote:
[]
Devices will indeed never care about voltage directly, but that will happen
indirectly because of:
- voltage domains dependency: Changing the MPU or IVA voltage domain might
force the CORE voltage to increase its
On Thu, May 5, 2011 at 5:21 PM, Adrian Hunter adrian.hun...@nokia.com wrote:
CERR and BADA were in the wrong place and there are only
32 not 35.
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
drivers/mmc/host/omap_hsmmc.c | 19 +++
1 files changed, 11
The current code base is not linking with the OMAP_PM_NONE
option set.
Since the option OMAP_PM_NOOP provides a no-op/debug layer,
OMAP_PM_NONE can be removed.
OMAP_PM_NOOP is enabled by default by Kconfig.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
arch/arm/plat-omap/Kconfig|
Please note that this code is based on khilman's for_2.6.40/pm-cleanup branch.
Jean
On Fri, May 6, 2011 at 11:11 AM, Jean Pihet jean.pi...@newoldbits.com wrote:
The current code base is not linking with the OMAP_PM_NONE
option set.
Since the option OMAP_PM_NOOP provides a no-op/debug layer,
Let the bootloader do all the pad configuration.
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
arch/arm/mach-omap2/board-rm680.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/board-rm680.c
b/arch/arm/mach-omap2/board-rm680.c
index
Go through the driver's set_power() functions rather than
calling regulator_enable/disable() directly because otherwise
pbias configuration for MMC1 is not done.
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
drivers/mmc/host/omap_hsmmc.c | 17 -
1 files changed, 8
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
Signed-off-by: Andy Shevchenko ext-andriy.shevche...@nokia.com
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
drivers/mmc/host/omap_hsmmc.c | 17 ++---
1 files changed, 6 insertions(+), 11 deletions(-)
diff --git
In the case of an I/O error, the DMA will have been
cleaned up in the MMC interrupt and the request
structure pointer will be null.
In that case, it is essential to check if the DMA
DMA is over before dereferencing host-mrq-data.
Oops as follows:
3[ 2293.695281] wl1271: ERROR sdio read failed
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
There are two pieces of code which similar, but not the same. Each of them
contains a bug.
The SYSCTL register should be read before write in the
omap_hsmmc_context_restore() to remain the state of the reserved bits.
Before set the clock
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
There are two places where the same calculations are done. Let's split them to
separate function.
In addition the new function is simplified by usage DIV_ROUND_UP kernel macro.
Signed-off-by: Andy Shevchenko ext-andriy.shevche...@nokia.com
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
There is similar piece of code in two functions which enables clock. Split this
code to omap_hsmmc_start_clock(). Re-use omap_hsmmc_stop_clock() in
omap_hsmmc_context_restore() as well.
Signed-off-by: Andy Shevchenko
Hi
Here is V2 of some patches for omap_hsmmc.
Changes in V2:
OMAP: sDMA: descriptor autoloading feature
- removed the feature entirely as per Tony Lindgren
mmc: omap_hsmmc: fix few bugs when set the clock divisor
- added cpu_relax() as per
CERR and BADA were in the wrong place and there are only
32 not 35.
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
Reviewed-by: Venkatraman S svenk...@ti.com
---
drivers/mmc/host/omap_hsmmc.c | 19 +++
1 files changed, 11 insertions(+), 8 deletions(-)
diff --git
eMMC may have a hardware reset line connected to a gpio,
so pass it to the driver.
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
arch/arm/mach-omap2/hsmmc.c |5 +
arch/arm/mach-omap2/hsmmc.h |1 +
arch/arm/plat-omap/include/plat/mmc.h |1 +
3 files
From: Sudhir Bera ext-sudhir.b...@nokia.com
In fact the no_off check here will not be hit because
'omap_hsmmc_disabled_to_sleep()' won't schedule a
deeper disable in the no_off case.
Signed-off-by: Sudhir Bera ext-sudhir.b...@nokia.com
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
Move the min and max frequency constants to the definition block in the source
file.
Signed-off-by: Andy Shevchenko ext-andriy.shevche...@nokia.com
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
drivers/mmc/host/omap_hsmmc.c |6
From: Jarkko Lavinen jarkko.lavi...@nokia.com
Allow the bootloader do all the muxing.
Signed-off-by: Jarkko Lavinen jarkko.lavi...@nokia.com
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
arch/arm/mach-omap2/hsmmc.c |3 ++-
arch/arm/mach-omap2/hsmmc.h |1 +
2 files changed, 3
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
There are few places with the same functionality. This patch creates two
functions omap_hsmmc_set_bus_width() and omap_hsmmc_set_bus_mode() to do the
job.
Signed-off-by: Andy Shevchenko ext-andriy.shevche...@nokia.com
Signed-off-by: Adrian
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
There are 3 new platform data methods which should help us to do a clock
switching when notification is happened or request is started.
The purpose of the patch is to avoid high frequency of MMC controller on low
OPPs due to an HW bug in OMAP
On Thu, May 5, 2011 at 8:28 PM, Kevin Hilman khil...@ti.com wrote:
Govindraj govindraj...@gmail.com writes:
[...]
... this is just putting back basically the same thing that was removed in
patch 1. IOW, this is now being checked for *every* PRCM wakeup, which
is no different than having
After a warm restart, an eMMC which cannot be powered off is
in an unknown state, so reset it to be sure it will initialize.
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
drivers/mmc/host/omap_hsmmc.c | 38 +-
1 files changed, 37 insertions(+), 1
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
We should like to adjust MMC host controller clock whenever the OPP is changed.
OPP affects to L3/L4 bus frequency. Due to this we update the maximum frequency
limits before each upcoming request and when the divisor is calculated.
Add API to determine IO-PAD wakeup event status for a given
hwmod dynamic_mux pad.
Signed-off-by: Govindraj.R govindraj.r...@ti.com
---
arch/arm/mach-omap2/mux.c| 28 ++
arch/arm/mach-omap2/mux.h| 13
Add two API's to set IO Pad wakeup capability based on hwmod
mux pins available and also to check the status of IO Pad wakeup
event.
This two patches are separated from uart_runtime patches posted
earlier and uart_runtime adaptation relies on these two API's.
Based on 2.6.39-rc6
Reference to
Add API to enable IO pad wakeup capability based on mux dynamic pad and
wake_up enable flag available from hwmod_mux initialization.
Use the wakeup_enable flag and enable wakeup capability
for the given pads. Wakeup capability will be enabled/disabled
during hmwod idle transition based on whether
On Fri, May 6, 2011 at 14:44, Adrian Hunter adrian.hun...@nokia.com wrote:
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
Add patch description here.
Signed-off-by: Andy Shevchenko ext-andriy.shevche...@nokia.com
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
On Fri, May 6, 2011 at 2:34 PM, Varadarajan, Charulatha ch...@ti.com wrote:
On Fri, May 6, 2011 at 14:44, Adrian Hunter adrian.hun...@nokia.com wrote:
From: Andy Shevchenko ext-andriy.shevche...@nokia.com
Add patch description here.
You mean something like following:
The code contains
Patch series for TWL4030 power scripts for OMAP3 boards and
workaround for TWL erratum 27.
Changes for implementing TWL4030 power scripts recommended by hardware team.
Introduced a new TWL4030 power script file, which can be used by different
OMAP3 board with the power companion chip TWL4030.
Only configure sleep script when the flag is TWL4030_SLEEP_SCRIPT.
Adding the missing brackets for fixing the issue.
Signed-off-by: Lesly A M lesl...@ti.com
Cc: Nishanth Menon n...@ti.com
Cc: David Derrick dderr...@ti.com
Cc: Samuel Ortiz sa...@linux.intel.com
---
drivers/mfd/twl4030-power.c |
Correcting the if condition check for printing the warning,
if wakeup script is not updated before updating the sleep script.
Since the flag 'order' is set to '1' while updating the wakeup script for P1P2,
the condition checking for printing the warning should be if(!order)
(ie: print the warning
Modifying the macro name Main_Ref to all caps(MAIN_REF).
Suggested by Nishanth Menon n...@ti.com
Signed-off-by: Lesly A M lesl...@ti.com
Cc: Nishanth Menon n...@ti.com
Cc: David Derrick dderr...@ti.com
Cc: Samuel Ortiz sa...@linux.intel.com
---
arch/arm/mach-omap2/board-rx51-peripherals.c |
Power bus message sequence for TWL4030 to enter sleep/wakeup/warm_reset.
TWL4030 power scripts which can be used by different OMAP3 boards
with the power companion chip (TWL4030 series).
The twl4030 generic script can be used by any board file to update
the power data in twl4030_platform_data.
Skip the i2c register writes in twl4030_configure_resource() if the new value
is same as the old value, for devgrp/type/remap regs.
Suggested by David Derrick dderr...@ti.com
Signed-off-by: Lesly A M lesl...@ti.com
Cc: Nishanth Menon n...@ti.com
Cc: David Derrick dderr...@ti.com
Cc: Samuel Ortiz
Workaround for TWL5030 Silicon Errata 27 28:
27 - VDD1, VDD2, may have glitches when their output value is updated.
28 - VDD1 and / or VDD2 DCDC clock may stop working when internal clock
is switched from internal to external.
Erratum 27:
If the DCDC
Added API to get the TWL5030 Si version from the IDCODE register.
It is used for enabling the workaround for TWL erratum 27.
Signed-off-by: Lesly A M lesl...@ti.com
Cc: Nishanth Menon n...@ti.com
Cc: David Derrick dderr...@ti.com
Cc: Samuel Ortiz sa...@linux.intel.com
---
drivers/mfd/twl-core.c
Hi,
On Fri, May 6, 2011 at 14:44, Adrian Hunter adrian.hun...@nokia.com wrote:
After a warm restart, an eMMC which cannot be powered off is
in an unknown state, so reset it to be sure it will initialize.
Signed-off-by: Adrian Hunter adrian.hun...@nokia.com
---
drivers/mmc/host/omap_hsmmc.c
On 05/05/2011 02:16 PM, Kevin Hilman wrote:
In any case, you've found a real bug, and your patch is valid. However,
it doesn't currently apply to mainline, and it looks like it's because
your patch is using spaces and the code being patched is using tabs.
Also, you can simplify the changelog
Salut Jean
On Fri, 6 May 2011, Jean Pihet wrote:
The current code base is not linking with the OMAP_PM_NONE
option set.
Since the option OMAP_PM_NOOP provides a no-op/debug layer,
OMAP_PM_NONE can be removed.
OMAP_PM_NOOP is enabled by default by Kconfig.
Signed-off-by: Jean Pihet
Not that this is particularly related to DVFS, but:
On Thu, 5 May 2011, Colin Cross wrote:
On Thu, May 5, 2011 at 2:08 PM, Cousson, Benoit b-cous...@ti.com wrote:
Colin Cross wrote:
omap_hwmod is entirely omap specific, and any generic solution cannot
be based on it.
For the
Hi Paul,
On Fri, May 6, 2011 at 6:16 PM, Paul Walmsley p...@pwsan.com wrote:
Salut Jean
On Fri, 6 May 2011, Jean Pihet wrote:
The current code base is not linking with the OMAP_PM_NONE
option set.
Since the option OMAP_PM_NOOP provides a no-op/debug layer,
OMAP_PM_NONE can be removed.
#ifdef clauses in arch/arm/mach-omap2/common-board-devices.h header file broke
kernel build when configured with CONFIG_TOUCHSCREEN_ADS7846 (XOR)
CONFIG_MTD_NAND_OMAP2
quick and dirty fix by using #ifdef clauses in the code file, too
---
arch/arm/mach-omap2/common-board-devices.c |7 +++
Hi Peter,
Peter Barada peter.bar...@gmail.com writes:
On 05/05/2011 02:16 PM, Kevin Hilman wrote:
In any case, you've found a real bug, and your patch is valid. However,
it doesn't currently apply to mainline, and it looks like it's because
your patch is using spaces and the code being
Commits 5e6a64b36ce346b7a2d481ef9fa315290eb28e5e (omap: move detection of
NAND CS to common-board-devices) and 96974a249b0cf3537f49115a59be67e2c54f315c
(omap: consolidate touch screen initialization among different boards)
break compilation when CONFIG_MTD_NAND_OMAP2 and
CONFIG_TOUCHSCREEN_ADS7846
On Fri, 6 May 2011, Jean Pihet wrote:
I checked the patch against the master branch of both Tony's and
Linus's trees, it applies and compiles OK.
Is that OK to you?
If it applies cleanly against Linus's current tree, then yes, that's fine.
- Paul
--
To unsubscribe from this list: send the
On Mon, 28 Mar 2011, G, Manjunath Kondaiah wrote:
Certain errata in OMAP2+ processors will require forcing
master standby to no standby mode before completing on going
operation. Without this, the results will be unpredictable.
Thanks, I've queued this one (provisionally) for 2.6.40, assuming
Hi
some comments
On Fri, 6 May 2011, Govindraj.R wrote:
Add API to enable IO pad wakeup capability based on mux dynamic pad and
wake_up enable flag available from hwmod_mux initialization.
Use the wakeup_enable flag and enable wakeup capability
for the given pads. Wakeup capability will
On Thu, 21 Apr 2011, Gulati, Shweta wrote:
Yes, but in current code clk_set_rate of dpll3_m2 -
'omap3_core_dpll_m2_set_rate'
doesn't update clk.rate, I will submit patch fixing that bug and will
make sure that
set_rate of all clocks should update clk.rate
Ping. Do you plan to post this
This is to inform you that your recent unsubscribe request was unsuccessful.
This is probably because we could find no current subscription in your name.
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo
56 matches
Mail list logo
