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>,
	Jonathan Marek <jonathan@marek.ca>,
	Michael Turquette <mturquette@baylibre.com>,
	Rob Herring <robh+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	devicetree@vger.kernel.org
Subject: Re: [RFC 0/4] clk: qcom: handle power domains links for GDSC
Date: Wed, 30 Sep 2020 17:23:43 -0700	[thread overview]
Message-ID: <160151182386.310579.7297378317318019098@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20200911130950.578483-1-dmitry.baryshkov@linaro.org>

Quoting Dmitry Baryshkov (2020-09-11 06:09:46)
> On SM8250 MDSS_GDSC requires MMCX domain to be powered to access GDSC
> registers. Handle this requirement in the gdsc code by binding the power
> domain via dts file. The example in the schema file demonstrates this
> binding (which is not required for SDM845).
> 

Please Cc the linux-clk list on clk patches. It might be obvious now
that I don't always look at this email pile to fish out clk things.

      parent reply	other threads:[~2020-10-01  0:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11 13:09 [RFC 0/4] clk: qcom: handle power domains links for GDSC Dmitry Baryshkov
2020-09-11 13:09 ` [RFC 1/4] dt-bindings: clock: qcom,dispcc: document power domain bindings Dmitry Baryshkov
2020-09-22 22:56   ` Rob Herring
2020-09-11 13:09 ` [RFC 2/4] clk: qcom: gdsc: enable external switchable power domain Dmitry Baryshkov
2020-09-23 14:42   ` Bjorn Andersson
2020-09-11 13:09 ` [RFC 3/4] clk: qcom: dispcc-sm8250: handle MMCX " Dmitry Baryshkov
2020-09-11 13:09 ` [RFC 4/4] arm64: dts: qcom: sm8250: pin MMCX to stop the board from crashing Dmitry Baryshkov
2020-10-01  0:23 ` 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=160151182386.310579.7297378317318019098@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=jonathan@marek.ca \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@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 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.