mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "João Paulo Silva Gonçalves" <joao.goncalves@toradex.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"peterhuewe@gmx.de" <peterhuewe@gmx.de>,
	"jarkko@kernel.org" <jarkko@kernel.org>,
	"jgg@ziepe.ca" <jgg@ziepe.ca>,
	"linux-integrity@vger.kernel.org"
	<linux-integrity@vger.kernel.org>
Cc: "l.sanfilippo@kunbus.com" <l.sanfilippo@kunbus.com>,
	"Alexander.Steffen@infineon.com" <Alexander.Steffen@infineon.com>
Subject: TPM interrupt patch on LTS
Date: Tue, 26 Dec 2023 14:50:55 +0000	[thread overview]
Message-ID: <4fc16271420c578cdafea70e005a2b4381c555d3.camel@toradex.com> (raw)

Hello, 

We are integrating a SPI TPM from Infineon with 6.1/5.15 LTS kernels for an 
embedded platform and it is giving an error message that interrupts are not working. 
There is a correction from [1] already on upstream but the patch that makes 
interrupts work, commit e644b2f498d2 ("tpm, tpm_tis: Enable interrupt test"), was 
not backported to LTS. This seems to be the only patch that was no backported 
from [1]. I read some discussion on lkml about TPM interrupts problems but did 
not get if it is related or the reason for not backporting the patch. 

Do you know the reason this single patch was not backported?  

[1] https://lore.kernel.org/lkml/20221124135538.31020-1-LinoSanfilippo@gmx.de/

Thanks!

Regards,
Joao Paulo Goncalves

             reply	other threads:[~2023-12-26 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-26 14:50 João Paulo Silva Gonçalves [this message]
2024-01-03 14:08 ` Jarkko Sakkinen

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=4fc16271420c578cdafea70e005a2b4381c555d3.camel@toradex.com \
    --to=joao.goncalves@toradex.com \
    --cc=Alexander.Steffen@infineon.com \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=l.sanfilippo@kunbus.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.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
all inboxes | Powered by JetHome®