From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [RFC 0/7] start hiding away vbt structure from the driver
Date: Tue, 15 Dec 2015 17:33:31 +0200 [thread overview]
Message-ID: <cover.1450192823.git.jani.nikula@intel.com> (raw)
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.
I think this is the right direction, but this has plenty of bikeshedding
potential. Therefore here's an early RFC. This is based on [1] but the
conflicts are small.
BR,
Jani.
[1] http://mid.gmane.org/cover.1450089383.git.jani.nikula@intel.com
Jani Nikula (7):
drm/i915: move drmP.h include to i915_drv.h
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/bios: hide away VBT specific things in a private bios header
drivers/gpu/drm/i915/i915_drv.h | 6 +-
drivers/gpu/drm/i915/intel_bios.c | 156 ++-
drivers/gpu/drm/i915/intel_bios.h | 1226 ++++----------------
.../i915/{intel_bios.h => intel_bios_private.h} | 230 +---
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 | 4 +-
drivers/gpu/drm/i915/intel_tv.c | 43 +-
9 files changed, 438 insertions(+), 1324 deletions(-)
rewrite drivers/gpu/drm/i915/intel_bios.h (76%)
rename drivers/gpu/drm/i915/{intel_bios.h => intel_bios_private.h} (81%)
--
2.1.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-12-15 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 15:33 Jani Nikula [this message]
2015-12-15 15:33 ` [RFC 1/7] drm/i915: move drmP.h include to i915_drv.h Jani Nikula
2015-12-15 15:33 ` [RFC 2/7] drm/i915: move VBT based TV presence check to intel_bios.c Jani Nikula
2015-12-16 10:58 ` Daniel Vetter
2015-12-15 15:33 ` [RFC 3/7] drm/i915: move VBT based LVDS " Jani Nikula
2015-12-15 15:33 ` [RFC 4/7] drm/i915: move VBT based eDP port " Jani Nikula
2015-12-15 15:33 ` [RFC 5/7] drm/i915: move VBT based DSI presence " Jani Nikula
2015-12-15 15:33 ` [RFC 6/7] drm/i915/panel: setup pwm backlight based on connector type Jani Nikula
2015-12-15 15:33 ` [RFC 7/7] drm/i915/bios: hide away VBT specific things in a private bios header Jani Nikula
2015-12-16 11:03 ` Daniel Vetter
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.1450192823.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).