mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: sboyd@kernel.org, Bjorn Andersson <andersson@kernel.org>,
	iskren.chernev@gmail.com
Cc: konrad.dybcio@somainline.org,
	~postmarketos/upstreaming@lists.sr.ht, a_skl39@protonmail.com,
	linux-clk@vger.kernel.org, mturquette@baylibre.com,
	phone-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, agross@kernel.org
Subject: Re: [PATCH 0/3] Merge non-standard qcom clk PLL offsets
Date: Mon, 26 Sep 2022 22:23:01 -0500	[thread overview]
Message-ID: <166424897977.1766486.8297085520259468743.b4-ty@kernel.org> (raw)
In-Reply-To: <20220830075620.974009-1-iskren.chernev@gmail.com>

On Tue, 30 Aug 2022 10:56:17 +0300, Iskren Chernev wrote:
> Both the qcm2290 and sm6115 gcc drivers need a non-standard Alpha PLL register
> map for DEFAULT and BRAMMO types.
> 
> The initial gcc-sm6115 was lacking the DEFAULT override, so fix that first,
> then merge the two overrides by using newly created DEFAULT_EVO and BRAMMO_EVO
> types.
> 
> [...]

Applied, thanks!

[1/3] clk: qcom: gcc-sm6115: Override default Alpha PLL regs
      commit: 068a0605ef5a6b430e7278c169bfcd25b680b28f
[2/3] clk: qcom: gcc-sm6115: Move alpha pll bramo overrides
      commit: 65f1fa35aa70b9e5abfd184ce3078c9aa93a1cb4
[3/3] clk: qcom: Merge alt alpha plls for qcm2260, sm6115
      commit: 9e48f0519bae644d91c85d0a99ea5887688e4bd5

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2022-09-27  3:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30  7:56 Iskren Chernev
2022-08-30  7:56 ` [PATCH 1/3] clk: qcom: gcc-sm6115: Override default Alpha PLL regs Iskren Chernev
2022-08-30  7:56 ` [PATCH 2/3] clk: qcom: gcc-sm6115: Move alpha pll bramo overrides Iskren Chernev
2022-08-30  7:56 ` [PATCH 3/3] clk: qcom: Merge alt alpha plls for qcm2260, sm6115 Iskren Chernev
2022-09-27  3:23 ` Bjorn Andersson [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=166424897977.1766486.8297085520259468743.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=a_skl39@protonmail.com \
    --cc=agross@kernel.org \
    --cc=iskren.chernev@gmail.com \
    --cc=konrad.dybcio@somainline.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=phone-devel@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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

all inboxes | Powered by JetHome®