[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <60283626a078dde6f56963f5cc763c0d.sboyd@kernel.org>
Date: Thu, 14 Nov 2024 15:00:03 -0800
From: Stephen Boyd <sboyd@...nel.org>
To: Conor Dooley <conor+dt@...nel.org>, Grégory Clement <gregory.clement@...tlin.com>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Michael Turquette <mturquette@...libre.com>, Rob Herring <robh@...nel.org>, Thomas Bogendoerfer <tsbogend@...ha.franken.de>, Théo Lebrun <theo.lebrun@...tlin.com>, Vladimir Kondratiev <vladimir.kondratiev@...ileye.com>
Cc: linux-mips@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org, Thomas Petazzoni <thomas.petazzoni@...tlin.com>, Tawfik Bayouk <tawfik.bayouk@...ileye.com>, Théo Lebrun <theo.lebrun@...tlin.com>
Subject: Re: [PATCH v2 05/10] clk: eyeq: add fixed factor clocks infrastructure
Quoting Théo Lebrun (2024-11-06 08:03:56)
> Driver can currently host two types of clocks:
> - PLLs derived directly from the main crystal (taken using a fwhandle).
> - Divider clocks derived from those PLLs.
>
> PLLs can be instantiated from of_clk_init() or platform device probe,
> using two separate clock providers. Divider clocks are all instantiated
> at platform device probe.
>
> Add a third type of clocks: fixed factors. Those can be instantiated at
> both stages. They can be parented to any clock from the driver. Early
> match data and match data store the list of fixed factor clocks.
>
> Signed-off-by: Théo Lebrun <theo.lebrun@...tlin.com>
> ---
Applied to clk-next
Powered by blists - more mailing lists