On Tue, Feb 13, 2024 at 01:56:40PM +0530, Udit Kumar wrote:
Most of clocks and their parents are defined in contiguous range,Is this the kind of errors I should expect in such situation?
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.
ti-sci-clk 44043000.system-controller:clock-controller: recalc-rate failed for dev=13, clk=7, ret=-19
If this is the case, I feel like this patch should be back-ported to
stable kernels.
Any malfunction because of these errors or just some noise in the logs?
Francesco