From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Alan Stern <stern@rowland.harvard.edu>, Marcel Holtmann <marcel@>
Subject: [RFC][Patch 2/3] bluetooth: Fix device_move() vs. dpm_list.
Date: Tue, 3 Mar 2009 11:21:03 +0100 [thread overview]
Message-ID: <20090303112103.22f30b5c@gondolin> (raw)
In-Reply-To: <20090224165311.5d103b67@gondolin>
Make use of the new device_pm_move_*() functions when moving
bluetooth ttys. They either get a new parent or are moved to
head. (Note: I didn't bother to implement proper handling of
device_move() failures...)
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
---
net/bluetooth/hci_sysfs.c | 5 ++++-
net/bluetooth/rfcomm/tty.c | 21 ++++++++++++++++-----
2 files changed, 20 insertions(+), 6 deletions(-)
--- linux-2.6.orig/net/bluetooth/rfcomm/tty.c
+++ linux-2.6/net/bluetooth/rfcomm/tty.c
@@ -730,8 +730,15 @@ static int rfcomm_tty_open(struct tty_st
set_current_state(TASK_RUNNING);
remove_wait_queue(&dev->wait, &wait);
- if (err == 0)
- device_move(dev->tty_dev, rfcomm_get_device(dev));
+ if (err == 0) {
+ struct device *target = rfcomm_get_device(dev);
+
+ device_pm_lock();
+ /* FIXME: handle device_move() errors */
+ if (!device_move(dev->tty_dev, target))
+ device_pm_move_before(dev->tty_dev, target);
+ device_pm_unlock();
+ }
rfcomm_tty_copy_pending(dev);
@@ -750,9 +757,13 @@ static void rfcomm_tty_close(struct tty_
atomic_read(&dev->opened));
if (atomic_dec_and_test(&dev->opened)) {
- if (dev->tty_dev->parent)
- device_move(dev->tty_dev, NULL);
-
+ if (dev->tty_dev->parent) {
+ device_pm_lock();
+ /* FIXME: handle device_move errors */
+ if (!device_move(dev->tty_dev, NULL))
+ device_pm_move_last(dev->tty_dev);
+ device_pm_unlock();
+ }
/* Close DLC and dettach TTY */
rfcomm_dlc_close(dev->dlc, 0);
--- linux-2.6.orig/net/bluetooth/hci_sysfs.c
+++ linux-2.6/net/bluetooth/hci_sysfs.c
@@ -140,7 +140,10 @@ static void del_conn(struct work_struct
dev = device_find_child(&conn->dev, NULL, __match_tty);
if (!dev)
break;
- device_move(dev, NULL);
+ device_pm_lock();
+ if (!device_move(dev, NULL))
+ device_pm_move_last(dev);
+ device_pm_unlock();
put_device(dev);
}
next prev parent reply other threads:[~2009-03-03 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090224165311.5d103b67@gondolin>
2009-03-03 10:21 ` [RFC][Patch 1/3] Add device_pm_move_*() API Cornelia Huck
2009-03-03 10:21 ` Cornelia Huck [this message]
2009-03-03 10:21 ` [RFC][Patch 3/3] s390: cio: Fix device_move() vs. dpm_list Cornelia Huck
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=20090303112103.22f30b5c@gondolin \
--to=cornelia.huck@de.ibm.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.