Hi Morimoto-san,
On Tue, Apr 11, 2017 at 2:36 AM, Kuninori Morimoto
<[email protected]> wrote:
> From: Kuninori Morimoto <[email protected]>
>
> Signed-off-by: Kuninori Morimoto <[email protected]>
> Tested-by: Hiroyuki Yokoyama <[email protected]>
> ---
> .../devicetree/bindings/clock/cs2000-cp.txt | 9 +++
> drivers/clk/clk-cs2000-cp.c | 73
> +++++++++++++++++++++-
> 2 files changed, 80 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/clock/cs2000-cp.txt
> b/Documentation/devicetree/bindings/clock/cs2000-cp.txt
> index 54e6df0..4c2f9cb 100644
> --- a/Documentation/devicetree/bindings/clock/cs2000-cp.txt
> +++ b/Documentation/devicetree/bindings/clock/cs2000-cp.txt
> @@ -8,6 +8,15 @@ Required properties:
> - clock-names: CLK_IN : clk_in, XTI/REF_CLK : ref_clk
> - #clock-cells: must be <0>
>
> +Option properties:
> +
> +- auxoutsrc: select AUX_OUT source from these.
> + refclk: Timing Reference Clock
> + clk_in: Frequency Reference Clock
> + pllclkout: PLL Clock Output
> + push-pull: PLL Lock/Unlock Indication
> + open-drain: PLL Lock/Unlock Indication
AUX_OUT is an output pin?
Hence, isn't this software configuration instead of hardware description?
Selection of refclk vs. clk_in vs. pllclkout can be implemented as a mux clock
driver with three parents.
PLL Lock/Unlock Indication and its pinctrl are something different.
How to support that?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
