From: Mark Brown <broonie@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINER SUMMIT] User-space requirements for accelerator drivers
Date: Mon, 13 Sep 2021 13:04:41 +0100 [thread overview]
Message-ID: <20210913120441.GD4283@sirena.org.uk> (raw)
In-Reply-To: <YTx2iShbdcrY4SMk@pendragon.ideasonboard.com>
[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]
On Sat, Sep 11, 2021 at 12:27:37PM +0300, Laurent Pinchart wrote:
> On Sat, Sep 11, 2021 at 02:38:11AM +0200, Mauro Carvalho Chehab wrote:
> > > which we
> > > could consider as an alternative to the open userspace implementation
> > > (a topic worth discussing I believe).
> > Yeah, a public datasheet sounds an interesting requirement. It offers
> > a problem, though: maybe some details could be missed on it, which
> > would prevent any real open source userspace development.
> Absolutely, and I don't think we can come up with any process and
> technical measure that would prevent a vendor from cheating if they
> really want to. It will always be possible to hide some features behind
> reserved registers that wouldn't need to be programmed for basic
> operation but that would be crucial to optimize the quality or
> performances. This is regardless of whether we want to enforce openness
> of documentation in the form of datasheets or source code.
This is already very standard in some parts of the industry, even
between vendors and customers. Sometimes it's done intentionally but
it's also often just that the actual practical configuration process
relies on some non-trivial test system and perhaps has as much art as
science involved. It can also be a decision about managing support
costs which works for everyone involved on the business side - sometimes
the product being delivered includes the vendor doing a good deal of the
tuning for some combination of cost and complexity reasons.
> I'm not too concerned about this though. If we can address most of this
> issue with a clear process and message I think it would be a very good
> step forward already.
Yeah, I'm personally not so concerned about the callibration and tuning
side - ideally that would be fully open but like you say even without
that we've achieved something and there may not actually be anything
extant to open.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-09-13 12:05 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 21:00 [MAINTAINER SUMMIT] User-space requirements for accelerator drivers Jonathan Corbet
2021-09-10 21:32 ` Josh Triplett
2021-09-13 13:50 ` Christian Brauner
2021-09-13 13:57 ` Daniel Vetter
2021-09-14 2:07 ` Laurent Pinchart
2021-09-14 14:40 ` Jani Nikula
2021-09-14 14:45 ` Geert Uytterhoeven
2021-09-14 14:59 ` Jani Nikula
2021-09-14 15:10 ` Geert Uytterhoeven
2021-09-10 21:51 ` James Bottomley
2021-09-10 21:59 ` Alexandre Belloni
2021-09-10 22:35 ` James Bottomley
2021-09-11 14:51 ` Jonathan Corbet
2021-09-11 15:24 ` James Bottomley
2021-09-11 21:52 ` Laurent Pinchart
2021-09-14 13:22 ` Johannes Berg
2021-09-11 0:08 ` Laurent Pinchart
2021-09-10 22:52 ` Mauro Carvalho Chehab
2021-09-10 23:45 ` Josh Triplett
2021-09-10 23:48 ` Dave Hansen
2021-09-11 0:13 ` Laurent Pinchart
2021-09-10 23:55 ` Thomas Gleixner
2021-09-11 0:20 ` Laurent Pinchart
2021-09-11 14:20 ` Steven Rostedt
2021-09-11 22:08 ` Laurent Pinchart
2021-09-11 22:42 ` Steven Rostedt
2021-09-11 23:10 ` Laurent Pinchart
2021-09-13 11:10 ` Mark Brown
2021-09-11 22:51 ` Mauro Carvalho Chehab
2021-09-11 23:22 ` Mauro Carvalho Chehab
2021-09-11 10:31 ` Leon Romanovsky
2021-09-11 11:41 ` Laurent Pinchart
2021-09-11 12:04 ` Leon Romanovsky
2021-09-11 22:04 ` Laurent Pinchart
2021-09-12 4:27 ` Leon Romanovsky
2021-09-12 7:26 ` Greg KH
2021-09-12 8:29 ` Leon Romanovsky
2021-09-12 13:25 ` Greg KH
2021-09-12 14:15 ` Leon Romanovsky
2021-09-12 14:34 ` Greg KH
2021-09-12 16:41 ` Laurent Pinchart
2021-09-12 20:35 ` Dave Airlie
2021-09-12 20:41 ` Dave Airlie
2021-09-12 20:49 ` Daniel Vetter
2021-09-12 21:12 ` Dave Airlie
2021-09-12 22:51 ` Linus Walleij
2021-09-12 23:15 ` Dave Airlie
2021-09-13 13:20 ` Arnd Bergmann
2021-09-13 13:54 ` Daniel Vetter
2021-09-13 22:04 ` Arnd Bergmann
2021-09-13 23:33 ` Dave Airlie
2021-09-14 9:08 ` Arnd Bergmann
2021-09-14 9:23 ` Daniel Vetter
2021-09-14 10:47 ` Laurent Pinchart
2021-09-14 12:58 ` Arnd Bergmann
2021-09-14 19:45 ` Daniel Vetter
2021-09-14 15:43 ` Luck, Tony
2021-09-13 14:52 ` James Bottomley
2021-09-14 13:07 ` Linus Walleij
2021-09-13 14:03 ` Mark Brown
2021-09-12 15:55 ` Laurent Pinchart
2021-09-12 16:43 ` James Bottomley
2021-09-12 16:58 ` Laurent Pinchart
2021-09-12 17:08 ` James Bottomley
2021-09-12 19:52 ` Dave Airlie
2021-09-12 7:46 ` Mauro Carvalho Chehab
2021-09-12 8:00 ` Leon Romanovsky
2021-09-12 14:53 ` Laurent Pinchart
2021-09-12 15:41 ` Mauro Carvalho Chehab
2021-09-10 23:46 ` Laurent Pinchart
2021-09-11 0:38 ` Mauro Carvalho Chehab
2021-09-11 9:27 ` Laurent Pinchart
2021-09-11 22:33 ` Mauro Carvalho Chehab
2021-09-13 12:04 ` Mark Brown [this message]
2021-09-12 19:13 ` Dave Airlie
2021-09-12 19:48 ` Laurent Pinchart
2021-09-13 2:26 ` Dave Airlie
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=20210913120441.GD4283@sirena.org.uk \
--to=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=mchehab@kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).