From: Jani Nikula <jani.nikula@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
rodrigo.vivi@intel.com, ville.syrjala@linux.intel.com
Subject: Re: [PATCH 2/4] drm/i915/display: Convert intel_pch towards intel_display
Date: Mon, 14 Apr 2025 11:14:22 +0300 [thread overview]
Message-ID: <87r01vtb1d.fsf@intel.com> (raw)
In-Reply-To: <dso7an5ln47xqjbhh5r7mighwt7fg3cooedxx46qi4ssde5qa5@qqka36ocja5i>
On Fri, 11 Apr 2025, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> why not merging intel_pch and intel_pch_display? Now that both are
> under display/, there isn't much reason for the split, is there?
One is about identifying the PCH, and the other is about supporting
outputs on the south display, and not all of the PCHs even have
that. The former doesn't need register reads/writes, the latter does.
I think they should stay separate.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-04-14 8:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 9:54 [PATCH 0/4] drm/{i915,xe}: Move PCH stuff under display Jani Nikula
2025-04-11 9:54 ` [PATCH 1/4] drm/{i915,xe}: Move intel_pch " Jani Nikula
2025-04-11 14:15 ` Lucas De Marchi
2025-04-11 9:54 ` [PATCH 2/4] drm/i915/display: Convert intel_pch towards intel_display Jani Nikula
2025-04-11 14:17 ` Lucas De Marchi
2025-04-14 8:14 ` Jani Nikula [this message]
2025-04-11 9:54 ` [PATCH 3/4] drm/i915/pch: move PCH detection to intel_display_driver_early_probe() Jani Nikula
2025-04-11 14:18 ` Lucas De Marchi
2025-04-11 9:54 ` [PATCH 4/4] drm/i915/pch: clean up includes Jani Nikula
2025-04-11 14:21 ` Lucas De Marchi
2025-04-11 10:00 ` ✓ CI.Patch_applied: success for drm/{i915,xe}: Move PCH stuff under display Patchwork
2025-04-11 10:00 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-11 10:01 ` ✓ CI.KUnit: success " Patchwork
2025-04-11 10:14 ` ✓ CI.Build: " Patchwork
2025-04-11 10:17 ` ✓ CI.Hooks: " Patchwork
2025-04-11 10:19 ` ✓ CI.checksparse: " Patchwork
2025-04-11 11:04 ` ✓ Xe.CI.BAT: " Patchwork
2025-04-11 12:46 ` ✓ Xe.CI.Full: " 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=87r01vtb1d.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@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