From: Jarkko Sakkinen <jarkko@kernel.org>
To: Eddie James <eajames@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander.Steffen@infineon.com, jgg@ziepe.ca, peterhuewe@gmx.de,
joel@jms.id.au
Subject: Re: [PATCH] tpm: tis_i2c: Fix sanity check interrupt enable mask
Date: Fri, 26 Aug 2022 07:10:52 +0300 [thread overview]
Message-ID: <YwhHzDL5agT3enUn@kernel.org> (raw)
In-Reply-To: <YwhGLZX2+dggWHcI@kernel.org>
On Fri, Aug 26, 2022 at 07:04:00AM +0300, Jarkko Sakkinen wrote:
> On Wed, Aug 17, 2022 at 03:03:33PM -0500, Eddie James wrote:
> > The sanity check mask for TPM_INT_ENABLE register was off by 8 bits,
> > resulting in failure to probe if the TPM_INT_ENABLE register was a
> > valid value.
> >
> > Fixes: bbc23a07b072 ("tpm: Add tpm_tis_i2c backend for tpm_tis_core")
> > Signed-off-by: Eddie James <eajames@linux.ibm.com>
> > ---
> > drivers/char/tpm/tpm_tis_i2c.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/char/tpm/tpm_tis_i2c.c b/drivers/char/tpm/tpm_tis_i2c.c
> > index 0692510dfcab..635a69dfcbbd 100644
> > --- a/drivers/char/tpm/tpm_tis_i2c.c
> > +++ b/drivers/char/tpm/tpm_tis_i2c.c
> > @@ -49,7 +49,7 @@
> >
> > /* Masks with bits that must be read zero */
> > #define TPM_ACCESS_READ_ZERO 0x48
> > -#define TPM_INT_ENABLE_ZERO 0x7FFFFF6
> > +#define TPM_INT_ENABLE_ZERO 0x7FFFFF60
> > #define TPM_STS_READ_ZERO 0x23
> > #define TPM_INTF_CAPABILITY_ZERO 0x0FFFF000
> > #define TPM_I2C_INTERFACE_CAPABILITY_ZERO 0x80000000
> > --
> > 2.31.1
> >
>
> Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
>
> Thank you.
I used "6.3 Handling of Multi-Byte Registers" I2C specification
to check this. I do not posses I2C chip.
https://trustedcomputinggroup.org/wp-content/uploads/TCG-TPM-I2C-Interface-Specification-v1.00.pdf
BR, Jarkko
next prev parent reply other threads:[~2022-08-26 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 20:03 [PATCH] tpm: tis_i2c: Fix sanity check interrupt enable mask Eddie James
2022-08-26 4:03 ` Jarkko Sakkinen
2022-08-26 4:10 ` Jarkko Sakkinen [this message]
2022-11-14 3:16 ` Joel Stanley
2022-11-26 0:14 ` 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=YwhHzDL5agT3enUn@kernel.org \
--to=jarkko@kernel.org \
--cc=Alexander.Steffen@infineon.com \
--cc=eajames@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=joel@jms.id.au \
--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 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.