APIs that didnt port well to multi-ness

[guruofquality]

• channel api -
  • frontend mapping - made the format a comma separated list. Not so bad, and this probably works for anyone using it - probably ok
• clock api -
  • clock rate api - sets the same rate to all devices -- probably ok
  • clock source api - no way to set source differently on different devices. A possible workaround might be to use comma separation like the frontend mapping.
• time api -
  • time source api - no way to set source differently on different devices. A possible workaround might be to use comma separation like the frontend mapping.
• register api -
  • read/write register does not specify a device -- this call is deprecated and has been replaced by a named version which will support multiple devices -- probably ok
• i2c and spi api - does not specify a specific bank, this api does not support multiple banks, let alone multiple devices. Probably needs named banks just like uarts, gpio, and the new register api

[guruofquality]

Created csv parser to use comma separate string for time and clock source as well as frontend mappings, this covers most important aspects of the multi-wrapper because we do need the time and clock part supported. HW interface wrappers probably dont matter here, but we can bank-ify them in the future API.