From: Jani Nikula <jani.nikula@intel.com>
To: Vandita Kulkarni <vandita.kulkarni@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [v7 1/3] drm/i915/display: Add write permissions for fec support
Date: Thu, 08 Jul 2021 16:05:45 +0300 [thread overview]
Message-ID: <87v95l551y.fsf@intel.com> (raw)
In-Reply-To: <20210708102549.27821-2-vandita.kulkarni@intel.com>
On Thu, 08 Jul 2021, Vandita Kulkarni <vandita.kulkarni@intel.com> wrote:
> Though there is a write option available on fec_suport
> debugfs file, so far it has been registering with read
> permissions only.
>
> Suggested-by: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Vandita Kulkarni <vandita.kulkarni@intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display_debugfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> index af9e58619667..942c4419e0cb 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> @@ -2428,7 +2428,7 @@ int intel_connector_debugfs_add(struct drm_connector *connector)
> }
>
> if ((DISPLAY_VER(dev_priv) >= 11 || IS_CANNONLAKE(dev_priv)) && ((connector->connector_type == DRM_MODE_CONNECTOR_DisplayPort && !to_intel_connector(connector)->mst_port) || connector->connector_type == DRM_MODE_CONNECTOR_eDP))
> - debugfs_create_file("i915_dsc_fec_support", S_IRUGO, root,
> + debugfs_create_file("i915_dsc_fec_support", 0644, root,
> connector, &i915_dsc_fec_support_fops);
>
> /* Legacy panels doesn't lpsp on any platform */
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-07-08 13:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 10:25 [Intel-gfx] [v7 0/3] Set BPP in the kernel Vandita Kulkarni
2021-07-08 10:25 ` [Intel-gfx] [v7 1/3] drm/i915/display: Add write permissions for fec support Vandita Kulkarni
2021-07-08 13:05 ` Jani Nikula [this message]
2021-07-08 10:25 ` [Intel-gfx] [v7 2/3] drm/i915/display/dsc: Add Per connector debugfs node for DSC BPP enable Vandita Kulkarni
2021-07-08 13:10 ` Jani Nikula
2021-07-08 13:13 ` Jani Nikula
2021-07-08 10:25 ` [Intel-gfx] [v7 3/3] drm/i915/display/dsc: Force dsc BPP Vandita Kulkarni
2021-07-08 13:09 ` Jani Nikula
2021-07-08 13:13 ` Jani Nikula
2021-07-08 13:24 ` Kulkarni, Vandita
2021-07-08 16:23 ` Jani Nikula
2021-07-08 16:40 ` Kulkarni, Vandita
2021-07-08 14:01 ` [Intel-gfx] [v2] " Vandita Kulkarni
2021-07-14 9:57 ` Sharma, Swati2
2021-07-08 10:28 ` [Intel-gfx] [v7 0/3] Set BPP in the kernel Kulkarni, Vandita
2021-07-08 14:09 ` Kulkarni, Vandita
2021-07-08 21:56 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Set BPP in the kernel (rev2) Patchwork
2021-07-08 22:21 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-09 11:42 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-07-16 11:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Set BPP in the kernel (rev4) Patchwork
2021-07-16 11:53 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-07-16 12:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-16 14:08 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-07-19 9:50 [Intel-gfx] [v7 0/3] Set BPP in the kernel Vandita Kulkarni
2021-07-19 9:50 ` [Intel-gfx] [v7 1/3] drm/i915/display: Add write permissions for fec support Vandita Kulkarni
2021-07-20 6:49 [Intel-gfx] [v7 0/3] Enable setting custom DSC BPP Vandita Kulkarni
2021-07-20 6:49 ` [Intel-gfx] [v7 1/3] drm/i915/display: Add write permissions for fec support Vandita Kulkarni
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=87v95l551y.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vandita.kulkarni@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