[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdby5dY7j9=r_dq+at_sqFduJWo15zt4tj4fvhY-KgCUYg@mail.gmail.com>
Date: Fri, 22 Mar 2024 15:28:05 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Francisco Ayala Le Brun <francisco@...eowindow.eu>, Adrian Hunter <adrian.hunter@...el.com>,
linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
ulf.hansson@...aro.org, Linux ACPI <linux-acpi@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>, Mario Limonciello <mario.limonciello@....com>,
"Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: Bug report: probe of AMDI0040:00 failed with error -16
On Thu, Mar 21, 2024 at 5:33 PM Rafael J. Wysocki <rjw@...ysocki.net> wrote:
> We actually can get away without defining a new IRQ flag, as in
> the patch below.
>
> It is not super-clean, but should do the work.
>
> Linus, what do you think?
Uhhh I rather not, the other approach will cover the invariably recurring
instances of this, it will not be the last time we see something like this.
We need tglx input on this, I could merge the patch below with some
big TODO to fix it properly if the discussion about the proper solution
takes too much time.
But I rather not hack around with IRQs without tglx (or marcz, but he
got overloaded) input.
Yours,
Linus Walleij
Powered by blists - more mailing lists