public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Cc: dmitry.osipenko@collabora.com, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2] clk: tegra: Add missing reset deassertion
Date: Wed, 4 May 2022 11:24:29 +0200	[thread overview]
Message-ID: <YnJGTVQTrkoQvcMp@orome> (raw)
In-Reply-To: <20220429125843.neqitcrxc7ntjclk@diogo-laptop>

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

On Fri, Apr 29, 2022 at 01:58:43PM +0100, Diogo Ivo wrote:
> Commit 4782c0a5dd88e3797426e08c5c437e95a3156631 ("clk: tegra: Don't
> deassert reset on enabling clocks") removed deassertion of reset lines
> when enabling peripheral clocks. This breaks the initialization of the
> DFLL driver which relied on this behaviour.
> 
> Fix this problem by adding explicit deassert/assert requests to the
> driver and the corresponding reset to the DT. Tested on Google Pixel C.
> 
> Cc: stable@vger.kernel.org
> Fixes: 4782c0a5dd88 ("clk: tegra: Don't deassert reset on enabling clocks")
> Signed-off-by: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
> ---
> Changes in v2:
>  - Changed reset getter to the optional variant
> 
>  arch/arm64/boot/dts/nvidia/tegra210.dtsi |  5 +++--
>  drivers/clk/tegra/clk-dfll.c             | 12 ++++++++++++
>  2 files changed, 15 insertions(+), 2 deletions(-)

I've applied this, but in the process split it up into two: one patch
for the clock driver and another for the device tree changes. For future
patches, please keep in mind that driver and device tree changes should
always be separate.

Thanks,
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-05-04  9:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 12:58 [PATCH v2] clk: tegra: Add missing reset deassertion Diogo Ivo
2022-05-04  9:24 ` Thierry Reding [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=YnJGTVQTrkoQvcMp@orome \
    --to=thierry.reding@gmail.com \
    --cc=diogo.ivo@tecnico.ulisboa.pt \
    --cc=dmitry.osipenko@collabora.com \
    --cc=linux-tegra@vger.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