All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: peterhuewe@gmx.de, jgg@ziepe.ca, linus.walleij@linaro.org,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Aw: Re: [PATCH v2] tpm, tpm_tis_spi: Allow to sleep in the interrupt handler
Date: Fri, 30 Jul 2021 13:45:48 +0200	[thread overview]
Message-ID: <trinity-23757337-a194-45c1-864b-6f96a754fed1-1627645548572@3c-app-gmx-bs53> (raw)
In-Reply-To: <20210623133420.gw2lziue5nkvjtps@kernel.org>

Hi Jarko,

> Gesendet: Mittwoch, 23. Juni 2021 um 15:34 Uhr
> Von: "Jarkko Sakkinen" <jarkko@kernel.org>
> An: "Lino Sanfilippo" <LinoSanfilippo@gmx.de>
> Cc: peterhuewe@gmx.de, jgg@ziepe.ca, linus.walleij@linaro.org, linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org
> Betreff: Re: [PATCH v2] tpm, tpm_tis_spi: Allow to sleep in the interrupt handler
>
> On Sun, Jun 20, 2021 at 04:34:44AM +0200, Lino Sanfilippo wrote:
> > Interrupt handling at least includes reading and writing the interrupt
> > status register within the interrupt routine. For accesses over SPI a mutex
> > is used in the concerning functions. Since this requires a sleepable
> > context request a threaded interrupt handler for this case.
> >
> > Cc: stable@vger.kernel.org
> > Fixes: 1a339b658d9d ("tpm_tis_spi: Pass the SPI IRQ down to the driver")
> > Signed-off-by: Lino Sanfilippo <LinoSanfilippo@gmx.de>
>
> I'll test this after rc1 PR (I have one NUC which uses tpm_tis_spi).
>
> /Jarkko
>

any news from this patch? Did you already have the opportunity to test it?

Regards,
Lino

      parent reply	other threads:[~2021-07-30 11:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-20  2:34 [PATCH v2] tpm, tpm_tis_spi: Allow to sleep in the interrupt handler Lino Sanfilippo
2021-06-23 13:34 ` Jarkko Sakkinen
2021-06-25  0:17   ` Lino Sanfilippo
2021-07-30 11:45   ` Lino Sanfilippo [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=trinity-23757337-a194-45c1-864b-6f96a754fed1-1627645548572@3c-app-gmx-bs53 \
    --to=linosanfilippo@gmx.de \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.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.