All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: linux-arm-msm@vger.kernel.org, Petr Vorel <petr.vorel@gmail.com>
Cc: Konrad Dybcio <konradybcio@gmail.com>,
	Taniya Das <tdas@codeaurora.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Douglas Anderson <dianders@chromium.org>,
	Andy Gross <agross@kernel.org>,
	linux-mmc@vger.kernel.org, Jean Thomas <virgule@jeanthomas.me>,
	Alexey Minnekhanov <alexeymin@postmarketos.org>
Subject: Re: (subset) [PATCH 0/6] msm8994-huawei-angler and msm8992-lg-bullhead sdhc1 fixes
Date: Mon, 31 Jan 2022 23:19:54 -0600	[thread overview]
Message-ID: <164369277345.3095904.15450214704701068210.b4-ty@linaro.org> (raw)
In-Reply-To: <20220113233358.17972-1-petr.vorel@gmail.com>

On Fri, 14 Jan 2022 00:33:52 +0100, Petr Vorel wrote:
> Besides fixing sdhc1 for msm8994-huawei-angler and msm8992-lg-bullhead
> I also rebased and reposted Jean's patches (Makefile didn't apply on
> current for-next) and also rename angler's DTS.
> 
> sdhc1 (i.e. mmc0) is working on both, but there are overclocking
> warnings. I suspected issue similar to using clk_rcg2_ops instead of
> clk_rcg2_floor_ops (i.e. 3f905469c8ce ("clk: qcom: gcc: Use floor ops
> for SDCC clocks") or 148ddaa89d4a ("clk: qcom: gcc-sc7180: Use floor ops
> for the correct sdcc1 clk"), but it looks to be correct for gcc-msm8994.c.
> 
> [...]

Applied, thanks!

[3/6] arm64: dts: qcom: msm8994: Provide missing "xo_board" and "sleep_clk" to GCC
      commit: 4dd1ad6192748523878463a285346db408b34a02
[4/6] arm64: dts: qcom: msm8994-huawei-angler: Add vendor name huawei
      commit: 8af90d6daa36a7180a2cd6aad874136aade27412

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

      parent reply	other threads:[~2022-02-01  5:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 23:33 [PATCH 0/6] msm8994-huawei-angler and msm8992-lg-bullhead sdhc1 fixes Petr Vorel
2022-01-13 23:33 ` [PATCH 1/6] arm64: dts: qcom: msm8992-lg-bullhead: Place LG Bullhead generic code into a DTSI file Petr Vorel
2022-01-13 23:33 ` [PATCH 2/6] arm64: dts: qcom: msm8992-lg-bullhead: Add support for LG Bullhead rev 1.0 Petr Vorel
2022-01-13 23:33 ` [PATCH 3/6] arm64: dts: qcom: msm8994: Provide missing "xo_board" and "sleep_clk" to GCC Petr Vorel
2022-01-13 23:33 ` [PATCH 4/6] arm64: dts: qcom: msm8994-huawei-angler: Add vendor name huawei Petr Vorel
2022-01-13 23:33 ` [PATCH 5/6] arm64: dts: qcom: msm8994-huawei-angler: Add sdhc{1,2} definitions Petr Vorel
2022-01-13 23:40   ` Petr Vorel
2022-01-14 18:27     ` Konrad Dybcio
2022-01-14 21:16       ` Petr Vorel
2022-01-14 21:19         ` Konrad Dybcio
2022-01-31 22:43   ` Bjorn Andersson
2022-01-31 22:46     ` Petr Vorel
2022-01-13 23:33 ` [PATCH 6/6] arm64: dts: qcom: msm8992-lg-bullhead: Disable sdhc2 Petr Vorel
2022-01-31 21:00 ` [PATCH 0/6] msm8994-huawei-angler and msm8992-lg-bullhead sdhc1 fixes patchwork-bot+linux-arm-msm
2022-02-01  5:19 ` 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=164369277345.3095904.15450214704701068210.b4-ty@linaro.org \
    --to=bjorn.andersson@linaro.org \
    --cc=agross@kernel.org \
    --cc=alexeymin@postmarketos.org \
    --cc=dianders@chromium.org \
    --cc=konradybcio@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=petr.vorel@gmail.com \
    --cc=tdas@codeaurora.org \
    --cc=ulf.hansson@linaro.org \
    --cc=virgule@jeanthomas.me \
    /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.