public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexandre Courbot <gnurou@gmail.com>, Alex Courbot <acourbot@nvidia.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
	Peter De Schrijver <pdeschrijver@nvidia.com>,
	Prashant Gaikwad <pgaikwad@nvidia.com>,
	"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: Wed, 04 Dec 2013 09:57:29 -0700	[thread overview]
Message-ID: <529F5EF9.5010707@wwwdotorg.org> (raw)
In-Reply-To: <CAAVeFuJpHXCANRO=AT5mKGpHzJRpmQoOuX4hjsctEMMAMjgqnQ@mail.gmail.com>

On 12/04/2013 12:09 AM, Alexandre Courbot wrote:
> Hi Stephen,
> 
> On Fri, Nov 22, 2013 at 10:35 AM, Alex Courbot <acourbot@nvidia.com> wrote:
>> 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.
> 
> I am not seeing this in your tree, have you applied it somewhere already?

I haven't applied anything for 3.14 yet. I was hoping to get the
DMA/clock/reset DT binding rework in first, but it's been dragging on
for while, so I'll probably take a look at what can be applied without
conflicting with that soon.


  reply	other threads:[~2013-12-04 16:57 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
2013-11-22  1:35   ` Alex Courbot
2013-12-04  7:09     ` Alexandre Courbot
2013-12-04 16:57       ` Stephen Warren [this message]
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=529F5EF9.5010707@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=acourbot@nvidia.com \
    --cc=gnurou@gmail.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