The X-Powers AC100 provides an RTC and an audio codec to at least the Banana Pi-M3 (a83t). Driver is ported from NetBSD, currently only supports the RTC bits.
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Skipped - Unit
Tests Skipped - Build Status
Buildable 12967
Event Timeline
sys/arm/allwinner/files.allwinner | ||
---|---|---|
16 | This should by optional ac100 |
It feels like this should be 2 drivers. One to talk with the ac100, and a second jsut for the rtc bits.
You never talk to the ac100, only to the rtc bits or the coded bits.
This is what DT calls MFD (Multi Function Device) and I never knew what is the best way to represent it in our drivers.
standard -> optional ac100, add ac100 to the arm/GENERIC config near rsb and axp209/axp81x.
This is what DT calls MFD (Multi Function Device) and I never knew what is the best way to represent it in our drivers.
How would an eventual codec driver interact with this one?
AFAICT, it's intended that the AC100 bits should be an all-in-one kind of driver, thus the codec driver would "attach" like the RTC does here; not actually having its own resources or anything to that effect, and sharing a context with the RTC.