From: Jani Nikula <jani.nikula@linux.intel.com>
To: Bhanuprakash Modem <bhanuprakash.modem@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org
Cc: Harry Wentland <harry.wentland@amd.com>
Subject: Re: [Intel-gfx] [CI 0/3] Expose max and current bpc via debugfs
Date: Mon, 23 May 2022 11:56:43 +0300 [thread overview]
Message-ID: <87o7zobp9w.fsf@intel.com> (raw)
In-Reply-To: <20220519095149.3560034-1-bhanuprakash.modem@intel.com>
On Thu, 19 May 2022, Bhanuprakash Modem <bhanuprakash.modem@intel.com> wrote:
> This series will expose the Connector's max supported bpc via connector
> debugfs and Crtc's current bpc via crtc debugfs. Also move the existing
> vendor specific "output_bpc" logic to drm.
Pushed the series to drm-misc-next, thanks for that patches, reviews and
acks.
BR,
Jani.
>
> Bhanuprakash Modem (3):
> drm/debug: Expose connector's max supported bpc via debugfs
> drm/i915/display/debug: Expose crtc current bpc via debugfs
> drm/amd/display: Move connector debugfs to drm
>
> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 4 --
> .../amd/display/amdgpu_dm/amdgpu_dm_debugfs.c | 38 +++++++------------
> .../amd/display/amdgpu_dm/amdgpu_dm_debugfs.h | 2 -
> drivers/gpu/drm/drm_debugfs.c | 21 ++++++++++
> .../drm/i915/display/intel_display_debugfs.c | 28 ++++++++++++++
> 5 files changed, 62 insertions(+), 31 deletions(-)
>
> --
> 2.35.1
>
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2022-05-23 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 9:51 [CI 0/3] Expose max and current bpc via debugfs Bhanuprakash Modem
2022-05-19 9:51 ` [CI 1/3] drm/debug: Expose connector's max supported " Bhanuprakash Modem
2022-05-19 9:51 ` [CI 2/3] drm/i915/display/debug: Expose crtc current " Bhanuprakash Modem
2022-05-19 9:51 ` [CI 3/3] drm/amd/display: Move connector debugfs to drm Bhanuprakash Modem
2022-05-23 8:56 ` Jani Nikula [this message]
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=87o7zobp9w.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bhanuprakash.modem@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=intel-gfx@lists.freedesktop.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