Home Explore Help
Sign In
phreedom2600net
/
linux-libre
Watch 2
Star 0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: c0b2c207da
Branches Tags
linux-libre
/
drivers
/
staging
/
iio
/
TODO

TODO 2.2 KB
History Raw

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677 
  1. 2009 8/18
    2. 

  2. 

  3. Core:
    4. 

  4. 1) Get reviews
    5. 

  5. 2) Additional testing
    6. 

  6. 3) Ensure all desirable features present by adding more devices.
    7. 

  7.    Major changes not expected except in response to comments
    8. 

  8. 

  9. Max1363 core:
    10. 

  10. 1) Possibly add sysfs exports of constant useful to userspace.
    11. 

  11. Would be nice
    12. 

  12. 2) Support hardware generated interrupts
    13. 

  13. 3) Expand device set. Lots of other maxim adc's have very
    14. 

  14.    similar interfaces.
    15. 

  15. 

  16. MXS LRADC driver:
    17. 

  17. This is a classic MFD device as it combines the following subdevices
    18. 

  18.  - touchscreen controller (input subsystem related device)
    19. 

  19.  - general purpose ADC channels
    20. 

  20.  - battery voltage monitor (power subsystem related device)
    21. 

  21.  - die temperature monitor (thermal management)
    22. 

  22. 

  23. At least the battery voltage and die temperature feature is required in-kernel
    24. 

  24. by a driver of the SoC's battery charging unit to avoid any damage to the
    25. 

  25. silicon and the battery.
    26. 

  26. 

  27. TSL2561
    28. 

  28. Would be nice
    29. 

  29. 1) Open question of userspace vs kernel space balance when
    30. 

  30. converting to useful light measurements from device ones.
    31. 

  31. 2) Add sysfs elements necessary to allow device agnostic
    32. 

  32. unit conversion.
    33. 

  33. 

  34. LIS3L02DQ core
    35. 

  35. 

  36. LIS3L02DQ ring
    37. 

  37. 

  38. KXSD9
    39. 

  39. Currently minimal driver, would be nice to add:
    40. 

  40. 1) Support for all chip generated interrupts (events),
    41. 

  41. basically get support up to level of lis3l02dq driver.
    42. 

  42. 

  43. Ring buffer core
    44. 

  44. 

  45. SCA3000
    46. 

  46. Would be nice
    47. 

  47. 1) Testing on devices other than sca3000-e05
    48. 

  48. 

  49. Trigger core support
    50. 

  50. 1) Discussion of approach. Is it general enough?
    51. 

  51. 

  52. Ring Buffer:
    53. 

  53. 1) Discussion of approach.
    54. 

  54. There are probably better ways of doing this. The
    55. 

  55. intention is to allow for more than one software ring
    56. 

  56. buffer implementation as different users will have
    57. 

  57. different requirements.  This one suits mid range
    58. 

  58. frequencies (100Hz - 4kHz).
    59. 

  59. 2) Lots of testing
    60. 

  60. 

  61. GPIO trigger
    62. 

  62. 1) Add control over the type of interrupt etc.  This will
    63. 

  63. necessitate a header that is also visible from arch board
    64. 

  64. files. (avoided at the moment to keep the driver set
    65. 

  65. contained in staging).
    66. 

  66. 

  67. ADI Drivers:
    68. 

  68. CC the device-drivers-devel@blackfin.uclinux.org mailing list when
    69. 

  69. e-mailing the normal IIO list (see below).
    70. 

  70. 

  71. Documentation
    72. 

  72. 1) Lots of cleanup and expansion.
    73. 

  73. 2) Some device require individual docs.
    74. 

  74. 

  75. Contact: Jonathan Cameron <jic23@kernel.org>.
    76. 

  76. Mailing list: linux-iio@vger.kernel.org
    77. 

  77.