[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5d03e3ba.1c69fb81.9c2c8.aa89@mx.google.com>
Date: Fri, 14 Jun 2019 11:13:13 -0700
From: Stephen Boyd <swboyd@...omium.org>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
Cc: Peter Huewe <peterhuewe@....de>,
Andrey Pronin <apronin@...omium.org>,
linux-kernel@...r.kernel.org, Jason Gunthorpe <jgg@...pe.ca>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-integrity@...r.kernel.org, devicetree@...r.kernel.org,
Duncan Laurie <dlaurie@...omium.org>,
Guenter Roeck <groeck@...omium.org>
Subject: Re: [PATCH 1/8] tpm: block messages while suspended
Quoting Jarkko Sakkinen (2019-06-14 08:27:00)
> On Thu, Jun 13, 2019 at 11:09:24AM -0700, Stephen Boyd wrote:
> > diff --git a/include/linux/tpm.h b/include/linux/tpm.h
> > index 1b5436b213a2..48df005228d0 100644
> > --- a/include/linux/tpm.h
> > +++ b/include/linux/tpm.h
> > @@ -132,6 +132,8 @@ struct tpm_chip {
> > int dev_num; /* /dev/tpm# */
> > unsigned long is_open; /* only one allowed */
> >
> > + unsigned long is_suspended;
> > +
> > char hwrng_name[64];
> > struct hwrng hwrng;
>
> I think it would better idea to have a bitmask of some sort that
> would have bits for 'open' and 'suspended'.
>
Sure. I can combine is_open and is_suspended into some sort of 'unsigned
long flags' member and then have #define TPM_IS_OPEN 0 and #define
TPM_IS_SUSPENDED 1 defines?
Powered by blists - more mailing lists