From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH v2 0/6] drm/i915: start hiding away vbt structure from the driver
Date: Mon, 11 Jan 2016 21:54:36 +0200 [thread overview]
Message-ID: <cover.1452541881.git.jani.nikula@intel.com> (raw)
Hi all, first real patches since the RFC at [1].
The VBT is a monster and it keeps growing. Originally we've extracted
bits and pieces out of there, and added them cleanly to our own
structures in dev_priv->vbt, with our own macros. Later on we've been
slipping and we have copied stuff from VBT verbatim, using the same
structs and defines as in VBT.
Start abstracting the VBT more, hiding away the VBT specific stuff that
should not be fiddled with outside of intel_bios.c. Make it more
explicit when we're doing so. At this stage, mostly just fork the
private parts into intel_bios_private.h. As prep work, move some stuff
to intel_bios.c to limit the amount of macros needing to be exposed
across the whole driver.
With the MIPI DSI VBT stuff out of the way, this now applies on top of
nightly.
BR,
Jani.
[1] http://mid.gmane.org/cover.1450192823.git.jani.nikula@intel.com
Jani Nikula (6):
drm/i915: move VBT based TV presence check to intel_bios.c
drm/i915: move VBT based LVDS presence check to intel_bios.c
drm/i915: move VBT based eDP port check to intel_bios.c
drm/i915: move VBT based DSI presence check to intel_bios.c
drm/i915/panel: setup pwm backlight based on connector type
drm/i915: hide away VBT private data in a separate header
Documentation/DocBook/gpu.tmpl | 2 +-
drivers/gpu/drm/i915/i915_drv.h | 5 +-
drivers/gpu/drm/i915/intel_bios.c | 156 +++++-
drivers/gpu/drm/i915/intel_bios.h | 860 ++----------------------------
drivers/gpu/drm/i915/intel_bios_private.h | 823 ++++++++++++++++++++++++++++
drivers/gpu/drm/i915/intel_dp.c | 21 +-
drivers/gpu/drm/i915/intel_dsi.c | 23 +-
drivers/gpu/drm/i915/intel_lvds.c | 53 +-
drivers/gpu/drm/i915/intel_panel.c | 2 +-
drivers/gpu/drm/i915/intel_tv.c | 43 +-
10 files changed, 1034 insertions(+), 954 deletions(-)
create mode 100644 drivers/gpu/drm/i915/intel_bios_private.h
--
2.1.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-01-11 19:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 19:54 Jani Nikula [this message]
2016-01-11 19:54 ` [PATCH v2 1/6] drm/i915: move VBT based TV presence check to intel_bios.c Jani Nikula
2016-01-12 9:45 ` Daniel Vetter
2016-01-14 12:51 ` Mika Kahola
2016-01-11 19:54 ` [PATCH v2 2/6] drm/i915: move VBT based LVDS " Jani Nikula
2016-01-14 12:52 ` Mika Kahola
2016-01-11 19:54 ` [PATCH v2 3/6] drm/i915: move VBT based eDP port " Jani Nikula
2016-01-14 12:52 ` Mika Kahola
2016-01-11 19:54 ` [PATCH v2 4/6] drm/i915: move VBT based DSI presence " Jani Nikula
2016-01-14 12:52 ` Mika Kahola
2016-01-11 19:54 ` [PATCH v2 5/6] drm/i915/panel: setup pwm backlight based on connector type Jani Nikula
2016-01-11 19:54 ` [PATCH v2 6/6] drm/i915: hide away VBT private data in a separate header Jani Nikula
2016-01-14 12:53 ` Mika Kahola
2016-01-11 20:07 ` [PATCH v2 0/6] drm/i915: start hiding away vbt structure from the driver Lukas Wunner
2016-01-12 5:51 ` Jani Nikula
2016-01-12 8:20 ` ✓ success: Fi.CI.BAT 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.1452541881.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.