From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: <intel-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>,
<amd-gfx@lists.freedesktop.org>, <jani.nikula@linux.intel.com>,
<ville.syrjala@linux.intel.com>, <harry.wentland@amd.com>,
<swati2.sharma@intel.com>
Subject: Re: [V2 0/3] Expose max and current bpc via debugfs
Date: Tue, 10 May 2022 16:48:57 +0530 [thread overview]
Message-ID: <d29626ce-6835-867d-de36-465bd17f84fb@intel.com> (raw)
In-Reply-To: <20220411095129.1652096-1-bhanuprakash.modem@intel.com>
Hi Jani,
Can you please help to push this series to drm-next?
CI result:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102502v7/index.html?
I'll merge IGT changes [1] first, so that we won't break the CI.
[1]: https://patchwork.freedesktop.org/series/102387/
- Bhanu
On Mon-11-04-2022 03:21 pm, Bhanuprakash Modem 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.
>
> Test-with: 20220411094147.1650859-2-bhanuprakash.modem@intel.com
>
> 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
>
prev parent reply other threads:[~2022-05-10 11:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 9:51 [V2 0/3] Expose max and current bpc via debugfs Bhanuprakash Modem
2022-04-11 9:51 ` [V2 1/3] drm/debug: Expose connector's max supported " Bhanuprakash Modem
2022-04-12 3:07 ` [Intel-gfx] " Murthy, Arun R
2022-04-12 4:03 ` Modem, Bhanuprakash
2022-04-29 14:27 ` Murthy, Arun R
2022-05-02 11:49 ` Jani Nikula
2022-05-02 18:51 ` Harry Wentland
2022-04-11 9:51 ` [V2 2/3] drm/i915/display/debug: Expose crtc current " Bhanuprakash Modem
2022-04-12 3:10 ` [Intel-gfx] " Murthy, Arun R
2022-05-16 8:39 ` Jani Nikula
2022-04-11 9:51 ` [V2 3/3] drm/amd/display: Move connector debugfs to drm Bhanuprakash Modem
2022-04-29 14:32 ` [Intel-gfx] " Murthy, Arun R
2022-05-02 13:28 ` Modem, Bhanuprakash
2022-05-02 13:38 ` Harry Wentland
2022-05-02 14:27 ` Modem, Bhanuprakash
2022-05-02 14:29 ` Harry Wentland
2022-05-02 18:54 ` Harry Wentland
2022-05-16 8:39 ` Jani Nikula
2022-05-18 5:38 ` Modem, Bhanuprakash
2022-05-18 14:08 ` Harry Wentland
2022-05-02 18:51 ` Harry Wentland
2022-05-10 11:18 ` Modem, Bhanuprakash [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=d29626ce-6835-867d-de36-465bd17f84fb@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=swati2.sharma@intel.com \
--cc=ville.syrjala@linux.intel.com \
/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 NNTP newsgroup(s).