From: Matthias Kaehlcke <mka@chromium.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Rajesh Yadav <ryadav@codeaurora.org>,
David Airlie <airlied@linux.ie>,
linux-arm-msm@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
David Brown <david.brown@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Sean Paul <seanpaul@chromium.org>,
Andy Gross <andy.gross@linaro.org>,
freedreno@lists.freedesktop.org
Subject: Re: [PATCH v3 8/8] ARM: dts: qcom-apq8064: Set 'xo_board' as ref clock of the DSI PHY
Date: Tue, 4 Dec 2018 09:16:21 -0800 [thread overview]
Message-ID: <20181204171621.GA14307@google.com> (raw)
In-Reply-To: <154394210277.88331.12250945038852318544@swboyd.mtv.corp.google.com>
On Tue, Dec 04, 2018 at 08:48:22AM -0800, Stephen Boyd wrote:
> Quoting Matthias Kaehlcke (2018-11-30 16:52:54)
> > Add 'xo_board' as ref clock for the DSI PHY, it was previously
> > hardcoded in the PLL 'driver' for the 28nm 8960 PHY.
>
> Why is driver in quotes?
It's not really a full fledged driver, but part of the 28nm 8960 PHY
driver.
> >
> > Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
>
> Reviewed-by: Stephen Boyd <swboyd@chromium.org>
Thanks for the review!
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-12-04 17:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 0:52 [PATCH v3 0/8] drm/msm/dsi: Get PHY ref clocks from the DT Matthias Kaehlcke
[not found] ` <20181201005254.139908-1-mka-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2018-12-01 0:52 ` [PATCH v3 1/8] dt-bindings: msm/dsi: Add ref clock for PHYs Matthias Kaehlcke
2018-12-04 16:37 ` Stephen Boyd
[not found] ` <20181201005254.139908-2-mka-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2018-12-04 17:15 ` Doug Anderson
2018-12-01 0:52 ` [PATCH v3 2/8] drm/msm/dsi: 28nm 8960 PHY: Get ref clock from the DT Matthias Kaehlcke
2018-12-04 16:44 ` Stephen Boyd
2018-12-04 17:35 ` Matthias Kaehlcke
2018-12-04 18:26 ` Stephen Boyd
2018-12-01 0:52 ` [PATCH v3 3/8] drm/msm/dsi: 28nm " Matthias Kaehlcke
2018-12-04 16:45 ` Stephen Boyd
2018-12-01 0:52 ` [PATCH v3 4/8] drm/msm/dsi: 14nm " Matthias Kaehlcke
2018-12-01 0:52 ` [PATCH v3 5/8] drm/msm/dsi: 10nm " Matthias Kaehlcke
2018-12-01 0:52 ` [PATCH v3 7/8] arm64: dts: sdm845: Set 'bi_tcxo' as ref clock of the DSI PHYs Matthias Kaehlcke
2018-12-04 16:47 ` Stephen Boyd
2018-12-01 0:52 ` [PATCH v3 6/8] arm64: dts: qcom: msm8916: Set 'xo_board' as ref clock of the DSI PHY Matthias Kaehlcke
2018-12-04 16:46 ` Stephen Boyd
2018-12-01 0:52 ` [PATCH v3 8/8] ARM: dts: qcom-apq8064: " Matthias Kaehlcke
[not found] ` <20181201005254.139908-9-mka-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2018-12-04 16:48 ` Stephen Boyd
2018-12-04 17:16 ` Matthias Kaehlcke [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=20181204171621.GA14307@google.com \
--to=mka@chromium.org \
--cc=airlied@linux.ie \
--cc=andy.gross@linaro.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=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=ryadav@codeaurora.org \
--cc=seanpaul@chromium.org \
--cc=swboyd@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).