From: Stephen Boyd <sboyd@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Taniya Das <quic_tdas@quicinc.com>
Cc: Andy Gross <agross@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] clk: qcom: common: Handle invalid index error
Date: Mon, 17 Apr 2023 16:40:16 -0700 [thread overview]
Message-ID: <3251d8e89d5f047784149419c5bff7c0.sboyd@kernel.org> (raw)
In-Reply-To: <ce6c952b-2e2b-67d9-5023-e740ed798758@quicinc.com>
Quoting Taniya Das (2023-04-16 21:40:48)
> Hi Dmitry,
>
> Thanks for the comments.
>
>
> On 3/3/2023 4:14 PM, Dmitry Baryshkov wrote:
> > On Fri, 3 Mar 2023 at 11:30, Taniya Das <quic_tdas@quicinc.com> wrote:
> >>
> >> Introduce start_index to handle invalid index error
> >> seen when there are two clock descriptors assigned
> >> to the same clock controller.
> >
> > Please provide details of the exact case that you are trying to solve
> > (this might go to the cover letter). I think the commit message is
> > slightly misleading here. Are you trying to add error messages or to
> > prevent them from showing up?
> >
>
> We are trying to avoid error messages from showing up.
>
> > I'm asking because error messages do not seem to correspond to patch
> > 2. You add start_index to make the kernel warn for the clock indices
> > less than LPASS_AUDIO_CC_CDIV_RX_MCLK_DIV_CLK_SRC = 4, while quoted
> > messages show indices 5,6,7.
> >
>
> Right, we want the kernel to warn if the clock index is less than
> start_index, along with that we also want to handle the case where
> num_rclks is uninitialized because of same clock descriptor being
> assigned to two clock controllers.
The start_index should be 0.
next prev parent reply other threads:[~2023-04-17 23:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 9:28 [PATCH 0/2] Handle invalid index error Taniya Das
2023-03-03 9:28 ` [PATCH 1/2] clk: qcom: common: " Taniya Das
2023-03-03 10:44 ` Dmitry Baryshkov
2023-04-17 4:40 ` Taniya Das
2023-04-17 11:49 ` Dmitry Baryshkov
2023-04-17 23:40 ` Stephen Boyd [this message]
2023-03-03 9:28 ` [PATCH 2/2] clk: qcom: lpass: Initialize start_index Taniya Das
2023-03-03 14:59 ` kernel test robot
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=3251d8e89d5f047784149419c5bff7c0.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_tdas@quicinc.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