search for: device_resum

...tion 'xen_suspend': linux-next-20080618/drivers/xen/manage.c:66: error: too few arguments to function 'device_power_up' linux-next-20080618/drivers/xen/manage.c: In function 'do_suspend': linux-next-20080618/drivers/xen/manage.c:115: error: too few arguments to function 'device_resume' make[3]: *** [drivers/xen/manage.o] Error 1 --- ~Randy Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA http://linuxplumbersconf.org/

...tion 'xen_suspend': linux-next-20080618/drivers/xen/manage.c:66: error: too few arguments to function 'device_power_up' linux-next-20080618/drivers/xen/manage.c: In function 'do_suspend': linux-next-20080618/drivers/xen/manage.c:115: error: too few arguments to function 'device_resume' make[3]: *** [drivers/xen/manage.o] Error 1 --- ~Randy Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA http://linuxplumbersconf.org/

...that can't be set by another cpu. However available hooks is run once on only one cpu so that ipi has to be used. During stop_machine_run() ipi can't be used because interrupt is masked. So add another hook after stop_machine_run(). Another approach might be use resume hook which is run by device_resume(). However device_resume() may be executed on suspend error recovery path. So it is necessary to determine whether it is executed on real resume path or error recovery path. Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> --- arch/x86/xen/suspend.c | 5 ++++- arch/x86/xen/xen-...

...that can't be set by another cpu. However available hooks is run once on only one cpu so that ipi has to be used. During stop_machine_run() ipi can't be used because interrupt is masked. So add another hook after stop_machine_run(). Another approach might be use resume hook which is run by device_resume(). However device_resume() may be executed on suspend error recovery path. So it is necessary to determine whether it is executed on real resume path or error recovery path. Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> --- arch/x86/xen/suspend.c | 5 ++++- arch/x86/xen/xen-...

...that can't be set by another cpu. However available hooks is run once on only one cpu so that ipi has to be used. During stop_machine_run() ipi can't be used because interrupt is masked. So add another hook after stop_machine_run(). Another approach might be use resume hook which is run by device_resume(). However device_resume() may be executed on suspend error recovery path. So it is necessary to determine whether it is executed on real resume path or error recovery path. Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> --- arch/x86/xen/suspend.c | 5 ++++- arch/x86/xen/xen-...

...evice_power_down' linux-next-20080528/drivers/xen/manage.c:65: error: implicit declaration of function 'device_power_up' linux-next-20080528/drivers/xen/manage.c: In function 'do_suspend': linux-next-20080528/drivers/xen/manage.c:114: error: implicit declaration of function 'device_resume' make[3]: *** [drivers/xen/manage.o] Error 1 --- ~Randy "He closes his eyes and drops the goggles. You can't get hurt by looking at a bitmap. Or can you?" -------------- next part -------------- A non-text attachment was scrubbed... Name: config-xen-nopm Type: application/octe...

...evice_power_down' linux-next-20080528/drivers/xen/manage.c:65: error: implicit declaration of function 'device_power_up' linux-next-20080528/drivers/xen/manage.c: In function 'do_suspend': linux-next-20080528/drivers/xen/manage.c:114: error: implicit declaration of function 'device_resume' make[3]: *** [drivers/xen/manage.o] Error 1 --- ~Randy "He closes his eyes and drops the goggles. You can't get hurt by looking at a bitmap. Or can you?" -------------- next part -------------- A non-text attachment was scrubbed... Name: config-xen-nopm Type: application/octe...

...cal resource. In this case, we need borrow some Linux PM stuff into xen suspend path, something like: Smp_suspend(); freeze_processes(); device_suspend(); device_power_down(); xenbus_suspend(); ... HYPERVISOR_suspend(virt_to_mfn(xen_start_info)); ... xenbus_resume(); device_power_up(); device_resume(); thaw_processes(); smp_resume(); It may be more difficult if we want to support wake-on-LAN when that NIC is assigned to domU, which is more tightly related to ACPI. So we will simply consider normal device suspend here. One interesting question is, why doesn''t current __xen_sus...

...x_status = st_fdma_tx_status; + fdev->dma_device.device_issue_pending = st_fdma_issue_pending; + fdev->dma_device.device_terminate_all = st_fdma_terminate_all; + fdev->dma_device.device_config = st_fdma_slave_config; + fdev->dma_device.device_pause = st_fdma_pause; + fdev->dma_device.device_resume = st_fdma_resume; + + fdev->dma_device.src_addr_widths = FDMA_DMA_BUSWIDTHS; + fdev->dma_device.dst_addr_widths = FDMA_DMA_BUSWIDTHS; + fdev->dma_device.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV); + fdev->dma_device.residue_granularity = DMA_RESIDUE_GRANULARITY_BURST; + + r...

Hi Vinod, Bjorn, Patrice, This patchset adds support for the Flexible Direct Memory Access (FDMA) core found on STi chipsets from STMicroelectronics. The FDMA is a slim core CPU with a dedicated firmware. It is a general purpose DMA controller supporting 16 independent channels and data can be moved from memory to memory or between memory and paced latency critical real time targets. After quite

Hi Vinod, Bjorn, Patrice, This patchset adds support for the Flexible Direct Memory Access (FDMA) core found on STi chipsets from STMicroelectronics. The FDMA is a slim core CPU with a dedicated firmware. It is a general purpose DMA controller supporting 16 independent channels and data can be moved from memory to memory or between memory and paced latency critical real time targets. After quite