Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/4] drm/i915: Simplify intel_cx0_program_phy_lane() with loop
Date: Mon, 31 Jul 2023 18:14:42 +0300	[thread overview]
Message-ID: <87y1iww1st.fsf@intel.com> (raw)
In-Reply-To: <169080830770.140656.12479044792983753457@gjsousa-mobl2>

On Mon, 31 Jul 2023, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
> Quoting Jani Nikula (2023-07-31 08:04:12-03:00)
>>On Tue, 25 Jul 2023, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
>>> It is possible to generalize the "disable" value for the transmitters to
>>> be a bit mask based on the port width and the port reversal boolean,
>>> with a small exception for DP-alt mode with "x1" port width.
>>>
>>> Simplify the code by using such a mask and a for-loop instead of using
>>> switch-case statements.
>>>
>>> BSpec: 64539
>>> Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
>>> ---
>>>  drivers/gpu/drm/i915/display/intel_cx0_phy.c | 79 +++++---------------
>>>  1 file changed, 20 insertions(+), 59 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/display/intel_cx0_phy.c b/drivers/gpu/drm/i915/display/intel_cx0_phy.c
>>> index b903ceb0b56a..f10ebdfd696a 100644
>>> --- a/drivers/gpu/drm/i915/display/intel_cx0_phy.c
>>> +++ b/drivers/gpu/drm/i915/display/intel_cx0_phy.c
>>> @@ -2604,7 +2604,8 @@ static void intel_cx0_program_phy_lane(struct drm_i915_private *i915,
>>>                                         struct intel_encoder *encoder, int lane_count,
>>>                                         bool lane_reversal)
>>>  {
>>> -        u8 l0t1, l0t2, l1t1, l1t2;
>>> +        int i;
>>> +        u8 disables;
>>>          bool dp_alt_mode = intel_tc_port_in_dp_alt_mode(enc_to_dig_port(encoder));
>>>          enum port port = encoder->port;
>>>  
>>> @@ -2614,66 +2615,26 @@ static void intel_cx0_program_phy_lane(struct drm_i915_private *i915,
>>>                                C10_VDR_CTRL_MSGBUS_ACCESS,
>>>                                MB_WRITE_COMMITTED);
>>>  
>>> -        /* TODO: DP-alt MFD case where only one PHY lane should be programmed. */
>>> -        l0t1 = intel_cx0_read(i915, port, INTEL_CX0_LANE0, PHY_CX0_TX_CONTROL(1, 2));
>>> -        l0t2 = intel_cx0_read(i915, port, INTEL_CX0_LANE0, PHY_CX0_TX_CONTROL(2, 2));
>>> -        l1t1 = intel_cx0_read(i915, port, INTEL_CX0_LANE1, PHY_CX0_TX_CONTROL(1, 2));
>>> -        l1t2 = intel_cx0_read(i915, port, INTEL_CX0_LANE1, PHY_CX0_TX_CONTROL(2, 2));
>>> -
>>> -        l0t1 |= CONTROL2_DISABLE_SINGLE_TX;
>>> -        l0t2 |= CONTROL2_DISABLE_SINGLE_TX;
>>> -        l1t1 |= CONTROL2_DISABLE_SINGLE_TX;
>>> -        l1t2 |= CONTROL2_DISABLE_SINGLE_TX;
>>> -
>>> -        if (lane_reversal) {
>>> -                switch (lane_count) {
>>> -                case 4:
>>> -                        l0t1 &= ~CONTROL2_DISABLE_SINGLE_TX;
>>> -                        fallthrough;
>>> -                case 3:
>>> -                        l0t2 &= ~CONTROL2_DISABLE_SINGLE_TX;
>>> -                        fallthrough;
>>> -                case 2:
>>> -                        l1t1 &= ~CONTROL2_DISABLE_SINGLE_TX;
>>> -                        fallthrough;
>>> -                case 1:
>>> -                        l1t2 &= ~CONTROL2_DISABLE_SINGLE_TX;
>>> -                        break;
>>> -                default:
>>> -                        MISSING_CASE(lane_count);
>>> -                }
>>> -        } else {
>>> -                switch (lane_count) {
>>> -                case 4:
>>> -                        l1t2 &= ~CONTROL2_DISABLE_SINGLE_TX;
>>> -                        fallthrough;
>>> -                case 3:
>>> -                        l1t1 &= ~CONTROL2_DISABLE_SINGLE_TX;
>>> -                        fallthrough;
>>> -                case 2:
>>> -                        l0t2 &= ~CONTROL2_DISABLE_SINGLE_TX;
>>> -                        l0t1 &= ~CONTROL2_DISABLE_SINGLE_TX;
>>> -                        break;
>>> -                case 1:
>>> -                        if (dp_alt_mode)
>>> -                                l0t2 &= ~CONTROL2_DISABLE_SINGLE_TX;
>>> -                        else
>>> -                                l0t1 &= ~CONTROL2_DISABLE_SINGLE_TX;
>>> -                        break;
>>> -                default:
>>> -                        MISSING_CASE(lane_count);
>>> -                }
>>> +        if (lane_reversal)
>>> +                disables = REG_GENMASK8(3, 0) >> lane_count;
>>> +        else
>>> +                disables = REG_GENMASK8(3, 0) << lane_count;
>>> +
>>> +        if (dp_alt_mode && lane_count == 1) {
>>> +                disables &= ~REG_GENMASK8(1, 0);
>>> +                disables |= REG_FIELD_PREP8(REG_GENMASK8(1, 0), 0x1);
>>>          }
>>>  
>>> -        /* disable MLs */
>>> -        intel_cx0_write(i915, port, INTEL_CX0_LANE0, PHY_CX0_TX_CONTROL(1, 2),
>>> -                        l0t1, MB_WRITE_COMMITTED);
>>> -        intel_cx0_write(i915, port, INTEL_CX0_LANE0, PHY_CX0_TX_CONTROL(2, 2),
>>> -                        l0t2, MB_WRITE_COMMITTED);
>>> -        intel_cx0_write(i915, port, INTEL_CX0_LANE1, PHY_CX0_TX_CONTROL(1, 2),
>>> -                        l1t1, MB_WRITE_COMMITTED);
>>> -        intel_cx0_write(i915, port, INTEL_CX0_LANE1, PHY_CX0_TX_CONTROL(2, 2),
>>> -                        l1t2, MB_WRITE_COMMITTED);
>>> +        /* TODO: DP-alt MFD case where only one PHY lane should be programmed. */
>>> +        for (i = 0; i < 4; i++) {
>>> +                int tx = i % 2 + 1;
>>> +                u8 lane_mask = i / 2 == 0 ? INTEL_CX0_LANE0 : INTEL_CX0_LANE1;
>>
>>I'm just catching up on mails and quickly eyeballing stuff, but
>>
>>        i / 2 == 0
>>
>>looks suspect.
>
> i / 2 == 0 should give us the correct selection of lane_mask: the first two
> iterations are for the first PHY lane and the last two are for the last PHY
> lane.

I think the most obvious way to express that is i < 2.

BR,
Jani.

>
> --
> Gustavo Sousa
>
>>
>>BR,
>>Jani.
>>
>>> +
>>> +                intel_cx0_rmw(i915, port, lane_mask, PHY_CX0_TX_CONTROL(tx, 2),
>>> +                              CONTROL2_DISABLE_SINGLE_TX,
>>> +                              disables & BIT(i) ? CONTROL2_DISABLE_SINGLE_TX : 0,
>>> +                              MB_WRITE_COMMITTED);
>>> +        }
>>>  
>>>          if (intel_is_c10phy(i915, intel_port_to_phy(i915, port)))
>>>                  intel_cx0_rmw(i915, port, INTEL_CX0_BOTH_LANES,
>>
>>-- 
>>Jani Nikula, Intel Open Source Graphics Center

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-07-31 15:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 21:27 [Intel-gfx] [PATCH 0/4] Fix C10/C20 implementation w.r.t. owned PHY lanes Gustavo Sousa
2023-07-25 21:27 ` [Intel-gfx] [PATCH 1/4] drm/i915/cx0: Add intel_cx0_get_owned_lane_mask() Gustavo Sousa
2023-08-02 21:41   ` Taylor, Clinton A
2023-08-03 14:02     ` Gustavo Sousa
2023-08-08 10:43       ` Kahola, Mika
2023-07-25 21:27 ` [Intel-gfx] [PATCH 2/4] drm/i915: Simplify intel_cx0_program_phy_lane() with loop Gustavo Sousa
2023-07-31 11:04   ` Jani Nikula
2023-07-31 12:58     ` Gustavo Sousa
2023-07-31 15:14       ` Jani Nikula [this message]
2023-07-31 16:03         ` Gustavo Sousa
2023-07-25 21:27 ` [Intel-gfx] [PATCH 3/4] drm/i915/cx0: Enable/disable TX only for owned PHY lanes Gustavo Sousa
2023-08-14  9:25   ` Kahola, Mika
2023-07-25 21:27 ` [Intel-gfx] [PATCH 4/4] drm/i915/cx0: Program vswing only for owned lanes Gustavo Sousa
2023-08-14  9:27   ` Kahola, Mika
2023-07-25 22:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Fix C10/C20 implementation w.r.t. owned PHY lanes Patchwork
2023-07-26  4:56 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=87y1iww1st.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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