[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <160819878921.1580929.15203556505418978794@swboyd.mtv.corp.google.com>
Date: Thu, 17 Dec 2020 01:53:09 -0800
From: Stephen Boyd <sboyd@...nel.org>
To: Alexandru Ardelean <alexandru.ardelean@...log.com>,
linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: mturquette@...libre.com, mdf@...nel.org, lars@...afoo.de,
ardeleanalex@...il.com,
Alexandru Ardelean <alexandru.ardelean@...log.com>
Subject: Re: [RESEND PATCH 1/2] clk: axi-clkgen: wrap limits in a struct and keep copy on the state object
Quoting Alexandru Ardelean (2020-12-02 23:40:36)
> Up until the these limits were global/hard-coded, since they are typically
> limits of the fabric.
>
> However, since this is an FPGA generated clock, this may run on setups
> where one clock is on a fabric, and another one synthesized on another
> fabric connected via PCIe (or some other inter-connect, and then these
> limits need to be adjusted for each instance of the AXI CLKGEN.
>
> This change wraps the current constants in 'axi_clkgen_limits' struct and
> the 'axi_clkgen' instance keeps a copy of these limits, which is
> initialized at probe from the default limits.
>
> The limits are stored on the device-tree OF table, so that we can adjust
> them via the compatible string.
>
> Signed-off-by: Alexandru Ardelean <alexandru.ardelean@...log.com>
> ---
Applied to clk-next
Powered by blists - more mailing lists