From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3 2/3] drm/i915/opregion: rvda is relative from opregion base in opregion 2.1+
Date: Fri, 08 Feb 2019 21:00:59 +0200 [thread overview]
Message-ID: <877eea5clw.fsf@intel.com> (raw)
In-Reply-To: <20190208185717.GX20097@intel.com>
On Fri, 08 Feb 2019, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Fri, Feb 08, 2019 at 08:42:53PM +0200, Jani Nikula wrote:
>> Starting from opregion version 2.1 (roughly corresponding to ICL+) the
>> RVDA field is relative from the beginning of opregion, not absolute
>> address.
>>
>> Fix the error path while at it.
>>
>> v2: Make relative vs. absolute conditional on the opregion version,
>> bumped for the purpose. Turned out there are machines relying on
>> absolute RVDA in the wild.
>>
>> v3: Fix the version checks
>>
>> Fixes: 04ebaadb9f2d ("drm/i915/opregion: handle VBT sizes bigger than 6 KB")
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Cc: Imre Deak <imre.deak@intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/intel_opregion.c | 24 +++++++++++++++++++++---
>> 1 file changed, 21 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_opregion.c b/drivers/gpu/drm/i915/intel_opregion.c
>> index f1b841580521..5e00ee9270b5 100644
>> --- a/drivers/gpu/drm/i915/intel_opregion.c
>> +++ b/drivers/gpu/drm/i915/intel_opregion.c
>> @@ -123,7 +123,8 @@ struct opregion_asle {
>> u64 fdss;
>> u32 fdsp;
>> u32 stat;
>> - u64 rvda; /* Physical address of raw vbt data */
>> + u64 rvda; /* Physical (2.0) or relative from opregion (2.1+)
>> + * address of raw VBT data. */
>> u32 rvds; /* Size of raw vbt data */
>> u8 rsvd[58];
>> } __packed;
>> @@ -964,9 +965,24 @@ int intel_opregion_setup(struct drm_i915_private *dev_priv)
>>
>> if (opregion->header->over.major >= 2 && opregion->asle &&
Push this line to short term memory.
>> opregion->asle->rvda && opregion->asle->rvds) {
>> - opregion->rvda = memremap(opregion->asle->rvda,
>> - opregion->asle->rvds,
>> + resource_size_t rvda = opregion->asle->rvda;
>> +
>> + /*
>> + * opregion 2.0: rvda is the physical VBT address.
>> + *
>> + * opregion 2.1+: rvda is unsigned, relative offset from
>> + * opregion base, and should never point within opregion.
>> + */
>> + if (opregion->header->over.major > 2 ||
>> + opregion->header->over.minor >= 1) {
>
> What happens with version 1.1?
Pop. ;)
BR,
Jani.
>
>> + WARN_ON(rvda < OPREGION_SIZE);
>> +
>> + rvda += asls;
>> + }
>> +
>> + opregion->rvda = memremap(rvda, opregion->asle->rvds,
>> MEMREMAP_WB);
>> +
>> vbt = opregion->rvda;
>> vbt_size = opregion->asle->rvds;
>> if (intel_bios_is_valid_vbt(vbt, vbt_size)) {
>> @@ -976,6 +992,8 @@ int intel_opregion_setup(struct drm_i915_private *dev_priv)
>> goto out;
>> } else {
>> DRM_DEBUG_KMS("Invalid VBT in ACPI OpRegion (RVDA)\n");
>> + memunmap(opregion->rvda);
>> + opregion->rvda = NULL;
>> }
>> }
>>
>> --
>> 2.20.1
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-02-08 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 18:42 [PATCH v3 1/3] drm/i915/opregion: fix version check Jani Nikula
2019-02-08 18:42 ` [PATCH v3 2/3] drm/i915/opregion: rvda is relative from opregion base in opregion 2.1+ Jani Nikula
2019-02-08 18:57 ` Ville Syrjälä
2019-02-08 19:00 ` Jani Nikula [this message]
2019-02-08 19:10 ` Ville Syrjälä
2019-02-11 15:36 ` Jani Nikula
2019-02-08 18:42 ` [PATCH v3 3/3] HACK: drm/i915/opregion: ICL should have opregion 2.1+ and relative rvda Jani Nikula
2019-02-08 18:51 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v3,1/3] drm/i915/opregion: fix version check Patchwork
2019-02-08 19:08 ` ✓ Fi.CI.BAT: success " Patchwork
2019-02-08 23:30 ` ✓ Fi.CI.IGT: " 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=877eea5clw.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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;
as well as URLs for NNTP newsgroup(s).