Re: Interface between IIO driver and an input driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09/06/16 08:59, Lars-Peter Clausen wrote:
> On 06/03/2016 11:39 AM, Jonathan Cameron wrote:
>> On 03/06/16 09:12, Marc Titinger wrote:
>>>
>>> Hi All,
>>>
>>>
>>> (sorry Quentin, I here just share a related thought, not actually
>>> helping you much).
>>>
>>> a nice feature would be to have some sort of "mixer" interface,
>>> similar to the one common with audio APIs. 
>> Lars in particular has been looking at extending the media controller
>> interface somewhat in this direction (and into audio ;) This is
>> the big hammer solution. It'll be cool in the long run but I don't
>> get the impression it'll come terribly quickly.
> 
> 
> That's primarily for describing the flow between different hardware modules
> in hardware. I think in this case we only have software flow and in my
> opinion this hardware is a classical case of multi-function device and
> should be implemented as such. The MFD would take care of things like
> interrupt multiplexing and resource allocation while each function gets its
> own driver making use of the facilities provided by the MFD.
Fair enough, I think I agree that unfortunately there is too much touch
screen specific hardware handling to make a generic solution work.

I really ought to catch up with the media controller stuff ;)

> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Input]     [Linux Kernel]     [Linux SCSI]     [X.org]

  Powered by Linux