Received-SPF: pass (google.com: domain of linux-kernel+bounces-75964-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Message-ID: <689300ed3176274c5150cf101eb53ca3.sboyd@kernel.org>
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <20240213082640.457316-1-u-kumar1@ti.com>
References: <20240213082640.457316-1-u-kumar1@ti.com>
Subject: Re: [PATCH v4] clk: keystone: sci-clk: Adding support for non contiguous clocks
From: Stephen Boyd <sboyd@kernel.org>
Cc: vigneshr@ti.com, mturquette@baylibre.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, Udit Kumar <u-kumar1@ti.com>
To: Udit Kumar <u-kumar1@ti.com>, chandru@ti.com, francesco@dolcini.it, kamlesh@ti.com, kristo@kernel.org, nm@ti.com, rishabh@ti.com, ssantosh@kernel.org
Date: Wed, 21 Feb 2024 21:59:57 -0800
User-Agent: alot/0.10

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.
>=20
> New firmware started returning error while calling get_freq and is_on
> API for non-available clock ids.
>=20
> In this fix, driver checks and adds only valid clock ids.
>=20
> [0] https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j7200/clocks.ht=
ml
> Section Clocks for NAVSS0_CPTS_0 Device, clock id 12-15 not present.
>=20
> Fixes: 3c13933c6033 ("clk: keystone: sci-clk: add support for dynamically=
 probing clocks")
> Signed-off-by: Udit Kumar <u-kumar1@ti.com>
> ---

Applied to clk-next