Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Stephen Boyd <sboyd@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Taniya Das <quic_tdas@quicinc.com>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH v2] clk: qcom: common: use parent_hws in _qcom_cc_register_board_clk()
Date: Mon, 16 Jan 2023 21:30:03 -0600	[thread overview]
Message-ID: <20230117033003.ky2i7fc2l72rhysd@builder.lan> (raw)
In-Reply-To: <CAA8EJppzHoHp5BVBJN-ZF0OmwbtKfxhX_qTEPc5cwSnLTvTcJQ@mail.gmail.com>

On Wed, Jan 11, 2023 at 06:49:29AM +0200, Dmitry Baryshkov wrote:
> On Wed, 11 Jan 2023 at 06:47, Bjorn Andersson <andersson@kernel.org> wrote:
> >
> > On Wed, Dec 28, 2022 at 10:35:55PM +0200, Dmitry Baryshkov wrote:
> > > Switch _qcom_cc_register_board_clk() to use parent_hws.
> > >
> >
> > There's more to this patch then this short sentence, please describe it
> > further.
> 
> True, I'll fix it for v3.
> 
> >
> > And given Dan's reported-by, I must assume that there's an issue with
> > the current code. Is there a Fixes?
> 
> No. Dan reported an issue with v1, thus his Reported-by was included into v2.
> 

I though it meant "this corrects an issue that was Reported-by".

IMHO including "issues was fixed during code review after being
Reported-by" diminishing the value of this trailer - in particular since
we don't use it broadly to capture anyone else's review feedback.


PS. I'm definitely in favour of introducing a trailer to give Dan, and
others, credit for reviews.

Regards,
Bjorn

> >
> > Regards,
> > Bjorn
> >
> > > Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> > > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> > > ---
> > >
> > > Changes since v1:
> > > - Properly fix the clock's parent data in case parent clock is present
> > >   in the dtsi.
> > >
> > > ---
> > >  drivers/clk/qcom/common.c | 11 +++++++++--
> > >  1 file changed, 9 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/clk/qcom/common.c b/drivers/clk/qcom/common.c
> > > index 75f09e6e057e..9f2bd37c9540 100644
> > > --- a/drivers/clk/qcom/common.c
> > > +++ b/drivers/clk/qcom/common.c
> > > @@ -133,7 +133,7 @@ static int _qcom_cc_register_board_clk(struct device *dev, const char *path,
> > >       struct device_node *node = NULL;
> > >       struct device_node *clocks_node;
> > >       struct clk_fixed_factor *factor;
> > > -     struct clk_fixed_rate *fixed;
> > > +     struct clk_fixed_rate *fixed = NULL;
> > >       struct clk_init_data init_data = { };
> > >       int ret;
> > >
> > > @@ -161,6 +161,8 @@ static int _qcom_cc_register_board_clk(struct device *dev, const char *path,
> > >       of_node_put(node);
> > >
> > >       if (add_factor) {
> > > +             struct clk_parent_data parent_data;
> > > +
> > >               factor = devm_kzalloc(dev, sizeof(*factor), GFP_KERNEL);
> > >               if (!factor)
> > >                       return -EINVAL;
> > > @@ -168,8 +170,13 @@ static int _qcom_cc_register_board_clk(struct device *dev, const char *path,
> > >               factor->mult = factor->div = 1;
> > >               factor->hw.init = &init_data;
> > >
> > > +             if (fixed)
> > > +                     parent_data.hw = &fixed->hw;
> > > +             else
> > > +                     parent_data.name = path;
> > > +
> > >               init_data.name = name;
> > > -             init_data.parent_names = &path;
> > > +             init_data.parent_data = &parent_data;
> > >               init_data.num_parents = 1;
> > >               init_data.flags = 0;
> > >               init_data.ops = &clk_fixed_factor_ops;
> > > --
> > > 2.39.0
> > >
> 
> 
> 
> -- 
> With best wishes
> Dmitry

  reply	other threads:[~2023-01-17  3:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28 20:35 [PATCH v2] clk: qcom: common: use parent_hws in _qcom_cc_register_board_clk() Dmitry Baryshkov
2023-01-11  4:47 ` Bjorn Andersson
2023-01-11  4:49   ` Dmitry Baryshkov
2023-01-17  3:30     ` Bjorn Andersson [this message]
2023-01-17 23:01       ` Dmitry Baryshkov

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=20230117033003.ky2i7fc2l72rhysd@builder.lan \
    --to=andersson@kernel.org \
    --cc=agross@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=quic_tdas@quicinc.com \
    --cc=sboyd@kernel.org \
    /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