Re: [PATCH 1/4] Smedia Glamo 3362 core/resource driver

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Samuel Ortiz
Date: Wednesday, August 18, 2010 - 6:39 am

Hi Thibaut,

On Wed, Jul 07, 2010 at 03:12:03PM +0200, Thibaut Girka wrote:
This is conflicting with enum glamo_irq, please fix your namespaces.


So you're saying that a couple users reported a bug on a specific kernel
revision, with the same HW, but all other users haven't ?
Couldnt that be related to a specific HW revision ? 
Also, this code should be scheduled for 2.6.37, and we're not going to
carry code to allow it to run on 2.6.28.


Please remove the commented code from this array.


So here you're busy looping in an interrupt handler, and that's not
recommended.


I think you want this definition outside of the DEBUGFS if.else.endif
scope. Have you tried building this driver without DEBUGFS enabled ?


Identation could be clearer here:
static const struct glamo_engine_reg_set glamo_lcd_regs[] = {
	{
		GLAMO_REG_CLOCK_LCD,

		GLAMO_CLOCK_LCD_EN_M5CLK |
		GLAMO_CLOCK_LCD_DG_M5CLK |
		GLAMO_CLOCK_LCD_EN_DMCLK,

		GLAMO_CLOCK_LCD_EN_DHCLK |
		GLAMO_CLOCK_LCD_EN_DCLK
	},
[...]



Same remark as with the module option: This is going to be a 2.6.37
driver, and I'd like you to check if you're still seeing those issues
before carrying these kind of hacks.


Shouldnt those values be set by your platform bootloader ? They're obviously
not, but I find it weird.


Please remove all #if 0 code from this driver.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH 1/4] Smedia Glamo 3362 core/resource driver, Thibaut Girka, (Wed Jul 7, 6:12 am)
Re: [PATCH 1/4] Smedia Glamo 3362 core/resource driver, Samuel Ortiz, (Wed Aug 18, 6:39 am)
Re: [PATCH 1/4] Smedia Glamo 3362 core/resource driver, Thibaut Girka, (Fri Aug 20, 8:05 am)