[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1351184161-31433-1-git-send-email-computersforpeace@gmail.com>
Date: Thu, 25 Oct 2012 09:55:58 -0700
From: Brian Norris <computersforpeace@...il.com>
To: Jeff Garzik <jgarzik@...ox.com>
Cc: <linux-ide@...r.kernel.org>, <linux-pm@...ts.linux-foundation.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Brian Norris <computersforpeace@...il.com>,
Kevin Cernekee <cernekee@...il.com>, Tejun Heo <tj@...nel.org>
Subject: [RFC 0/3] libata/ahci unbinding, power down sequence
Hello,
I sent out a few questions/suggestions earlier, regarding some trouble I was
having in supporting my SoC SATA controller under the libata / ahci_platform
driver:
http://article.gmane.org/gmane.linux.ide/52951/match=unbind+rmmod
I think I have identified a problem in libata's handling of hardware activity
at device removal/exit (relevant to my use-case of unbind or rmmod). This patch series:
(1) Allows ahci_platform to unbind a device from the driver. This is useful for
allowing total power-off of the device, for instance.
(2) Modifies libata-core so that ata_host_stop() is not called as a devres
cleanup function (after all driver-specific functions, including power-off)
The first two patches are relatively harmless and correct, I believe, where the
third patch is more significant and could use good review. I am sending code
because I hear no response to my standalone suggestions :) Please see my
previous email (URL above) and/or patch 3/3 for a more detailed description.
Thanks,
Brian
Brian Norris (3):
ahci_platform: enable hotplug unbinding
ahci_platform: convert to module_platform_driver
libata: don't perform HW activity in devres
drivers/ata/ahci_platform.c | 16 +++-------------
drivers/ata/libata-core.c | 18 +++---------------
2 files changed, 6 insertions(+), 28 deletions(-)
--
1.7.11.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists