On Thu, Jun 17, 2021 at 05:38:36PM +0200, Philippe CORNU wrote:
> 
> 
> On 6/16/21 4:38 PM, Maxime Ripard wrote:
> > New KMS properties come with a bunch of requirements to avoid each
> > driver from running their own, inconsistent, set of properties,
> > eventually leading to issues like property conflicts, inconsistencies
> > between drivers and semantics, etc.
> > 
> > Let's document what we expect.
> > 
> > Cc: Alexandre Belloni <alexandre.bell...@bootlin.com>
> > Cc: Alexandre Torgue <alexandre.tor...@foss.st.com>
> > Cc: Alex Deucher <alexander.deuc...@amd.com>
> > Cc: Alison Wang <alison.w...@nxp.com>
> > Cc: Alyssa Rosenzweig <alyssa.rosenzw...@collabora.com>
> > Cc: Andrew Jeffery <and...@aj.id.au>
> > Cc: Andrzej Hajda <a.ha...@samsung.com>
> > Cc: Anitha Chrisanthus <anitha.chrisant...@intel.com>
> > Cc: Benjamin Gaignard <benjamin.gaign...@linaro.org>
> > Cc: Ben Skeggs <bske...@redhat.com>
> > Cc: Boris Brezillon <bbrezil...@kernel.org>
> > Cc: Brian Starkey <brian.star...@arm.com>
> > Cc: Chen Feng <puck.c...@hisilicon.com>
> > Cc: Chen-Yu Tsai <w...@csie.org>
> > Cc: Christian Gmeiner <christian.gmei...@gmail.com>
> > Cc: "Christian König" <christian.koe...@amd.com>
> > Cc: Chun-Kuang Hu <chunkuang...@kernel.org>
> > Cc: Edmund Dea <edmund.j....@intel.com>
> > Cc: Eric Anholt <e...@anholt.net>
> > Cc: Fabio Estevam <feste...@gmail.com>
> > Cc: Gerd Hoffmann <kra...@redhat.com>
> > Cc: Haneen Mohammed <hamohammed...@gmail.com>
> > Cc: Hans de Goede <hdego...@redhat.com>
> > Cc: "Heiko Stübner" <he...@sntech.de>
> > Cc: Huang Rui <ray.hu...@amd.com>
> > Cc: Hyun Kwon <hyun.k...@xilinx.com>
> > Cc: Inki Dae <inki....@samsung.com>
> > Cc: Jani Nikula <jani.nik...@linux.intel.com>
> > Cc: Jernej Skrabec <jernej.skra...@siol.net>
> > Cc: Jerome Brunet <jbru...@baylibre.com>
> > Cc: Joel Stanley <j...@jms.id.au>
> > Cc: John Stultz <john.stu...@linaro.org>
> > Cc: Jonas Karlman <jo...@kwiboo.se>
> > Cc: Jonathan Hunter <jonath...@nvidia.com>
> > Cc: Joonas Lahtinen <joonas.lahti...@linux.intel.com>
> > Cc: Joonyoung Shim <jy0922.s...@samsung.com>
> > Cc: Jyri Sarha <jyri.sa...@iki.fi>
> > Cc: Kevin Hilman <khil...@baylibre.com>
> > Cc: Kieran Bingham <kieran.bingham+rene...@ideasonboard.com>
> > Cc: Krzysztof Kozlowski <krzysztof.kozlow...@canonical.com>
> > Cc: Kyungmin Park <kyungmin.p...@samsung.com>
> > Cc: Laurent Pinchart <laurent.pinch...@ideasonboard.com>
> > Cc: Linus Walleij <linus.wall...@linaro.org>
> > Cc: Liviu Dudau <liviu.du...@arm.com>
> > Cc: Lucas Stach <l.st...@pengutronix.de>
> > Cc: Ludovic Desroches <ludovic.desroc...@microchip.com>
> > Cc: Marek Vasut <ma...@denx.de>
> > Cc: Martin Blumenstingl <martin.blumensti...@googlemail.com>
> > Cc: Matthias Brugger <matthias....@gmail.com>
> > Cc: Maxime Coquelin <mcoquelin.st...@gmail.com>
> > Cc: Maxime Ripard <mrip...@kernel.org>
> > Cc: Melissa Wen <melissa....@gmail.com>
> > Cc: Neil Armstrong <narmstr...@baylibre.com>
> > Cc: Nicolas Ferre <nicolas.fe...@microchip.com>
> > Cc: "Noralf Trønnes" <nor...@tronnes.org>
> > Cc: NXP Linux Team <linux-...@nxp.com>
> > Cc: Oleksandr Andrushchenko <oleksandr_andrushche...@epam.com>
> > Cc: Patrik Jakobsson <patrik.r.jakobs...@gmail.com>
> > Cc: Paul Cercueil <p...@crapouillou.net>
> > Cc: Pekka Paalanen <pekka.paala...@collabora.com>
> > Cc: Pengutronix Kernel Team <ker...@pengutronix.de>
> > Cc: Philippe Cornu <philippe.co...@foss.st.com>
> > Cc: Philipp Zabel <p.za...@pengutronix.de>
> > Cc: Qiang Yu <yuq...@gmail.com>
> > Cc: Rob Clark <robdcl...@gmail.com>
> > Cc: Robert Foss <robert.f...@linaro.org>
> > Cc: Rob Herring <r...@kernel.org>
> > Cc: Rodrigo Siqueira <rodrigosiqueiram...@gmail.com>
> > Cc: Rodrigo Vivi <rodrigo.v...@intel.com>
> > Cc: Roland Scheidegger <srol...@vmware.com>
> > Cc: Russell King <li...@armlinux.org.uk>
> > Cc: Sam Ravnborg <s...@ravnborg.org>
> > Cc: Sandy Huang <h...@rock-chips.com>
> > Cc: Sascha Hauer <s.ha...@pengutronix.de>
> > Cc: Sean Paul <s...@poorly.run>
> > Cc: Seung-Woo Kim <sw0312....@samsung.com>
> > Cc: Shawn Guo <shawn...@kernel.org>
> > Cc: Simon Ser <cont...@emersion.fr>
> > Cc: Stefan Agner <ste...@agner.ch>
> > Cc: Steven Price <steven.pr...@arm.com>
> > Cc: Sumit Semwal <sumit.sem...@linaro.org>
> > Cc: Thierry Reding <thierry.red...@gmail.com>
> > Cc: Tian Tao <tiant...@hisilicon.com>
> > Cc: Tomeu Vizoso <tomeu.viz...@collabora.com>
> > Cc: Tomi Valkeinen <to...@kernel.org>
> > Cc: VMware Graphics <linux-graphics-maintai...@vmware.com>
> > Cc: Xinliang Liu <xinliang....@linaro.org>
> > Cc: Xinwei Kong <kong.kongxin...@hisilicon.com>
> > Cc: Yannick Fertre <yannick.fer...@foss.st.com>
> > Cc: Zack Rusin <za...@vmware.com>
> > Reviewed-by: Daniel Vetter <daniel.vet...@ffwll.ch>
> > Signed-off-by: Maxime Ripard <max...@cerno.tech>
> > 
> > ---
> > 
> > Changes from v3:
> >    - Roll back to the v2
> >    - Add Simon and Pekka in Cc
> > 
> > Changes from v2:
> >    - Take into account the feedback from Laurent and Lidiu to no longer
> >      force generic properties, but prefix vendor-specific properties with
> >      the vendor name
> > 
> > Changes from v1:
> >    - Typos and wording reported by Daniel and Alex
> > ---
> >   Documentation/gpu/drm-kms.rst | 19 +++++++++++++++++++
> >   1 file changed, 19 insertions(+)
> > 
> > diff --git a/Documentation/gpu/drm-kms.rst b/Documentation/gpu/drm-kms.rst
> > index 87e5023e3f55..c28b464dd397 100644
> > --- a/Documentation/gpu/drm-kms.rst
> > +++ b/Documentation/gpu/drm-kms.rst
> > @@ -463,6 +463,25 @@ KMS Properties
> >   This section of the documentation is primarily aimed at user-space 
> > developers.
> >   For the driver APIs, see the other sections.
> > +Requirements
> > +------------
> > +
> > +KMS drivers might need to add extra properties to support new features.
> > +Each new property introduced in a driver need to meet a few
> > +requirements, in addition to the one mentioned above.:
> > +
> > +- It must be standardized, with some documentation to describe how the
> > +  property can be used.
> > +
> > +- It must provide a generic helper in the core code to register that
> > +  property on the object it attaches to.
> > +
> > +- Its content must be decoded by the core and provided in the object's
> > +  associated state structure. That includes anything drivers might want to
> > +  precompute, like :c:type:`struct drm_clip_rect <drm_clip_rect>` for 
> > planes.
> > +
> > +- An IGT test must be submitted where reasonable.
> > +
> >   Property Types and Blob Property Support
> >   ----------------------------------------
> > 
> 
> Hi,
> 
> Regarding properties, we have a “case study example” related in a certain
> way to this documentation update :-)
> 
> The use case: on a front desk at an exhibition, there is a welcome screen
> you can touch for searching various information. When this welcome screen is
> in idle, a small logo is displayed at its center (around 20% of the
> fullscreen). The logo has a white background color. We want to reduce the
> ddr usage for lowering the power (the board is battery powered) so the idea
> is to use a white background color around this logo, produced by the drm
> CRTC so the image in ddr is only the size of the logo.
> 
> Reading the thread
> https://lists.freedesktop.org/archives/dri-devel/2019-October/239733.html
> dissuade us from coding a generic solution, so we started to implement a
> "STM_" private background color property, it works... but we are not at all
> convince this is the right way and we clearly prefer mainline/generic sw for
> both kernel & userland.
> 
> So now, what are our options... well, this v4 documentation update is I
> think clear enough: we have to document + provide a generic helper in the
> core code (similar to the original patch) + update IGT test, right?

Yeah, also background color has been talked about for a while (lots of hw
can do it), it's just that no one ever found a use-case to make the
background somethign else than "black". There's a pile of drivers who
could expose this, so definitely makes sense to have this generic.
-Daniel

> 
> Thanks
> Philippe :-)
> 
> Note: It is really a pleasure to read such interesting thread, exposing the
> “complexity” of our job, dealing with various hw and sw... thank you to all
> of you.
> 
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

Reply via email to