From: Greg KH <greg@kroah.com>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org,
Patrick Mochel <mochel@digitalimplant.org>,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: recursively unregistering platform devices
Date: Wed, 16 Feb 2005 15:56:50 -0800 [thread overview]
Message-ID: <20050216235649.GA15537@kroah.com> (raw)
In-Reply-To: <20050206142912.GE13303@pengutronix.de>
On Sun, Feb 06, 2005 at 03:29:12PM +0100, Robert Schwebel wrote:
> Hi,
>
> I have a locking problem with platform devices in a little bit unusual
> scenario; we have an FPGA which has a device information memory block
> for the several "parts" in the FPGA. So we have written a base driver
> which registers the device information block with the driver model, then
> looks what is in the FPGA, registers the according "devices" with the
> driver model and issues hotplug events to load the related drivers.
>
> The registration works fine, although we call platform_add_devices()
> from the base driver for all the "sub devices"; but when we try to
> unload the drivers there is a deadlock. On driver exit we call
> platform_device_unregister() for the base driver which seems to be run
> under a lock which is also being aquired when unregistering the devices
> "inside" the FPGA.
>
> Before I investigate deeper - did anyone see this behaviour before?
Known issue, you can't recursivly register or unregister with the driver
core right now. I'm working on fixing this issue.
thanks,
greg k-h
next prev parent reply other threads:[~2005-02-17 0:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 14:29 recursively unregistering platform devices Robert Schwebel
2005-02-16 23:56 ` Greg KH [this message]
2005-02-17 6:51 ` Robert Schwebel
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=20050216235649.GA15537@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=mochel@digitalimplant.org \
--cc=r.schwebel@pengutronix.de \
/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