From: Thomas Gleixner <tglx@linutronix.de>
To: Stefan Eichenberger <eichest@gmail.com>,
andrew@lunn.ch, gregory.clement@bootlin.com,
sebastian.hesselbarth@gmail.com,
shivamurthy.shastri@linutronix.de, anna-maria@linutronix.de
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] irqchip/irq-mvebu-icu: Fix access to msi_data from irq_domain
Date: Mon, 27 Jan 2025 11:30:32 +0100 [thread overview]
Message-ID: <87sep48s6v.ffs@tglx> (raw)
In-Reply-To: <20250124085140.44792-1-eichest@gmail.com>
On Fri, Jan 24 2025 at 09:50, Stefan Eichenberger wrote:
> Previously, we incorrectly cast irq_domain->host_data directly to
Previously 'we' do nothing. The current implementation casts inconrrectly.
> mvebu_icu_msi_data. However, host_data actually stores a structure of
> type msi_domain_info.
>
> This incorrect assumption caused issues such as the thermal sensors of
> the CP110 platform malfunctioning. Specifically, the translation of the
> SEI interrupt to IRQ_TYPE_EDGE_RISING failed, preventing proper
> interrupt handling. The following error was observed:
> genirq: Setting trigger mode 4 for irq 85 failed (irq_chip_set_type_parent+0x0/0x34)
> armada_thermal f2400000.system-controller:thermal-sensor@70: Cannot request threaded IRQ 85
>
> This commit resolves the issue by first casting host_data to
This commit is equally wrong as 'This patch'. See Documentation/process/
> msi_domain_info and then accessing the mvebu_icu_msi_data through
> msi_domain_info->chip_data.
I fixed it up for you.
Thanks,
tglx
prev parent reply other threads:[~2025-01-27 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 8:50 [PATCH v2] irqchip/irq-mvebu-icu: Fix access to msi_data from irq_domain Stefan Eichenberger
2025-01-27 10:13 ` [tip: irq/urgent] irqchip/irq-mvebu-icu: Fix access to msi_data from irq_domain::host_data tip-bot2 for Stefan Eichenberger
2025-01-27 10:30 ` Thomas Gleixner [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=87sep48s6v.ffs@tglx \
--to=tglx@linutronix.de \
--cc=andrew@lunn.ch \
--cc=anna-maria@linutronix.de \
--cc=eichest@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=shivamurthy.shastri@linutronix.de \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.