Re: [rtc-linux] [PATCH 1/2] rtc: rtc-lpc32xx: Introduce RTC driver for the LPC32XX SoC

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Wolfram Sang
Date: Tuesday, August 10, 2010 - 3:25 am

Hi Kevin,

driver seems to work fine here, a few comments though.

On Mon, Aug 09, 2010 at 09:17:29AM -0700, wellsk40@gmail.com wrote:

Empty line to seperate variables from the code


You can drop this cast.


How about using managed resources (devm_*)? They usually simplify the
error paths and make the probe more readable.


I saw that a number of rtc-drivers register their irq after they
register the device. I wonder if this is OK here? Couldn't it happen
that after rtc_device_register() there is a preemption and another
process could set the alarm? Then there is a race between interrupts
already enabled and no handler available, no?


Minor nitpick: The trend seems to be to put those lines directly after
the function.


Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [rtc-linux] [PATCH 1/2] rtc: rtc-lpc32xx: Introduce RT ..., Wolfram Sang, (Tue Aug 10, 3:25 am)
Re: [rtc-linux] [PATCH 1/2] rtc: rtc-lpc32xx: Introduce RT ..., Uwe Kleine-König, (Tue Aug 10, 5:00 am)