tpmdd-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: Josh Zimmerman <joshz@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tpmdd-devel@lists.sourceforge.net"
	<tpmdd-devel@lists.sourceforge.net>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [tpmdd-devel] [PATCH] Add "shutdown" to "struct class".
Date: Mon, 15 May 2017 09:51:10 -0600	[thread overview]
Message-ID: <20170515155110.GC3433@obsidianresearch.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B641D7A27@hasmsx108.ger.corp.intel.com>

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?

Can the kernel really shut down the eMMC while the hidden platform
stuff is still possibly using it? Goofy..

Jason

  reply	other threads:[~2017-05-15 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 23:32 [PATCH] Add "shutdown" to "struct class" Josh Zimmerman
     [not found] ` <20170512233203.23659-1-joshz-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2017-05-13 12:43   ` Winkler, Tomas
2017-05-15 15:51     ` Jason Gunthorpe [this message]
     [not found]       ` <20170515155110.GC3433-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-05-15 16:17         ` Winkler, Tomas

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=20170515155110.GC3433@obsidianresearch.com \
    --to=jgunthorpe@obsidianresearch.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joshz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=tomas.winkler@intel.com \
    --cc=tpmdd-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).