From: Imre Deak <imre.deak@intel.com>
To: Manasi Navare <manasi.d.navare@intel.com>
Cc: igt-dev@lists.freedesktop.org,
Anusha Srivatsa <anusha.srivatsa@intel.com>,
Petri Latvala <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_dp_dsc: Force a full modeset when we force dsc enable
Date: Thu, 4 Apr 2019 00:42:33 +0300 [thread overview]
Message-ID: <20190403214233.GA21640@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <20190403204944.GF17236@intel.com>
On Wed, Apr 03, 2019 at 01:49:44PM -0700, Manasi Navare wrote:
> [...]
> Currently we have inh i915_dsc_fec_support_show:
> DSC_enabled:
> DSC_sink_support:
> FEC_sink_support:
Yes, and after the kernel change you'll have an additional
Force DSC enable: yes/no
line here.
> And this node we open as a read only first and then as write node and
> force_dsc_enable() from IGT just writes a 1 to this, so you are saying
> that in the kernel _write() node, I accept this and write to
> force_dsc_enable entry in this file instead of rewriting the whole
> file?
I'm not sure what you mean. Currently "1" or "0" is written to the
debugfs file which will set intel_dp->force_dsc_enable. This doesn't
need to be changed at all, no need to rewrite the whole file.
> So in IGT also I will have to parse the file and write 1 for
> force_dsc_enable entry?
You can get the original value of it similarly to how it's done already
for 'DSC_Sink_Support', by reading the file and doing
strstr(buf, "Force DSC enable: yes");
on the content.
> I still cant figure out how the restore() function work, we write the
> stored_values and write for each of the entries in the file? And then
> in the kernel debugfs_write, get these and write back to each entry?
Only force_dsc_enable need to be restored, the only value that you
change by writing to the debugfs file. All the rest are calculated
values that you don't need to care about.
--Imre
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-04-03 21:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 19:31 [igt-dev] [PATCH i-g-t] tests/kms_dp_dsc: Force a full modeset when we force dsc enable Manasi Navare
2019-04-02 20:10 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-04-03 7:46 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-04-03 10:06 ` [igt-dev] [PATCH i-g-t] " Petri Latvala
2019-04-03 13:25 ` Imre Deak
2019-04-03 18:20 ` Manasi Navare
2019-04-03 19:33 ` Imre Deak
2019-04-03 20:17 ` Manasi Navare
2019-04-03 20:34 ` Imre Deak
2019-04-03 20:49 ` Manasi Navare
2019-04-03 21:42 ` Imre Deak [this message]
2019-04-03 22:48 ` Manasi Navare
2019-04-03 23:02 ` Imre Deak
2019-04-03 23:11 ` Manasi Navare
2019-04-03 23:15 ` Imre Deak
2019-04-04 23:44 ` Manasi Navare
2019-04-05 10:06 ` Imre Deak
2019-04-05 18:28 ` Manasi Navare
2019-04-03 17:38 ` Srivatsa, Anusha
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=20190403214233.GA21640@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=anusha.srivatsa@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=manasi.d.navare@intel.com \
--cc=petri.latvala@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