From: Lucas Stach <l.stach@pengutronix.de>
To: Daniel Vetter <daniel@ffwll.ch>, "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Lubomir Rintel <lkundrak@v3.sk>,
"Sarvela, Tomi P" <tomi.p.sarvela@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux PM <linux-pm@vger.kernel.org>,
Liviu Dudau <Liviu.Dudau@arm.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
DRI Development <dri-devel@lists.freedesktop.org>,
Thierry Reding <thierry.reding@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sean Paul <sean@poorly.run>, Peter Rosin <peda@axentia.se>
Subject: Re: Armada DRM: bridge with componentized devices
Date: Fri, 18 Jan 2019 10:36:58 +0100 [thread overview]
Message-ID: <1547804218.2626.7.camel@pengutronix.de> (raw)
In-Reply-To: <CAKMK7uHV=8Jpb1z_iRK-WBWW+oA6dYO7-Yj6tHkf7Be98_Xitg@mail.gmail.com>
Am Donnerstag, den 17.01.2019, 13:20 +0100 schrieb Daniel Vetter:
[...]
>
> > I don't think it is addressed here.
> >
> > Can anyone please explain to me what happens in more detail?
>
> My understanding (and this might be wrong, Russell, Andrzej, ... pls
> correct) is that the following sequence goes wrong:
>
> - componentized driver (both producer and consumer) fully loaded&working
> - you unbind the producer/one of the components
> - component framework or driver core through device_link also unbinds
> the master/consumer
> - you reload/rebind the component
> - with the component framework this results in the master being
> rebound, and the overall driver working again. With device_links
> nothing happens.
>
> I think there was a patch floating around once to put drivers unbound
> due to device_links onto the deferred probe list, so that the next
> time something is bound they have a chance to rebind. But I can't find
> that patch anymore, maybe someone else has the link still?
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1348023.html
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1355243.html
I can repost if this is finally deemed a good idea.
Regards,
Lucas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-01-18 9:37 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 9:47 Armada DRM: bridge with componentized devices Lubomir Rintel
2019-01-03 13:11 ` Russell King - ARM Linux
2019-01-07 10:45 ` Daniel Vetter
2019-01-07 11:26 ` Andrzej Hajda
2019-01-07 16:08 ` Daniel Vetter
2019-01-07 16:27 ` Andrzej Hajda
2019-01-07 21:56 ` Daniel Vetter
2019-01-08 8:35 ` Andrzej Hajda
2019-01-08 8:47 ` Daniel Vetter
2019-01-08 9:22 ` Andrzej Hajda
2019-01-08 10:23 ` Russell King - ARM Linux
2019-01-08 10:32 ` Andrzej Hajda
2019-01-08 10:24 ` Daniel Vetter
2019-01-08 11:25 ` Andrzej Hajda
2019-01-08 11:38 ` Russell King - ARM Linux
2019-01-08 12:27 ` Andrzej Hajda
2019-01-08 13:21 ` Russell King - ARM Linux
2019-01-08 13:34 ` Daniel Vetter
2019-01-08 14:33 ` Andrzej Hajda
2019-01-08 15:07 ` Russell King - ARM Linux
2019-01-08 18:07 ` Daniel Vetter
2019-01-09 9:12 ` Andrzej Hajda
2019-01-09 9:24 ` Rafael J. Wysocki
2019-01-09 9:30 ` Russell King - ARM Linux
2019-01-11 14:20 ` Daniel Vetter
2019-01-11 14:26 ` Rafael J. Wysocki
2019-01-11 14:32 ` Russell King - ARM Linux
2019-01-11 14:36 ` Daniel Vetter
2019-01-11 14:40 ` Rafael J. Wysocki
2019-01-11 14:36 ` Rafael J. Wysocki
2019-01-11 14:49 ` Russell King - ARM Linux
2019-01-14 12:32 ` Rafael J. Wysocki
2019-01-15 0:04 ` Rafael J. Wysocki
2019-01-15 22:47 ` Rafael J. Wysocki
2019-01-16 18:42 ` Daniel Vetter
2019-01-16 22:43 ` Rafael J. Wysocki
2019-01-17 12:20 ` Daniel Vetter
2019-01-18 9:36 ` Lucas Stach [this message]
2019-01-18 10:03 ` Rafael J. Wysocki
2019-01-18 11:06 ` Daniel Vetter
2019-01-18 11:17 ` Rafael J. Wysocki
2019-01-18 11:37 ` Rafael J. Wysocki
2019-01-18 12:57 ` Daniel Vetter
2019-01-24 11:00 ` Rafael J. Wysocki
2019-01-17 17:26 ` Russell King - ARM Linux admin
2019-01-17 22:43 ` Rafael J. Wysocki
2019-01-18 11:07 ` Linus Walleij
2019-01-08 10:16 ` Russell King - ARM Linux
2019-01-08 10:31 ` Daniel Vetter
2019-01-07 16:12 ` Russell King - ARM Linux
2019-01-07 21:55 ` Daniel Vetter
2019-01-08 0:39 ` Russell King - ARM Linux
2019-01-08 14:29 ` Liviu Dudau
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=1547804218.2626.7.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=Liviu.Dudau@arm.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkundrak@v3.sk \
--cc=peda@axentia.se \
--cc=rjw@rjwysocki.net \
--cc=sean@poorly.run \
--cc=thierry.reding@gmail.com \
--cc=tomi.p.sarvela@intel.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