On Mon, 2010-02-08 at 07:25 +0100, ext Stephen Rothwell wrote:
Hi Tomi,
Today's linux-next merge of the omap_dss2 tree got a conflict in
arch/arm/mach-omap2/board-am3517evm.c between commit
13560d875d67c06239c82a6148c1b87075701fe9 (AM3517: Enable basic I2C
Support) from the omap tree and
Thanks Paul for your help.
Switch on the #define DEBUG in this both files skip almost all
kernel boot messages before this warning and gives just this: !?!
Uncompressing Linux done, booting the kernel.
lock: associated clk usbtll_ick to clkdm core_l4_clkdm
Clocking rate
Hi Tomi,
On Mon, 08 Feb 2010 11:29:06 +0200 Tomi Valkeinen tomi.valkei...@nokia.com
wrote:
P.S. Tomi, this omap_dss2 commit only has your Acked-by not Signed-off-by.
Hmm, do you mean there's something wrong with that, or jfyi? Aren't I,
as a subsys maintainer, supposed to ack the patches?
On Wed, Jan 13, 2010 at 12:16 PM, Vimal Singh vimal.neww...@gmail.com wrote:
From 4fbddd880c7a0da61fb66ae1d2c2553e3fbc82cb Mon Sep 17 00:00:00 2001
From: Vimal Singh vimalsi...@ti.com
Date: Tue, 12 Jan 2010 18:14:14 +0530
Subject: [PATCH] OMAP: NAND: support flashes on sdp boards
Reposting
On Fri, Feb 05, 2010 at 10:45:09PM +0200, Mike Rapoport wrote:
On Thu, Feb 4, 2010 at 6:21 PM, Mark Brown
The bodge I'm thinking of would do something like log an error and
substitute in a dummy regulator when regulator_get() would have failed
so that the driver sees behaviour equivalent
Hi,
On Mon, 2010-02-08 at 11:57 +0100, ext Stephen Rothwell wrote:
Hi Tomi,
On Mon, 08 Feb 2010 11:29:06 +0200 Tomi Valkeinen tomi.valkei...@nokia.com
wrote:
P.S. Tomi, this omap_dss2 commit only has your Acked-by not Signed-off-by.
Hmm, do you mean there's something wrong with
From 35da04834f4b0363e90a628bdb369318d80b7a6c Mon Sep 17 00:00:00 2001
From: Vimal Singh vimalsi...@ti.com
Date: Fri, 5 Feb 2010 05:56:18 +0530
Subject: [PATCH 1/3] Introducing 'gpmc-nand.c' for GPMC specific NAND init
Introducing 'gpmc-nand.c' for GPMC specific NAND init.
For example: GPMC
From e586d2fbbecc60bc66687c4e6d4798913bb33b7a Mon Sep 17 00:00:00 2001
From: Vimal Singh vimalsi...@ti.com
Date: Mon, 8 Feb 2010 05:02:45 +0530
Subject: [PATCH 2/3] OMAP: SDP: Introducing 'board-sdp-flash.c' for flash init
This patch adds 'board-sdp-flash.c', which could be utilized
by boards
From d3e5ee6d8a6449aee01fbc93313201a4674f5577 Mon Sep 17 00:00:00 2001
From: Vimal Singh vimalsi...@ti.com
Date: Mon, 8 Feb 2010 05:06:33 +0530
Subject: [PATCH 3/3] OMAP3: Add support for flash on 3430SDP board
This patch adds support for flashes on 3430SDP boards. All three
NAND, NOR and OneNAND
The platform data allocated with kmalloc() will become unreachable once
the init is complete, so it should be freed. The problem was discovered
by kmemleak.
Signed-off-by: Aaro Koskinen aaro.koski...@nokia.com
---
arch/arm/mach-omap2/hsmmc.c |7 ++-
1 files changed, 6 insertions(+), 1
diff --git a/arch/arm/mach-omap2/board-sdp-flash.c
b/arch/arm/mach-omap2/board-sdp-flash.c
new file mode 100644
index 000..54ef19f
--- /dev/null
+++ b/arch/arm/mach-omap2/board-sdp-flash.c
[snip]
+static void omap_set_vpp(struct map_info *map, int enable)
+{
+ static int
On Mon, Feb 8, 2010 at 7:22 PM, Ladislav Michl ladislav.mi...@seznam.cz wrote:
diff --git a/arch/arm/mach-omap2/board-sdp-flash.c
b/arch/arm/mach-omap2/board-sdp-flash.c
new file mode 100644
index 000..54ef19f
--- /dev/null
+++ b/arch/arm/mach-omap2/board-sdp-flash.c
[snip]
+static
In this version: (as per comments recieved for 2nd version)
- remove 'omap_set_vpp' function
- set 'set_vpp' to null
These changes do not have any impact on rest of the patches in series.
-vimal
From 6199d9c4db83dfd006f7cc2e74089ca1e9fdf8dc Mon Sep 17 00:00:00 2001
From: Vimal Singh
THis patch series has Clock changes related to OMAP3630. The major Clock
releated changes are
1. DPLL4 type has changed to j type.
2. Frequency Selection (FREQSEL) is no longer required for 3630
3. CLKSEL field width is increased for DPLL4 M2, M3, M4, M5 and M6
4. DPLL4 M2 o/p can be either
DPLL_FREQSEL field in CLKEN_PLL register is no longer valid for
OMAP3630. So remove
references to that.
Signed-off-by: Vishwanath BS vishwanath...@ti.com
---
arch/arm/mach-omap2/dpll3xxx.c | 11 +++
1 files changed, 7 insertions(+), 4 deletions(-)
diff --git
DPLL4 HS Divider (M2, M3, M4, M5 and M6) field width has been increased
by 1 bit in 3630. This patch has changes to accommodate this in CM
dynamically based on chip version.
Basically new clock nodes have been added for 3630 DPLL4 M2,M3,M4,M5 and
M6 and value of these nodes are used if cpu type is
In 3630, DPLL4M2 o/p can be 96MH or 192MHz (for SGX to run at 192). This
patch has changes to support this feature. 96MHz clock is generated by
dividing 192Mhz clock by 2 using CM_CLKSEL_CORE register.
SGX can select Core Clock, 192MHz clock or CM_96M_FCLK as it's
functional clock. In summary
DPLL4 for 3630 introduces a changed block called j type dpll, requiring
special divisor bits and additional reg fields. To allow for silicons to
use this, this is introduced as a flag and is enabled for 3630 silicon.
OMAP4 also has j type dpll for usb.
Tested with 3630 ZOOM3 and OMAP3430 ZOOM2
THis patch series has Clock changes related to OMAP3630. The major Clock
releated changes are
1. DPLL4 type has changed to j type.
2. Frequency Selection (FREQSEL) is no longer required for 3630
3. CLKSEL field width is increased for DPLL4 M2, M3, M4, M5 and M6
4. DPLL4 M2 o/p can be either
On Mon, Feb 08, 2010 at 06:38:57PM +0530, Vimal Singh wrote:
In this version: (as per comments recieved for 2nd version)
- remove 'omap_set_vpp' function
- set 'set_vpp' to null
Ah, I'm sorry for not being quite exact. leave set_vpp set to NULL means
there is no need to asign anything to that
On Mon, Feb 8, 2010 at 9:02 PM, Ladislav Michl ladislav.mi...@seznam.cz wrote:
On Mon, Feb 08, 2010 at 06:38:57PM +0530, Vimal Singh wrote:
In this version: (as per comments recieved for 2nd version)
- remove 'omap_set_vpp' function
- set 'set_vpp' to null
Ah, I'm sorry for not being quite
Sorry, mailer corrupted the last patch (line wrapped).
Here is the correct patch.
-
vimal
From f931fb85b774f97db3b0a25cde4a8154bb8d6dba Mon Sep 17 00:00:00 2001
From: Vimal Singh vimalsi...@ti.com
Date: Mon, 8 Feb 2010 05:02:45 +0530
Subject: [PATCH] OMAP: SDP: Introducing 'board-sdp-flash.c'
Here are some smallish patches for DSS2 for review. Some fixes, couple of new
ioctls, and DSI changes.
They can also be found from
http://gitorious.org/linux-omap-dss2/linux master branch
Aaro Koskinen (1):
OMAP: DSS: Taal: fix error returns in taal_probe()
Tomi Valkeinen (12):
OMAP: DSS2:
Previously the only place to get the size of the display was from the
DSS's sysfs interface, making, for example, configuring overlays and doing
updates on manual displays more difficult.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
drivers/video/omap2/omapfb/omapfb-ioctl.c | 20
Currently applications can reserve fb memory with OMAPFB_SETUP_MEM
ioctl, which takes the size in bytes as an argument. This falls apart
when using VRFB, as the memory need for VRFB is not trivial
This patch implements OMAPFB_RESERVE_BUFFER ioctl, which reserves memory
just like SETUP_MEM, but
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
drivers/video/omap2/omapfb/omapfb.h |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/video/omap2/omapfb/omapfb.h
b/drivers/video/omap2/omapfb/omapfb.h
index f7c9c73..4ae0b64 100644
---
It looks like on OMAP3 some DSS pins need VDDS_DSI to function properly.
This has not been confirmed from TI, but looking at figure 15-1 Display
subsystem highlight from the TRM, some data pins come near the DSI and SDI
blocks. This is not very hard evidence, but the fact remains that with the
The regulator is now enabled by DSS driver, and thus the panel driver
doesn't need to touch it.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/mach-omap2/board-3430sdp.c|4 --
.../video/omap2/displays/panel-sharp-ls037v7dw01.c | 35
Instead of configuring only VC0 to be usable, configure all four VCs
similarly. This is needed to utilize the other VCs.
Setting the FIFO sizes evenly for all VCs, regardless of how many VCs are
actually used, is not optimal. However, this affects only cases when
larger amounts of data are
From: Aaro Koskinen aaro.koski...@nokia.com
The workqueue creation error branch attempted to destroy a NULL wq,
and, in turn, a failed registration does not destroy the newly created
workqueue.
The problem was reported by a static analysis tool.
Signed-off-by: Aaro Koskinen
Rename and export dsi_vc_enable_hs() so that the display drivers can
control the mode of the DSI link.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h |2 ++
drivers/video/omap2/dss/dsi.c | 13 -
2 files changed,
Fix compilation of the CONFIG_OMAP2_DSS_COLLECT_IRQ_STATS feature.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
drivers/video/omap2/dss/core.c |4 +++-
drivers/video/omap2/dss/dispc.c |2 --
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git
Add helper functions for most common DCS read and write operations.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h |3 ++
drivers/video/omap2/dss/dsi.c | 30 +
2 files changed, 33 insertions(+), 0
Helper function to clean up the checking of the bus lock.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
drivers/video/omap2/dss/dsi.c | 13 +
1 files changed, 9 insertions(+), 4 deletions(-)
diff --git a/drivers/video/omap2/dss/dsi.c b/drivers/video/omap2/dss/dsi.c
dss_select_clk_source() was rather confusing. Selecting the source with
enums is much clearer.
The clk source selection is also stored into memory, so that we know what
is the selected source, even when clocks are off. This is important during
setup, as we need to what clocks to turn on before
It was not used.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
drivers/video/omap2/dss/dsi.c | 21 -
1 files changed, 0 insertions(+), 21 deletions(-)
diff --git a/drivers/video/omap2/dss/dsi.c b/drivers/video/omap2/dss/dsi.c
index 131bd53..4b85ed2 100644
---
Here are a bunch of patches that change the DSS2 driver's driver model a bit.
This change was triggered by trying to support new hardware, and realizing that
the current model just won't work.
Currently the omapdss driver is in control of most aspects of the DSS, and
omapdss calls necessary
Physical DSI bus is protected by a mutex. This patch changed the mutex to
a semaphore, so that we can lock and unlock the bus_lock from different
threads.
This is needed as the update process is started by user space program, and
thus the lock is acquired in that context, but the lock can be
Remove performance measurement for auto-update. Auto-update and thus
performance measurement cannot be supported after the driver change where
the control is moved to display drivers.
This is part of a larger patch-set, which moves the control from omapdss
driver to the display driver.
Move memory_read() from omap_dss_device to omap_dss_driver.
This is part of a larger patch-set, which moves the control from omapdss
driver to the display driver.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h |4 ---
Move get/set_rotate() from omap_dss_device to omap_dss_driver.
This is part of a larger patch-set, which moves the control from omapdss
driver to the display driver.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h |3 --
Move set/get_mirror() from omap_dss_device to omap_dss_driver.
This is part of a larger patch-set, which moves the control from omapdss
driver to the display driver.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h |3 ---
Move run_test() from omap_dss_device to omap_dss_driver.
This is part of a larger patch-set, which moves the control from omapdss
driver to the display driver.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h |1 -
Move enable/get_te() from omap_dss_device to omap_dss_driver.
This is part of a larger patch-set, which moves the control from omapdss
driver to the display driver.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h |5 +--
Move update() and sync() from omap_dss_device to omap_dss_driver.
This is part of a larger patch-set, which moves the control from omapdss
driver to the display driver.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h | 23 ++-
Move enable/disable_channel() from omap_dss_device to overlay manager.
This is part of a larger patch-set, which moves the control from omapdss
driver to the display driver.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h |3 +++
Move get_resolution() from omap_dss_device to omap_dss_driver.
This is part of a larger patch-set, which moves the control from omapdss
driver to the display driver.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h |7 +--
Move set/get_update_mode() from omap_dss_device to omap_dss_driver.
This is part of a larger patch-set, which moves the control from omapdss
driver to the display driver.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h |9 +-
Move enable/disable/suspend/resume from omap_dss_device to
omap_dss_driver.
This is part of a larger patch-set, which moves the control from omapdss
driver to the display driver.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h | 18
Move get_recommended_bpp() from omap_dss_device to omap_dss_driver.
This is part of a larger patch-set, which moves the control from omapdss
driver to the display driver.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h |7 ++---
Move check/set/get_timings() from omap_dss_device to omap_dss_driver.
This is part of a larger patch-set, which moves the control from omapdss
driver to the display driver.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h | 18 ---
Update was hardcoded to use virtual channel 0. This patch adds a parameter
that specifies the VC.
Signed-off-by: Tomi Valkeinen tomi.valkei...@nokia.com
---
arch/arm/plat-omap/include/plat/display.h |1 +
drivers/video/omap2/dss/dsi.c | 13 +
2 files changed, 10
In OMAP3 Some modules like Smartreflex do not have the regular sysconfig
register.Instead clockactivity bits are part of another register at a
different bit position than the usual bit positions 8 and 9.
In OMAP4, a new scheme is available due to the new protocol
between the PRCM and the IPs.
Hi Paul,
On Sat, 06-Feb-10 1:46 AM +0530, Paul Walmsley wrote:
Hi Ranjith,
On Tue, 19 Jan 2010, Ranjith Lohithakshan wrote:
Current implementation defines clock idle state indicators based on the
cpu information (cpu_is_omap24xx() or cpu_is_omap34xx()) in a system wide
manner. This patch
Hi Paul,
On Sat, 06-Feb-10 1:49 AM +0530, Paul Walmsley wrote:
On Thu, 28 Jan 2010, Ranjith Lohithakshan wrote:
This patch adds clock support for the following AM35xx modules
- Ethernet MAC
- CAN Controller (HECC)
- New MUSB OTG Controller with integrated Phy
- Video
Hi Ranjith,
On Mon, 8 Feb 2010, Ranjith Lohithakshan wrote:
On Sat, 06-Feb-10 1:46 AM +0530, Paul Walmsley wrote:
I had to make some changes to this patch for it to apply after the recent
clock split patches. Could you please check this patch and make sure it
is okay?
It looks good
On Mon, 8 Feb 2010, Ranjith Lohithakshan wrote:
You could queue this up now. I have verified the previous one. Thanks
for your help.
OK, queued for 2.6.34.
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More
Vishwa,
some more comments on this patch are below -- all of which should be
easily fixable:
On Mon, 8 Feb 2010, Vishwanath BS wrote:
DPLL4 for 3630 introduces a changed block called j type dpll, requiring
special divisor bits and additional reg fields. To allow for silicons to
use this,
On Mon, 8 Feb 2010, Vishwanath BS wrote:
DPLL_FREQSEL field in CLKEN_PLL register is no longer valid for
OMAP3630. So remove
references to that.
Signed-off-by: Vishwanath BS vishwanath...@ti.com
Thanks, queued for 2.6.34.
- Paul
--
To unsubscribe from this list: send the line unsubscribe
Hi Vishwanath,
On Mon, 8 Feb 2010, Vishwanath BS wrote:
DPLL4 HS Divider (M2, M3, M4, M5 and M6) field width has been increased
by 1 bit in 3630. This patch has changes to accommodate this in CM
dynamically based on chip version.
Basically new clock nodes have been added for 3630 DPLL4
On Mon, 8 Feb 2010, Vishwanath BS wrote:
In 3630, DPLL4M2 o/p can be 96MH or 192MHz (for SGX to run at 192). This
patch has changes to support this feature. 96MHz clock is generated by
dividing 192Mhz clock by 2 using CM_CLKSEL_CORE register.
SGX can select Core Clock, 192MHz clock or
Hi Thara,
I went ahead and queued this patch, but some minor changes were necessary;
please note them for your future patches.
The revised patch is included at the end of the message.
On Mon, 8 Feb 2010, Thara Gopinath wrote:
diff --git a/arch/arm/mach-omap2/omap_hwmod.c
Also, the:
#include linux/list.h
has been moved from omap_hwmod_common_data.c to plat/omap_hwmod.h. This
is because omap_hwmod_common_data.c does not need this header file at all,
but plat/omap_hwmod.h does.
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
Background: bridge_close() has the responsibility to cleanup all the
resources allocated by user space process. One of those resources is
DMMRes which is used for tracking DMM resource allocation done in
PROC_Map() and PROC_UnMap().
DRV_ProcFreeDMMRes() function was used for cleaning up DMMRes
From 07880b3410ad19962d16ce1415f0423dfeed17da Mon Sep 17 00:00:00 2001
From: Fernando Guzman Lugo x0095...@ti.com
Date: Fri, 5 Feb 2010 01:35:35 -0600
Subject: [PATCH] DSPBRIDGE: Replace page_address with kmap
Replace page_address with kmap to get address in case of high mem allocation.
From 727c83cd8b7e4aca51b214412eaa1b95cde6e4ea Mon Sep 17 00:00:00 2001
From: Fernando Guzman Lugo x0095...@ti.com
Date: Tue, 2 Feb 2010 20:38:10 -0600
Subject: [PATCH] DSPBRIDGE: Reclaim all pending buffer on resource cleanup
Before in case of pending buffer while we try to close
a stream, it was
On 2/4/2010 9:33 AM, Ameya Palande wrote:
kmemleak offeres the same functionality as custom MEM_CHECK
mechanism, so get rid of MEM_CHECK.
Signed-off-by: Ameya Palandeameya.pala...@nokia.com
---
drivers/dsp/bridge/services/mem.c | 212 +
1 files changed, 2
On 2/6/2010 9:16 AM, ameya.pala...@nokia.com wrote:
[...]
If no objection I'll be pushing tomorrow.
No problem :)
Pushed to dspbridge
- omar
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On 2/4/2010 9:33 AM, Ameya Palande wrote:
vfree() is NULL safe so MEM_VFree() doesn't provide any significant
advantage. By getting rid of MEM_VFree() and the NULL pointer check
associated with it, we can save on:
1. One level of indirection which translates to a function call cost.
2. NULL
This patch adds support in omap device layer to register devices
as early platform devices. Certain devices needed during system boot up
like timers, gpio etc can be registered as early devices. This will
allow for them to be probed very early on during system boot up.
This patch adds a parameter
On Tue, 9 Feb 2010, Thara Gopinath wrote:
This patch adds support in omap device layer to register devices
as early platform devices. Certain devices needed during system boot up
like timers, gpio etc can be registered as early devices. This will
allow for them to be probed very early on
-Original Message-
From: Gomez Castellanos, Ivan
Sent: Monday, February 08, 2010 11:42 PM
To: linux-omap@vger.kernel.org
Cc: ameya.pala...@nokia.com; hiroshi.d...@nokia.com;
felipe.contre...@nokia.com; Menon, Nishanth
Subject: [PATCH] DSPBRIDGE: Check pointers before they are
72 matches
Mail list logo
