[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190818011044.B21742173B@mail.kernel.org>
Date: Sat, 17 Aug 2019 18:10:43 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Jeffrey Hugo <jeffrey.l.hugo@...il.com>, mturquette@...libre.com
Cc: agross@...nel.org, david.brown@...aro.org,
bjorn.andersson@...aro.org, robh+dt@...nel.org,
mark.rutland@....com, marc.w.gonzalez@...e.fr,
jcrouse@...eaurora.org, linux-arm-msm@...r.kernel.org,
linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Jeffrey Hugo <jeffrey.l.hugo@...il.com>
Subject: Re: [PATCH v3 1/2] clk: qcom: Add MSM8998 GPU Clock Controller (GPUCC) driver
Quoting Jeffrey Hugo (2019-06-11 12:20:49)
> +
> +static int gpucc_msm8998_probe(struct platform_device *pdev)
> +{
> + struct regmap *regmap;
> + struct clk *xo;
> +
> + /*
> + * We must have a valid XO to continue until orphan probe defer is
> + * implemented. XO is basically the root of everything. Since we
> + * cannot control probe order, its possible XO won't be available
> + * and the clk framework will allow clients to operate on their
> + * clocks that depend on XO, which has been observed to cause issues.
> + */
> + xo = clk_get(&pdev->dev, "xo");
Sorry, it still bothers me. Please remove any clk consumer API calls in
these MSM8998 drivers and don't put XO into DT for these nodes until the
"observed issues" are resolved with the clk framework.
> + if (IS_ERR(xo))
Powered by blists - more mailing lists