On Fri, Dec 11, 2015 at 07:48:54AM -0800, Tony Lindgren wrote: > There's a problem with MAX_CON_ID 16 hardcoded allocated name length. Absolutely right... > In this case I have 13 instances of plls with 3 - 4 outputs each and I'd > like to use "481c5040.adpll.clkout" style naming starting with the instance > address. Also "adpll5.clkdcoldo" style naming would work, Because it's a connection ID, not a clock _name_. I see that we're still making all the same mistakes with clocks that were made years ago, and which lead down the path of amazingly complex drivers having conditional clock names and the like. Is there a reason why you can't split this into separate device and input names, and use clk_get_sys() rather than passing NULL as the device to clk_get(). This is exactly why we've ended up with clk_get_sys(), to cater for the cases where there is no struct device to associate with the connection ID: the idea behind clk_get_sys() is that you pass the device name explicitly, along with the connection ID. -- RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- 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
