This series cleanups the nvec code a bit. The LED driver is renamed to
paz00 because it only makes sense on this device.

Some plan for the future:
        - add device tree init for the mfd childs and remove the hard coded
          (device dependent) init from the core driver
        - add a gpio and event driver
        - wait for tegra-slave support to arrive so the core driver can get
          rid of its own i2c init (which will kill most of the ToDo list).
        - fix the rest and try to push all the stuff one directory upwards

Changes since V3:
        - revert Change from V2->V3 again
        - pull out s/printk/drv_warn/ from first patch into a new patch

Changes since V2:
        - rebased against "[PATCH] Staging: nvec: fix coding style issues" from
          Adnan Ali <[email protected]>

Changes since V1:
        - fix several format patch issues
        - add driver registration to the power supply driver
        - add remove functions to mfd cells

Marc Dietrich (7):
  staging: nvec: convert to devm_ functions
  staging: nvec: use dev_warn instead of printk
  staging: nvec: cleanup driver registration
  staging: nvec: add NVEC_CALL helper macro
  staging: nvec: cleanup the string mess
  staging: nvec: rename led driver to board specific paz00 driver
  staging: nvec: add remove function to nvec childs

 drivers/staging/nvec/Kconfig                       |    9 +-
 drivers/staging/nvec/Makefile                      |    2 +-
 drivers/staging/nvec/nvec.c                        |  116 +++++++++-----------
 drivers/staging/nvec/nvec.h                        |   87 ++++++++++++++-
 drivers/staging/nvec/nvec_kbd.c                    |   47 ++++----
 drivers/staging/nvec/{nvec_leds.c => nvec_paz00.c} |   51 +++------
 drivers/staging/nvec/nvec_power.c                  |   43 +++++---
 drivers/staging/nvec/nvec_ps2.c                    |   60 +++++-----
 8 files changed, 243 insertions(+), 172 deletions(-)
 rename drivers/staging/nvec/{nvec_leds.c => nvec_paz00.c} (63%)

-- 
1.7.9.5

_______________________________________________
devel mailing list
[email protected]
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel

Reply via email to