From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexandre Courbot <acourbot@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: tegra: switch FUSE clock on before usage
Date: Thu, 21 Nov 2013 13:30:16 -0700 [thread overview]
Message-ID: <528E6D58.6050503@wwwdotorg.org> (raw)
In-Reply-To: <1385001613-19098-1-git-send-email-acourbot@nvidia.com>
On 11/20/2013 07:40 PM, Alexandre Courbot wrote:
> FUSE clock is enabled by most bootloaders, but we cannot expect it to be
> on in all contexts (e.g. kexec).
>
> Ensure the FUSE clock is enabled before any of its registers is touched.
> Since FUSE is touched very early during system boot (before the clock
> devices are registered), directly manipulate the clock register bit in
> case the clock device cannot be acquired.
This looks reasonable to me. I'll apply it soon after -rc1.
next prev parent reply other threads:[~2013-11-21 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 2:40 [PATCH v2] ARM: tegra: switch FUSE clock on before usage Alexandre Courbot
2013-11-21 20:30 ` Stephen Warren [this message]
[not found] ` <528E6D58.6050503-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-22 1:35 ` Alex Courbot
[not found] ` <528EB4EE.309-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-12-04 7:09 ` Alexandre Courbot
[not found] ` <CAAVeFuJpHXCANRO=AT5mKGpHzJRpmQoOuX4hjsctEMMAMjgqnQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-12-04 16:57 ` Stephen Warren
[not found] ` <1385001613-19098-1-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-12-04 19:36 ` Stephen Warren
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=528E6D58.6050503@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=acourbot@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@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).