Archit, > -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > owner@xxxxxxxxxxxxxxx] On Behalf Of Taneja, Archit > Sent: Friday, September 24, 2010 7:41 AM > To: Nayak, Rajendra > Cc: linux-omap@xxxxxxxxxxxxxxx; Guruswamy, Senthilvadivu > Subject: Query on clock naming conventions in clockxxxx_data.c > > Hi, > > I had a couple of queries regarding the clock structures in the > clockxxxx_data.c files: > > -I have seen that the name of the structure itself explains the name of > the clock as > given in the TRM. > -The member "name" also tries to mimic the clock name. > > The drivers get the clock struct using the "name" member in the clk_get() > api. Is it > okay if we can change the "name" member to a more generic string. So that > the driver > code stays more generic? > > For example, the SYS_CLK which comes into DSS is called "dss2_alwon_fck" > on omap3 and > "dss_sys_clk" on omap4. This will make our driver need to have cpu_is_omap > checks while > calling clk_get(). > I guess migrating to hwmod should resolve the issue you mentioned. Thank you, Best regards, Hari -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
