From: Mike Turquette <mturquette@linaro.org>
Cc: devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
sboyd@codeaurora.org, linux-kernel@vger.kernel.org,
Kumar Gala <galak@codeaurora.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: qcom: Various fixes for MSM8960's global clock controller
Date: Mon, 28 Apr 2014 23:51:14 -0700 [thread overview]
Message-ID: <20140429065114.7224.13620@quantum> (raw)
In-Reply-To: <1396629176-7413-1-git-send-email-galak@codeaurora.org>
Quoting Kumar Gala (2014-04-04 09:32:56)
> * Remove CE2_SLEEP_CLK, doesn't exist on 8960 family SoCs
> * Fix incorrect offset for PMIC_SSBI2_RESET
> * Fix typo:
> SIC_TIC -> SPS_TIC_H
> SFAB_ADM0_M2_A_CLK -> SFAB_ADM0_M2_H_CLK
> * Fix naming convention:
> SFAB_CFPB_S_HCLK -> SFAB_CFPB_S_H_CLK
> SATA_SRC_CLK -> SATA_CLK_SRC
I'll take these through clk-next instead of clk-fixes since there is no
mention of a regression.
<snip>
> diff --git a/include/dt-bindings/clock/qcom,gcc-msm8960.h b/include/dt-bindings/clock/qcom,gcc-msm8960.h
> index 03bbf49..f9f5471 100644
> --- a/include/dt-bindings/clock/qcom,gcc-msm8960.h
> +++ b/include/dt-bindings/clock/qcom,gcc-msm8960.h
> @@ -51,7 +51,7 @@
> #define QDSS_TSCTR_CLK 34
> #define SFAB_ADM0_M0_A_CLK 35
> #define SFAB_ADM0_M1_A_CLK 36
> -#define SFAB_ADM0_M2_A_CLK 37
> +#define SFAB_ADM0_M2_H_CLK 37
Technically these changes break backwards compatibility, but I guess
that field updates to newer kernel images for this SoC are not a
concern?
Thanks,
Mike
next prev parent reply other threads:[~2014-04-29 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 16:32 [PATCH] clk: qcom: Various fixes for MSM8960's global clock controller Kumar Gala
2014-04-04 18:18 ` Stephen Boyd
2014-04-29 6:51 ` Mike Turquette [this message]
2014-04-30 15:53 ` Stephen Boyd
2014-04-30 19:14 ` Mike Turquette
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=20140429065114.7224.13620@quantum \
--to=mturquette@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@codeaurora.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).