Re: [PATCH 07/10 V3] omap3: clk: use pm accessor functions for cpufreq table

Little comment bellow, On Wed, Nov 25, 2009 at 05:09:16AM +0100, ext Nishanth Menon wrote: > omap2_clk_init_cpufreq_table currently directly accesses the opp > table, making it unscalable to various OMAPs. Instead use the > accessor functions to populate the cpufreq table > > Cc: Benoit Cousson

Re: [PATCH 09/10 V3] omap3: pm: introduce 3630 opps

Hello Nishanth, Few comments bellow. On Wed, Nov 25, 2009 at 05:09:18AM +0100, ext Nishanth Menon wrote: > Introduce the OMAP3630 OPPs including the defined OPP tuples. > > Further information on OMAP3630 can be found here: > http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateI

Re: [RFC][RFT][PATCH 3/4 v5b] OMAP: McBSP: Introduce caching in register write operations

Hi, sorry not commenting for few days. On Mon, 7 Dec 2009 13:06:31 -0800 Tony Lindgren wrote: > > For me, the fact that more than one processor type can be configured side > > by > > side it not enough reason here. With your code, if more then one processor > > type is configured, twice or tr

Re: [RESUBMIT][PATCH-v2][RFC] OMAP4: I2C Support for OMAP4430

> > Thu, 20 Aug 2009 14:19:04 -0700 > > On Tue, Aug 18, 2009 at 03:35:31PM +0530, Syed Rafiuddin wrote: > > Ben, > > > > > On Fri, Jul 24, 2009 at 04:40:02PM +0530, Syed Rafiuddin wrote: > > >> Hi Ben, > > >> > > >> > This patch adds OMAP4 support to the I2C driver. All I2C register > > >> > addres

Re: [PATCH 2/8] Board file of Always Innovating OMAP3-based Touch Book

* Tim Yamin [091207 14:10]: > 2009/12/7 Tony Lindgren : > >> One more thing just came in my mind, have you thought of using standard > >> backlight class driver??? > > > > I'll add this without the backlight code so we get the basic > > support into mainline while using the backlight class driver

[APPLIED] [PATCH] arch/arm/plat-omap/devices.c - sort alphabetically

This patch has been applied to the linux-omap by youw fwiendly patch wobot. Branch in linux-omap: for-next-vol2 Initial commit ID (Likely to change): 6d6789d0a5b94d627f10d954490f8e2484a47f4c PatchWorks http://patchwork.kernel.org/patch/65171/ Git (Likely to change, and takes a while to get mirr

[APPLIED] [PATCH] [OMAP] I2C mux and clocks for omap7xx

This patch has been applied to the linux-omap by youw fwiendly patch wobot. Branch in linux-omap: for-next-vol2 Initial commit ID (Likely to change): dca06476d0535c299fa87fa5737cf4c07f60 PatchWorks http://patchwork.kernel.org/patch/65105/ Git (Likely to change, and takes a while to get mirr

[APPLIED] [PATCH v3] omap: serial: fix non-empty uart fifo read abort

This patch has been applied to the linux-omap by youw fwiendly patch wobot. Branch in linux-omap: for-next-vol2 Initial commit ID (Likely to change): 679089aa0dede39863a083a491b40928c5ec8379 PatchWorks http://patchwork.kernel.org/patch/65022/ Git (Likely to change, and takes a while to get mirr

[APPLIED] [PATCH] Correcting GPMC_CONFIG1_DEVICETYPE_NAND

This patch has been applied to the linux-omap by youw fwiendly patch wobot. Branch in linux-omap: for-next-vol2 Initial commit ID (Likely to change): 11da11ab7cbe212240b684672ff66133d2e41e5b PatchWorks http://patchwork.kernel.org/patch/64551/ Git (Likely to change, and takes a while to get mirr

[APPLIED] [PATCH] Zoom2/3:Update hsmmc board config params.

This patch has been applied to the linux-omap by youw fwiendly patch wobot. Branch in linux-omap: for-next-vol2 Initial commit ID (Likely to change): d110a6b269e46dd6b0b94bd5dd5020d959f2f9d8 PatchWorks http://patchwork.kernel.org/patch/62616/ Git (Likely to change, and takes a while to get mirr

Re: [PATCH 1/4] AM3517: MMC: Add low-level init code for HSMMC controller

* Anuj Aggarwal [091123 10:24]: > Add init code for HSMMC controller for AM3517 platform. This seems like a copy of the older mmc-twl4030.c? Can you please specify what is different compared to mmc-twl4030.c? I'd rather not have all this code duplicated, it's going to be a pain to maintain. I g

[APPLIED] [PATCH 2/2] usb: ehci: Allow EHCI to be built on OMAP3

This patch has been applied to the linux-omap by youw fwiendly patch wobot. Branch in linux-omap: for-next-vol2 Initial commit ID (Likely to change): caeaa2f4d7e3c8a2576bff1ca1b58e104e8f0266 PatchWorks http://patchwork.kernel.org/patch/62727/ Git (Likely to change, and takes a while to get mirr

Re: [PATCH 2/8] Board file of Always Innovating OMAP3-based Touch Book

2009/12/7 Tony Lindgren : >> One more thing just came in my mind, have you thought of using standard >> backlight class driver??? > > I'll add this without the backlight code so we get the basic > support into mainline while using the backlight class driver > issue is being discussed. But the boa

[APPLIED] [PATCH] OMAP3 : Enable TWL4030 Keypad for Zoom2 and Zoom3 boards

This patch has been applied to the linux-omap by youw fwiendly patch wobot. Branch in linux-omap: for-next-vol2 Initial commit ID (Likely to change): 4d758c4c38db37fb4caf5df6c0a0bc1d5ab35d21 PatchWorks http://patchwork.kernel.org/patch/60715/ Git (Likely to change, and takes a while to get mirr

Re: [PATCH 2/8] Board file of Always Innovating OMAP3-based Touch Book

Hi, * Hiremath, Vaibhav [091119 20:19]: > > > -Original Message- > > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > > ow...@vger.kernel.org] On Behalf Of Gregoire Gentil > > Sent: Thursday, November 19, 2009 10:48 PM > > To: linux-omap@vger.kernel.org > > Cc: Gregoire Genti

Re: [PATCH] OMAP3: PM: Enable wake-up from McBSP2, 3 and 4 modules

* Peter Ujfalusi [091207 05:37]: > Hello Tony, Kevin, > > On Thursday 26 November 2009 15:18:50 Ujfalusi Peter (Nokia-D/Tampere) wrote: > > Wake-up from McBSP ports are needed, especially when the THRESHOLD > > dma mode is in use for audio playback. > > > > Signed-off-by: Peter Ujfalusi > > ---

Re: [PATCH 0/2] [RESEND] Amstrad Delta: add support for LCD contrast

* Janusz Krzysztofik [091205 05:54]: > Monday 23 November 2009 18:57:51 Janusz Krzysztofik napisał(a): > > Initialy submitted on 2009-11-16 > > (http://www.spinics.net/lists/linux-omap/msg20629.html). > > Resendig due to fbdev mailing list address changed. > > > > The series consists of 2 patches:

[APPLIED] [PATCH v5] OMAP1: LCD_DMA: Use some define rather than a

This patch has been applied to the linux-omap by youw fwiendly patch wobot. Branch in linux-omap: for-next-vol2 Initial commit ID (Likely to change): 7b381eef0d82f9bbdff08d930e9cfc43ee98f0b7 PatchWorks http://patchwork.kernel.org/patch/62623/ Git (Likely to change, and takes a while to get mirr

Re: [PATCH v5] OMAP1: LCD_DMA: Use some define rather than a hexadecimal constant for LCD register

* Janusz Krzysztofik [091205 05:48]: > Tuesday 24 November 2009 22:34:10 Janusz Krzysztofik napisał(a): > > The patch corrects the issue introduced with one of my earlier patches: > > OMAP: DMA: Fix omapfb/lcdc on OMAP1510 broken when PM set[1] > > as pointed out by OMAP subsystem maintainer.

Re: [RFC][RFT][PATCH 3/4 v5b] OMAP: McBSP: Introduce caching in register write operations

* Janusz Krzysztofik [091207 11:38]: > Monday 07 December 2009 18:55:35 Tony Lindgren napisał(a): > > Hi, > > > > This is pretty close :) Few more tweaks are still needed. > > > > * Janusz Krzysztofik [091205 05:46]: > > > Reserve static space for storing cached copies of McBSP register values. >

Re: [RFC][RFT][PATCH 3/4 v5b] OMAP: McBSP: Introduce caching in register write operations

Monday 07 December 2009 18:55:35 Tony Lindgren napisał(a): > Hi, > > This is pretty close :) Few more tweaks are still needed. > > * Janusz Krzysztofik [091205 05:46]: > > Reserve static space for storing cached copies of McBSP register values. > > Split omap_mcbsp_read()/omap_mcbsp_write() into s

Re: [PATCH 1/2]: OMAP: SDP: Introducing 'board-sdp-flash.c' for flash init

* Vimal Singh [091206 22:39]: > On Sat, Dec 5, 2009 at 3:47 AM, Tony Lindgren wrote: > > Hi, > > > > * Vimal Singh [091203 06:09]: > >> From 13d52884956a26f93826c443e2b8bd78615f74d6 Mon Sep 17 00:00:00 2001 > >> From: Vimal Singh > >> Date: Thu, 26 Nov 2009 16:10:24 +0530 > >> Subject: [PATCH]

Re: [PATCH 2/3] [OMAP] Add spi100k configuration to OMAP1

* Cory Maccarrone [091206 20:48]: > This change implements the clocks, platform driver, and register > information necessary to use the spi100k bus with OMAP 7xx systems. > > The clocks added are dummy clocks because, although we're pretty > sure there are clocks used for SPI, all current booting

Re: [PATCH 1/3] [SPI] [OMAP] Add OMAP spi100k driver

Hi, * Cory Maccarrone [091206 20:48]: > This change adds the OMAP SPI 100k driver created by > Fabrice Crohas . This SPI bus is found on > OMAP7xx-series smartphones, and for many, the touchscreen is > attached to this bus. > > The lion's share of the work was done by Fabrice on this driver --

Re: [RFC] use physmap-flash

* Ladislav Michl [091205 15:34]: > Hi! > > and sorry for touching ancient stuff again... Also sorry for long Cc list, > which is not even complete, because some projects seem to be dead now. > > So, are there any objections to remove drivers/mtd/maps/omap_nor.c entirely > in favour of physmap-fl

Re: What's in omap git tree for 2.6.33

* Sid Boyce [091207 02:59]: > On 06/12/09 03:37, Gadiyar, Anand wrote: > > Sid Boyce wrote: > >> Still a few fragments missing on beagleboard - Very roughly: > >> drivers/usb/Kconfig > >> + default y if ARCH_OMAP34X > > > > > > This one's in Greg's queue for sure. > > > >

Re: [PATCH 2/2]: Introducing 'gpmc-nand.c' for GPMC specific NAND init

* Vimal Singh [091207 05:28]: > On Mon, Dec 7, 2009 at 11:59 AM, Vimal Singh wrote: > > On Sat, Dec 5, 2009 at 3:31 AM, Tony Lindgren wrote: > >> Hi, > >> > >> Looks good, just one comment below. > >> > >> * Govindraj.R [091204 05:37]: > >>> From: Vimal Singh > >>> Date: Wed, 25 Nov 2009 18:23

Re: [RFC][RFT][PATCH 3/4 v5b] OMAP: McBSP: Introduce caching in register write operations

Hi, This is pretty close :) Few more tweaks are still needed. * Janusz Krzysztofik [091205 05:46]: > Reserve static space for storing cached copies of McBSP register values. > Split omap_mcbsp_read()/omap_mcbsp_write() into separate functions for OMAP1 > and OMAP2/3/4, move them from plat-omap t

Re: [PATCH] omap3: cm-t35: add mux initialization

* Gadiyar, Anand [091207 08:35]: > Tony Lindgren wrote: > > * Mike Rapoport [091206 07:30]: > > > Tony, > > > Any chance this can go to 2.6.33? > > > > Sure, I was just waiting to hear back if the OUTPUT_PULLUP is > > needed for sure? Or is just OUTPUT enough for musb to work? > > > > Tony > >

RE: [PATCH 03/10 V3] omap3: pm: use opp accessor functions for omap34xx

One additional comment to this patch, compilation of board-rx51.c fails unless #include "pm.h" is added to it. This might be true for other boards also seeing it has been added to zoom2 at least. >-Original Message- >From: linux-omap-ow...@vger.kernel.org >[mailto:linux-omap-ow...@vger.k

RE: [PATCH 04/10 V3] omap3: pm: srf: use opp accessor functions

Hi, Couple of comments below. >-Original Message- >From: linux-omap-ow...@vger.kernel.org >[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of ext >Nishanth Menon >Sent: 25 November, 2009 06:09 >To: linux-omap >Cc: Nishanth Menon; Benoit Cousson; Kevin Hilman; Madhusudhan >Chikkature R

RE: [PATCH 07/10 V3] omap3: clk: use pm accessor functions for cpufreq table

Hi, One comment below. >-Original Message- >From: linux-omap-ow...@vger.kernel.org >[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of ext >Nishanth Menon >Sent: 25 November, 2009 06:09 >To: linux-omap >Cc: Nishanth Menon; Benoit Cousson; Kevin Hilman; Madhusudhan >Chikkature Rajas

RE: [PATCH] omap3: cm-t35: add mux initialization

Tony Lindgren wrote: > * Mike Rapoport [091206 07:30]: > > Tony, > > Any chance this can go to 2.6.33? > > Sure, I was just waiting to hear back if the OUTPUT_PULLUP is > needed for sure? Or is just OUTPUT enough for musb to work? > > Tony > OUTPUT should work too. The ULPI spec recommends a

Re: [PATCH] omap3: cm-t35: add mux initialization

* Mike Rapoport [091206 07:30]: > Tony, > Any chance this can go to 2.6.33? Sure, I was just waiting to hear back if the OUTPUT_PULLUP is needed for sure? Or is just OUTPUT enough for musb to work? Tony > Mike Rapoport wrote: > > Tony, > > > > These patches are follow-ups to your mux rework

Re: [PATCH 1/1] mfd: twl4030: clarify the return value for read and write

On Mon, Dec 07, 2009 at 01:17:29PM +0100, ext Amit Kucheria wrote: > Infact, we can just return -EIO so that caller knows for sure that all > messages were not tranferred. Please consider fixed patch instead. > > We should be checking if all the messages were tranferred or not. And return > -1 for

Re: [PATCH] OMAP3: PM: Enable wake-up from McBSP2, 3 and 4 modules

Hello Tony, Kevin, On Thursday 26 November 2009 15:18:50 Ujfalusi Peter (Nokia-D/Tampere) wrote: > Wake-up from McBSP ports are needed, especially when the THRESHOLD > dma mode is in use for audio playback. > > Signed-off-by: Peter Ujfalusi > --- > arch/arm/mach-omap2/pm34xx.c |8 ++-- >

Re: [PATCH 2/2]: Introducing 'gpmc-nand.c' for GPMC specific NAND init

On Mon, Dec 7, 2009 at 11:59 AM, Vimal Singh wrote: > On Sat, Dec 5, 2009 at 3:31 AM, Tony Lindgren wrote: >> Hi, >> >> Looks good, just one comment below. >> >> * Govindraj.R [091204 05:37]: >>> From: Vimal Singh >>> Date: Wed, 25 Nov 2009 18:23:15 +0530 >>> Subject: [PATCH] Introducing 'gpmc-

commit f4633d810405d4df8b3ea98f617856d149af636a breaks non-DSS2 pxafb support

Hi, all! I have custom external framebuffer driver based on drivers/video/omap/hwa742.c It is broken by commit f4633d810405d4df8b3ea98f617856d149af636a. if I revert it, it starts working. What is needed to be done to fix driver to make it work with non-DSS2 omapdss device? S. -- To unsubscribe fr

RE: [PATCH 0/8] OMAP clock: convert static definitions in header files to C files

Hi Rajendra et al, On Fri, 4 Dec 2009, Nayak, Rajendra wrote: > Some patches in this series seem to be missing, specifically 5/8 and 6/8. > Can you please re-post? They are now posted at: http://www.pwsan.com/omap/patches/clk_twist/ - Paul -- To unsubscribe from this list: send the line "

[PATCH 1/1] mfd: twl4030: clarify the return value for read and write

Infact, we can just return -EIO so that caller knows for sure that all messages were not tranferred. Please consider fixed patch instead. We should be checking if all the messages were tranferred or not. And return -1 for failure. Currently we return success (0) even if none of messages were trans

Re: What's in omap git tree for 2.6.33

On 06/12/09 03:37, Gadiyar, Anand wrote: > Sid Boyce wrote: >> Still a few fragments missing on beagleboard - Very roughly: >> drivers/usb/Kconfig >> + default y if ARCH_OMAP34X > > > This one's in Greg's queue for sure. > >

PM branch

Hi, all! When new PM branch will be available, is there any plans? I just want to use both DSS2 and PM, but can't make it work by plain merging of master and pm branches :( Thanks a lot, S. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to major

Re: Preventing OMAP3 serial driver to take control of all UARTs

On Thu, Dec 03, 2009 at 11:52:44AM -0800, Tony Lindgren wrote: > * Artem Bityutskiy [091203 00:46]: > > On Thu, 2009-12-03 at 08:56 +0200, Mika Westerberg wrote: > > > On Thu, Dec 03, 2009 at 02:00:52AM +0100, ext Tony Lindgren wrote: > > > > * Grant Likely [091202 07:06]: > > > > > On Mon, Nov 3

Re: DSS2 and power supplies

On Mon, Dec 7, 2009 at 10:44 AM, Tomi Valkeinen wrote: > Hi, > > On Fri, 2009-12-04 at 11:53 +0100, ext Grazvydas Ignotas wrote: >> hi, >> >> it seems DSS block in OMAP needs SDI/DSI supplies to operate properly >> even with parallel displays, or else it doesn't drive some data lines >> resulting

Re: [PATCH] Fix include problem. Signed-off-by: Marek Belisko

On Sat, 2009-12-05 at 00:00 +0100, ext Tony Lindgren wrote: > * Cory Maccarrone [091203 07:28]: > > On Thu, Dec 3, 2009 at 5:28 AM, Belisko Marek > > wrote: > > > > > > Hi, > > > > > > when make htcherald_defconfig on current linux-omap tree > > > (82f1d8f22f2c65e70206e40a6f17688bf64a892c) compi

Re: DSS2 and power supplies

Hi, On Fri, 2009-12-04 at 11:53 +0100, ext Grazvydas Ignotas wrote: > hi, > > it seems DSS block in OMAP needs SDI/DSI supplies to operate properly > even with parallel displays, or else it doesn't drive some data lines > resulting in missing/wrong colors. Take a look at figure 15-1 on OMAP3 > TR