Date: Fri, 03 Oct 2003 02:21:19 +0800 From: Jia-Shiun Li <jsli@mail2000.com.tw> To: walter@pelissero.de Cc: hackers@freebsd.org Subject: Re: CAM suspend Message-ID: <3F7C6C9F.5060401@mail2000.com.tw> In-Reply-To: <16250.55661.682838.198052@hyde.home.loc> References: <16250.55661.682838.198052@hyde.home.loc>
next in thread | previous in thread | raw e-mail | index | archive | help
Since the memory content will be kept across suspension, I guess there is no need for da to take special care. Just like what ad does. The actual suspend/resume method is for ata-pci. For hardware devices to come back to previous state, the correct place may be in SCSI HBA driver like ahc, sym, etc.? Jia-Shiun. Walter C. Pelissero wrote: > Having noticed that there is not a big interest in it, among the > fellow FreeBSDers, I was about to set off and hack up the scsi > subsystem to implement spindown on suspend and spinup on resume of the > da devices, when I realized that there seems to be no hook in the SCSI > code for this events. > > I'm not a device driver expert, so I'm looking for clues. > > What I mean is that the ata-pci driver, for instance, specifies hooks > via the device_method_t structure which is not available in the > scsi_all or scsi_da modules. I understand that they are simply > different kind of beasts (sitting on different layers of the kernel > code), but I was wondering if there might be a similar mechanism to do > what I want. > > So, what is the recommended way (if there is one), to hook a function > of the SCSI subsystem to an event like suspend/resume? > > I would most appreciate if anyone could point me to a suitable > document or even anything related to FreeBSD kernel hacking. > > Cheers, >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F7C6C9F.5060401>