From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Ryan Roberts <ryan.roberts@arm.com>,
kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 1/2] arm64/sysreg: Update TCR_EL1 register
Date: Tue, 9 Sep 2025 09:20:26 +0530 [thread overview]
Message-ID: <bfe55fd9-e00f-44a8-bf4f-0b0a6cfc16bb@arm.com> (raw)
In-Reply-To: <a195095c-8ebd-4d74-959b-7b407d416a1f@sirena.org.uk>
On 08/09/25 7:28 PM, Mark Brown wrote:
> On Sun, Sep 07, 2025 at 05:59:59PM +0530, Anshuman Khandual wrote:
>
>> Update TCR_EL1 register fields as per latest ARM ARM DDI 0487 L.B and while
>> here drop an explicit sysreg definition SYS_TCR_EL1 from sysreg.h, which is
>> now redundant.
>
> I actually checked against DDI0601 2025-06 to spare my poor machine the
> strain of loading the ARM.
Right, they are the same.
>
> Reviewed-by: Mark Brown <broonie@kernel.org>
Thanks !
>
> I guess the cleanup of the redundant definition could've been a separate
> patch but it's not super important.
Dropping SYS_TCR_EL1 definition from header (asm/sysreg.h)
into a separate patch ?
#define SYS_TCR_EL1 sys_reg(3, 0, 2, 0, 2)
next prev parent reply other threads:[~2025-09-09 6:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 12:29 [PATCH V4 0/2] arm64/sysreg: Clean up TCR_EL1 field macros Anshuman Khandual
2025-09-07 12:29 ` [PATCH V4 1/2] arm64/sysreg: Update TCR_EL1 register Anshuman Khandual
2025-09-08 13:58 ` Mark Brown
2025-09-09 3:50 ` Anshuman Khandual [this message]
2025-09-09 11:22 ` Mark Brown
2025-09-07 12:30 ` [PATCH V4 2/2] arm64/sysreg: Replace TCR_EL1 field macros Anshuman Khandual
2025-09-18 12:08 ` Will Deacon
2025-09-19 9:22 ` Anshuman Khandual
2025-09-15 2:24 ` [PATCH V4 0/2] arm64/sysreg: Clean up " Anshuman Khandual
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=bfe55fd9-e00f-44a8-bf4f-0b0a6cfc16bb@arm.com \
--to=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox