From: Sai Pavan Boddu <sai.pavan.boddu@xilinx.com>
To: "Edgar E . Iglesias" <edgar.iglesias@gmail.com>,
Alistair Francis <alistair@alistair23.me>,
Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <anthony@codemonkey.ws>,
afaerber@suse.de
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: [PATCH v3 0/3] Fix number of priority bits for arm boards
Date: Mon, 24 Feb 2020 15:09:21 +0530 [thread overview]
Message-ID: <1582537164-764-1-git-send-email-sai.pavan.boddu@xilinx.com> (raw)
This patch series implements the mask for unimplemented priority bits in
arm-gic. Which will return the expected number of priority bits on read.
Changes for V2:
Followed gicv3 code for defining mask for unimplemented bits
Hardcoded num priority bits for A9 and ARM11MPCore boards
Changes for V3:
Fixed the code as suggested in V1.
Implemented checks for max and min priority bits.
Sai Pavan Boddu (3):
arm_gic: Mask the un-supported priority bits
cpu/a9mpcore: Set number of GIC priority bits to 5
cpu/arm11mpcore: Set number of GIC priority bits to 4
hw/cpu/a9mpcore.c | 4 ++++
hw/cpu/arm11mpcore.c | 5 +++++
hw/intc/arm_gic.c | 33 +++++++++++++++++++++++++++++++--
hw/intc/arm_gic_common.c | 1 +
include/hw/intc/arm_gic.h | 2 ++
include/hw/intc/arm_gic_common.h | 1 +
6 files changed, 44 insertions(+), 2 deletions(-)
--
2.7.4
next reply other threads:[~2020-02-24 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 9:39 Sai Pavan Boddu [this message]
2020-02-24 9:39 ` [PATCH v3 1/3] arm_gic: Mask the un-supported priority bits Sai Pavan Boddu
2020-02-24 9:39 ` [PATCH v3 2/3] cpu/a9mpcore: Set number of GIC priority bits to 5 Sai Pavan Boddu
2020-02-24 9:39 ` [PATCH v3 3/3] cpu/arm11mpcore: Set number of GIC priority bits to 4 Sai Pavan Boddu
2020-02-25 13:03 ` [PATCH v3 0/3] Fix number of priority bits for arm boards Peter Maydell
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=1582537164-764-1-git-send-email-sai.pavan.boddu@xilinx.com \
--to=sai.pavan.boddu@xilinx.com \
--cc=afaerber@suse.de \
--cc=alistair@alistair23.me \
--cc=anthony@codemonkey.ws \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).