[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <689300ed3176274c5150cf101eb53ca3.sboyd@kernel.org>
Date: Wed, 21 Feb 2024 21:59:57 -0800
From: Stephen Boyd <sboyd@...nel.org>
To: Udit Kumar <u-kumar1@...com>, chandru@...com, francesco@...cini.it, kamlesh@...com, kristo@...nel.org, nm@...com, rishabh@...com, ssantosh@...nel.org
Cc: vigneshr@...com, mturquette@...libre.com, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org, Udit Kumar <u-kumar1@...com>
Subject: Re: [PATCH v4] clk: keystone: sci-clk: Adding support for non contiguous clocks
Quoting Udit Kumar (2024-02-13 00:26:40)
> Most of clocks and their parents are defined in contiguous range,
> But in few cases, there is gap in clock numbers[0].
> Driver assumes clocks to be in contiguous range, and add their clock
> ids incrementally.
>
> New firmware started returning error while calling get_freq and is_on
> API for non-available clock ids.
>
> In this fix, driver checks and adds only valid clock ids.
>
> [0] https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j7200/clocks.html
> Section Clocks for NAVSS0_CPTS_0 Device, clock id 12-15 not present.
>
> Fixes: 3c13933c6033 ("clk: keystone: sci-clk: add support for dynamically probing clocks")
> Signed-off-by: Udit Kumar <u-kumar1@...com>
> ---
Applied to clk-next
Powered by blists - more mailing lists