[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20191213134708.GA4286@lunn.ch>
Date: Fri, 13 Dec 2019 14:47:08 +0100
From: Andrew Lunn <andrew@...n.ch>
To: biao huang <biao.huang@...iatek.com>
Cc: davem@...emloft.net, Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Giuseppe Cavallaro <peppe.cavallaro@...com>,
Alexandre Torgue <alexandre.torgue@...com>,
Jose Abreu <joabreu@...opsys.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Matthias Brugger <matthias.bgg@...il.com>,
netdev@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, yt.shen@...iatek.com
Subject: Re: [PATCH 1/2] net-next: stmmac: mediatek: add more suuport for RMII
> The clock labeled as "rmii_internal" is needed only in RMII(when MAC provides
> reference clock), and useless for RGMII/MII/RMII(when phy provides reference
> clock).
>
> So, add a boolean flag to indicate where the RMII reference clock is from, MAC
> or PHY, if MAC, enable the "rmii_internal", or disable it.
> and this clock already documented in dt-binding in PATCH 2/2.
>
> For power saving, it should not be enabled in default, so can't add it to the
> existing list of clocks directly.
>
> Any advice for this special case?
O.K. Add the boolean, but also add the clock to the list of clocks in
DT. Don't hard code the clock name in the driver.
Andrew
Powered by blists - more mailing lists