Hi Lukas, On 5/23/23 17:16, Lukas Wunner wrote: > On Tue, May 23, 2023 at 12:14:28PM +0300, Péter Ujfalusi wrote: >> On 23/05/2023 10:44, Lukas Wunner wrote: <snip> >>> The corresponding message emitted in tpm_tis_core_init() for >>> an interrupt that's *never* asserted uses dev_err(), so using >>> dev_err() here as well serves consistency: >>> >>> dev_err(&chip->dev, FW_BUG >>> "TPM interrupt not working, polling instead\n"); >>> >>> That way the same severity is used both for the never asserted and >>> the never deasserted interrupt case. >> >> Oh, OK. >> Is there anything the user can do to have a ERROR less boot? > > You're right that the user can't do anything about it and that > toning the message down to KERN_WARN or even KERN_NOTICE severity > may be appropriate. > > However the above-quoted message for the never asserted interrupt > in tpm_tis_core_init() should then likewise be toned down to the > same severity. > > I'm wondering why that message uses FW_BUG. That doesn't make any > sense to me. It's typically not a firmware bug, but a hardware issue, > e.g. an interrupt pin may erroneously not be connected or may be > connected to ground. Lino used HW_ERR, which seems more appropriate > to me. This issue seems to have mostly been seen on x86/ACPI systems and the issue seems to mostly be a misconfiguration of the IOAPIC (e.g. wrong trigger type). Besides this, the IRQ info always comes from either the ACPI tables or from devicetree both of which are firmware and if the IRQ does not work on a specific board then the firmware should simply not provide any IRQ info to the driver rather the pointing to a broken IRQ. Hence my suggestion to use dev_warn(dev, FW_BUG "....", ...); Regards, Hans
