On Mon, Jul 6, 2020 at 2:30 AM Andy Duan <fugang.duan@xxxxxxx> wrote: > > From: Sven Van Asbroeck <thesven73@xxxxxxxxx> Sent: Sunday, July 5, 2020 11:34 PM > > > > ext phy---------| \ > > | | > > enet_ref-o------|M |----pad------| \ > > | |_/ | | > > | |M |----mac_gtx > > | | | > > o-----------------------|_/ > > > > > > How do we tell the clock framework that clk_pad has a mux that can be > > connected to _any_ external clock? and also enet_ref? > > 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. > > To make thing simple, we can just control the second "M" that is controlled > by gpr bit. Would it make sense to use compatible = "mmio-mux"; like we do on imx7s, imx6qdl.dtsi and imx8mq.dtsi?
