From: Feng Kan <fkan@apm.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Linux PM <linux-pm@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Helgaas <bhelgaas@google.com>, Toan Le <toanle@apm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3] PM / core: fix deferred probe breaking suspend resume order
Date: Wed, 4 Apr 2018 14:10:41 -0700 [thread overview]
Message-ID: <CAL85gmBtFnXje9tPngXEyCCwuvxvH6YHB=HrvjfU7npPDiSTCw@mail.gmail.com> (raw)
In-Reply-To: <20180330225024.GH9322@bhelgaas-glaptop.roam.corp.google.com>
On Fri, Mar 30, 2018 at 3:50 PM, Bjorn Helgaas <helgaas@kernel.org> wrote:
> On Thu, Mar 15, 2018 at 11:41:33AM -0700, Feng Kan wrote:
>> On Mon, Mar 5, 2018 at 10:29 AM, Feng Kan <fkan@apm.com> wrote:
>> > When bridge and its endpoint is enumerated the devices are added to the
>> > dpm list. Afterward, the bridge defers probe when IOMMU is not ready.
>> > This causes the bridge to be moved to the end of the dpm list when
>> > deferred probe kicks in. The order of the dpm list for bridge and
>> > endpoint is reversed.
>> >
>> > Add reordering code to move the bridge and its children and consumers to
>> > the end of the pm list so the order for suspend and resume is not altered.
>> > The code also move device and its children and consumers to the tail of
>> > device_kset list if it is registered.
>> >
>> > Signed-off-by: Feng Kan <fkan@apm.com>
>> > Signed-off-by: Toan Le <toanle@apm.com>
>> > ...
>> >
>> Hi, just wanted to check if there is anything else I need to change on
>> this. Thanks.
>
> I'm assuming Rafael will handle this.
Rafael, sorry to ping again. Do you have a position on this patch yet?
next prev parent reply other threads:[~2018-04-04 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 18:29 [PATCH V3] PM / core: fix deferred probe breaking suspend resume order Feng Kan
2018-03-15 18:41 ` Feng Kan
2018-03-30 22:50 ` Bjorn Helgaas
2018-04-04 21:10 ` Feng Kan [this message]
2018-04-05 16:38 ` Rafael J. Wysocki
2018-04-05 16:40 ` Rafael J. Wysocki
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='CAL85gmBtFnXje9tPngXEyCCwuvxvH6YHB=HrvjfU7npPDiSTCw@mail.gmail.com' \
--to=fkan@apm.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjw@rjwysocki.net \
--cc=toanle@apm.com \
/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).