All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [Intel-gfx] [PATCH 0/9] drm/i915/bios: stop using vbt.ddi_port_info directly
Date: Fri, 17 Jan 2020 16:29:20 +0200	[thread overview]
Message-ID: <cover.1579270868.git.jani.nikula@intel.com> (raw)

My long term plan is to reference all post-setup VBT child device
details through the encoder. We can add an (opaque) encoder->child
pointer, and forgo the dance to get to the relevant VBT details. This
will be helpful in, for example, adding support for multiple local
panels; the data must be made encoder specific instead of just using
i915->vbt.edp or i915->vbt.dsi directly.

The i915->vbt.ddi_port_info[] array stands in the way. Start hiding it
in intel_bios.c. We do gain a lot of intel_bios_*() accessors which may
seem noisy. But it seems to me this is a helpful iterative step no
matter what.

BR,
Jani.


Jani Nikula (9):
  drm/i915/bios: add intel_bios_max_tmds_encoder()
  drm/i915/bios: add intel_bios_hdmi_level_shift()
  drm/i915/bios: intel_bios_dp_boost_level()
  drm/i915/bios: intel_bios_hdmi_boost_level()
  drm/i915/bios: add intel_bios_dp_max_link_rate()
  drm/i915/bios: add intel_bios_alternate_ddc_pin()
  drm/i915/bios: add intel_bios_port_supports_*()
  drm/i915/bios: check port presence based on child device
  drm/i915: use intel_bios_is_port_present()

 drivers/gpu/drm/i915/display/intel_bios.c     | 74 ++++++++++++++++++-
 drivers/gpu/drm/i915/display/intel_bios.h     | 11 +++
 .../gpu/drm/i915/display/intel_combo_phy.c    |  4 +-
 drivers/gpu/drm/i915/display/intel_ddi.c      | 36 ++++-----
 drivers/gpu/drm/i915/display/intel_dp.c       |  6 +-
 drivers/gpu/drm/i915/display/intel_hdmi.c     | 25 +++----
 6 files changed, 115 insertions(+), 41 deletions(-)

-- 
2.20.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2020-01-17 14:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 14:29 Jani Nikula [this message]
2020-01-17 14:29 ` [Intel-gfx] [PATCH 1/9] drm/i915/bios: add intel_bios_max_tmds_encoder() Jani Nikula
2020-01-17 14:43   ` Ville Syrjälä
2020-01-17 14:29 ` [Intel-gfx] [PATCH 2/9] drm/i915/bios: add intel_bios_hdmi_level_shift() Jani Nikula
2020-01-17 14:45   ` Ville Syrjälä
2020-01-17 14:29 ` [Intel-gfx] [PATCH 3/9] drm/i915/bios: intel_bios_dp_boost_level() Jani Nikula
2020-01-17 14:29 ` [Intel-gfx] [PATCH 4/9] drm/i915/bios: intel_bios_hdmi_boost_level() Jani Nikula
2020-01-17 14:29 ` [Intel-gfx] [PATCH 5/9] drm/i915/bios: add intel_bios_dp_max_link_rate() Jani Nikula
2020-01-17 14:29 ` [Intel-gfx] [PATCH 6/9] drm/i915/bios: add intel_bios_alternate_ddc_pin() Jani Nikula
2020-01-17 14:29 ` [Intel-gfx] [PATCH 7/9] drm/i915/bios: add intel_bios_port_supports_*() Jani Nikula
2020-01-17 15:10   ` Ville Syrjälä
2020-01-17 14:29 ` [Intel-gfx] [PATCH 8/9] drm/i915/bios: check port presence based on child device Jani Nikula
2020-01-17 15:12   ` Ville Syrjälä
2020-01-17 15:13     ` Ville Syrjälä
2020-01-17 15:23       ` Ville Syrjälä
2020-01-17 15:28       ` Jani Nikula
2020-01-17 15:37         ` Ville Syrjälä
2020-01-21  9:44           ` Jani Nikula
2020-01-17 14:29 ` [Intel-gfx] [PATCH 9/9] drm/i915: use intel_bios_is_port_present() Jani Nikula
2020-01-17 15:14   ` Ville Syrjälä
2020-01-17 23:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/bios: stop using vbt.ddi_port_info directly Patchwork
2020-01-17 23:44 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2020-01-20 18:33 ` [Intel-gfx] ✓ Fi.CI.IGT: success " 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=cover.1579270868.git.jani.nikula@intel.com \
    --to=jani.nikula@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.