From: Josh Zimmerman <joshz@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, "Winkler,
Tomas" <tomas.winkler@intel.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
tpmdd-devel@lists.sourceforge.net,
Josh Zimmerman <joshz@google.com>
Subject: Re: [PATCH v3] Add "shutdown" to "struct class".
Date: Mon, 15 May 2017 10:39:08 -0700 [thread overview]
Message-ID: <CAHSjozBLBUpSzxrRsfnO49Thf9__MHdOmUdsX+5ST55=T2BWLA@mail.gmail.com> (raw)
In-Reply-To: <20170515173438.13420-1-joshz@google.com>
(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.
Thanks,
Josh
next prev parent reply other threads:[~2017-05-15 17:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 17:34 [PATCH v3] Add "shutdown" to "struct class" Josh Zimmerman
2017-05-15 17:39 ` Josh Zimmerman [this message]
[not found] ` <CAHSjozBLBUpSzxrRsfnO49Thf9__MHdOmUdsX+5ST55=T2BWLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-15 17:45 ` Jason Gunthorpe
[not found] ` <20170515174533.GB6229-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-05-15 20:49 ` Winkler, Tomas
[not found] ` <5B8DA87D05A7694D9FA63FD143655C1B641D90DB-Jy8z56yoSI8MvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2017-05-18 15:20 ` Josh Zimmerman
[not found] ` <20170515173438.13420-1-joshz-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2017-05-25 13:09 ` Greg Kroah-Hartman
[not found] ` <20170525130930.GA16244-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-05-25 15:40 ` Josh Zimmerman
[not found] ` <CAHSjozAkGo1OnjK8HO3m1YyAwamd4CNZ9rUNiwmBeQz6Gau9VA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-25 16:09 ` Greg Kroah-Hartman
2017-05-25 16:24 ` Josh Zimmerman
2017-05-25 16:41 ` Greg Kroah-Hartman
[not found] ` <20170525164118.GA28995-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-05-25 22:40 ` Jarkko Sakkinen
2017-05-25 17:06 ` Jarkko Sakkinen
2017-05-25 17:05 ` Jarkko Sakkinen
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='CAHSjozBLBUpSzxrRsfnO49Thf9__MHdOmUdsX+5ST55=T2BWLA@mail.gmail.com' \
--to=joshz@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--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).