From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Lee, Shawn C" <shawn.c.lee@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Syrjala, Ville" <ville.syrjala@intel.com>,
"Roper, Matthew D" <matthew.d.roper@intel.com>
Subject: Re: [PATCH] drm/i915/display: update BW buddy initialization for LPDDR4 and LPDDR5
Date: Fri, 29 May 2026 15:46:02 +0000 [thread overview]
Message-ID: <d11d0432e1b442ecc187e9f5ef43ab2e42b28947.camel@intel.com> (raw)
In-Reply-To: <ahmupPZMuah4etPi@intel.com>
On Fri, 2026-05-29 at 18:20 +0300, Ville Syrjälä wrote:
> On Fri, May 29, 2026 at 04:39:13PM +0300, Jani Nikula wrote:
> > On Thu, 28 May 2026, Vinod Govindapillai
> > <vinod.govindapillai@intel.com> wrote:
> > > Pcode reports the number of subchannels for LPDDR4 and LPDDR5.
> > > But the page mask selection table is based on the channels. So
> > > adjust the number of channels for LPDDR4 and LPDDR5 so that the
> > > correct page mask can be picked. There are two subchannels per
> > > channel.
> >
> > IMO the parsing of the information belongs in intel_dram.c. If you
> > get
> > subchannels from pcode or where ever, intel_dram.c should figure it
> > out,
> > and store the number of channels in ->num_channels.
>
> We actually want subchannels for QGV stuff. And that's what modern
> pcode gives us, older pcode gave us channels instead and we convert
> that to subchannels in the QGV code on those platforms. I have a
> patch
> to move the adjustment into intel_dram.c for those platforms so that
> we get consistent data out of intel_dram.c everywhere.
>
> For this thing here I think the best thing would be to change the
> table to use subchannels instead. Looks like Vinod didn't file the
> Bspec
> issue asking for the table to be updated there, so I just did that.
Oh.. sorry.. I suggested a wrong code yesterday on jira to be tried by
the customer. So wanted to fix that! Will use the updated table when it
is updated.
BR
Vinod
>
next prev parent reply other threads:[~2026-05-29 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 18:26 [PATCH] drm/i915/display: update BW buddy initialization for LPDDR4 and LPDDR5 Vinod Govindapillai
2026-05-28 19:52 ` ✗ i915.CI.BAT: failure for " Patchwork
2026-05-29 13:26 ` ✓ i915.CI.BAT: success " Patchwork
2026-05-29 13:39 ` [PATCH] " Jani Nikula
2026-05-29 15:20 ` Ville Syrjälä
2026-05-29 15:46 ` Govindapillai, Vinod [this message]
2026-06-01 20:00 ` Govindapillai, Vinod
2026-05-30 0:48 ` ✓ i915.CI.Full: success for " Patchwork
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=d11d0432e1b442ecc187e9f5ef43ab2e42b28947.camel@intel.com \
--to=vinod.govindapillai@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=matthew.d.roper@intel.com \
--cc=shawn.c.lee@intel.com \
--cc=ville.syrjala@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