On Wed, Nov 02, 2022 at 01:20:33PM +, padmarao.beg...@microchip.com wrote:
> Hi Conor,
>
> > On Tue, 2022-10-25 at 08:58 +0100, Conor Dooley wrote:
> > Currently the clock driver for PolarFire SoC takes a very naive
> > approach
> > to the relationship between clocks. It reads the dt to get
Hi Conor,
> On Tue, 2022-10-25 at 08:58 +0100, Conor Dooley wrote:
> Currently the clock driver for PolarFire SoC takes a very naive
> approach
> to the relationship between clocks. It reads the dt to get an input
> clock, assumes that that is fixed frequency, reads the "clock-
s/that that/that
On Tue, Oct 25, 2022 at 08:58:45AM +0100, Conor Dooley wrote:
> Currently the clock driver for PolarFire SoC takes a very naive approach
> to the relationship between clocks. It reads the dt to get an input
> clock, assumes that that is fixed frequency, reads the "clock-frequency"
> property &
Currently the clock driver for PolarFire SoC takes a very naive approach
to the relationship between clocks. It reads the dt to get an input
clock, assumes that that is fixed frequency, reads the "clock-frequency"
property & uses that to set up both the "cfg" and "periph" clocks.
Simplifying for
4 matches
Mail list logo