From: Alex Courbot <acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Peter De Schrijver
<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Prashant Gaikwad
<pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2] ARM: tegra: switch FUSE clock on before usage
Date: Fri, 22 Nov 2013 10:35:42 +0900 [thread overview]
Message-ID: <528EB4EE.309@nvidia.com> (raw)
In-Reply-To: <528E6D58.6050503-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On 11/22/2013 05:30 AM, Stephen Warren wrote:
> 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.
Thanks. Be careful as I noticed I misformatted my commit message. The
part after the "--" will not be stripped by git am as I intended it to
be. I understood what I did wrong and will hopefully not make that
mistake again.
Sorry for the inconvenience.
WARNING: multiple messages have this Message-ID (diff)
From: acourbot@nvidia.com (Alex Courbot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: tegra: switch FUSE clock on before usage
Date: Fri, 22 Nov 2013 10:35:42 +0900 [thread overview]
Message-ID: <528EB4EE.309@nvidia.com> (raw)
In-Reply-To: <528E6D58.6050503@wwwdotorg.org>
On 11/22/2013 05:30 AM, Stephen Warren wrote:
> 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.
Thanks. Be careful as I noticed I misformatted my commit message. The
part after the "--" will not be stripped by git am as I intended it to
be. I understood what I did wrong and will hopefully not make that
mistake again.
Sorry for the inconvenience.
WARNING: multiple messages have this Message-ID (diff)
From: Alex Courbot <acourbot@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>,
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-arm-kernel@lists.infradead.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: tegra: switch FUSE clock on before usage
Date: Fri, 22 Nov 2013 10:35:42 +0900 [thread overview]
Message-ID: <528EB4EE.309@nvidia.com> (raw)
In-Reply-To: <528E6D58.6050503@wwwdotorg.org>
On 11/22/2013 05:30 AM, Stephen Warren wrote:
> 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.
Thanks. Be careful as I noticed I misformatted my commit message. The
part after the "--" will not be stripped by git am as I intended it to
be. I understood what I did wrong and will hopefully not make that
mistake again.
Sorry for the inconvenience.
next prev parent reply other threads:[~2013-11-22 1:35 UTC|newest]
Thread overview: 17+ 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 2:40 ` Alexandre Courbot
2013-11-21 2:40 ` Alexandre Courbot
2013-11-21 20:30 ` Stephen Warren
2013-11-21 20:30 ` Stephen Warren
[not found] ` <528E6D58.6050503-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-22 1:35 ` Alex Courbot [this message]
2013-11-22 1:35 ` Alex Courbot
2013-11-22 1:35 ` Alex Courbot
[not found] ` <528EB4EE.309-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-12-04 7:09 ` Alexandre Courbot
2013-12-04 7:09 ` Alexandre Courbot
2013-12-04 7:09 ` Alexandre Courbot
[not found] ` <CAAVeFuJpHXCANRO=AT5mKGpHzJRpmQoOuX4hjsctEMMAMjgqnQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-12-04 16:57 ` Stephen Warren
2013-12-04 16:57 ` Stephen Warren
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
2013-12-04 19:36 ` Stephen Warren
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=528EB4EE.309@nvidia.com \
--to=acourbot-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.