linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Suzuki.Poulose@arm.com (Suzuki K Poulose)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] arm64: cpuinfo: Expose MIDR_EL1 and REVIDR_EL1 to sysfs
Date: Mon, 13 Jun 2016 18:40:45 +0100	[thread overview]
Message-ID: <575EF01D.4020203@arm.com> (raw)
In-Reply-To: <20160613172616.GC17128@leverpostej>

On 13/06/16 18:26, Mark Rutland wrote:
> On Mon, Jun 13, 2016 at 06:08:09PM +0100, Suzuki K Poulose wrote:
>> +/*
>> + * Both MIDR_EL1 and REVIDR_EL1 are 32bit registers. However, per C5.1.1,
>> + * "Principles of the System instruction class encoding" in ARM DDI 0487A.i,
>> + * when a system register is escribed as 32-bit, this only means that the
>> + * upper 32 bits are RES0, not that they will never be made use of. To avoid
>> + * changing the ABI for the future, the values are exported as 64bit values.
>> + */
>
> I see this is a direct copy+paste of my earlier message, typo and all.

>
> I'd prefer something like the below:
>
> /*
>   * The ARM ARM uses the phrase "32-bit register" to describe a register
>   * whose upper 32 bits are RES0 (per C5.1.1, ARM DDI 0487A.i), however
>   * no statement is made as to whether the upper 32 bits will or will not
>   * be made use of in future, and between ARM DDI 0487A.c and ARM DDI
>   * 0487A.d CLIDR_EL1 was expanded from 32-bit to 64-bit.
>   *
>   * Thus, while both MIDR_EL1 and REVIDR_EL1 are described as 32-bit
>   * registers, we expose them both as 64 bit values to cater for possible
>   * future expansion without an ABI break.
>   */

Sorry about that, will fix it.

      reply	other threads:[~2016-06-13 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 17:08 [PATCH v4] arm64: cpuinfo: Expose MIDR_EL1 and REVIDR_EL1 to sysfs Suzuki K Poulose
2016-06-13 17:21 ` Russell King - ARM Linux
2016-06-14 11:01   ` Catalin Marinas
2016-06-13 17:26 ` Mark Rutland
2016-06-13 17:40   ` Suzuki K Poulose [this message]

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=575EF01D.4020203@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).