From: Shanker Donthineni <sdonthineni@nvidia.com>
To: Marc Zyngier <maz@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Vikram Sethi <vsethi@nvidia.com>, Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH v3] irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4
Date: Fri, 17 Mar 2023 23:11:32 -0500 [thread overview]
Message-ID: <9af4b672-29e9-0208-83f8-b10504186727@nvidia.com> (raw)
In-Reply-To: <20230317162636.851085-1-sdonthineni@nvidia.com>
Hi Marc,
On 3/17/23 11:26, Shanker Donthineni wrote:
> #define T241_CHIPN_MASK GENMASK_ULL(45, 44)
> +#define T241_CHIP_GICDA_OFFSET 0x1580000
> +#define SMCCC_SOC_ID_T241 0x036b0241
> +
> +static bool gic_enable_quirk_nvidia_t241(void *data)
> +{
> + s32 soc_id = arm_smccc_get_soc_id_version();
> + unsigned long chip_bmask = 0;
> + phys_addr_t phys;
> + u32 i;
> +
> + /* Check JEP106 code for NVIDIA T241 chip (036b:0241) */
> + if ((soc_id < 0) || (soc_id != SMCCC_SOC_ID_T241))
> + return false;
> +
> + /* Find the chips based on GICR regions PHYS addr */
> + for (i = 0; i < gic_data.nr_redist_regions; i++) {
> + chip_bmask |= BIT(FIELD_GET(T241_CHIPN_MASK,
> + gic_data.redist_regions[i].phys_base));
> + }
Apologies for the oversight on my part, I failed to address the build issue
for the 32-bit architecture and mistakenly submitted an incorrect patch.
Please ignore this patch and review v4 patch.
Correct change:
for (i = 0; i < gic_data.nr_redist_regions; i++) {
chip_bmask |= BIT(FIELD_GET(T241_CHIPN_MASK,
- gic_data.redist_regions[i].phys_base));
+ (u64)gic_data.redist_regions[i].phys_base));
-Shaker
prev parent reply other threads:[~2023-03-18 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 16:26 Shanker Donthineni
2023-03-18 0:57 ` kernel test robot
2023-03-18 4:11 ` Shanker Donthineni [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=9af4b672-29e9-0208-83f8-b10504186727@nvidia.com \
--to=sdonthineni@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tglx@linutronix.de \
--cc=treding@nvidia.com \
--cc=vsethi@nvidia.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
all inboxes | Powered by JetHome®