As discussed the Arizona device tree bindings documentation
will be split up into a seperate document holding properties
specific to each subsystem.
This series factors out the regulator and extcon
bindings. It will probably make sense to split out a GPIO
binding document as well but at the moment the only property
here is the gpio-defaults which are still handled in the MFD
driver and probably require significantly more thought to
split out.
Thanks,
Charles
Charles Keepax (3):
extcon: arizona: Add extcon specific device tree binding document
regulator: arizona: Add regulator specific device tree binding
document
mfd: arizona: Remove bindings covered in new subsystem specific docs
.../devicetree/bindings/extcon/extcon-arizona.txt | 15 +++++++++
Documentation/devicetree/bindings/mfd/arizona.txt | 30 ++---------------
.../bindings/regulator/arizona-regulator.txt | 34 ++++++++++++++++++++
MAINTAINERS | 3 ++
4 files changed, 55 insertions(+), 27 deletions(-)
create mode 100644 Documentation/devicetree/bindings/extcon/extcon-arizona.txt
create mode 100644
Documentation/devicetree/bindings/regulator/arizona-regulator.txt
--
1.7.2.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
