<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/Documentation/gpu/drm-kms.rst, branch linux-6.4.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.4.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.4.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2022-12-01T10:12:44Z</updated>
<entry>
<title>drm/doc: Fix title underline length</title>
<updated>2022-12-01T10:12:44Z</updated>
<author>
<name>Maxime Ripard</name>
</author>
<published>2022-11-28T08:19:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b99070c07b78f1d318f8625b31128f405fef0e60'/>
<id>urn:sha1:b99070c07b78f1d318f8625b31128f405fef0e60</id>
<content type='text'>
The underline length for the new Analog TV properties section doesn't
match the title length, resulting in a warning.

Fixes: 7d63cd8526f1 ("drm/connector: Add TV standard property")
Reported-by: kernel test robot &lt;lkp@intel.com&gt;
Reviewed-by: Javier Martinez Canillas &lt;javierm@redhat.com&gt;
Link: https://lore.kernel.org/r/20221128081938.742410-1-maxime@cerno.tech
Signed-off-by: Maxime Ripard &lt;maxime@cerno.tech&gt;
</content>
</entry>
<entry>
<title>drm/connector: Add TV standard property</title>
<updated>2022-11-24T11:42:39Z</updated>
<author>
<name>Maxime Ripard</name>
</author>
<published>2022-11-17T09:28:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7d63cd8526f1b70d1438b1aa90620cde941162c3'/>
<id>urn:sha1:7d63cd8526f1b70d1438b1aa90620cde941162c3</id>
<content type='text'>
The TV mode property has been around for a while now to select and get the
current TV mode output on an analog TV connector.

Despite that property name being generic, its content isn't and has been
driver-specific which makes it hard to build any generic behaviour on top
of it, both in kernel and user-space.

Let's create a new enum tv norm property, that can contain any of the
analog TV standards currently supported by kernel drivers. Each driver can
then pass in a bitmask of the modes it supports, and the property
creation function will filter out the modes not supported.

We'll then be able to phase out the older tv mode property.

Tested-by: Mateusz Kwiatkowski &lt;kfyatek+publicgit@gmail.com&gt;
Acked-in-principle-or-something-like-that-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Link: https://lore.kernel.org/r/20220728-rpi-analog-tv-properties-v10-5-256dad125326@cerno.tech
Signed-off-by: Maxime Ripard &lt;maxime@cerno.tech&gt;
</content>
</entry>
<entry>
<title>Documentation/gpu/amdgpu/amdgpu_dm: add DM docs for pixel blend mode</title>
<updated>2022-08-16T22:14:32Z</updated>
<author>
<name>Melissa Wen</name>
</author>
<published>2022-08-04T15:01:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=33fa4f1df53076d0078be091d5a88d457de54936'/>
<id>urn:sha1:33fa4f1df53076d0078be091d5a88d457de54936</id>
<content type='text'>
AMD GPU display manager (DM) maps DRM pixel blend modes (None,
Pre-multiplied, Coverage) to MPC hw blocks through blend configuration
options. Describe relevant elements and how to set and test them to get
the expected DRM blend mode on DCN hw.

v2:
- add ref tag (Tales)

Signed-off-by: Melissa Wen &lt;mwen@igalia.com&gt;
Reviewed-by: Tales Aparecida &lt;tales.aparecida@gmail.com&gt;
Reviewed-by: Rodrigo Siqueira &lt;Rodrigo.Siqueira@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/doc: overview before functions for drm_writeback.c</title>
<updated>2022-01-11T21:10:49Z</updated>
<author>
<name>Daniel Vetter</name>
</author>
<published>2022-01-11T20:27:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d1f5a6d9d02e3e1dd91379e642f5bc4133f5cf2b'/>
<id>urn:sha1:d1f5a6d9d02e3e1dd91379e642f5bc4133f5cf2b</id>
<content type='text'>
Otherwise it's really hard to link to that, which I realized when I
wanted to link to the property definitions for a question on irc.

Fix it.

Reviewed-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
Fixes: e2d7fc20b3e2 ("drm/writeback: wire drm_writeback.h to kernel-doc")
Cc: Sam Ravnborg &lt;sam@ravnborg.org&gt;
Cc: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Cc: Laurent Pinchart &lt;laurent.pinchart+renesas@ideasonboard.com&gt;
Cc: Brian Starkey &lt;brian.starkey@arm.com&gt;
Cc: Liviu Dudau &lt;liviu.dudau@arm.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20220111202714.1128406-1-daniel.vetter@ffwll.ch
</content>
</entry>
<entry>
<title>drm/connector: Add support for privacy-screen properties (v4)</title>
<updated>2021-10-14T11:12:20Z</updated>
<author>
<name>Rajat Jain</name>
</author>
<published>2021-10-05T20:23:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=107fe904302092c683cf5462b4af3cb3cfa40998'/>
<id>urn:sha1:107fe904302092c683cf5462b4af3cb3cfa40998</id>
<content type='text'>
Add support for generic electronic privacy screen properties, that
can be added by systems that have an integrated EPS.

Changes in v2 (Hans de Goede)
- Create 2 properties, "privacy-screen sw-state" and
  "privacy-screen hw-state", to deal with devices where the OS might be
  locked out of making state changes
- Write kerneldoc explaining how the 2 properties work together, what
  happens when changes to the state are made outside of the DRM code's
  control, etc.

Changes in v3 (Hans de Goede)
- Some small tweaks to the kerneldoc describing the 2 properties

Changes in v4 (Hans de Goede)
- Change the "Enabled, locked" and "Disabled, locked" hw-state enum value
  names to "Enabled-locked" and "Disabled-locked". The xrandr command shows
  all possible enum values separated by commas in its output, so having a
  comma in an enum name is not a good idea.
- Do not add a privacy_screen_hw_state member to drm_connector_state
  since this property is immutable its value must be directly stored in the
  obj-&gt;properties-&gt;values array

Signed-off-by: Rajat Jain &lt;rajatja@google.com&gt;
Acked-by: Pekka Paalanen &lt;pekka.paalanen@collabora.com&gt;
Reviewed-by: Mario Limonciello &lt;Mario.limonciello@dell.com&gt;
Reviewed-by: Emil Velikov &lt;emil.l.velikov@gmail.com&gt;
Reviewed-by: Lyude Paul &lt;lyude@redhat.com&gt;
Co-developed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20211005202322.700909-2-hdegoede@redhat.com
</content>
</entry>
<entry>
<title>drm: document drm_mode_get_property</title>
<updated>2021-08-02T10:59:33Z</updated>
<author>
<name>Simon Ser</name>
</author>
<published>2021-08-02T07:28:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6e5b47a4f1dde38d42b054cc6d16b6840de08bd2'/>
<id>urn:sha1:6e5b47a4f1dde38d42b054cc6d16b6840de08bd2</id>
<content type='text'>
It's not obvious what the fields mean and how they should be used.
The most important detail is the link to drm_property.flags, which
describes how property types work.

v2: document enum drm_mode_property_enum, add ref to "Modeset Base
Object Abstraction" (Daniel)

Signed-off-by: Simon Ser &lt;contact@emersion.fr&gt;
Acked-by: Pekka Paalanen &lt;pekka.paalanen@collabora.com&gt;
Acked-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Cc: Leandro Ribeiro &lt;leandro.ribeiro@collabora.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20210802072826.500078-1-contact@emersion.fr
</content>
</entry>
<entry>
<title>drm/plane: Move drm_plane_enable_fb_damage_clips into core</title>
<updated>2021-07-27T10:21:22Z</updated>
<author>
<name>Daniel Vetter</name>
</author>
<published>2021-07-23T08:34:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ba6cd766e0bf933611dc66fcb86f72ac80a446bc'/>
<id>urn:sha1:ba6cd766e0bf933611dc66fcb86f72ac80a446bc</id>
<content type='text'>
We're trying to have a fairly strict split between core functionality
that defines the uapi, including the docs, and the helper functions to
implement it.

Move drm_plane_enable_fb_damage_clips and associated kerneldoc into
drm_plane from drm_damage_helper.c to fix this.

Reviewed-by: José Roberto de Souza &lt;jose.souza@intel.com&gt;
Cc: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Cc: Gwan-gyeong Mun &lt;gwan-gyeong.mun@intel.com&gt;
Cc: José Roberto de Souza &lt;jose.souza@intel.com&gt;
Cc: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@intel.com&gt;
Cc: Maarten Lankhorst &lt;maarten.lankhorst@linux.intel.com&gt;
Cc: Maxime Ripard &lt;mripard@kernel.org&gt;
Cc: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;
Cc: David Airlie &lt;airlied@linux.ie&gt;
Cc: Daniel Vetter &lt;daniel@ffwll.ch&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20210723083457.696939-3-daniel.vetter@ffwll.ch
</content>
</entry>
<entry>
<title>Documentation: gpu: Mention the requirements for new properties</title>
<updated>2021-07-23T11:51:58Z</updated>
<author>
<name>Maxime Ripard</name>
</author>
<published>2021-07-20T14:35:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c18c36dc75fefa8e1672d3ae2d565a9c7136d38d'/>
<id>urn:sha1:c18c36dc75fefa8e1672d3ae2d565a9c7136d38d</id>
<content type='text'>
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.

Acked-by: Dave Airlie &lt;airlied@redhat.com&gt;
Reviewed-by: Pekka Paalanen &lt;pekka.paalanen@collabora.com&gt;
Reviewed-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Maxime Ripard &lt;maxime@cerno.tech&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20210720143544.571760-1-maxime@cerno.tech
</content>
</entry>
<entry>
<title>drm/doc: introduce new section for standard plane properties</title>
<updated>2020-12-17T15:56:40Z</updated>
<author>
<name>Simon Ser</name>
</author>
<published>2020-12-17T11:32:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=77a71abbdd77a32245f47bb1418ef8f05f905154'/>
<id>urn:sha1:77a71abbdd77a32245f47bb1418ef8f05f905154</id>
<content type='text'>
Introduce a new "Standard Plane Properties" section for properties
defined in drm_plane.c. Move the mis-placed IN_FORMATS docs there.

Signed-off-by: Simon Ser &lt;contact@emersion.fr&gt;
Reviewed-by: Daniel Vetter &lt;daniel@ffwll.ch&gt;
Cc: Pekka Paalanen &lt;ppaalanen@gmail.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20201217113220.102271-3-contact@emersion.fr
</content>
</entry>
<entry>
<title>drm/doc: the KMS properties section is for user-space devs</title>
<updated>2020-12-17T15:56:12Z</updated>
<author>
<name>Simon Ser</name>
</author>
<published>2020-12-17T11:32:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=46f9be4c8a7bde68e6f63a61fae4778cf3b61750'/>
<id>urn:sha1:46f9be4c8a7bde68e6f63a61fae4778cf3b61750</id>
<content type='text'>
State that the "KMS Properties" section is mainly for user-space
developers.

Signed-off-by: Simon Ser &lt;contact@emersion.fr&gt;
Cc: Pekka Paalanen &lt;ppaalanen@gmail.com&gt;
Reviewed-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20201217113220.102271-2-contact@emersion.fr
</content>
</entry>
</feed>
