On Mon, Jun 12, 2017 at 06:23:58PM -0700, Andrey Smirnov wrote: > Add a driver for RAVE Supervisory Processor, an MCU implementing > varoius bits of housekeeping functionality (watchdoging, backlight > control, LED control, etc) on RAVE family of products by Zodiac > Inflight Innovations. > > This driver implementes core MFD/serdev device as well as > communication subroutines necessary for commanding the device. > > Cc: cphealy@xxxxxxxxx > Cc: Lucas Stach <l.stach@xxxxxxxxxxxxxx> > Cc: Nikita Yushchenko <nikita.yoush@xxxxxxxxxxxxxxxxxx> > Cc: Rob Herring <robh+dt@xxxxxxxxxx> > Cc: Mark Rutland <mark.rutland@xxxxxxx> > Cc: devicetree@xxxxxxxxxxxxxxx > Cc: linux-kernel@xxxxxxxxxxxxxxx > Signed-off-by: Andrey Smirnov <andrew.smirnov@xxxxxxxxx> > --- > > Changes since [v1]: > > - Fix MODULE_LICENSE to specify "GPL v2" > > - Fix a bug in rave_sp_get_status() > > - Use %zu to fix warning repored by kbuild test robot > > - Remove "status" properties from examples zii,rave-sp.txt as well as > clarify the fact that device node is expected to be a child of a > serial device node > > NOTE: > > * The driver for "zii,rave-sp-watchdog" exists, but I haven't > submitted it yet, becuase I wanted to make sure that API exposed by > this MFD is acceptable and doesn't need drastic changes > > * This driver is dependent on crc_ccitt_false() introduced in > 2da9378d531f8cc6670c7497f20d936b706ab80b in 'linux-next' > > > [v1] lkml.kernel.org/r/20170606180643.14258-1-andrew.smirnov@xxxxxxxxx > > > .../devicetree/bindings/mfd/zii,rave-sp.txt | 36 + Acked-by: Rob Herring <robh@xxxxxxxxxx> > drivers/mfd/Kconfig | 9 + > drivers/mfd/Makefile | 1 + > drivers/mfd/rave-sp.c | 1009 ++++++++++++++++++++ > include/linux/rave-sp.h | 54 ++ > 5 files changed, 1109 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mfd/zii,rave-sp.txt > create mode 100644 drivers/mfd/rave-sp.c > create mode 100644 include/linux/rave-sp.h -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
