public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Sharma, Shashank" <shashank.sharma@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH v2 3/4] drm/i915: Parse VBT data for lspcon
Date: Fri, 01 Jul 2016 11:54:43 +0530	[thread overview]
Message-ID: <57760CAB.6020108@intel.com> (raw)
In-Reply-To: <CABVU7+sCQFNkztRnNsVvqfzjJEH0e+QCPQOAaXux_AUBUAO9aA@mail.gmail.com>

Regards
Shashank

On 7/1/2016 4:18 AM, Rodrigo Vivi wrote:
> On Tue, Jun 21, 2016 at 8:00 AM, Shashank Sharma
> <shashank.sharma@intel.com> wrote:
>> Many GEN9 boards come with on-board lspcon cards.
>> Fot these boards, VBT configuration should properly point out
>> if a particular port contains lspcon device, so that driver can
>> initialize it properly.
>>
>> This patch adds a utility function, which checks the VBT flag
>> for lspcon bit, and tells us if a port is configured to have a
>> lspcon device or not.
>>
>> V2: Fixed review comments from Ville
>> - Do not forget PORT_D while checking lspcon for GEN9
>>
>> Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
>> ---
>>   drivers/gpu/drm/i915/i915_drv.h   |  3 +++
>>   drivers/gpu/drm/i915/intel_bios.c | 49 +++++++++++++++++++++++++++++++++++++++
>>   2 files changed, 52 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
>> index 25ebe46..3719b81 100644
>> --- a/drivers/gpu/drm/i915/i915_drv.h
>> +++ b/drivers/gpu/drm/i915/i915_drv.h
>> @@ -3671,6 +3671,9 @@ bool intel_bios_is_port_dp_dual_mode(struct drm_i915_private *dev_priv, enum por
>>   bool intel_bios_is_dsi_present(struct drm_i915_private *dev_priv, enum port *port);
>>   bool intel_bios_is_port_hpd_inverted(struct drm_i915_private *dev_priv,
>>                                       enum port port);
>> +bool intel_bios_is_lspcon_present(struct drm_i915_private *dev_priv,
>> +                               enum port port);
>> +
>>
>>   /* intel_opregion.c */
>>   #ifdef CONFIG_ACPI
>> diff --git a/drivers/gpu/drm/i915/intel_bios.c b/drivers/gpu/drm/i915/intel_bios.c
>> index da5ed4a..2b00c89 100644
>> --- a/drivers/gpu/drm/i915/intel_bios.c
>> +++ b/drivers/gpu/drm/i915/intel_bios.c
>> @@ -1759,3 +1759,52 @@ intel_bios_is_port_hpd_inverted(struct drm_i915_private *dev_priv,
>>
>>          return false;
>>   }
>> +
>> +/**
>> + * intel_bios_is_lspcon_present - if LSPCON is attached on %port
>> + * @dev_priv:  i915 device instance
>> + * @port:      port to check
>> + *
>> + * Return true if LSPCON is present on this port
>> + */
>> +bool
>> +intel_bios_is_lspcon_present(struct drm_i915_private *dev_priv,
>> +                               enum port port)
>> +{
>> +       int i;
>> +
>> +       if (WARN_ON_ONCE(!IS_GEN9(dev_priv)))
>> +               return false;
>
> This will cause noise on other platforms.
>
> Also I'd prefer gen < 9 assuming next gens will inherit this support.
> Or also create a HAS_LSPCON on the platform definition and there use gen < 9.
>
That's a good suggestion. I assumed that we have native HDMI 2.0 
controllers in gen10 onwards, so LSPCON would be required only for GEN9 
devices which are not native HDMI 2.0 capable. Do you see anything which 
will inherit LSPCON ?
>> +
>> +       for (i = 0; i < dev_priv->vbt.child_dev_num; i++) {
>> +               if (!dev_priv->vbt.child_dev[i].common.lspcon)
>> +                       continue;
>> +
>> +               switch (dev_priv->vbt.child_dev[i].common.dvo_port) {
>> +               case DVO_PORT_DPA:
>> +               case DVO_PORT_HDMIA:
>> +                       if (port == PORT_A)
>> +                               return true;
>> +                       break;
>> +               case DVO_PORT_DPB:
>> +               case DVO_PORT_HDMIB:
>> +                       if (port == PORT_B)
>> +                               return true;
>> +                       break;
>> +               case DVO_PORT_DPC:
>> +               case DVO_PORT_HDMIC:
>> +                       if (port == PORT_C)
>> +                               return true;
>> +                       break;
>> +               case DVO_PORT_DPD:
>> +               case DVO_PORT_HDMID:
>> +                       if (port == PORT_D)
>> +                               return true;
>> +                       break;
>> +               default:
>> +                       break;
>> +               }
>> +       }
>> +
>> +       return false;
>> +}
>> --
>> 1.9.1
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-07-01  6:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 15:00 [PATCH v2 0/4] Enable lspcon support for GEN9 devices Shashank Sharma
2016-06-21 15:00 ` [PATCH v2 1/4] drm: Helper for lspcon in drm_dp_dual_mode Shashank Sharma
2016-06-30 22:16   ` Rodrigo Vivi
2016-07-01  5:58     ` Sharma, Shashank
2016-07-01 14:11       ` Rodrigo Vivi
2016-06-21 15:00 ` [PATCH v2 2/4] drm/i915: Add lspcon support for I915 driver Shashank Sharma
2016-06-30 22:30   ` Rodrigo Vivi
2016-07-01  6:22     ` Sharma, Shashank
2016-07-02  0:13       ` Rodrigo Vivi
2016-06-21 15:00 ` [PATCH v2 3/4] drm/i915: Parse VBT data for lspcon Shashank Sharma
2016-06-30 22:48   ` Rodrigo Vivi
2016-07-01  6:24     ` Sharma, Shashank [this message]
2016-06-21 15:00 ` [PATCH v2 4/4] drm/i915: Enable lspcon initialization Shashank Sharma
2016-06-30 22:53   ` Rodrigo Vivi
2016-07-01  6:27     ` Sharma, Shashank
2016-07-02  0:14       ` Rodrigo Vivi
2016-06-21 15:38 ` ✗ Ro.CI.BAT: failure for Enable lspcon support for GEN9 devices (rev2) 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=57760CAB.6020108@intel.com \
    --to=shashank.sharma@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@intel.com \
    --cc=rodrigo.vivi@gmail.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