From: Vinod Koul <vinod.koul@intel.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Zhang Rui <rui.zhang@intel.com>, Rob Herring <robh+dt@kernel.org>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Sensors and similar - subsystem interactions, divisions, bindings etc.
Date: Sun, 31 Jul 2016 23:17:58 +0530 [thread overview]
Message-ID: <20160731174758.GP9681@localhost> (raw)
In-Reply-To: <579A54A6.5060303@metafoo.de>
On Thu, Jul 28, 2016 at 08:53:26PM +0200, Lars-Peter Clausen wrote:
> So new hardware often tends to be general purpose and can be used in
> many different applications.
>
> But our kernel frameworks are designed around application specific tasks.
>
> * ALSA is for audio data capture/playback
> * V4L2 is for video data capture/playback
> * DRM is for video display
> * IIO is for sensor data capture/playback
Spot on. Even if you look at kernel source code we have directory based on
end usage..
Also these subsystems expose a user interface for sending/receiving data.
The interface is application specific. One can argue that designing a generic
data interface is kernel which can take care of high volume, bursty or
continuous data, then potentially we can unify these
> When you capture data over a particular interface there is a specific
> meaning associated to the data rather than the data just being data,
> which is how the hardware might see it.
>
> On the kernel side we have started to address this by having generic
> frameworks like DMAengine. I've used the same DMA core with the same
> DMAengine driver exposed to userspace for all four different types
> listed above depending on the application.
Yes DMAengine framework is generic for application usage. We don't define
the purpose of DMA but we care about nature, memcpy, slave, interleaved...
You can use these for audio, video, RAID or anything else..
> This of course would be a very grand task and maybe we'll loose
> ourselves in endless discussions about the details and all the corner
> cases that need to be considered. But if we want to find a solution that
> keeps up with the current trend that the hardware landscape seems to be
> going in we might have no other choice. Otherwise I'd say it is
> inevitable that we see more and more hardware which has multiple
> drivers, each driver handling a different type of application.
Given that SoCs are becoming complex and HW folks are merging stuff, I
wont be surprised if we get a converged hardware which does multiple
jobs, so we would need these to be unified.
--
~Vinod
next prev parent reply other threads:[~2016-07-31 17:40 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 21:18 Jonathan Cameron
2016-07-21 7:39 ` Hans Verkuil
2016-07-22 19:37 ` Jonathan Cameron
2016-07-28 16:50 ` Laurent Pinchart
2016-07-21 19:10 ` Mark Brown
2016-07-22 3:29 ` Guenter Roeck
2016-07-22 4:18 ` Torokhov
2016-07-22 19:01 ` Jonathan Cameron
2016-07-22 10:21 ` Mark Brown
2016-07-22 19:31 ` Jonathan Cameron
2016-07-23 2:29 ` Sebastian Reichel
2016-07-28 21:30 ` Lars-Peter Clausen
2016-07-28 22:39 ` Jonathan Cameron
2016-07-29 0:56 ` Guenter Roeck
2016-07-29 5:54 ` Jonathan Cameron
2016-07-22 12:04 ` Linus Walleij
2016-07-22 19:22 ` Jonathan Cameron
2016-07-28 16:46 ` Laurent Pinchart
2016-07-28 18:08 ` Lars-Peter Clausen
2016-08-02 19:55 ` Linus Walleij
2016-07-28 22:07 ` Jonathan Cameron
2016-08-02 19:50 ` Linus Walleij
2016-07-27 3:12 ` Vinod Koul
2016-07-28 11:58 ` Mauro Carvalho Chehab
2016-07-28 16:42 ` Laurent Pinchart
2016-07-28 22:09 ` Jonathan Cameron
2016-08-01 11:03 ` Laurent Pinchart
2016-07-29 7:28 ` Hans Verkuil
2016-08-01 11:47 ` Laurent Pinchart
2016-07-28 22:32 ` Jonathan Cameron
2016-07-28 16:39 ` Laurent Pinchart
2016-07-28 18:53 ` Lars-Peter Clausen
2016-07-28 19:46 ` Mark Brown
2016-07-31 17:47 ` Vinod Koul [this message]
2016-08-01 12:14 ` Laurent Pinchart
2016-07-28 22:26 ` Jonathan Cameron
2016-07-29 7:36 ` Hans Verkuil
2016-08-01 11:19 ` Laurent Pinchart
2016-07-28 19:12 ` Lars-Peter Clausen
2016-07-28 23:38 ` Alexandre Belloni
2016-07-29 6:04 ` 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=20160731174758.GP9681@localhost \
--to=vinod.koul@intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=lars@metafoo.de \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox