This patch adds the check for whether a omap_device and in turn
platform_device and device pointers exist for the device before
adding it's opp table into the global table. This is because all
the later accesses to the opp entries are based on dev pointer and
hence there is no point in adding a
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of
Gopinath, Thara
Sent: Thursday, July 15, 2010 10:56 AM
To: Paul Walmsley; linux-omap@vger.kernel.org;
linux-arm-ker...@lists.infradead.org
Cc: Kevin Hilman
Subject: RE:
Good to see this driver on list.
Few comments.
-Original Message-
From: Sin, David
Sent: Saturday, July 24, 2010 4:52 AM
To: linux-arm-ker...@lists.arm.linux.org.uk; linux-omap@vger.kernel.org;
Tony Lindgren; Russell King
Cc: Kanigeri, Hari; Ohad Ben-Cohen; Hiremath, Vaibhav;
-Original Message-
From: Sin, David
Sent: Saturday, July 24, 2010 4:52 AM
To: linux-arm-ker...@lists.arm.linux.org.uk; linux-omap@vger.kernel.org;
Tony Lindgren; Russell King
Cc: Kanigeri, Hari; Ohad Ben-Cohen; Hiremath, Vaibhav; Shilimkar, Santosh;
Molnar, Lajos; Sin, David;
-Original Message-
From: Sin, David
Sent: Saturday, July 24, 2010 4:52 AM
To: linux-arm-ker...@lists.arm.linux.org.uk; linux-omap@vger.kernel.org;
Tony Lindgren; Russell King
Cc: Kanigeri, Hari; Ohad Ben-Cohen; Hiremath, Vaibhav; Shilimkar, Santosh;
Ramachandra, Ravikiran; Molnar,
-Original Message-
From: Sin, David
Sent: Saturday, July 24, 2010 4:52 AM
To: linux-arm-ker...@lists.arm.linux.org.uk; linux-omap@vger.kernel.org;
Tony Lindgren; Russell King
Cc: Kanigeri, Hari; Ohad Ben-Cohen; Hiremath, Vaibhav; Shilimkar, Santosh;
Molnar, Lajos; Sin, David
-Original Message-
From: Sin, David
Sent: Saturday, July 24, 2010 4:52 AM
To: linux-arm-ker...@lists.arm.linux.org.uk; linux-omap@vger.kernel.org;
Tony Lindgren; Russell King
Cc: Kanigeri, Hari; Ohad Ben-Cohen; Hiremath, Vaibhav; Shilimkar, Santosh;
Molnar, Lajos; Sin, David
David,
-Original Message-
From: Sin, David
Sent: Saturday, July 24, 2010 4:52 AM
To: linux-arm-ker...@lists.arm.linux.org.uk; linux-omap@vger.kernel.org;
Tony Lindgren; Russell King
Cc: Kanigeri, Hari; Ohad Ben-Cohen; Hiremath, Vaibhav; Shilimkar, Santosh;
Sin, David
Subject: [RFC
On Fri, Jul 23, 2010 at 06:22:27PM -0500, David Sin wrote:
+struct platform_driver tiler_driver_ldm = {
+ .driver = {
+ .owner = THIS_MODULE,
+ .name = tiler,
+ },
+ .probe = NULL,
+ .shutdown = NULL,
+ .remove = NULL,
+};
What's the purpose of
On Fri, Jul 23, 2010 at 06:22:24PM -0500, David Sin wrote:
+/* allocate and flush a page */
+static struct mem *alloc_mem(void)
+{
+ struct mem *m = kzalloc(sizeof(*m), GFP_KERNEL);
+ if (!m)
+ return NULL;
+
+ m-pg = alloc_page(GFP_KERNEL | GFP_DMA);
+ if
On Fri, Jul 23, 2010 at 06:22:21PM -0500, David Sin wrote:
+static struct platform_driver dmm_driver_ldm = {
+ .driver = {
+ .owner = THIS_MODULE,
+ .name = dmm,
+ },
+ .probe = NULL,
+ .shutdown = NULL,
+ .remove = NULL,
+};
What's the point
On Fri, Jul 23, 2010 at 10:15:35PM +0100, Russell King - ARM Linux wrote:
On Fri, Jul 23, 2010 at 09:58:29PM +0200, Uwe Kleine-König wrote:
omapfb_reserve_sdram() is only called by omap1_map_common_io() and
_omap2_map_common_io() that both live in .init.text. So this is save
for
This is what I'd expect to see. This uses a hardware-upwards registration
scheme, so by registering a 'dmm' device, when the driver for 'dmm' gets
registered, it automatically registers with the next level up.
However, you should think carefully about this kind of layered approach.
Would it be
Hi David,
On Saturday 24 July 2010 01:22:20 David Sin wrote:
TILER is a hardware block made by Texas Instruments. Its purpose is to
organize video/image memory in a 2-dimensional fashion to limit memory
bandwidth and facilitate 0 effort rotation and mirroring. The TILER
driver
+s32 tiler_mmap_blk(struct tiler_block_t *blk, u32 offs, u32 size,
+ struct vm_area_struct *vma, u32 voffs)
+{
+ u32 v, p, len;
+
+ /* don't allow mremap */
+ vma-vm_flags |= VM_DONTEXPAND | VM_RESERVED;
Should we add VM_LOCKED as well considering
-Original Message-
From: Hari Kanigeri [mailto:hari.kanig...@gmail.com]
Sent: Saturday, July 24, 2010 7:12 PM
To: Shilimkar, Santosh
Cc: Sin, David; linux-arm-ker...@lists.arm.linux.org.uk; linux-
o...@vger.kernel.org; Tony Lindgren; Russell King; Kanigeri, Hari; Ohad
Ben-Cohen;
Hi Santosh,
On 7/20/2010 4:12 PM, Kanigeri, Hari wrote:
Santosh,
Hari Kanigeri (1):
omap:hwspinlocks-ensure the order of registration
Simon Que (4):
omap:hwmod-hwspinlock-enable
omap:hwspinlock-define HWSPINLOCK base address
I think you should fold patch 1/5 , 2/5 into patch 3/5.
-Original Message-
From: Cousson, Benoit
Sent: Saturday, July 24, 2010 8:35 PM
To: Kanigeri, Hari
Cc: Shilimkar, Santosh; Linux Omap; Tony Lindgren; Que, Simon
Subject: Re: [PATCH 0/5] omap:hwspinlock support-omap4
Hi Santosh,
On 7/20/2010 4:12 PM, Kanigeri, Hari wrote:
On 7/24/2010 5:35 PM, Shilimkar, Santosh wrote:
From: Cousson, Benoit
Sent: Saturday, July 24, 2010 8:35 PM
Hi Santosh,
On 7/20/2010 4:12 PM, Kanigeri, Hari wrote:
Santosh,
Hari Kanigeri (1):
omap:hwspinlocks-ensure the order of registration
Simon Que (4):
Hi Simon and Hari,
On 7/19/2010 6:50 PM, Kanigeri, Hari wrote:
From: Simon Ques...@ti.com
Created driver for OMAP hardware spinlock. This driver supports:
- Reserved spinlocks for internal use
- Dynamic allocation of unreserved locks
- Lock, unlock, and trylock functions, with or without
20 matches
Mail list logo
