From: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [RFC 06/15] drm/i915: Classify vbt type based on its residence
Date: Mon, 8 Jan 2024 15:05:08 -0800 [thread overview]
Message-ID: <20240108230517.1497504-7-radhakrishna.sripada@intel.com> (raw)
In-Reply-To: <20240108230517.1497504-1-radhakrishna.sripada@intel.com>
Vbt can be read from different sources viz. firmware, opregion,
oprom or spi. This will be useful for us to handle the vbt cleanup
during bios remove phase.
Signed-off-by: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
---
drivers/gpu/drm/i915/display/intel_bios.c | 15 ++++++++++++---
drivers/gpu/drm/i915/display/intel_display_core.h | 8 ++++++++
drivers/gpu/drm/i915/display/intel_opregion.c | 3 +++
3 files changed, 23 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_bios.c b/drivers/gpu/drm/i915/display/intel_bios.c
index 0944802ecbd5..bd46a14a04f5 100644
--- a/drivers/gpu/drm/i915/display/intel_bios.c
+++ b/drivers/gpu/drm/i915/display/intel_bios.c
@@ -2996,6 +2996,7 @@ static struct vbt_header *spi_oprom_get_vbt(struct drm_i915_private *i915)
i915->display.vbt.vbt = vbt;
i915->display.vbt.vbt_size = vbt_size;
+ i915->display.vbt.type = I915_VBT_SPI;
drm_dbg_kms(&i915->drm, "Found valid VBT in SPI flash\n");
return (struct vbt_header *)vbt;
@@ -3057,6 +3058,7 @@ static struct vbt_header *oprom_get_vbt(struct drm_i915_private *i915)
i915->display.vbt.vbt = vbt;
i915->display.vbt.vbt_size = vbt_size;
+ i915->display.vbt.type = I915_VBT_OPROM;
drm_dbg_kms(&i915->drm, "Found valid VBT in PCI ROM\n");
return vbt;
@@ -3082,6 +3084,13 @@ void intel_bios_init(struct drm_i915_private *i915)
const struct vbt_header *vbt = i915->display.vbt.vbt;
struct vbt_header *oprom_vbt = NULL;
const struct bdb_header *bdb;
+ const char * const vbt_type[] = {
+ [I915_VBT_NONE] = "None",
+ [I915_VBT_FIRMWARE] = "Firmware",
+ [I915_VBT_OPREGION] = "Opregion",
+ [I915_VBT_OPROM] = "Oprom",
+ [I915_VBT_SPI] = "SPI",
+ };
INIT_LIST_HEAD(&i915->display.vbt.data.display_devices);
INIT_LIST_HEAD(&i915->display.vbt.data.bdb_blocks);
@@ -3114,9 +3123,9 @@ void intel_bios_init(struct drm_i915_private *i915)
bdb = get_bdb_header(vbt);
i915->display.vbt.data.version = bdb->version;
- drm_dbg_kms(&i915->drm,
- "VBT signature \"%.*s\", BDB version %d\n",
- (int)sizeof(vbt->signature), vbt->signature, i915->display.vbt.data.version);
+ drm_dbg_kms(&i915->drm, "%s VBT signature \"%.*s\", BDB version %d\n",
+ vbt_type[i915->display.vbt.type], (int)sizeof(vbt->signature),
+ vbt->signature, i915->display.vbt.data.version);
init_bdb_blocks(i915, bdb);
diff --git a/drivers/gpu/drm/i915/display/intel_display_core.h b/drivers/gpu/drm/i915/display/intel_display_core.h
index 9e134b08aea0..4807edc88f81 100644
--- a/drivers/gpu/drm/i915/display/intel_display_core.h
+++ b/drivers/gpu/drm/i915/display/intel_display_core.h
@@ -236,6 +236,14 @@ struct intel_vbt {
void *vbt_firmware;
const void *vbt;
u32 vbt_size;
+ enum {
+ I915_VBT_NONE = 0,
+ I915_VBT_FIRMWARE,
+ I915_VBT_OPREGION,
+ I915_VBT_OPROM,
+ I915_VBT_SPI
+ } type;
+
struct intel_vbt_data data;
};
diff --git a/drivers/gpu/drm/i915/display/intel_opregion.c b/drivers/gpu/drm/i915/display/intel_opregion.c
index cf7312cfd94a..5c4a5ddba01d 100644
--- a/drivers/gpu/drm/i915/display/intel_opregion.c
+++ b/drivers/gpu/drm/i915/display/intel_opregion.c
@@ -862,6 +862,7 @@ static int intel_load_vbt_firmware(struct drm_i915_private *dev_priv)
"Found valid VBT firmware \"%s\"\n", name);
vbt->vbt = vbt->vbt_firmware;
vbt->vbt_size = fw->size;
+ vbt->type = I915_VBT_FIRMWARE;
ret = 0;
} else {
ret = -ENOMEM;
@@ -918,6 +919,7 @@ static int intel_load_opregion_vbt(struct drm_i915_private *i915,
"Found valid VBT in ACPI OpRegion (RVDA)\n");
vbt->vbt = vbt_data;
vbt->vbt_size = vbt_size;
+ vbt->type = I915_VBT_OPREGION;
goto out;
} else {
drm_dbg_kms(&i915->drm,
@@ -943,6 +945,7 @@ static int intel_load_opregion_vbt(struct drm_i915_private *i915,
"Found valid VBT in ACPI OpRegion (Mailbox #4)\n");
vbt->vbt = vbt_data;
vbt->vbt_size = vbt_size;
+ vbt->type = I915_VBT_OPREGION;
} else {
drm_dbg_kms(&i915->drm,
"Invalid VBT in ACPI OpRegion (Mailbox #4)\n");
--
2.34.1
next prev parent reply other threads:[~2024-01-08 23:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 23:05 [RFC 00/15] VBT read Cleanup Radhakrishna Sripada
2024-01-08 23:05 ` [RFC 01/15] drm/i915: Extract display->vbt_data to a new vbt structure Radhakrishna Sripada
2024-01-08 23:05 ` [RFC 02/15] drm/i915: Move vbt fields from opregion to its own structure Radhakrishna Sripada
2024-01-08 23:05 ` [RFC 03/15] drm/i915: Cache opregion asls pointer Radhakrishna Sripada
2024-01-08 23:05 ` [RFC 04/15] drm/i915: Extract opregion vbt capture to its own function Radhakrishna Sripada
2024-01-08 23:05 ` [RFC 05/15] drm/i915: Init vbt fields when read from oprom/spi Radhakrishna Sripada
2024-01-08 23:05 ` Radhakrishna Sripada [this message]
2024-01-08 23:05 ` [RFC 07/15] drm/i915: Collate vbt cleanup for different types Radhakrishna Sripada
2024-01-08 23:05 ` [RFC 08/15] drm/i915: Make intel_bios_init operate on intel_vbt Radhakrishna Sripada
2024-01-08 23:05 ` [RFC 09/15] drm/i915: Move vbt load from opregion to bios init Radhakrishna Sripada
2024-01-08 23:05 ` [RFC 10/15] drm/i915: Move vbt firmware load into intel_bios_init Radhakrishna Sripada
2024-01-08 23:05 ` [RFC 11/15] drm/i915: Make oprom_get_vbt operate on intel_vbt Radhakrishna Sripada
2024-01-08 23:05 ` [RFC 12/15] drm/i915: Make spi_oprom_get_vbt " Radhakrishna Sripada
2024-01-08 23:05 ` [RFC 13/15] drm/i915: Make intel_load_vbt_firmware " Radhakrishna Sripada
2024-01-08 23:05 ` [RFC 14/15] drm/i915: Kill reduntant vbt_firmware from intel_vbt Radhakrishna Sripada
2024-01-08 23:05 ` [RFC 15/15] drm/i915: Use vbt type to determine its validity Radhakrishna Sripada
2024-01-09 1:58 ` ✗ Fi.CI.SPARSE: warning for VBT read Cleanup Patchwork
2024-01-09 2:17 ` ✓ Fi.CI.BAT: success " Patchwork
2024-01-09 11:57 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-01-10 12:33 ` [RFC 00/15] " Jani Nikula
2024-01-11 22:46 ` Sripada, Radhakrishna
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=20240108230517.1497504-7-radhakrishna.sripada@intel.com \
--to=radhakrishna.sripada@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