From: Mark Brown <broonie@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: ksummit-discuss@lists.linuxfoundation.org,
Rob Herring <robh+dt@kernel.org>, Zhang Rui <rui.zhang@intel.com>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Sensors and similar - subsystem interactions, divisions, bindings etc.
Date: Thu, 21 Jul 2016 20:10:28 +0100 [thread overview]
Message-ID: <20160721191028.GS6509@sirena.org.uk> (raw)
In-Reply-To: <5222c3bb-d6b7-0ccc-bf9e-becf5046a37a@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
On Wed, Jul 20, 2016 at 10:18:11PM +0100, Jonathan Cameron wrote:
> 4) Should we drop all the bindings for bridging between such subsystems
> and do it all from userspace?
This clearly doesn't seem sensible, we have plenty of hardware that's
obviously wired up in a fixed function format even if it could be
general purpose and several duplicated ABIs (eg, hwmon and power_supply
have clear overlap).
> I think we may end up with a hybrid of the two, but need to be able to
> make it work in 'standard' cases without userspace being involved. That
> hybrid solution may well be devicetree overlay based... Unclear so far.
> + plenty of crazy things that 'might' make sense where there isn't even
> the pretence of representing real hardware.
I'm definitely seeing people choosing their kernel subsystem on the
basis of libiio.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-07-21 19:10 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 [this message]
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
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=20160721191028.GS6509@sirena.org.uk \
--to=broonie@kernel.org \
--cc=jic23@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--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