* Nishanth Menon n...@ti.com [100708 22:31]:
I think this 'lazy reviewability' comes at the cost of very
abstraction the features framework is intended to provide, not to
mention the question of correct selection (is this a OMAP4 specific
feature or is OMAP5 expected to have it ?). and
* Nishanth Menon n...@ti.com [100708 17:46]:
Tony Lindgren had written, on 07/08/2010 04:37 AM, the following:
@@ -112,6 +114,12 @@ void omap_get_die_id(struct omap_die_id *odi)
odi-id_3 = read_tap_reg(OMAP_TAP_DIE_ID_3);
}
+u32 omap2_has_feature(u32 feat_mask)
+{
+/* REVISIT:
* Mathias Nyman mathias.ny...@nokia.com [100708 16:59]:
From: Mathias Nyman mathias.ny...@nokia.com
This will enable usage of tsl2563 ambient light sensor on Nokia N900.
Signed-off-by: Ameya Palande ameya.pala...@nokia.com
Is this your patch or Ameya's patch originally?
Looks like your
The following set of patches applies on top of for-next branch.
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git
Patches verified on: omap3430-SDP, omap3630-sdp, zoom3 and beagle board
And these are the patches required to address the following input -
1.
Board file modified for not to provide gpmc phys_base address to nand driver.
The gpmc_nand_init funciton is now used to detect the nand and required to
adopt _prob function as in nand/omap2.c
Signed-off-by: Sukumar Ghorai s-gho...@ti.com
---
arch/arm/mach-omap2/board-cm-t35.c | 20
This patch removes direct reference of gpmc address from generic nand platform
code.
Nand platform code now uses wrapper functions which are implemented in gpmc
module.
Signed-off-by: Sukumar Ghorai s-gho...@ti.com
---
arch/arm/mach-omap2/gpmc-nand.c| 38 ++
few functions added in gpmc module and to be used by other drivers like NAND.
Signed-off-by: Sukumar Ghorai s-gho...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 276 ++--
arch/arm/plat-omap/include/plat/gpmc.h | 39 -
drivers/mtd/nand/omap2.c
* Gadiyar, Anand gadi...@ti.com [100708 20:31]:
Tony Lindgren wrote:
Hi all,
FYI, I'll be mostly offline after Friday for several weeks.
I'll post few more patchsets for review, but will not be merging
any other omap code after that for the upcoming merge window.
Cheers,
Add a missing break at end of switch statement. At the moment it is a
fall through to WARN_ON(1) and return -EEXIST.
Signed-off-by: Thomas Weber we...@corscience.de
---
arch/arm/mach-omap2/powerdomain.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
From: Mathias Nyman mathias.ny...@nokia.com
This will enable usage of tsl2563 ambient light sensor on Nokia N900.
Signed-off-by: Ameya Palande ameya.pala...@nokia.com
Signed-off-by: Mathias Nyman mathias.ny...@nokia.com
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 14 ++
1
Hi Ohad,
On 07/08/2010 11:10 PM, ext Ohad Ben-Cohen wrote:
Hi Nicolas and Roger,
On Tue, Jul 6, 2010 at 8:42 PM, Nicolas Pitren...@fluxnic.net wrote:
On Tue, 6 Jul 2010, Roger Quadros wrote:
If the Power enable GPIO can be treated as SDIO slot supply (i.e. vmmc), then
the SDIO/MMC core
* Ajay Kumar Gupta ajay.gu...@ti.com [100708 13:59]:
From: Anand Gadiyar gadi...@ti.com
This pin-muxing is best done in the board files. The driver should
not do this explicitly.
Also, this code causes a warning to be thrown when OMAP2430 and OMAP3/4
support are enabled in the same
Removed include files from usb-musb.c which were not required.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
arch/arm/mach-omap2/usb-musb.c |7 ---
1 files changed, 0 insertions(+), 7 deletions(-)
diff --git a/arch/arm/mach-omap2/usb-musb.c b/arch/arm/mach-omap2/usb-musb.c
index
Removed unneeded 'power' and 'mode' field from musb_config as
they are now getting updated by the values provided from board
files at usb_musb_init().
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
arch/arm/mach-omap2/usb-musb.c | 13 -
1 files changed, 0 insertions(+), 13
* Sukumar Ghorai s-gho...@ti.com [100709 10:19]:
The following set of patches applies on top of for-next branch.
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git
Patches verified on: omap3430-SDP, omap3630-sdp, zoom3 and beagle board
And these are the
Hi Roger,
On Fri, Jul 9, 2010 at 11:12 AM, Roger Quadros roger.quad...@nokia.com wrote:
You are already
creating a new platform device for wl1271_sdio just to pass platform_data
With the new approach, I can remove this platform device altogether,
and completely rely on the sdio function device
* Ameya Palande ameya.pala...@nokia.com [100708 15:55]:
Hi Tony,
On Wed, 2010-07-07 at 11:44 +0200, ext Tony Lindgren wrote:
From: Ameya Palande ameya.pala...@nokia.com
This commit will enable usage of tsl2563 ambient light sensor on Nokia N900.
Signed-off-by: Ameya Palande
The following set of patches applies on top of for-next branch.
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git
Patches verified on: omap3430-SDP, omap3630-sdp, zoom3 and beagle board
And these are the patches required to address the following input -
1.
Board file modified for not to provide gpmc phys_base address to nand driver.
The gpmc_nand_init funciton is now used to detect the nand and required to
adopt _prob function as in nand/omap2.c
Signed-off-by: Sukumar Ghorai s-gho...@ti.com
---
arch/arm/mach-omap2/board-cm-t35.c | 20
few functions added in gpmc module and to be used by other drivers like NAND.
Signed-off-by: Sukumar Ghorai s-gho...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 276 ++--
arch/arm/plat-omap/include/plat/gpmc.h | 39 -
drivers/mtd/nand/omap2.c
This patch removes direct reference of gpmc address from generic nand platform
code.
Nand platform code now uses wrapper functions which are implemented in gpmc
module.
Signed-off-by: Sukumar Ghorai s-gho...@ti.com
---
arch/arm/mach-omap2/gpmc-nand.c| 38 ++
On Fri, Jul 9, 2010 at 11:32 AM, Ohad Ben-Cohen o...@wizery.com wrote:
Hi Roger,
On Fri, Jul 9, 2010 at 11:12 AM, Roger Quadros roger.quad...@nokia.com
wrote:
You are already
creating a new platform device for wl1271_sdio just to pass platform_data
With the new approach, I can remove this
Tony,
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Friday, July 09, 2010 2:03 PM
To: Ghorai, Sukumar
Cc: linux-omap@vger.kernel.org; linux-...@lists.infradead.org
Subject: Re: [PATCH v6 0/3] omap3 nand: cleanup exiting platform related
code
* Sukumar
On Fri, 2010-06-25 at 16:46 -0500, Nishanth Menon wrote:
Add unlikely checks to better optimize the rare occurrance of
erroneous conditions.
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Thara Gopinath th...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
unlikely and friends make
From: Artem Bityutskiy artem.bityuts...@nokia.com
This patch fixes the following problem indicated by kmemleak:
kmemleak: unreferenced object 0xdf93c280 (size 64):
kmemleak: backtrace:
kmemleak: [c00df6d4] create_object+0x104/0x200
kmemleak: [c00d7638] kmem_cache_alloc+0xe4/0xf4
From: Artem Bityutskiy artem.bityuts...@nokia.com
Do not forget to check the 'platform_device_add_data()' error code
in 'omap_device_build_ss()'.
Signed-off-by: Artem Bityutskiy artem.bityuts...@nokia.com
---
arch/arm/plat-omap/omap_device.c |4 +++-
1 files changed, 3 insertions(+), 1
On Fri, 2010-07-09 at 16:20 +0300, Artem Bityutskiy wrote:
From: Artem Bityutskiy artem.bityuts...@nokia.com
This patch fixes the following problem indicated by kmemleak:
kmemleak: unreferenced object 0xdf93c280 (size 64):
kmemleak: backtrace:
kmemleak: [c00df6d4]
Artem Bityutskiy had written, on 07/09/2010 08:12 AM, the following:
On Fri, 2010-06-25 at 16:46 -0500, Nishanth Menon wrote:
Add unlikely checks to better optimize the rare occurrance of
erroneous conditions.
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Thara Gopinath th...@ti.com
On Fri, 2010-07-09 at 08:40 -0500, Nishanth Menon wrote:
Artem Bityutskiy had written, on 07/09/2010 08:12 AM, the following:
On Fri, 2010-06-25 at 16:46 -0500, Nishanth Menon wrote:
Add unlikely checks to better optimize the rare occurrance of
erroneous conditions.
Cc: Kevin Hilman
Artem Bityutskiy had written, on 07/09/2010 09:15 AM, the following:
On Fri, 2010-07-09 at 08:40 -0500, Nishanth Menon wrote:
Artem Bityutskiy had written, on 07/09/2010 08:12 AM, the following:
On Fri, 2010-06-25 at 16:46 -0500, Nishanth Menon wrote:
Add unlikely checks to better optimize
The following set of patches applies on top of for-next branch.
And these are the patches required to enable nand (nor and onenand for sdp
only) for different platform.
v4: patch rebase on latest code base; depend on
This patch adds NAND support to ZOOM2 board.
Signed-off-by: Sukumar Ghorai s-gho...@ti.com
Signed-off-by: Vimal Singh vimalsi...@ti.com
---
arch/arm/mach-omap2/Makefile |1 +
arch/arm/mach-omap2/board-zoom2.c | 43 +
patch adds NAND support to zoom3 board.
Signed-off-by: Sukumar Ghorai s-gho...@ti.com
Signed-off-by: Vimal Singh vimalsi...@ti.com
---
arch/arm/mach-omap2/Makefile |1 +
arch/arm/mach-omap2/board-zoom3.c | 43 +
2 files changed, 44 insertions(+), 0
patch adds NAND support to LDP board.
Signed-off-by: Vimal Singh vimalsi...@ti.com
Signed-off-by: Sukumar Ghorai s-gho...@ti.com
---
arch/arm/mach-omap2/Makefile|1 +
arch/arm/mach-omap2/board-ldp.c | 35 +++
2 files changed, 36 insertions(+), 0
add support for NAND, OneNAND, NOR on omap 3630-sdp board.
Signed-off-by: Sukumar Ghorai s-gho...@ti.com
---
arch/arm/mach-omap2/Makefile|1 +
arch/arm/mach-omap2/board-3630sdp.c | 120 +++
2 files changed, 121 insertions(+), 0 deletions(-)
diff
rename board-sdp-flash.c(board-flash.c) and board-sdp.h(board-flash.h) to
used by other board e.g. zoom
Signed-off-by: Sukumar Ghorai s-gho...@ti.com
---
arch/arm/mach-omap2/Makefile |2 +-
arch/arm/mach-omap2/board-3430sdp.c| 16 +++-
On Wed, Jul 07, 2010 at 01:52:14PM +0300, Tony Lindgren wrote:
Hi Russell,
Is your lmb branch going to stay static?
Not at the moment, I'm still tweaking things in there, and the main
lmb conversion commit needs a better description... I think there's
also a few bits missing from the
Artem Bityutskiy had written, on 07/09/2010 08:20 AM, the following:
From: Artem Bityutskiy artem.bityuts...@nokia.com
Do not forget to check the 'platform_device_add_data()' error code
in 'omap_device_build_ss()'.
Signed-off-by: Artem Bityutskiy artem.bityuts...@nokia.com
Acked-by: Nishanth
From: Artem Bityutskiy artem.bityuts...@nokia.com
This patch fixes the following problem indicated by kmemleak:
kmemleak: unreferenced object 0xdf93c280 (size 64):
kmemleak: backtrace:
kmemleak: [c00df6d4] create_object+0x104/0x200
kmemleak: [c00d7638] kmem_cache_alloc+0xe4/0xf4
On Fri, 2010-07-09 at 20:35 +0530, Gopinath, Thara wrote:
-Original Message-
From: Artem Bityutskiy [mailto:dedeki...@gmail.com]
Sent: Friday, July 09, 2010 6:50 PM
To: linux-omap@vger.kernel.org
Cc: Menon, Nishanth; Kevin Hilman; Gopinath, Thara; Peter p2 De Schrijver
Subject:
Artem Bityutskiy had written, on 07/09/2010 10:44 AM, the following:
On Fri, 2010-07-09 at 20:35 +0530, Gopinath, Thara wrote:
-Original Message-
From: Artem Bityutskiy [mailto:dedeki...@gmail.com]
Sent: Friday, July 09, 2010 6:50 PM
To: linux-omap@vger.kernel.org
Cc: Menon, Nishanth;
On Fri, 2010-07-09 at 10:51 -0500, Nishanth Menon wrote:
So the logic is:
1. The subject line is a short description which gives the idea what the
commit is about. So, my subject line says:
1.1. It is about omap3 (which is true)
1.2. It is about sr (which is true)
I think Thara's
-Original Message-
From: Artem Bityutskiy [mailto:dedeki...@gmail.com]
Sent: Friday, July 09, 2010 10:51 AM
On Fri, 2010-07-09 at 10:51 -0500, Nishanth Menon wrote:
So the logic is:
1. The subject line is a short description which gives the idea what
the
commit is about.
On Fri, 2010-07-09 at 11:00 -0500, Menon, Nishanth wrote:
-Original Message-
From: Artem Bityutskiy [mailto:dedeki...@gmail.com]
Sent: Friday, July 09, 2010 10:51 AM
On Fri, 2010-07-09 at 10:51 -0500, Nishanth Menon wrote:
So the logic is:
1. The subject line is a
Tony Lindgren had written, on 07/09/2010 02:08 AM, the following:
* Nishanth Menon n...@ti.com [100708 17:46]:
Tony Lindgren had written, on 07/08/2010 04:37 AM, the following:
@@ -112,6 +114,12 @@ void omap_get_die_id(struct omap_die_id *odi)
odi-id_3 =
Tony Lindgren had written, on 07/09/2010 02:04 AM, the following:
* Nishanth Menon n...@ti.com [100708 22:31]:
I think this 'lazy reviewability' comes at the cost of very
abstraction the features framework is intended to provide, not to
mention the question of correct selection (is this a
On Fri, Jul 09, 2010 at 11:15:33AM +0300, Tony Lindgren wrote:
* Ajay Kumar Gupta ajay.gu...@ti.com [100708 13:59]:
From: Anand Gadiyar gadi...@ti.com
This pin-muxing is best done in the board files. The driver should
not do this explicitly.
Also, this code causes a warning to be
Hi!
So for people who really care about running a mainline kernel on their
android device doing that part first on a generic ARM board in qemu
might be much better first step work.
On the other hand I've heard
that various hardware vendors or parties closed to them are rather
On Tue, May 25, 2010 at 8:54 AM, Mickael Chazaux
mickael.chaz...@gmail.com wrote:
Hi,
I am working on adding the support of an omap3 based board in the
kernel. This board uses an ADS7843 touchscreen controller, on the SPI
bus. The in-kernel driver (drivers/input/touchscreen/ads7646.c) works
This patch fix a compilation error in uuid_hex_to_bin
due to the patch simplify and clean up
Signed-off-by: Rene Sapiens rene.sapi...@ti.com
---
drivers/staging/tidspbridge/gen/uuidutil.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
mode change 100644 = 100755
Add revision detection for ES1.1 and ES1.2. Set default
revision as ES1.2.
Add CHIP_GE_OMAP3630ES1_1 to detect revisions 1.1 and later.
This is needed for at least one feature that is broken in
3630ES1.0 but exists on older (3430 ES3.1) and newer revisions.
Additionally, update some of the
USBTLL Save-and-Restore is broken in 3630 ES1.0. Having it
enabled could result in incorrect register restores as
the OMAP exits off-mode. This could potentially result in
unexpected wakeup events.
This is fixed in ES1.1. So disable it for ES1.0s.
Signed-off-by: Anand Gadiyar gadi...@ti.com
Cc:
On Sat, Jul 10, 2010 at 1:48 AM, Rene Sapiens rene.sapi...@ti.com wrote:
This patch fix a compilation error in uuid_hex_to_bin
due to the patch simplify and clean up
Signed-off-by: Rene Sapiens rene.sapi...@ti.com
Oh, previous version of patch was sent. Thanks for fix.
ACK.
---
The intention of this patch is to rename the remaining variables with camel
case. Variables will be renamed avoiding camel case and Hungarian notation.
The words to be renamed in this patch are:
dspAddr to dsp_address
dspAdr to dsp_adr
dspBaseVirt to
The intention of this patch is to rename the remaining variables with camel
case. Variables will be renamed avoiding camel case and Hungarian notation.
The words to be renamed in this patch are:
phDevContext to device_ctx
phDevNode to dev_nde
phDevObject to
The intention of this patch is to rename the remaining variables with camel
case. Variables will be renamed avoiding camel case and Hungarian notation.
The words to be renamed in this patch are:
ulBrdState to brd_state
ulChnl to chnl
ulDspAddr to dsp_add
The intention of this patch is to rename the remaining variables with camel
case. Variables will be renamed avoiding camel case and Hungarian notation.
The words to be renamed in this patch are:
pPhysAddr to phys_addr
pPhysicalAddress to physical_address
The intention of this patch is to rename the remaining variables with camel
case. Variables will be renamed avoiding camel case and Hungarian notation.
The words to be renamed in this patch are:
puLen to len
pulEntry to entry_pt
pulFxnAddr to fxn_addr
pulId
The intention of this patch is to rename the remaining variables with camel
case. Variables will be renamed avoiding camel case and Hungarian notation.
The words to be renamed in this patch are:
segmentId to segmnt_id
SetPageDirty to set_page_dirty
This patch renames the variables in the parameter lists and in the function
definitions to make them match.
Signed-off-by: Rene Sapiens rene.sapi...@ti.com
---
drivers/staging/tidspbridge/core/chnl_sm.c |2 +-
drivers/staging/tidspbridge/core/io_sm.c | 20 +++---
The intention of this patch is to rename the remaining variables with camel
case. Variables will be renamed avoiding camel case and Hungarian notation.
The words to be renamed in this patch are:
pMemStatBuf to mem_stat_buf
pMgrAttrs to mgr_attrts
pMgrInfo
The intention of this patch is to rename the remaining variables with camel
case. Variables will be renamed avoiding camel case and Hungarian notation.
The words to be renamed in this patch are:
pdwSize to buff_size
pdwState to board_state
pdwValue to value
The intention of this patch is to rename the remaining variables with camel
case. Variables will be renamed avoiding camel case and Hungarian notation.
The words to be renamed in this patch are:
pstrFxn to str_fxn
pstrLibName to str_lib_name
pstrSect to
The intention of this patch is to rename the remaining variables with camel
case. Variables will be renamed avoiding camel case and Hungarian notation.
The words to be renamed in this patch are:
validBit to valid_bit
victimEntryNum to victim_entry_num
The intention of this serie of patches is to rename the remaining variables
with camel case. Words will be renamed avoiding CamelCase and Hungarian
notation. Also the variables in the prototypes will be renamed to make them
match with the ones in the function definitions.
The variables to be
The intention of this patch is to rename the remaining variables with camel
case. Variables will be renamed avoiding camel case and Hungarian notation.
The words to be renamed in this patch are:
pArb to arb
pbAlreadyAttached to already_attached
pBaseAddr to
66 matches
Mail list logo
