DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=bsfBo/a+Ubzzq9IyX0uNsSOljFlzDzNAEeifFT/IqnYefC//I4FoecOzWxTgIgUvy3LrXwUE1cGCbBukBT1cxOPUIIJL1hPWLsBe3RuF//GiLrv8RP3y3b/rtxcALqXe8o/bLpb35mFxeGV/DRFvbRjjYvvCTDDqr+yTpy7Jo5c=
Message-ID: <8b67d60803051525g3aca775dmc14d1c2450b34168@mail.gmail.com>
Date: Wed, 5 Mar 2008 23:25:48 +0000
From: "Adrian McMenamin" <lkmladrian@gmail.com>
To: "Greg KH" <greg@kroah.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Behaviour of device_register
Cc: linux-sh <linux-sh@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 798
Lines: 19

The observed behaviour for me is that it appears to be blocking the
vblank interrupt on my box (or more accurately stopping the workqueue
that the interrupt handler calls from running). And without the vblank
my bus won't process dma and so therefore the attempt to register the
device in question fails.

But I can see no reason from a glance over the code why that (vblanks
being blocked) would be the case - have I missed something and the
vblanks will be blocked, or should I be looking elsewhere for the root
cause of this problem?

Thanks

Adrian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/