From: Stephen Boyd <sboyd@codeaurora.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: clock: tegra: Add sor1_out clock
Date: Fri, 3 Nov 2017 08:16:44 -0700 [thread overview]
Message-ID: <20171103151644.GT11011@codeaurora.org> (raw)
In-Reply-To: <20171102084605.GA29341@ulmo>
On 11/02, Thierry Reding wrote:
> On Thu, Nov 02, 2017 at 01:16:48AM -0700, Stephen Boyd wrote:
> > On 09/01, Thierry Reding wrote:
> > > From: Thierry Reding <treding@nvidia.com>
> > >
> > > The sor1_src clock implemented on Tegra210 is modelled the wrong way
> > > around, which causes some issues with HDMI and DP support. This clock
> > > implementation is provided by BPMP on Tegra186, which models this in
> > > a more correct way. Since this introduces incompatibilities between
> > > the two SoC generations which we want to avoid, the Tegra210 will be
> > > fixed in subsequent patches.
> > >
> > > This change adds sor1_out as an alias for sor1_src.
> > >
> > > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > > ---
> >
> > Applied to clk-next
>
> Hi Stephen,
>
> sorry for not having been clear about this. This patch and the 2-4 are
> part of the pull request I sent out earlier (and for which I have an
> updated one to fix the regression I mentioned last week). I'd prefer to
> send this to you via pull request because there is a dependency on this
> from the ARM SoC tree (for a DT change).
>
Sure I can back out the changes. Next time please indicate your
merge path/strategy in some sort of cover letter so I can ignore
changes in the review queue. Also, if you pick up a patch from
the list please send a note that you applied it to your tree so I
know to wait for a PR later.
Is the PR coming soon? I forgot about it because we were waiting
for the second one.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-11-03 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 14:53 [PATCH 1/4] dt-bindings: clock: tegra: Add sor1_out clock Thierry Reding
2017-09-01 14:53 ` [PATCH 2/4] clk: tegra: Add peripheral clock registration helper Thierry Reding
2017-11-02 8:16 ` Stephen Boyd
2017-09-01 14:53 ` [PATCH 3/4] clk: tegra: Use tegra_clk_register_periph_data() Thierry Reding
2017-11-02 8:16 ` Stephen Boyd
2017-09-01 14:53 ` [PATCH 4/4] clk: tegra: Fix sor1_out clock implementation Thierry Reding
2017-11-02 8:16 ` Stephen Boyd
2017-11-02 8:16 ` [PATCH 1/4] dt-bindings: clock: tegra: Add sor1_out clock Stephen Boyd
2017-11-02 8:46 ` Thierry Reding
2017-11-03 15:16 ` Stephen Boyd [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=20171103151644.GT11011@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=thierry.reding@gmail.com \
/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).