From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.3 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_IN_DEF_DKIM_WL autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AD3EBC3F68F for ; Wed, 11 Dec 2019 18:06:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 840562077B for ; Wed, 11 Dec 2019 18:06:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="CJ3seZm3" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730740AbfLKSGG (ORCPT ); Wed, 11 Dec 2019 13:06:06 -0500 Received: from mail-yb1-f194.google.com ([209.85.219.194]:42374 "EHLO mail-yb1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729512AbfLKSGF (ORCPT ); Wed, 11 Dec 2019 13:06:05 -0500 Received: by mail-yb1-f194.google.com with SMTP id p137so9370218ybg.9 for ; Wed, 11 Dec 2019 10:06:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Mzph4oRYSdP4XB6lnmsVX28t3uDJtwjo66piREwlnZo=; b=CJ3seZm3TNcFL0JuYlD82O0DXLlJhLI2L0gi5h5SiNm2+s8CUp6Q8oweDq3/j38gpI 8tF1VvFdOXPaLMnJlwyE0+6HFdWAWF3tnAGlg7ZHd/VKihXM1V08GEOVE30822XMdn3I dbFmsuJVyT64fcZSYlUTIXoNE3Huf8Nv9z5HDdOerv35oorKROPYxJ+V3Q1miJ1+bUCK xDSHV6xMMTNN9n4Yt8cm5Ci7Dz+BgSTPbiECkALqzUHeRtihEJGe57bCcsf5nIeATGo8 7S4ssremZfvXcWA3rmNmKy6q00iTjk02pBPOBq3meSfS8dDy5el9GO388Xt/a0c6macK Ab1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Mzph4oRYSdP4XB6lnmsVX28t3uDJtwjo66piREwlnZo=; b=oofKW/KJgn0LXC5xtO2o0op+/4BwEq+XDyMKRWeeVAV9wwzOR9dfyesO/2wRFIEtL5 N71lbWtU5Oy9ws/3CeTUmAtrxITzMAwc77UXNdsF1GL+6SdAYYtb8BRJ5E+coHr9kUpb a4kYKlzthgo4UJLZ4uc5LHQoul1lAUMWYcXzUsjIMQQXepAcE9r7XrF1KcIJH97e7Bnp xBw/smwm91bj24PZ/DA67D9JZQxqfPQwAlTlbkYEo60FjHVDI/+SSjJ1vJvXJsLMNsfR MGEvauamJWIouOZgZrgBoLEeESKsxYLKf1j+OUjdo1xmMZsWvZquVvbi1lZYvfZDwLz0 tDhg== X-Gm-Message-State: APjAAAW98mVqbDatVM3lYPgVyX19fRUJMsCHiAriWffGI+RUcI0aIE6h wDmBpBL3Ez4q1fp6aBOMZWba+OzEvyQhk8IF1yemJg== X-Google-Smtp-Source: APXvYqyO2/s0U2KFrlOdyOXWx12vh5Q2gWo9cY+d2QONSuipAFzpcXSOZnRUQukVA1QPy8HGFOxXm4YZ6Tzhcq5W7Bg= X-Received: by 2002:a25:5008:: with SMTP id e8mr940654ybb.277.1576087564293; Wed, 11 Dec 2019 10:06:04 -0800 (PST) MIME-Version: 1.0 References: <20191210210735.9077-1-sashal@kernel.org> <20191210210735.9077-238-sashal@kernel.org> <20191211175651.GK4516@linux.intel.com> In-Reply-To: <20191211175651.GK4516@linux.intel.com> From: Guenter Roeck Date: Wed, 11 Dec 2019 10:05:52 -0800 Message-ID: Subject: Re: [PATCH AUTOSEL 5.4 277/350] tpm: Add a flag to indicate TPM power is managed by firmware To: Jarkko Sakkinen Cc: Sasha Levin , linux-kernel , "# v4 . 10+" , Stephen Boyd , Andrey Pronin , Duncan Laurie , Jason Gunthorpe , Arnd Bergmann , Greg Kroah-Hartman , Guenter Roeck , Alexander Steffen , Heiko Stuebner , linux-integrity@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Wed, Dec 11, 2019 at 9:57 AM Jarkko Sakkinen wrote: > > On Tue, Dec 10, 2019 at 01:32:15PM -0800, Guenter Roeck wrote: > > On Tue, Dec 10, 2019 at 1:12 PM Sasha Levin wrote: > > > > > > From: Stephen Boyd > > > > > > [ 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. > Thought so. In that case this patch should be dropped. Guenter