From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933354AbdEORpr (ORCPT ); Mon, 15 May 2017 13:45:47 -0400 Received: from quartz.orcorp.ca ([184.70.90.242]:59952 "EHLO quartz.orcorp.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932621AbdEORpp (ORCPT ); Mon, 15 May 2017 13:45:45 -0400 Date: Mon, 15 May 2017 11:45:33 -0600 From: Jason Gunthorpe To: Josh Zimmerman Cc: Greg Kroah-Hartman , linux-kernel@vger.kernel.org, "Winkler, Tomas" , Jarkko Sakkinen , tpmdd-devel@lists.sourceforge.net Subject: Re: [PATCH v3] Add "shutdown" to "struct class". Message-ID: <20170515174533.GB6229@obsidianresearch.com> References: <20170515173438.13420-1-joshz@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Broken-Reverse-DNS: no host name found for IP address 10.0.0.156 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 15, 2017 at 10:39:08AM -0700, Josh Zimmerman wrote: > (Continuing thread from patch v1) > > > On Sat, May 13, 2017 at 12:43:11PM +0000, Winkler, Tomas wrote: > > > > > The TPM class has some common shutdown code that must be executed > > > > > for all drivers. This adds some needed functionality for that > > > > > > > > The issue with this is, that on some platforms the only storage can be > > > > eMMC and TPM is using it,. It has to be ensured that the storage > > > > device won't go down before TPM2_shutdown is called. And there is no > > > > direct device hierarchy to ensure an orderly shutdown. > > > > > > Something will have to use the new device links stuff to define that > > > dependency, but that seems unrelated to this patch? > > > > > > Yep, it's not directly related to this specific patch, this is more relevant particularly to TPM2_shutdown. > > Jason, do you want me to do that in my patch on the tpmdd-devel list? > If so, mind giving me a documentation pointer or two? I'm not familiar > with this area. No.. Ordering power management events is something someone with knowledge of the specific emmc platform is going to have to tackle.. It isn't really a core problem, platform specific code will have to setup the needed device links to order power management properly.. Jason