linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <ansuelsmth@gmail.com>
To: "'Stephen Boyd'" <sboyd@kernel.org>, "'Andy Gross'" <agross@kernel.org>
Cc: "'Mathieu Olivari'" <mathieu@codeaurora.org>,
	"'Bjorn Andersson'" <bjorn.andersson@linaro.org>,
	"'Rob Herring'" <robh+dt@kernel.org>,
	"'Mark Rutland'" <mark.rutland@arm.com>,
	"'Michael Turquette'" <mturquette@baylibre.com>,
	<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>
Subject: R: [PATCH v2] ARM: qcom: Disable i2c device on gsbi4 for ipq806x
Date: Fri, 3 Apr 2020 03:39:04 +0200	[thread overview]
Message-ID: <00f701d60958$a9ed46c0$fdc7d440$@gmail.com> (raw)
In-Reply-To: <158587766752.125146.7582840761926137726@swboyd.mtv.corp.google.com>



> -----Messaggio originale-----
> Da: Stephen Boyd <sboyd@kernel.org>
> Inviato: venerdì 3 aprile 2020 03:34
> A: Andy Gross <agross@kernel.org>; Ansuel Smith
> <ansuelsmth@gmail.com>
> Cc: Ansuel Smith <ansuelsmth@gmail.com>; Mathieu Olivari
> <mathieu@codeaurora.org>; Bjorn Andersson
> <bjorn.andersson@linaro.org>; Rob Herring <robh+dt@kernel.org>; Mark
> Rutland <mark.rutland@arm.com>; Michael Turquette
> <mturquette@baylibre.com>; linux-arm-msm@vger.kernel.org;
> devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
> clk@vger.kernel.org
> Oggetto: Re: [PATCH v2] ARM: qcom: Disable i2c device on gsbi4 for
> ipq806x
> 
> Quoting Ansuel Smith (2020-03-30 13:56:46)
> > diff --git a/drivers/clk/qcom/gcc-ipq806x.c b/drivers/clk/qcom/gcc-
> ipq806x.c
> > index b0eee0903807..f7d7a2bc84c1 100644
> > --- a/drivers/clk/qcom/gcc-ipq806x.c
> > +++ b/drivers/clk/qcom/gcc-ipq806x.c
> > @@ -991,6 +991,7 @@ static struct clk_branch gsbi4_h_clk = {
> >                 .hw.init = &(struct clk_init_data){
> >                         .name = "gsbi4_h_clk",
> >                         .ops = &clk_branch_ops,
> > +                       .flags = CLK_IGNORE_UNUSED,
> 
> Is this necessary? Shouldn't we skip clks that are protected during the
> unused phase?
> 

gsbi4_h_clk is not protected. gsbi4_h_clk needs to not be disabled if unused
(as it's used by rpm) but can't be protected since it's used by uart gsbi4.
(With some test protecting also this clk cause the malfunction of uart gsb4)

> >                 },
> >         },
> >  };
> > --
> > 2.25.1
> >


  reply	other threads:[~2020-04-03  1:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30 20:56 [PATCH v2] ARM: qcom: Disable i2c device on gsbi4 for ipq806x Ansuel Smith
2020-04-03  1:34 ` Stephen Boyd
2020-04-03  1:39   ` ansuelsmth [this message]
2020-04-05  3:10     ` R: " Stephen Boyd
2020-04-15 23:12       ` R: " ansuelsmth

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='00f701d60958$a9ed46c0$fdc7d440$@gmail.com' \
    --to=ansuelsmth@gmail.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu@codeaurora.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).