From: Patrick Rudolph <patrick.rudolph@9elements.com>
To: u-boot@lists.denx.de, linux-kernel@vger.kernel.org
Cc: Patrick Rudolph <patrick.rudolph@9elements.com>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Subject: [PATCH v9 19/37] arm: gic-v3-its: Rename objects
Date: Wed, 16 Oct 2024 08:04:05 +0200 [thread overview]
Message-ID: <20241016060523.888804-20-patrick.rudolph@9elements.com> (raw)
In-Reply-To: <20241016060523.888804-1-patrick.rudolph@9elements.com>
The code accesses the gic-v3 node, but not the gic-v3-its node,
thus rename the objects to clarify which node it operates on.
The following commit will make use of the gic-v3-its node for real.
Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
---
arch/arm/lib/gic-v3-its.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/arch/arm/lib/gic-v3-its.c b/arch/arm/lib/gic-v3-its.c
index 2cc0a32f9d..22fa46a341 100644
--- a/arch/arm/lib/gic-v3-its.c
+++ b/arch/arm/lib/gic-v3-its.c
@@ -35,10 +35,10 @@ static int gic_v3_its_get_gic_addr(struct gic_v3_its_priv *priv)
int ret;
ret = uclass_get_device_by_driver(UCLASS_IRQ,
- DM_DRIVER_GET(arm_gic_v3_its), &dev);
+ DM_DRIVER_GET(arm_gic_v3), &dev);
if (ret) {
pr_err("%s: failed to get %s irq device\n", __func__,
- DM_DRIVER_GET(arm_gic_v3_its)->name);
+ DM_DRIVER_GET(arm_gic_v3)->name);
return ret;
}
@@ -158,13 +158,13 @@ int gic_lpi_tables_init(u64 base, u32 num_redist)
return 0;
}
-static const struct udevice_id gic_v3_its_ids[] = {
+static const struct udevice_id gic_v3_ids[] = {
{ .compatible = "arm,gic-v3" },
{}
};
-U_BOOT_DRIVER(arm_gic_v3_its) = {
+U_BOOT_DRIVER(arm_gic_v3) = {
.name = "gic-v3",
.id = UCLASS_IRQ,
- .of_match = gic_v3_its_ids,
+ .of_match = gic_v3_ids,
};
--
2.46.2
next prev parent reply other threads:[~2024-10-16 6:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241016060523.888804-1-patrick.rudolph@9elements.com>
2024-10-16 6:04 ` [PATCH v9 18/37] drivers/cpu: Add generic armv8 cpu driver Patrick Rudolph
2024-10-16 6:04 ` Patrick Rudolph [this message]
2024-10-16 6:04 ` [PATCH v9 20/37] arm: gic-v3-its: Implement of_xlate Patrick Rudolph
2024-10-16 20:09 ` Moritz Fischer
2024-10-16 6:04 ` [PATCH v9 23/37] drivers/arm: Implement acpi_fill_madt Patrick Rudolph
2024-10-16 6:04 ` [PATCH v9 24/37] common: Enable BLOBLIST_TABLES on arm Patrick Rudolph
2024-10-17 23:18 ` Simon Glass
2024-10-21 8:26 ` Patrick Rudolph
2024-10-21 16:32 ` Simon Glass
2024-10-21 17:57 ` Peter Robinson
2024-10-22 12:15 ` Simon Glass
2024-10-22 16:18 ` Patrick Rudolph
2024-10-22 17:00 ` Simon Glass
2024-10-16 6:04 ` [PATCH v9 27/37] arm: mach-bcm283x: Bring in some header files from tianocore Patrick Rudolph
2024-10-16 6:04 ` [PATCH v9 31/37] armv8: cpu: Enable ACPI parking protocol Patrick Rudolph
2024-10-16 6:04 ` [PATCH v9 32/37] arm: Implement read_mpidr on armv7 Patrick Rudolph
2024-10-16 6:04 ` [PATCH v9 35/37] bloblist: Fix use of uninitialized variable Patrick Rudolph
2024-10-16 6:04 ` [PATCH v9 37/37] CI: Enable qemu_sbsa Patrick Rudolph
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=20241016060523.888804-20-patrick.rudolph@9elements.com \
--to=patrick.rudolph@9elements.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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