[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191211175651.GK4516@linux.intel.com>
Date: Wed, 11 Dec 2019 19:57:03 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Guenter Roeck <groeck@...gle.com>
Cc: Sasha Levin <sashal@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"# v4 . 10+" <stable@...r.kernel.org>,
Stephen Boyd <swboyd@...omium.org>,
Andrey Pronin <apronin@...omium.org>,
Duncan Laurie <dlaurie@...omium.org>,
Jason Gunthorpe <jgg@...pe.ca>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Guenter Roeck <groeck@...omium.org>,
Alexander Steffen <Alexander.Steffen@...ineon.com>,
Heiko Stuebner <heiko@...ech.de>,
linux-integrity@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 5.4 277/350] tpm: Add a flag to indicate TPM
power is managed by firmware
On Tue, Dec 10, 2019 at 01:32:15PM -0800, Guenter Roeck wrote:
> On Tue, Dec 10, 2019 at 1:12 PM Sasha Levin <sashal@...nel.org> wrote:
> >
> > From: Stephen Boyd <swboyd@...omium.org>
> >
> > [ Upstream commit 2e2ee5a2db06c4b81315514b01d06fe5644342e9 ]
> >
> > On some platforms, the TPM power is managed by firmware and therefore we
> > don't need to stop the TPM on suspend when going to a light version of
> > suspend such as S0ix ("freeze" suspend state). Add a chip flag,
> > TPM_CHIP_FLAG_FIRMWARE_POWER_MANAGED, to indicate this so that certain
> > platforms can probe for the usage of this light suspend and avoid
> > touching the TPM state across suspend/resume.
> >
>
> Are the patches needed to support CR50 (which need this patch) going
> to be applied to v5.4.y as well ? If not, what is the purpose of
> applying this patch to v5.4.y ?
>
> Thanks,
> Guenter
Thanks Guenter. I think not.
/Jarkko
Powered by blists - more mailing lists