From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Daniel Vetter <daniel@ffwll.ch>, Lukas Wunner <lukas@wunner.de>,
Andrzej Hajda <a.hajda@samsung.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Lucas Stach <l.stach@pengutronix.de>,
Linus Walleij <linus.walleij@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Joerg Roedel <jroedel@suse.de>
Subject: [PATCH 0/4] driver core: Managed device links rework and "consumer autoprobe" flag
Date: Tue, 29 Jan 2019 00:03:59 +0100 [thread overview]
Message-ID: <2405639.4es7pRLqn0@aspire.rjw.lan> (raw)
Hi Greg at al,
This is on top of the series I posted on Thursday last week:
https://lore.kernel.org/lkml/2493187.oiOpCWJBV7@aspire.rjw.lan/
and the purpose here is to (1) clean up the remaining device link management
issues mentioned in the cover letter above and (2) make device links support
the "composite device" use case mentioned during the recent discussion on
possibly using device links in the DRM subsystem (see for example
https://marc.info/?l=linux-pm&m=154832771905309&w=2).
Patch [1/4] simply makes two IOMMU drivers pass DL_FLAG_STATELESS to
device_link_add(), because the cleanup part of their device links
handling will not work any more after patch [2/4] and there is no
reason why those links cannot be stateless AFAICS.
Patch [2/4] can be regarded as a fix as it cleans up some link management
issues related to device links reference counting and stateful (managed)
device links.
Patch [3/4] add a "consumer autoprobe" flag causing the driver core to
probe consumer drivers automatically after binding the supplier driver
for persistent managed device links.
Patch [4/4] is just another fix on top of the previous series of device
links patches and it doesn't depend on patches [1-3/4].
For easier testing I have created a git branch containing these patches
along with the previous series (including the v2 of the 5th patch) which
can be pulled from:
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
device-links
(not that this branch may be rebased in the future).
Cheers,
Rafael
next reply other threads:[~2019-01-28 23:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 23:03 Rafael J. Wysocki [this message]
2019-01-28 23:05 ` [PATCH 1/4] IOMMU: Make dwo drivers use stateless device links Rafael J. Wysocki
2019-01-29 8:55 ` Marek Szyprowski
2019-01-29 9:17 ` Joerg Roedel
2019-01-28 23:06 ` [PATCH 2/4] driver core: Make driver core own stateful " Rafael J. Wysocki
2019-01-28 23:07 ` [PATCH 3/4] driver core: Add device link flag DL_FLAG_AUTOPROBE_CONSUMER Rafael J. Wysocki
2019-01-28 23:08 ` [PATCH 4/4] driver core: Do not call rpm_put_suppliers() in pm_runtime_drop_link() 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=2405639.4es7pRLqn0@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=a.hajda@samsung.com \
--cc=daniel@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--cc=jroedel@suse.de \
--cc=l.stach@pengutronix.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukas@wunner.de \
--cc=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.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).