lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 6 Jul 2020 10:53:24 -0400
From:   Sven Van Asbroeck <>
To:     Andy Duan <>
Cc:     Fabio Estevam <>,
        Shawn Guo <>,
        Rob Herring <>,
        "David S. Miller" <>,
        Jakub Kicinski <>,
        netdev <>,
        Sascha Hauer <>,
        Pengutronix Kernel Team <>,
        dl-linux-imx <>,
        "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
        linux-kernel <>
Subject: Re: [EXT] Re: [PATCH v5 3/3] ARM: imx6plus: optionally enable
 internal routing of clk_enet_ref

Hi Andy,

On Mon, Jul 6, 2020 at 1:30 AM Andy Duan <> wrote:
> The clock depends on board design, HW refer guide can describe the clk
> usage in detail and customer select one clk path as their board design.

Yes, I agree. But how does a board designer practically describe this
in the devicetree?

Example: mac_gtx -> clk_pad (the default)

Imagine I have a fixed oscillator on the board:

phy_ref_clk: oscillator {
    compatible = "fixed-clock";
    #clock-cells = <0>;
    clock-frequency = <50000000>;

How can I now make <&phy_ref_clk> the parent of
<&clks CLK_PAD> ?

Powered by blists - more mailing lists