public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Patrick Mochel <mochel@digitalimplant.org>,
	Marc Kleine-Budde <mkl@pengutronix.de>
Subject: recursively unregistering platform devices
Date: Sun, 6 Feb 2005 15:29:12 +0100	[thread overview]
Message-ID: <20050206142912.GE13303@pengutronix.de> (raw)

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? 

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

             reply	other threads:[~2005-02-06 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06 14:29 Robert Schwebel [this message]
2005-02-16 23:56 ` recursively unregistering platform devices Greg KH
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=20050206142912.GE13303@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=mochel@digitalimplant.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