From: Thierry Reding <thierry.reding@gmail.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Dmitry Osipenko <digetx@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Michael Turquette <mturquette@baylibre.com>,
Nicolas Chauvet <kwizart@gmail.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
linux-tegra@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] clk: tegra: Fix duplicated SE clock entry
Date: Thu, 10 Dec 2020 09:03:00 +0100 [thread overview]
Message-ID: <X9HWNLZKVRUJja9G@ulmo> (raw)
In-Reply-To: <160756363099.1580929.2375956922093495697@swboyd.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
On Wed, Dec 09, 2020 at 05:27:10PM -0800, Stephen Boyd wrote:
> Quoting Dmitry Osipenko (2020-10-25 15:42:12)
> > The periph_clks[] array contains duplicated entry for Security Engine
> > clock which was meant to be defined for T210, but it wasn't added
> > properly. This patch corrects the T210 SE entry and fixes the following
> > error message on T114/T124: "Tegra clk 127: register failed with -17".
> >
> > Fixes: dc37fec48314 ("clk: tegra: periph: Add new periph clks and muxes for Tegra210")
> > Tested-by Nicolas Chauvet <kwizart@gmail.com>
> > Reported-by Nicolas Chauvet <kwizart@gmail.com>
> > Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> > ---
>
> Looks correct. Should I pick this up Thierry?
Yes, please. Thanks for catching this, it had slipped through my filter.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-12-10 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 22:42 [PATCH v1] clk: tegra: Fix duplicated SE clock entry Dmitry Osipenko
2020-12-10 1:27 ` Stephen Boyd
2020-12-10 8:03 ` Thierry Reding [this message]
2020-12-10 8:02 ` Thierry Reding
2020-12-10 20:52 ` Stephen Boyd
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=X9HWNLZKVRUJja9G@ulmo \
--to=thierry.reding@gmail.com \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kwizart@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=sboyd@kernel.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).