On Sat, Aug 17, 2013 at 05:13:20PM +0200, Tomasz Figa wrote: > On Saturday 17 of August 2013 17:00:02 Sascha Hauer wrote: > > On Sat, Aug 17, 2013 at 02:26:40PM +0200, Tomasz Figa wrote: > > > > You mean tx<0-7>. > > > > > > > > Also I would make this option required. Use a dummy clock for mux > > > > inputs that are grounded for a specific SoC. > > > > > > Why do you need a dummy clock? > > > > > > The driver can simply try to grab all the possible clocks and discard > > > those that failed, so you can just keep those grounded clocks > > > unspecified. > > We don't need dummy clocks. My motivation saying this that I was afraid > > people try to configure the driver by skipping the clocks they don't > > want from the devicetree. > > I'm not really sure if the same abuse couldn't be easily achieved by > putting dummy clocks in place of those skipped clocks. That's right, yes. > > Adding a note in binding documentation that says that all clocks that are > fed to the IP shall be specified should be fine IMHO. ok. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- 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
