au1000_eth platform device/driver conversion
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 10 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | alchemy: register au1000_eth as a platform driver part onearch/ | +64 | 5 replies | |
| 2/4 | au1000_eth: convert to a platform_driver part onedrivers/ | +157 | 0 replies | |
| 3/4 | alchemy: pass PHY informations to au1000_etharch/ arch/ | +36 | 0 replies | |
| 4/4 | au1000_eth: platform_driver conversion part twodrivers/ drivers/ | +81 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] au1000_eth platform device/driver conversion
Hi Ralf, David, Manuel,
The following patches convert the AMD Alchemy au1000_eth driver to become a platform device/driver. The patches are splitted that way:
PATCH 1: set up the infrastructure in the board code to register au1000_eth as as platform device.
PATCH 2: convert au1000_eth to become a real platform driver PATCH 3: add infrastructure to pass PHY informations to the au1000_eth driver PATCH 4: use those platform_data PHY informations in the au1000_eth driver
The result is a driver which is equally functionnal with no platform-related ifdefs aiming towards easier integration of the upcoming Alchemy 1300 SoC. The conversion was made in two times to ease code review as the driver was a real ifdef mess prior to these changes.
David, on top of this series I send driver cleanups.
Thanks !
Signature · 5 lines
Best regards, Florian Fainelli Email: [email protected] Web: http://openwrt.org IRC: [florian] on irc.freenode.net -------------------------------