From: Jani Nikula <jani.nikula@linux.intel.com>
To: imre.deak@intel.com
Cc: Dibin Moolakadan Subrahmanian
<dibin.moolakadan.subrahmanian@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
uma.shankar@intel.com
Subject: Re: [PATCH v3] drm/i915/display: Mask RO bits in gen9_write_dc_state()
Date: Wed, 03 Jun 2026 18:16:49 +0300 [thread overview]
Message-ID: <2b4a8d43bf1e2c5c578d9a3fe93c3da932bb9742@intel.com> (raw)
In-Reply-To: <aiATv_6EYar1AQHX@ideak-desk.lan>
On Wed, 03 Jun 2026, Imre Deak <imre.deak@intel.com> wrote:
> On Wed, Jun 03, 2026 at 11:30:04AM +0300, Jani Nikula wrote:
>> On Tue, 02 Jun 2026, Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com> wrote:
>> > +static u32 dc_state_ro_mask(struct intel_display *display)
>> > +{
>> > + if (DISPLAY_VER(display) >= 20)
>> > + return BIT(10) | BIT(11);
>> > + else if (DISPLAY_VER(display) >= 13 && !display->platform.dg2)
>> > + return BIT(10);
>>
>> Register contents need to be defined next to the register definition.
>>
>> But even so, the caller already has the mask we want to change, I
>> already suggested passing that in. What's wrong with that?
>
> The mask used by the caller only contains the bits which the driver
> changes. However I would like to know that writing all the other bits in
> the register also take their effect, reflected by the read-back after the
> write.
Fair enough. The first comment still stands, let's not hardcode the bits
here inline.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-06-03 15:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<20260506130321.487414-1-dibin.moolakadan.subrahmanian@intel.com>
2026-06-01 9:01 ` [PATCH v2] drm/i915/display: Mask RO bits in gen9_write_dc_state() Dibin Moolakadan Subrahmanian
2026-06-01 9:38 ` Jani Nikula
2026-06-01 11:47 ` Imre Deak
2026-06-02 4:51 ` Dibin Moolakadan Subrahmanian
2026-06-02 11:31 ` [PATCH v3] " Dibin Moolakadan Subrahmanian
2026-06-03 8:30 ` Jani Nikula
2026-06-03 11:45 ` Imre Deak
2026-06-03 15:16 ` Jani Nikula [this message]
2026-06-05 7:52 ` Dibin Moolakadan Subrahmanian
2026-06-01 11:38 ` ✓ CI.KUnit: success for " Patchwork
2026-06-01 12:18 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-01 14:51 ` ✓ Xe.CI.FULL: " Patchwork
2026-06-02 12:15 ` ✓ CI.KUnit: success for drm/i915/display: Mask RO bits in gen9_write_dc_state() (rev2) Patchwork
2026-06-02 12:53 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-02 21:31 ` ✓ Xe.CI.FULL: " Patchwork
2026-05-06 13:03 [PATCH] drm/i915/display: Use rmw in gen9_write_dc_state() to preserve non-DC bits Dibin Moolakadan Subrahmanian
2026-05-06 13:10 ` ✓ CI.KUnit: success for " Patchwork
2026-05-06 13:35 ` [PATCH] " Imre Deak
2026-05-07 5:47 ` Dibin Moolakadan Subrahmanian
2026-05-07 6:36 ` Imre Deak
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=2b4a8d43bf1e2c5c578d9a3fe93c3da932bb9742@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dibin.moolakadan.subrahmanian@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=uma.shankar@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