Add dev_sysdata and use it for ACPI
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Add arch specific dev_sysdata to struct deviceinclude/ include/ include/ +24 more | +367 | 2 replies | |
| 2/2 | Change ACPI to use dev_sysdata instead of firmware_datadrivers/ include/ include/ +3 more | +21 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] Add dev_sysdata and use it for ACPI
Due to the total absence of feedback (except Cornelia who'd like to use this for s390 too), I'm reposting them here as they affect all archs (and Willy admitted not seeing them on lkml).
I've already rebased all of my pending 2.6.20 powerpc stuff on top of Patch 1/2, so I hope there won't be any major objection.
Patch 2/2 is not as urgent/important, Len, it's up to you to decide wether you want to take the approach or not, but I feel like this void * firmware_data in struct device is now userless, so ...
1/2 - Add a dev_sysdata structure to struct device whose content is arch specific. It will allow architectures like powerpc, arm, i386, ... who need different types of DMA ops for busses and other kind of auxilliary data for devices in general (numa node id, firmware data, etc...) to put them in there, without bloating all architectures. The patch adds an empty definition for the structure to all architectures.
2/2 - As an example (patch test built but not test booted), I removed ACPI usage of device->firmware_data, removed the firmware_data field completely from struct device (as it was, apparently, the only user), and instead used an "acpi_handle" field in i386, x86_64 and ia64 dev_sysdata.
Cheers,
Ben.