From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Josh Zimmerman <joshz-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org
Subject: Re: [PATCH v4 2/2] Add "shutdown" to "struct class".
Date: Wed, 31 May 2017 16:18:11 -0600 [thread overview]
Message-ID: <20170531221811.GA12603@obsidianresearch.com> (raw)
In-Reply-To: <CAHSjozBDNX-bEQGjUtjqJzG_kuSWgxmrjPmdA=nfYhr1DFGgYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, May 31, 2017 at 03:01:13PM -0700, Josh Zimmerman wrote:
> >> + if (dev->class && dev->class->shutdown) {
> >> + if (initcall_debug)
> >> + dev_info(dev, "shutdown\n");
> >> + dev->class->shutdown(dev);
> >> + }
> >> if (dev->bus && dev->bus->shutdown) {
>
> I just looked again at this line, which I am suddenly skeptical of. Is there
> any reason to run _both_ the class and the bus or driver shutdown
> functions? In the code as-is, only the bus or the driver function will
> execute. Right now, this patch will change that behavior. I suspect I
> should just add the appropriate "else", but I'm not sure if there is
> some reason to prefer the behavior as implemented in this version of
> the patch.
Yes, I think the else should be there.
>From what I could tell, the intent is that the most generic will then
call the least generic in the proper order, eg tpm class shutdown full
should then call bus and driver shutdown, if they are defined.
This allows each step to inject some action both before and after
calling the lower level steps, and follows the same pattern used
elsewhere.
Jason
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2017-05-31 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 23:20 [PATCH v4 2/2] Add "shutdown" to "struct class" Josh Zimmerman
[not found] ` <CAHSjozD_NjH0Ta=ELCOqG6ezX=qgteumKBnN2ceqE4ty2FaAZQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-30 5:08 ` Jarkko Sakkinen
2017-05-30 7:54 ` Jarkko Sakkinen
[not found] ` <20170530075419.766mlyxomxrzbxz6-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-05-31 22:01 ` Josh Zimmerman
[not found] ` <CAHSjozBDNX-bEQGjUtjqJzG_kuSWgxmrjPmdA=nfYhr1DFGgYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-31 22:18 ` Jason Gunthorpe [this message]
2017-06-01 17:07 ` Jarkko Sakkinen
[not found] ` <20170601170721.uyjhkjtuey6p3gmt-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-06-02 22:00 ` Josh Zimmerman
[not found] ` <CAHSjozDaMwGspg=hhTGR7CUa+tMV7qC8FAssMKin9h_bFcysaA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-05 12:48 ` Jarkko Sakkinen
[not found] ` <20170605124834.e6myswydwvvscaao-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-06-05 18:32 ` Josh Zimmerman
[not found] ` <CAHSjozAhiR0E5FvuZGgJ39hyd9oT3NYeHm=BCdouhCOXBdi+SA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-12 23:08 ` Josh Zimmerman via tpmdd-devel
[not found] ` <CAHSjozA4Jpq4JDgmfqMk6p_AHjjW4tpeAehFXBcWxe0WsY3psA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-13 19:11 ` 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=20170531221811.GA12603@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org \
--cc=joshz-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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).