Messages in this thread | | | Date | Tue, 22 May 2012 08:49:58 +0100 | From | Jonathan Cameron <> | Subject | Re: [PATCH v4] iio: add LM3533 ambient-light-sensor driver |
| |
On 5/22/2012 8:45 AM, Michael Hennerich wrote: > On 05/21/2012 06:37 PM, Jonathan Cameron wrote: >> Michael cc'd for comments on core support of some stuff that is also >> in frequency drivers down the end of the email. >> >> On 05/21/2012 10:50 AM, Johan Hovold wrote: >>> On Sat, May 19, 2012 at 09:48:23AM +0100, Jonathan Cameron wrote: >>>> On 05/18/2012 02:07 PM, Johan Hovold wrote: >>>> So to summarise, we get the following new sysfs-entries for the ALS >>>> (where the first set replace targetX_Y): >>>> >>>> out_currentX_currentY_raw r/w, (0..255), X in 0..2, Y in 0..4 >>>> out_currentX_raw ro (0..255), X in 0..2 >>>> >>>> Is there any support in core for the first set or should I simply >>>> rename my target attributes? >> No support in the core yet for this sort of thing.. >> Michael, any thoughts on this? In a sense it's very similar to >> out_altvoltageX_frequencyY_raw etc... >> > Hi, > > Exactly it's similar to what we have on the DDS parts. > The DDS parts would also benefit from a second index. > > Can someone think of an use case where we have 'differential' or 'modified' > together with this pattern? > > If not we could use channel2 and introduce an new flag, but I fear > that we end up using channel2 for too many things. > So we should better introduce an new variable? > New variable. Tedious but channel2 is getting rather too overloaded.
| |