From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>,
Marc Titinger <mtitinger@baylibre.com>,
Quentin Schulz <quentin.schulz@free-electrons.com>,
linux-iio@vger.kernel.org
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
Antoine Tenart <antoine.tenart@free-electrons.com>
Subject: Re: Interface between IIO driver and an input driver
Date: Thu, 9 Jun 2016 09:59:42 +0200 [thread overview]
Message-ID: <575921EE.9090808@metafoo.de> (raw)
In-Reply-To: <1fb6beed-af47-8ffc-3422-d5ac53c8e832@kernel.org>
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.
next prev parent reply other threads:[~2016-06-09 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 7:17 Interface between IIO driver and an input driver Quentin Schulz
2016-06-03 8:12 ` Marc Titinger
2016-06-03 9:39 ` Jonathan Cameron
2016-06-09 7:59 ` Lars-Peter Clausen [this message]
2016-06-11 12:35 ` Jonathan Cameron
2016-06-03 9:21 ` Jonathan Cameron
2016-06-03 9:25 ` Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=575921EE.9090808@metafoo.de \
--to=lars@metafoo.de \
--cc=antoine.tenart@free-electrons.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=mtitinger@baylibre.com \
--cc=quentin.schulz@free-electrons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.