From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
intel-xe@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [Intel-xe] [PATCH 1/3] drm/i915/lnl: Extend C10/C20 phy
Date: Thu, 02 Nov 2023 11:37:40 +0200 [thread overview]
Message-ID: <8734xo4hsr.fsf@intel.com> (raw)
In-Reply-To: <20231101151528.1840900-1-lucas.demarchi@intel.com>
On Wed, 01 Nov 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> For Lunar Lake, DDI-A is connected to C10 PHY, while TC1-TC3 are connected
> to C20 phy, like in Meteor Lake. Update the check in intel_is_c10phy()
> accordingly.
>
> This reverts the change in commit e388ae97e225 ("drm/i915/display:
> Eliminate IS_METEORLAKE checks") that turned that into a display engine
> version check. The phy <-> port connection is very SoC-specific and not
> related to that version.
>
> IS_LUNARLAKE() is defined to 0 in i915 as it's expected that the
> (upcoming) xe driver is the one defining the platform, with i915 only
> driving the display side.
On the series,
Acked-by: Jani Nikula <jani.nikula@intel.com>
--
Jani Nikula, Intel
prev parent reply other threads:[~2023-11-02 9:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 15:15 [Intel-xe] [PATCH 1/3] drm/i915/lnl: Extend C10/C20 phy Lucas De Marchi
2023-11-01 15:15 ` [Intel-xe] [PATCH 2/3] drm/i915/lnl: Fix check for TC phy Lucas De Marchi
2023-11-01 15:15 ` [Intel-xe] [PATCH 3/3] fixup! drm/xe/display: Implement display support Lucas De Marchi
2023-11-01 15:58 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/3] drm/i915/lnl: Extend C10/C20 phy Patchwork
2023-11-01 15:58 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-11-01 15:59 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-11-01 16:06 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-11-01 16:07 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-11-01 16:08 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-11-01 16:47 ` [Intel-xe] ✓ CI.BAT: success " Patchwork
2023-11-02 9:37 ` Jani Nikula [this message]
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=8734xo4hsr.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@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