Re: [RFC][PATCH 2/5] OMAP SSI driver interface

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Felipe Balbi
Date: Monday, October 6, 2008 - 4:29 pm

On Fri, Oct 03, 2008 at 02:52:27PM +0300, Carlos Chinea wrote:

add a patch description body here.


why wouldn't ssi.h be enough as a header name ?

looks much better and much easier to type: #include <linux/ssi.h>


hmm... I wonder you really need these ? Maybe I have to wait until I
review the other patches but at least for the irq names, they look
weird. Are them used for request_irq() only ? If so, remove them and
pass it in the driver. There's no need for such a global definition.


Most likely this will be platform_specific right ? So pass it to the
driver using a struct resource.


CHANNEL is not generic enough name, use, at least, SSI_CHANNEL and add
spaces around that left shift.


hmm... ioctls, let's if they're really needed later.


please don't pass clock names via platform_data. It's ugly and we're
having quite a big amount of work trying to find a solution to clean
omap drivers. Looks like we're gonna introduce omap_clk_associate()
which will associate the user device with the clock structure and
introduce a clk alias name (called function name) to avoid the problem
we have now with different omap versions (different clock names).

	    ^ trailing whitespace


and then this will be the only bus not using the MODULE_DEVICE_TABLE,
please fix. Introduce a MODULE_DEVICE_TABLE. i2c did it recently and
it's quite simple. Most likely this will have a similar implementation.

			    ^ trailing whitespace

let's try to keep a consistency with several other register and
unregister functions in the kernel and rename this to
ssi_register_driver(), likewise to ssi_unregister_driver()

					^ this comma should be in the
					previous line


#endif /* __SSI__ blablabla */

btw, a bit of kerneldoc wouldn't hurt. Please document all these
structures.

-- 
balbi
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[RFC][PATCH 2/5] OMAP SSI driver interface, Carlos Chinea, (Fri Oct 3, 4:52 am)
[RFC][PATCH 3/5] OMAP SSI driver code, Carlos Chinea, (Fri Oct 3, 4:52 am)
[RFC][PATCH 4/5] OMAP SSI integration into misc drivers, Carlos Chinea, (Fri Oct 3, 4:52 am)
[RFC][PATCH 5/5] OMAP SSI API documentation, Carlos Chinea, (Fri Oct 3, 4:52 am)
Re: [RFC][PATCH 2/5] OMAP SSI driver interface, Felipe Balbi, (Mon Oct 6, 4:29 pm)
Re: [RFC][PATCH 3/5] OMAP SSI driver code, Felipe Balbi, (Mon Oct 6, 5:03 pm)
Re: [RFC][PATCH 2/5] OMAP SSI driver interface, David Brownell, (Mon Oct 6, 6:03 pm)
RE: [RFC][PATCH 2/5] OMAP SSI driver interface, Woodruff, Richard, (Tue Oct 7, 4:56 am)
Re: [RFC][PATCH 3/5] OMAP SSI driver code, Felipe Balbi, (Tue Oct 7, 3:01 pm)
Re: [RFC][PATCH 5/5] OMAP SSI API documentation, Felipe Balbi, (Thu Oct 9, 9:47 am)