i2c: Use the standard, alias-based device/driver matching scheme
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 of 3 patches 7 repliesIn review
2 of 3 patches are in this archive. The cover letter announces 3.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | i2c: Add support for device alias namesdrivers/ drivers/ drivers/ +10 more | +90 | 0 replies | |
| 2/3 | i2c: Convert all new-style drivers to use module aliasingarch/ arch/ arch/ +17 more | +120 | 5 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] i2c: Use the standard, alias-based device/driver matching scheme
Hi all,
Here comes a patch set, based on earlier work by Jon Smirl, that updates the i2c subsystem to support and use the standard, alias-based device/driver matching scheme that most other subsystems are using. Contrary to Jon's patch set, this one only supports Linux names and not OF names, although it might be added later (just not sure how exactly.)
Patch 1/3 adds support for this standard matching scheme, patch 2/3 converts all the in-tree drivers to make use of it, and patch 3/3 removes the old driver_name/type matching scheme that has no users left at this point.
This new approach makes the i2c device drivers smaller in general (because the name matching code moved to i2c-core), the exception being drivers which support only one device, for which the device ID table adds a small overhead (88 bytes on x86_64).
The key benefit compared to the original matching scheme is that platform code no longer needs to know which driver supports which device. This means that support for a given device can move from one driver to another without changing the platform code.
Note: all the arm and powerpc stuff is untested.
Signature · 1 line
Jean Delvare