As with many vintage and antique pieces, the value of a grandfather clock depends on a number of factors, including age, rarity, appearance, mechanical soundness, etc.
Ridgeway clocks serial number lookup serial#
> void of_clk_init(const struct of_device_id *matches) > const char *of_clk_get_parent_name(struct device_node *np, int index) > +struct clk *of_clk_src_onecell_get(struct of_phandle_args *clkspec, void *data) > struct clk *of_clk_src_simple_get(struct of_phandle_args *clkspec, > void of_clk_del_provider(struct device_node *np) > diff -git a/include/linux/clk-provider.h b/include/linux/clk-provider.h > * Device node pointer associated with clock provider > * of_clk_add_provider() - Register a clock provider for a node > +EXPORT_SYMBOL_GPL(of_clk_src_onecell_get) > + pr_err("%s: invalid clock index %d\n", _func_, idx) > + struct clk_onecell_data *clk_data = data > EXPORT_SYMBOL_GPL(of_clk_src_simple_get)
> -1582,6 +1582,20 struct clk *of_clk_src_simple_get(struct of_phandle_args *clkspec, > diff -git a/drivers/clk/clk.c b/drivers/clk/clk.c > 2 files changed, 19 insertions(+), 0 deletions(-) I have some reservations about how generic this will end up being, but > Add a generic of_clk_src_onecell_get() function for this purpose. > the client device specify the index of the clock it consumes in the > DT bindings could reasonably define #clock-cells as 1 and require > For those SoCs that have hundreds of clock outputs, their clock 6:41 ` Shawn Guo 1 sibling, 0 replies 26+ messages in thread Void of_clk_init(const struct of_device_id *matches) +struct clk *of_clk_src_onecell_get(struct of_phandle_args *clkspec, void *data) Ĭonst char *of_clk_get_parent_name(struct device_node *np, int index) Struct clk *of_clk_src_simple_get(struct of_phandle_args *clkspec, Void of_clk_del_provider(struct device_node *np) * Device node pointer associated with clock providerĭiff -git a/include/linux/clk-provider.h b/include/linux/clk-provider.h * of_clk_add_provider() - Register a clock provider for a node
+EXPORT_SYMBOL_GPL(of_clk_src_onecell_get) + pr_err("%s: invalid clock index %d\n", _func_, idx) + struct clk_onecell_data *clk_data = data +struct clk *of_clk_src_onecell_get(struct of_phandle_args *clkspec, void *data) +++ -1582,6 +1582,20 struct clk *of_clk_src_simple_get(struct of_phandle_args *clkspec,ĮXPORT_SYMBOL_GPL(of_clk_src_simple_get) The client device specify the index of the clock it consumes in theĪdd a generic of_clk_src_onecell_get() function for this purpose.Ģ files changed, 19 insertions(+), 0 deletions(-)ĭiff -git a/drivers/clk/clk.c b/drivers/clk/clk.c ` (2 subsequent siblings) 3 siblings, 0 replies 26+ messages in threadįor those SoCs that have hundreds of clock outputs, their clockĭT bindings could reasonably define #clock-cells as 1 and require 13:36 ` ARM: im圆q: replace clk_register_clkdev with clock DT lookup Shawn Guo * clk: add of_clk_src_onecell_get() support.
devicetree/bindings/clock/im圆q-clock.txt | 222 ++++++++++++++++++++Īrch/arm/boot/dts/im圆q-sabrelite.dts | 1 +Īrch/arm/boot/dts/im圆q.dtsi | 73 ++++++-ĭrivers/clk/mxs/clk-imx28.c | 113 +-ġ3 files changed, 550 insertions(+), 202 deletions(-)Ĭreate mode 100644 Documentation/devicetree/bindings/clock/imx23-clock.txtĬreate mode 100644 Documentation/devicetree/bindings/clock/imx28-clock.txtĬreate mode 100644 Documentation/devicetree/bindings/clock/im圆q-clock.txt Then we can save that big clock name list in dts and the stringĬlk: add of_clk_src_onecell_get() supportĪRM: im圆q: replace clk_register_clkdev with clock DT lookupĬlk: mxs: replace imx28 clk_register_clkdev with clock DT lookupĬlk: mxs: replace imx23 clk_register_clkdev with clock DT lookup Provided by device tree and the clks array provided by clock driver. * Rewrite of_clk_src_onecell_get() to get the clk using the index ` (4 more replies) 0 siblings, 5 replies 26+ messages in thread 13:36 ` clk: add of_clk_src_onecell_get() support Shawn Guo Move im圆q/28/23 clock lookup over to device tree All of help / color / mirror / Atom feed * Move im圆q/28/23 clock lookup over to device tree 13:36 Shawn Guo
0 kommentar(er)
