From: Pratyush Anand <[email protected]> Platform functions passed to the driver may also need some private data. Till, now following approaches have been taken to manage these data: -- SPEAr13xx platform keep it locally in the files defining platform functions. -- IMX has created a new ahci platform device as a child of platform device created by DT and then attached this data as the driver_data of ahci's dev->parent.
Adding a driver_data field helps in using the same platform driver as that of created by DT. Signed-off-by: Pratyush Anand <[email protected]> Tested-by: Mohit Kumar <[email protected]> Cc: Viresh Kumar <[email protected]> Cc: [email protected] Cc: [email protected] Cc: Tejun Heo <[email protected]> Cc: [email protected] Cc: [email protected] Cc: Arnd Bergmann <[email protected]> --- include/linux/ahci_platform.h | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/include/linux/ahci_platform.h b/include/linux/ahci_platform.h index 73a2500..76d35e8 100644 --- a/include/linux/ahci_platform.h +++ b/include/linux/ahci_platform.h @@ -28,6 +28,7 @@ struct ahci_platform_data { const struct ata_port_info *ata_port_info; unsigned int force_port_map; unsigned int mask_port_map; + void *driver_data; }; #endif /* _AHCI_PLATFORM_H */ -- 1.7.0.1 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
