[RFC 0/2] [media] si4713 DT binding

From: Sebastian Reichel
Date: Sun Apr 06 2014 - 07:52:54 EST


Hi,

This is an RFC patch adding DT support to the si4713 radio transmitter i2c
driver. The changes can be summarized as follows:

* Move regulator information back into the driver. The regulators needed are
documented in the chip and have nothing to do with boarddata. Instead
devm_regulator_get_optional and errors are handled quite loosely now.
Maybe the USB driver should provide dummy regulators.
* GPIO handling is updated to gpiod consumer interface, resulting in a driver
cleanup and easy DT handling
* The driver is updated to use managed resources wherever possible

So much about the nice stuff. But there is also

* Instantiation of the platform device from the i2c (sub-)device. Since DT
is not supposed to contain linuxisms the device is a simple i2c node
resulting in the i2c probe function being called. Thus registering the main
v4l device must happen from there.

Tested:
* Compilation on torvalds/linux.git:master
* Booting in DT mode
* Some simply driver queries using v4l2-ctl

Not tested:
* The USB driver, since I do not own the USB dongle
* The legacy platform code (only DT boot has been tested).
(The legacy platform code is supposed to removed in the near future anyways)

-- Sebastian

Sebastian Reichel (2):
[media] si4713: add Device Tree support
[media] Ad DT binding documentation for si4713

Documentation/devicetree/bindings/media/si4713.txt | 30 ++++
arch/arm/mach-omap2/board-rx51-peripherals.c | 67 ++++-----
drivers/media/radio/si4713/radio-platform-si4713.c | 28 +---
drivers/media/radio/si4713/si4713.c | 166 +++++++++++++--------
drivers/media/radio/si4713/si4713.h | 15 +-
include/media/radio-si4713.h | 30 ----
include/media/si4713.h | 4 +-
7 files changed, 183 insertions(+), 157 deletions(-)
create mode 100644 Documentation/devicetree/bindings/media/si4713.txt
delete mode 100644 include/media/radio-si4713.h

--
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/