renegade-project/linux-next
2
0
Fork 0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-12-29 07:34:06 +08:00
Code
2b07be2493
linux-next/arch/sparc/include/asm/device.h

24 lines
375 B
C
Raw Normal View History

Driver core: add dev_archdata to struct device Add arch specific dev_archdata to struct device Adds an arch specific struct dev_arch to struct device. This enables architecture to add specific fields to every device in the system, like DMA operation pointers, NUMA node ID, firmware specific data, etc... Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Acked-by: Andi Kleen <ak@suse.de> Acked-By: David Howells <dhowells@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-11-11 14:18:39 +08:00
/*
* Arch specific extensions to struct device
*
* This file is released under the GPLv2
*/
[SPARC]: Define minimal struct dev_archdata, similarly to sparc64. Signed-off-by: David S. Miller <davem@davemloft.net>
2007-07-19 11:59:54 +08:00
#ifndef _ASM_SPARC_DEVICE_H
#define _ASM_SPARC_DEVICE_H
struct device_node;
struct of_device;
struct dev_archdata {
[SPARC64]: Fix conflicts in SBUS/PCI/EBUS/ISA DMA handling. Fully unify all of the DMA ops so that subordinate bus types to the DMA operation providers (such as ebus, isa, of_device) can work transparently. Basically, we just make sure that for every system device we create, the dev->archdata 'iommu' and 'stc' fields are filled in. Then we have two platform variants of the DMA ops, one for SUN4U which actually programs the real hardware, and one for SUN4V which makes hypervisor calls. This also fixes the crashes in parport_pc on sparc64, reported by Meelis Roos. Signed-off-by: David S. Miller <davem@davemloft.net>
2007-07-28 13:39:14 +08:00
void *iommu;
void *stc;
void *host_controller;
[SPARC]: Define minimal struct dev_archdata, similarly to sparc64. Signed-off-by: David S. Miller <davem@davemloft.net>
2007-07-19 11:59:54 +08:00
struct of_device *op;
[SPARC64]: NUMA device infrastructure. Record and propagate NUMA information for devices. Signed-off-by: David S. Miller <davem@davemloft.net>
2008-03-19 19:52:48 +08:00
int numa_node;
[SPARC]: Define minimal struct dev_archdata, similarly to sparc64. Signed-off-by: David S. Miller <davem@davemloft.net>
2007-07-19 11:59:54 +08:00
};
Driver Core: Add platform device arch data V3 Allow architecture specific data in struct platform_device V3. With this patch struct pdev_archdata is added to struct platform_device, similar to struct dev_archdata in found in struct device. Useful for architecture code that needs to keep extra data associated with each platform device. Struct pdev_archdata is different from dev.platform_data, the convention is that dev.platform_data points to driver-specific data. It may or may not be required by the driver. The format of this depends on driver but is the same across architectures. The structure pdev_archdata is a place for architecture specific data. This data is handled by architecture specific code (for example runtime PM), and since it is architecture specific it should _never_ be touched by device driver code. Exactly like struct dev_archdata but for platform devices. [rjw: This change is for power management mostly and that's why it goes through the suspend tree.] Signed-off-by: Magnus Damm <damm@igel.co.jp> Acked-by: Kevin Hilman <khilman@deeprootsystems.com> Acked-by: Greg Kroah-Hartman <gregkh@suse.de> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2009-07-08 19:21:31 +08:00
struct pdev_archdata {
};
[SPARC]: Define minimal struct dev_archdata, similarly to sparc64. Signed-off-by: David S. Miller <davem@davemloft.net>
2007-07-19 11:59:54 +08:00
#endif /* _ASM_SPARC_DEVICE_H */
Copy Permalink