From: Vinod Koul <vkoul@kernel.org>
To: quic_vamslank@quicinc.com
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
mturquette@baylibre.com, sboyd@kernel.org, robh+dt@kernel.org,
tglx@linutronix.de, maz@kernel.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
manivannan.sadhasivam@linaro.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v4 3/6] clk: qcom: Add SDX65 GCC support
Date: Tue, 16 Nov 2021 14:03:02 +0530 [thread overview]
Message-ID: <YZNsvjwp0/AX0Hdo@matsya> (raw)
In-Reply-To: <b61d16ad890bcf07057f8fbd83dfffaf9812cda6.1637047731.git.quic_vamslank@quicinc.com>
On 15-11-21, 23:38, quic_vamslank@quicinc.com wrote:
> From: Vamsi Krishna Lanka <quic_vamslank@quicinc.com>
>
> Add Global Clock Controller (GCC) support for SDX65 SoCs from Qualcomm.
>
> Signed-off-by: Vamsi Krishna Lanka <quic_vamslank@quicinc.com>
> Reported-by: kernel test robot <lkp@intel.com>
Missing support reported ??
> +static struct clk_branch gcc_ahb_pcie_link_clk = {
> + .halt_reg = 0x2e004,
> + .halt_check = BRANCH_HALT,
> + .clkr = {
> + .enable_reg = 0x2e004,
> + .enable_mask = BIT(0),
> + .hw.init = &(struct clk_init_data){
> + .name = "gcc_ahb_pcie_link_clk",
> + .flags = CLK_IS_CRITICAL,
> + .ops = &clk_branch2_ops,
> + },
If this clk is critical then why model in linux, enable directly in probe
and leave it...?
> +static struct clk_branch gcc_pcie_0_clkref_en = {
> + .halt_reg = 0x88004,
> + .halt_check = BRANCH_HALT_DELAY,
Why delay, add a comment at least for that
> + .clkr = {
> + .enable_reg = 0x88004,
> + .enable_mask = BIT(0),
> + .hw.init = &(struct clk_init_data){
> + .name = "gcc_pcie_0_clkref_en",
> + .ops = &clk_branch2_ops,
> + },
> + },
> +};
> +
> +static struct clk_branch gcc_pcie_aux_clk = {
> + .halt_reg = 0x43034,
> + .halt_check = BRANCH_HALT_DELAY,
Here too
> +static struct clk_branch gcc_pcie_mstr_axi_clk = {
> + .halt_reg = 0x43024,
> + .halt_check = BRANCH_HALT_VOTED,
> + .hwcg_reg = 0x43024,
> + .hwcg_bit = 1,
> + .clkr = {
> + .enable_reg = 0x6d010,
> + .enable_mask = BIT(1),
> + .hw.init = &(struct clk_init_data){
> + .name = "gcc_pcie_mstr_axi_clk",
> + .ops = &clk_branch2_ops,
> + },
> + },
> +};
> +
> +static struct clk_branch gcc_pcie_pipe_clk = {
> + .halt_reg = 0x4303c,
> + .halt_check = BRANCH_HALT_DELAY,
here as well and few more places I guess
> +static struct clk_branch gcc_xo_pcie_link_clk = {
> + .halt_reg = 0x2e008,
> + .halt_check = BRANCH_HALT,
> + .hwcg_reg = 0x2e008,
> + .hwcg_bit = 1,
> + .clkr = {
> + .enable_reg = 0x2e008,
> + .enable_mask = BIT(0),
> + .hw.init = &(struct clk_init_data){
> + .name = "gcc_xo_pcie_link_clk",
> + .flags = CLK_IS_CRITICAL,
Here as well
--
~Vinod
next prev parent reply other threads:[~2021-11-16 8:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 7:38 [PATCH v4 0/6] Add Pdc, GCC and RPMh clock support for SDX65 quic_vamslank
2021-11-16 7:38 ` [PATCH v4 1/6] dt-bindings: clock: Add SDX65 GCC clock bindings quic_vamslank
2021-11-19 1:06 ` Rob Herring
2021-11-16 7:38 ` [PATCH v4 2/6] clk: qcom: Add LUCID_EVO PLL type for SDX65 quic_vamslank
2021-11-16 8:25 ` Vinod Koul
2021-11-18 1:54 ` Vamsi Krishna Lanka
2021-11-18 4:41 ` Vinod Koul
2021-11-16 7:38 ` [PATCH v4 3/6] clk: qcom: Add SDX65 GCC support quic_vamslank
2021-11-16 8:33 ` Vinod Koul [this message]
2021-11-18 1:51 ` Vamsi Krishna Lanka
2021-11-18 4:39 ` Vinod Koul
2021-11-18 5:04 ` Vamsi Krishna Lanka
2021-11-18 5:08 ` Vinod Koul
2021-11-16 7:38 ` [PATCH v4 4/6] dt-bindings: clock: Introduce RPMHCC bindings for SDX65 quic_vamslank
2021-11-16 8:34 ` Vinod Koul
2021-11-16 7:38 ` [PATCH v4 5/6] clk: qcom: Add support for SDX65 RPMh clocks quic_vamslank
2021-11-16 8:35 ` Vinod Koul
2021-11-16 7:38 ` [PATCH v4 6/6] dt-bindings: clock: Introduce pdc bindings for SDX65 quic_vamslank
2021-11-16 8:36 ` Vinod Koul
2021-11-16 8:33 ` [PATCH v4 0/6] Add Pdc, GCC and RPMh clock support " Vinod Koul
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=YZNsvjwp0/AX0Hdo@matsya \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=maz@kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_vamslank@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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