From: Stephen Boyd <swboyd@chromium.org>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Andy Gross <andy.gross@linaro.org>,
David Airlie <airlied@linux.ie>,
David Brown <david.brown@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Clark <robdclark@gmail.com>, Rob Herring <robh+dt@kernel.org>,
Archit Taneja <architt@codeaurora.org>,
Sean Paul <seanpaul@chromium.org>,
Rajesh Yadav <ryadav@codeaurora.org>,
Douglas Anderson <dianders@chromium.org>,
Jeykumar Sankaran <jsanka@codeaurora.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 4/8] drm/msm/dsi: 14nm PHY: Get ref clock from the DT
Date: Wed, 19 Dec 2018 14:32:19 -0800 [thread overview]
Message-ID: <154525873917.79149.9742850766307036349@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20181219222222.GA261387@google.com>
Quoting Matthias Kaehlcke (2018-12-19 14:22:22)
> On Mon, Dec 10, 2018 at 07:51:19AM -0800, Stephen Boyd wrote:
> > Quoting Matthias Kaehlcke (2018-12-04 14:42:30)
> > > diff --git a/drivers/gpu/drm/msm/dsi/pll/dsi_pll_14nm.c b/drivers/gpu/drm/msm/dsi/pll/dsi_pll_14nm.c
> > > index 71fe60e5f01f1..032bf3e8614bd 100644
> > > --- a/drivers/gpu/drm/msm/dsi/pll/dsi_pll_14nm.c
> > > +++ b/drivers/gpu/drm/msm/dsi/pll/dsi_pll_14nm.c
> > > @@ -40,7 +40,6 @@
> > >
> > > #define NUM_PROVIDED_CLKS 2
> > >
> > > -#define VCO_REF_CLK_RATE 19200000
> > > #define VCO_MIN_RATE 1300000000UL
> > > #define VCO_MAX_RATE 2600000000UL
> > >
> > > @@ -139,6 +138,7 @@ struct dsi_pll_14nm {
> > > /* protects REG_DSI_14nm_PHY_CMN_CLK_CFG0 register */
> > > spinlock_t postdiv_lock;
> > >
> > > + struct clk *vco_ref_clk;
> >
> > Is there any need to keep it in the struct? Or just get the clk, find
> > the rate, and then put the clk and call pll_14nm_postdiv_register()?
>
> I suppose you mean passing the clock name to pll_14nm_register()?
Yes, whatever makes it possible to avoid storing the pointer in the
struct.
>
> Is putting the clock really needed or preferable, or is it just fine
> to auto-put it when the device is deleted?
Up to you. If you don't have a need for the clk anymore it seems fine to
just put the clk and be done.
next prev parent reply other threads:[~2018-12-19 22:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 22:42 [PATCH v4 0/8] drm/msm/dsi: Get PHY ref clocks from the DT Matthias Kaehlcke
2018-12-04 22:42 ` [PATCH v4 1/8] dt-bindings: msm/dsi: Add ref clock for PHYs Matthias Kaehlcke
2018-12-07 23:18 ` Rob Herring
2018-12-04 22:42 ` [PATCH v4 2/8] drm/msm/dsi: 28nm 8960 PHY: Get ref clock from the DT Matthias Kaehlcke
2018-12-10 15:47 ` Stephen Boyd
2018-12-04 22:42 ` [PATCH v4 3/8] drm/msm/dsi: 28nm " Matthias Kaehlcke
2018-12-10 15:48 ` Stephen Boyd
2018-12-12 22:07 ` Niklas Cassel
2018-12-19 20:57 ` Matthias Kaehlcke
2018-12-04 22:42 ` [PATCH v4 4/8] drm/msm/dsi: 14nm " Matthias Kaehlcke
2018-12-10 15:51 ` Stephen Boyd
2018-12-19 22:22 ` Matthias Kaehlcke
2018-12-19 22:32 ` Stephen Boyd [this message]
2018-12-04 22:42 ` [PATCH v4 5/8] drm/msm/dsi: 10nm " Matthias Kaehlcke
2018-12-10 15:52 ` Stephen Boyd
2018-12-04 22:42 ` [PATCH v4 6/8] arm64: dts: qcom: msm8916: Set 'xo_board' as ref clock of the DSI PHY Matthias Kaehlcke
2018-12-04 22:42 ` [PATCH v4 7/8] arm64: dts: sdm845: Set 'bi_tcxo' as ref clock of the DSI PHYs Matthias Kaehlcke
2018-12-04 22:42 ` [PATCH v4 8/8] ARM: dts: qcom-apq8064: Set 'xo_board' as ref clock of the DSI PHY Matthias Kaehlcke
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=154525873917.79149.9742850766307036349@swboyd.mtv.corp.google.com \
--to=swboyd@chromium.org \
--cc=airlied@linux.ie \
--cc=andy.gross@linaro.org \
--cc=architt@codeaurora.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jsanka@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=ryadav@codeaurora.org \
--cc=seanpaul@chromium.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).