From: "Rob Herring (Arm)" <robh@kernel.org>
To: Saravana Kannan <saravanak@google.com>,
Anup Patel <apatel@ventanamicro.com>,
Marc Zyngier <maz@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org
Subject: [PATCH v2 0/2] of: Fix interrupt-map for fw_devlink
Date: Wed, 29 May 2024 14:59:19 -0500 [thread overview]
Message-ID: <20240529-dt-interrupt-map-fix-v2-0-ef86dc5bcd2a@kernel.org> (raw)
The duplicated parsing continued to bother me, so I've refactored things
to avoid that for parsing the interrupt parent and args in the
interrupt-map.
It passes testing with unittests on QEMU virt platform, but I don't
think that catches the problematic cases. So please test.
v1: https://lore.kernel.org/all/20240528164132.2451685-1-maz@kernel.org/
- Refactor existing interrupt-map parsing code and use it for
fw_devlink
Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
---
Marc Zyngier (1):
of: property: Fix fw_devlink handling of interrupt-map
Rob Herring (Arm) (1):
of/irq: Factor out parsing of interrupt-map parent phandle+args from of_irq_parse_raw()
drivers/of/irq.c | 127 +++++++++++++++++++++++++++++-------------------
drivers/of/of_private.h | 3 ++
drivers/of/property.c | 30 ++++--------
3 files changed, 89 insertions(+), 71 deletions(-)
---
base-commit: 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0
change-id: 20240529-dt-interrupt-map-fix-a37b9aff5ca0
Best regards,
--
Rob Herring (Arm) <robh@kernel.org>
next reply other threads:[~2024-05-29 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 19:59 Rob Herring (Arm) [this message]
2024-05-29 19:59 ` [PATCH v2 1/2] of/irq: Factor out parsing of interrupt-map parent phandle+args from of_irq_parse_raw() Rob Herring (Arm)
2024-05-30 13:46 ` Marc Zyngier
2024-05-29 19:59 ` [PATCH v2 2/2] of: property: Fix fw_devlink handling of interrupt-map Rob Herring (Arm)
2024-05-30 13:54 ` [PATCH v2 0/2] of: Fix interrupt-map for fw_devlink Marc Zyngier
2024-05-30 14:52 ` Anup Patel
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=20240529-dt-interrupt-map-fix-v2-0-ef86dc5bcd2a@kernel.org \
--to=robh@kernel.org \
--cc=apatel@ventanamicro.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=saravanak@google.com \
/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).