From: Werner Sembach <wse@tuxedocomputers.com>
To: harry.wentland@amd.com, sunpeng.li@amd.com,
alexander.deucher@amd.com, christian.koenig@amd.com,
airlied@linux.ie, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, jani.nikula@linux.intel.com,
joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/4] Add "activ bpc" drm property and use it in AMD and Intel driver
Date: Fri, 4 Jun 2021 19:17:19 +0200 [thread overview]
Message-ID: <20210604171723.10276-1-wse@tuxedocomputers.com> (raw)
I started work on my proposal for better color handling in Linux display
drivers: https://lkml.org/lkml/2021/5/12/764
Since the first read-only property is now implemented for amdgpu and i915 I
wanted to collect some feedback, since the other two read-only properties will
be quite similar, I hope.
I have already commited the first patch in this series independently as it fixes
a function already in use.
The actuall update of the values is implemented in patch three and four in the
atomic_commit_tail() function of amdgpu and i915 respectifly. It does get
updated more often than needed with the current approach, but without harm since
just the same value is written again. A check if the update is required would be
the same amount of computation. Let me know if you know a better place to put
the update than attomic_commit_tail().
WARNING: multiple messages have this Message-ID (diff)
From: Werner Sembach <wse@tuxedocomputers.com>
To: harry.wentland@amd.com, sunpeng.li@amd.com,
alexander.deucher@amd.com, christian.koenig@amd.com,
airlied@linux.ie, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, jani.nikula@linux.intel.com,
joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/4] Add "activ bpc" drm property and use it in AMD and Intel driver
Date: Fri, 4 Jun 2021 19:17:19 +0200 [thread overview]
Message-ID: <20210604171723.10276-1-wse@tuxedocomputers.com> (raw)
I started work on my proposal for better color handling in Linux display
drivers: https://lkml.org/lkml/2021/5/12/764
Since the first read-only property is now implemented for amdgpu and i915 I
wanted to collect some feedback, since the other two read-only properties will
be quite similar, I hope.
I have already commited the first patch in this series independently as it fixes
a function already in use.
The actuall update of the values is implemented in patch three and four in the
atomic_commit_tail() function of amdgpu and i915 respectifly. It does get
updated more often than needed with the current approach, but without harm since
just the same value is written again. A check if the update is required would be
the same amount of computation. Let me know if you know a better place to put
the update than attomic_commit_tail().
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Werner Sembach <wse@tuxedocomputers.com>
To: harry.wentland@amd.com, sunpeng.li@amd.com,
alexander.deucher@amd.com, christian.koenig@amd.com,
airlied@linux.ie, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, jani.nikula@linux.intel.com,
joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/4] Add "activ bpc" drm property and use it in AMD and Intel driver
Date: Fri, 4 Jun 2021 19:17:19 +0200 [thread overview]
Message-ID: <20210604171723.10276-1-wse@tuxedocomputers.com> (raw)
I started work on my proposal for better color handling in Linux display
drivers: https://lkml.org/lkml/2021/5/12/764
Since the first read-only property is now implemented for amdgpu and i915 I
wanted to collect some feedback, since the other two read-only properties will
be quite similar, I hope.
I have already commited the first patch in this series independently as it fixes
a function already in use.
The actuall update of the values is implemented in patch three and four in the
atomic_commit_tail() function of amdgpu and i915 respectifly. It does get
updated more often than needed with the current approach, but without harm since
just the same value is written again. A check if the update is required would be
the same amount of computation. Let me know if you know a better place to put
the update than attomic_commit_tail().
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2021-06-04 17:17 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 17:17 Werner Sembach [this message]
2021-06-04 17:17 ` [PATCH 0/4] Add "activ bpc" drm property and use it in AMD and Intel driver Werner Sembach
2021-06-04 17:17 ` [Intel-gfx] " Werner Sembach
2021-06-04 17:17 ` [PATCH 1/4] drm/amd/display: Add missing cases convert_dc_color_depth_into_bpc Werner Sembach
2021-06-04 17:17 ` Werner Sembach
2021-06-04 17:17 ` [Intel-gfx] " Werner Sembach
2021-06-04 17:17 ` [PATCH 2/4] drm/uAPI: Add "active bpc" as feedback channel for "max bpc" drm property Werner Sembach
2021-06-04 17:17 ` Werner Sembach
2021-06-04 17:17 ` [Intel-gfx] " Werner Sembach
2021-06-04 17:26 ` Ville Syrjälä
2021-06-04 17:26 ` Ville Syrjälä
2021-06-04 17:26 ` [Intel-gfx] " Ville Syrjälä
2021-06-04 17:26 ` Ville Syrjälä
2021-06-07 6:46 ` Werner Sembach
2021-06-07 6:46 ` Werner Sembach
2021-06-07 6:46 ` [Intel-gfx] " Werner Sembach
2021-06-07 6:46 ` Werner Sembach
2021-06-08 6:12 ` Ville Syrjälä
2021-06-08 6:12 ` Ville Syrjälä
2021-06-08 6:12 ` [Intel-gfx] " Ville Syrjälä
2021-06-08 6:12 ` Ville Syrjälä
2021-06-07 7:40 ` Maxime Ripard
2021-06-07 7:40 ` Maxime Ripard
2021-06-07 7:40 ` [Intel-gfx] " Maxime Ripard
2021-06-07 7:40 ` Maxime Ripard
2021-06-07 8:00 ` Werner Sembach
2021-06-07 8:00 ` Werner Sembach
2021-06-07 8:00 ` [Intel-gfx] " Werner Sembach
2021-06-07 8:00 ` Werner Sembach
2021-06-07 7:52 ` Pekka Paalanen
2021-06-07 7:52 ` Pekka Paalanen
2021-06-07 7:52 ` [Intel-gfx] " Pekka Paalanen
2021-06-07 7:52 ` Pekka Paalanen
2021-06-07 8:53 ` Werner Sembach
2021-06-07 8:53 ` Werner Sembach
2021-06-07 8:53 ` [Intel-gfx] " Werner Sembach
2021-06-04 17:17 ` [PATCH 3/4] drm/amd/display: Add handling for new "active bpc" property Werner Sembach
2021-06-04 17:17 ` Werner Sembach
2021-06-04 17:17 ` [Intel-gfx] " Werner Sembach
2021-06-04 17:17 ` [PATCH 4/4] drm/i915/display: " Werner Sembach
2021-06-04 17:17 ` Werner Sembach
2021-06-04 17:17 ` [Intel-gfx] " Werner Sembach
2021-06-04 17:30 ` Ville Syrjälä
2021-06-04 17:30 ` Ville Syrjälä
2021-06-04 17:30 ` [Intel-gfx] " Ville Syrjälä
2021-06-04 17:30 ` Ville Syrjälä
2021-06-07 6:47 ` Werner Sembach
2021-06-07 6:47 ` Werner Sembach
2021-06-07 6:47 ` [Intel-gfx] " Werner Sembach
2021-06-07 6:47 ` Werner Sembach
2021-06-07 20:33 ` Werner Sembach
2021-06-07 20:33 ` Werner Sembach
2021-06-07 20:33 ` [Intel-gfx] " Werner Sembach
2021-06-07 20:33 ` Werner Sembach
2021-06-08 17:19 ` Werner Sembach
2021-06-08 17:19 ` Werner Sembach
2021-06-08 17:19 ` [Intel-gfx] " Werner Sembach
2021-06-08 17:19 ` Werner Sembach
2021-06-10 14:29 ` Ville Syrjälä
2021-06-10 14:29 ` Ville Syrjälä
2021-06-10 14:29 ` [Intel-gfx] " Ville Syrjälä
2021-06-10 14:29 ` Ville Syrjälä
2021-06-04 17:26 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Add "activ bpc" drm property and use it in AMD and Intel driver Patchwork
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=20210604171723.10276-1-wse@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=sunpeng.li@amd.com \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.