All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Taniya Das <tdas@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	Rajendra Nayak <rnayak@codeaurora.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>
Subject: Re: [PATCH] clk: qcom: gcc-msm8996: Drop (again) gcc_aggre1_pnoc_ahb_clk
Date: Fri, 05 Nov 2021 15:29:46 -0700	[thread overview]
Message-ID: <20211105222947.A047A60EE9@mail.kernel.org> (raw)
In-Reply-To: <20211104011155.2209654-1-dmitry.baryshkov@linaro.org>

Quoting Dmitry Baryshkov (2021-11-03 18:11:55)
> The gcc_aggre1_pnoc_ahb_clk is crucial for the proper MSM8996/APQ8096
> functioning. If it gets disabled, several subsytems will stop working
> (including eMMC/SDCC and USB). There are no in-kernel users of this
> clock, so it is much simpler to remove from the kernel.
> 
> The clock was first removed in the commit 9e60de1cf270 ("clk: qcom:
> Remove gcc_aggre1_pnoc_ahb_clk from msm8996") by Stephen Boyd, but got
> added back in the commit b567752144e3 ("clk: qcom: Add some missing gcc
> clks for msm8996") by Rajendra Nayak.
> 
> Let's remove it again in hope that nobody adds it back.
> 
> Reported-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
> Cc: Rajendra Nayak <rnayak@codeaurora.org>
> Cc: Konrad Dybcio <konrad.dybcio@somainline.org>
> Fixes: b567752144e3 ("clk: qcom: Add some missing gcc clks for msm8996")
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---

Applied to clk-next

      reply	other threads:[~2021-11-05 22:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04  1:11 [PATCH] clk: qcom: gcc-msm8996: Drop (again) gcc_aggre1_pnoc_ahb_clk Dmitry Baryshkov
2021-11-05 22:29 ` Stephen Boyd [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=20211105222947.A047A60EE9@mail.kernel.org \
    --to=sboyd@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=rnayak@codeaurora.org \
    --cc=tdas@codeaurora.org \
    --cc=vladimir.zapolskiy@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.