On Tue, 26 Nov 2013, Tero Kristo wrote: > The OMAP clock driver now supports DPLL clock type. This patch also > adds support for DT DPLL nodes. > > Signed-off-by: Tero Kristo <t-kristo@xxxxxx> ... > +/* > + * struct clk_hw_omap.flags possibilities > + * > + * XXX document the rest of the clock flags here > + * > + * ENABLE_REG_32BIT: (OMAP1 only) clock control register must be accessed > + * with 32bit ops, by default OMAP1 uses 16bit ops. > + * CLOCK_IDLE_CONTROL: (OMAP1 only) clock has autoidle support. > + * CLOCK_NO_IDLE_PARENT: (OMAP1 only) when clock is enabled, its parent > + * clock is put to no-idle mode. > + * ENABLE_ON_INIT: Clock is enabled on init. > + * INVERT_ENABLE: By default, clock enable bit behavior is '1' enable, '0' > + * disable. This inverts the behavior making '0' enable and '1' disable. > + * CLOCK_CLKOUTX2: (OMAP4 only) DPLL CLKOUT and CLKOUTX2 GATE_CTRL > + * bits share the same register. This flag allows the > + * omap4_dpllmx*() code to determine which GATE_CTRL bit field > + * should be used. This is a temporary solution - a better approach > + * would be to associate clock type-specific data with the clock, > + * similar to the struct dpll_data approach. > + * REGMAP_ADDRESSING: Use regmap addressing to access clock registers. > + */ Nice work adding the additional flag documentation here. - Paul -- 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
