From: "Kumar, Udit" <u-kumar1@ti.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: <nm@ti.com>, <kristo@kernel.org>, <ssantosh@kernel.org>,
<chandru@ti.com>, <rishabh@ti.com>, <kamlesh@ti.com>,
<vigneshr@ti.com>, <mturquette@baylibre.com>, <sboyd@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>
Subject: Re: [PATCH v4] clk: keystone: sci-clk: Adding support for non contiguous clocks
Date: Mon, 26 Feb 2024 19:17:31 +0530 [thread overview]
Message-ID: <aa180f33-9c42-4435-aff2-f23c42bcadea@ti.com> (raw)
In-Reply-To: <20240226105435.GA11908@francesco-nb>
On 2/26/2024 4:24 PM, Francesco Dolcini wrote:
> On Tue, Feb 13, 2024 at 01:56:40PM +0530, Udit Kumar wrote:
>> 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.
> Is this the kind of errors I should expect in such situation?
>
> 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.
Sure will send to stable@vger.kernel.org
> Any malfunction because of these errors or just some noise in the logs?
Error is noise in logs, no impact on function as these reserved clocks
are not used by drivers.
>
> Francesco
>
prev parent reply other threads:[~2024-02-26 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 8:26 [PATCH v4] clk: keystone: sci-clk: Adding support for non contiguous clocks Udit Kumar
2024-02-16 17:09 ` Nishanth Menon
2024-02-22 5:59 ` Stephen Boyd
2024-02-26 10:54 ` Francesco Dolcini
2024-02-26 13:47 ` Kumar, Udit [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aa180f33-9c42-4435-aff2-f23c42bcadea@ti.com \
--to=u-kumar1@ti.com \
--cc=chandru@ti.com \
--cc=francesco@dolcini.it \
--cc=kamlesh@ti.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=rishabh@ti.com \
--cc=sboyd@kernel.org \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).