From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 4/6] drm/i915/lspcon: change signature of lspcon_wait_pcon_mode()
Date: Wed, 05 Feb 2025 19:53:12 +0200 [thread overview]
Message-ID: <87wme42s8n.fsf@intel.com> (raw)
In-Reply-To: <Z6KbmjHjZkkRajai@intel.com>
On Tue, 04 Feb 2025, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Tue, Feb 04, 2025 at 03:58:41PM +0200, Jani Nikula wrote:
>> Switch from struct intel_lspcon to struct intel_digital_port to unify.
>
> in the previous patch and in this one I'm asking myself if we
> are not going to the opposite direction that we should...
> and make the lspcon component to use lspcon structs as entry
> but looking to the patch itself the code gets cleaner because
> digport is an information that is broadly available. So, let's
> continue:
I had mostly similar thoughts, and conclusions, and settled on this.
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Thanks, pushed the series to din.
BR,
Jani.
>
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_dp.c | 3 +--
>> drivers/gpu/drm/i915/display/intel_lspcon.c | 4 +++-
>> drivers/gpu/drm/i915/display/intel_lspcon.h | 4 +---
>> 3 files changed, 5 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
>> index 2db7741c25bd..14d81538c912 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
>> @@ -3501,7 +3501,6 @@ void intel_dp_set_power(struct intel_dp *intel_dp, u8 mode)
>> ret = drm_dp_dpcd_writeb(&intel_dp->aux, DP_SET_POWER, mode);
>> } else {
>> struct intel_digital_port *dig_port = dp_to_dig_port(intel_dp);
>> - struct intel_lspcon *lspcon = dp_to_lspcon(intel_dp);
>>
>> lspcon_resume(dig_port);
>>
>> @@ -3520,7 +3519,7 @@ void intel_dp_set_power(struct intel_dp *intel_dp, u8 mode)
>> }
>>
>> if (ret == 1 && intel_lspcon_active(dig_port))
>> - lspcon_wait_pcon_mode(lspcon);
>> + lspcon_wait_pcon_mode(dig_port);
>> }
>>
>> if (ret != 1)
>> diff --git a/drivers/gpu/drm/i915/display/intel_lspcon.c b/drivers/gpu/drm/i915/display/intel_lspcon.c
>> index 2dd2b700b0f3..45b63fea3642 100644
>> --- a/drivers/gpu/drm/i915/display/intel_lspcon.c
>> +++ b/drivers/gpu/drm/i915/display/intel_lspcon.c
>> @@ -656,8 +656,10 @@ u32 lspcon_infoframes_enabled(struct intel_encoder *encoder,
>> return val;
>> }
>>
>> -void lspcon_wait_pcon_mode(struct intel_lspcon *lspcon)
>> +void lspcon_wait_pcon_mode(struct intel_digital_port *dig_port)
>> {
>> + struct intel_lspcon *lspcon = &dig_port->lspcon;
>> +
>> lspcon_wait_mode(lspcon, DRM_LSPCON_MODE_PCON);
>> }
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_lspcon.h b/drivers/gpu/drm/i915/display/intel_lspcon.h
>> index 18cc15e5221d..20581af1ddb2 100644
>> --- a/drivers/gpu/drm/i915/display/intel_lspcon.h
>> +++ b/drivers/gpu/drm/i915/display/intel_lspcon.h
>> @@ -8,18 +8,16 @@
>>
>> #include <linux/types.h>
>>
>> -struct drm_connector;
>> struct drm_connector_state;
>> struct intel_crtc_state;
>> struct intel_digital_port;
>> struct intel_encoder;
>> -struct intel_lspcon;
>>
>> bool lspcon_init(struct intel_digital_port *dig_port);
>> bool intel_lspcon_active(struct intel_digital_port *dig_port);
>> bool lspcon_detect_hdr_capability(struct intel_digital_port *dig_port);
>> void lspcon_resume(struct intel_digital_port *dig_port);
>> -void lspcon_wait_pcon_mode(struct intel_lspcon *lspcon);
>> +void lspcon_wait_pcon_mode(struct intel_digital_port *dig_port);
>> void lspcon_write_infoframe(struct intel_encoder *encoder,
>> const struct intel_crtc_state *crtc_state,
>> unsigned int type,
>> --
>> 2.39.5
>>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-02-05 17:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 13:58 [PATCH v2 0/6] drm/i915/lspcon: interface cleanups Jani Nikula
2025-02-04 13:58 ` [PATCH v2 1/6] drm/i915/hdmi: move declarations for hsw_read/write_infoframe() to the right place Jani Nikula
2025-02-04 22:55 ` Rodrigo Vivi
2025-02-04 13:58 ` [PATCH v2 2/6] drm/i915/lspcon: add intel_lspcon_active() and use it Jani Nikula
2025-02-04 22:55 ` Rodrigo Vivi
2025-02-04 13:58 ` [PATCH v2 3/6] drm/i915/lspcon: change signature of lspcon_detect_hdr_capability() Jani Nikula
2025-02-04 22:57 ` Rodrigo Vivi
2025-02-04 13:58 ` [PATCH v2 4/6] drm/i915/lspcon: change signature of lspcon_wait_pcon_mode() Jani Nikula
2025-02-04 22:58 ` Rodrigo Vivi
2025-02-05 17:53 ` Jani Nikula [this message]
2025-02-04 13:58 ` [PATCH v2 5/6] drm/i915/lspcon: remove dp_to_lspcon(), hide enc_to_intel_lspcon() Jani Nikula
2025-02-04 22:59 ` Rodrigo Vivi
2025-02-04 13:58 ` [PATCH v2 6/6] drm/i915/lspcon: rename interfaces to intel_lspcon_* to unify Jani Nikula
2025-02-04 22:59 ` Rodrigo Vivi
2025-02-04 17:48 ` ✓ CI.Patch_applied: success for drm/i915/lspcon: interface cleanups Patchwork
2025-02-04 17:48 ` ✓ CI.checkpatch: " Patchwork
2025-02-04 17:49 ` ✓ CI.KUnit: " Patchwork
2025-02-04 18:06 ` ✓ CI.Build: " Patchwork
2025-02-04 18:08 ` ✓ CI.Hooks: " Patchwork
2025-02-04 18:09 ` ✗ CI.checksparse: warning " Patchwork
2025-02-04 18:31 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-04 21:55 ` ✗ Xe.CI.Full: failure " 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=87wme42s8n.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@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