From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] arm: omap2: timer: don't disable our timers
Date: Tue, 6 Oct 2015 01:00:29 -0700 [thread overview]
Message-ID: <20151006080028.GI23801@atomide.com> (raw)
In-Reply-To: <1444092332-9011-1-git-send-email-balbi@ti.com>
* Felipe Balbi <balbi@ti.com> [151005 17:49]:
> We actually want these devices to be created because
> we will be moving timers to drivers/clocksource and
> this will prevent them from probing.
Great. Is this safe to appy on it's own? We are not getting
system timers re-inited to the default values?
> The only situation where we want secure timers to be
> actually disabled is when we *know* we're running on
> non-GP (read: HS or EMU) chips, because the secure
> timer will NOT be available for the public world.
Yup.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: omap2: timer: don't disable our timers
Date: Tue, 6 Oct 2015 01:00:29 -0700 [thread overview]
Message-ID: <20151006080028.GI23801@atomide.com> (raw)
In-Reply-To: <1444092332-9011-1-git-send-email-balbi@ti.com>
* Felipe Balbi <balbi@ti.com> [151005 17:49]:
> We actually want these devices to be created because
> we will be moving timers to drivers/clocksource and
> this will prevent them from probing.
Great. Is this safe to appy on it's own? We are not getting
system timers re-inited to the default values?
> The only situation where we want secure timers to be
> actually disabled is when we *know* we're running on
> non-GP (read: HS or EMU) chips, because the secure
> timer will NOT be available for the public world.
Yup.
Regards,
Tony
next prev parent reply other threads:[~2015-10-06 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 0:45 [PATCH v2] arm: omap2: timer: don't disable our timers Felipe Balbi
2015-10-06 0:45 ` Felipe Balbi
2015-10-06 8:00 ` Tony Lindgren [this message]
2015-10-06 8:00 ` Tony Lindgren
2015-10-06 15:00 ` Felipe Balbi
2015-10-06 15:00 ` Felipe Balbi
2015-10-06 16:09 ` Felipe Balbi
2015-10-06 16:09 ` Felipe Balbi
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=20151006080028.GI23801@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@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 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.