From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Paul Mackerras <paulus@ozlabs.org>, linuxppc-dev@ozlabs.org
Subject: Re: [1/3] powerpc: Use feature bit for RTC presence rather than timebase presence
Date: Mon, 26 Mar 2018 19:56:59 +1100 (AEDT) [thread overview]
Message-ID: <408p180CQvz9s1l@ozlabs.org> (raw)
In-Reply-To: <1521495973-3237-2-git-send-email-paulus@ozlabs.org>
On Mon, 2018-03-19 at 21:46:11 UTC, Paul Mackerras wrote:
> All PowerPC CPUs other than the original PPC601 have a timebase
> register rather than the "real-time clock" (RTC) register that the
> PPC601 (and the original POWER and POWER2 CPUs) had. Currently
> we have a CPU feature bit to indicate the presence of the timebase,
> but it makes more sense to use a bit to indicate the unusual
> situation rather than the common situation. This therefore defines
> a CPU_FTR_USE_RTC bit in place of the CPU_FTR_USE_TB bit, and
> arranges for it to be set on PPC601 systems.
>
> Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/c0d64cf9fefd58831ce2cc81b2683b
cheers
next prev parent reply other threads:[~2018-03-26 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 21:46 [PATCH 0/3] powerpc: Free up CPU feature bits Paul Mackerras
2018-03-19 21:46 ` [PATCH 1/3] powerpc: Use feature bit for RTC presence rather than timebase presence Paul Mackerras
2018-03-26 8:56 ` Michael Ellerman [this message]
2018-03-19 21:46 ` [PATCH 2/3] powerpc: Book E: Remove unused CPU_FTR_L2CSR bit Paul Mackerras
2018-03-19 21:46 ` [PATCH 3/3] powerpc: Free up CPU feature bits on 64-bit machines Paul Mackerras
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=408p180CQvz9s1l@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@ozlabs.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;
as well as URLs for NNTP newsgroup(s).