On Wed, Sep 24, 2014 at 02:23:38PM +0200, Arnd Bergmann wrote: > On Wednesday 24 September 2014 19:29:05 Peter Chen wrote: > > > > So, it is IP CORE LIB (you suggest) vs IP CORE Platform Driver > > (dwc3, musb, chipidea) you are talking about, right? Except for > > creating another platform driver as well as related DT node (optional), > > are there any advantages compared to current IP core driver structure? > > Having a library module usually requires less code, and is more consistent > with other drivers, which helps new developers understand what the > driver is doing. Yes, more consistent is a good reason. > > The most important aspect though is the DT binding: once the structure > with separate kernel drivers leaks out into the DT format, you can't > easily change the driver any more, e.g. to make a property that was > introduced for one glue driver more general so it can get handled by > the common part. Having a single node lets us convert to the library > model later, so that would be a strong reason to keep the DT binding > simple, without child nodes. > > Following that logic, it turns into another reason for using the library > model to start with, because otherwise the child device does not have > any DT properties itself and has to rely on the parent device properties, > which somewhat complicates the driver structure. > Although it is not a problem for chipidea, chipidea core exports API to handle parent's common DT entries. It is a little inconsistent for current chipidea core driver, it works as a driver, but exports some APIs for other drivers use which is like a library. One more benefit I can see is the platform driver can visit the common struct like io address if using library, currently, the platform driver isn't suitable to visit core driver's struct, since they are two drivers. For chipidea, it doesn't has child device DT node, so it can convert to core library + platform driver model with moderate effort, I will do it at next two versions, thanks. -- Best Regards, Peter Chen -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
