Re: [PATCH v5 04/14] clk: max77686: Improve Maxim 77686 PMIC clocks binding

2014-07-02 Thread Javier Martinez Canillas
Hello Mike, On 07/01/2014 07:29 PM, Mike Turquette wrote: Quoting Javier Martinez Canillas (2014-06-26 11:15:36) Like most clock drivers, the Maxim 77686 PMIC clock binding follows the convention that the #clock-cells property is used to specify the number of cells in a clock provider. But

Re: [PATCH v5 04/14] clk: max77686: Improve Maxim 77686 PMIC clocks binding

2014-07-02 Thread Mike Turquette
Quoting Javier Martinez Canillas (2014-07-02 03:17:54) Hello Mike, On 07/01/2014 07:29 PM, Mike Turquette wrote: Quoting Javier Martinez Canillas (2014-06-26 11:15:36) Like most clock drivers, the Maxim 77686 PMIC clock binding follows the convention that the #clock-cells property is

Re: [PATCH v5 04/14] clk: max77686: Improve Maxim 77686 PMIC clocks binding

2014-07-01 Thread Mike Turquette
Quoting Javier Martinez Canillas (2014-06-26 11:15:36) Like most clock drivers, the Maxim 77686 PMIC clock binding follows the convention that the #clock-cells property is used to specify the number of cells in a clock provider. But the binding document is not clear enough that it shall be

[PATCH v5 04/14] clk: max77686: Improve Maxim 77686 PMIC clocks binding

2014-06-26 Thread Javier Martinez Canillas
Like most clock drivers, the Maxim 77686 PMIC clock binding follows the convention that the #clock-cells property is used to specify the number of cells in a clock provider. But the binding document is not clear enough that it shall be set to 1 since the PMIC support multiple clocks outputs.