From: Chris Wilson <chris@chris-wilson.co.uk>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 2/3] drm/i915: Document our lackluster FSB frequency readout
Date: Sat, 16 May 2020 14:28:15 +0100 [thread overview]
Message-ID: <158963569526.29850.12146935623702308405@build.alporthouse.com> (raw)
In-Reply-To: <20200514123838.3017-2-ville.syrjala@linux.intel.com>
Quoting Ville Syrjala (2020-05-14 13:38:37)
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Document the fact that we aren't reading out the actual FSB
> frequency but rather just the state of the FSB straps.
> Some BIOSen allow you to configure the two independently.
> So if someone sets the two up in an inconsistent manner
> we'll get the wrong answer here and thus will end up with
> incorrect aux/pps clock dividers. Alas, proper docs are no
> longer around so we can't do any better.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-05-16 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 12:38 [Intel-gfx] [PATCH v2 1/3] drm/i915: Fix 400 MHz FSB readout on elk Ville Syrjala
2020-05-14 12:38 ` [Intel-gfx] [PATCH v2 2/3] drm/i915: Document our lackluster FSB frequency readout Ville Syrjala
2020-05-16 13:28 ` Chris Wilson [this message]
2020-05-14 12:38 ` [Intel-gfx] [PATCH v2 3/3] drm/i915: Read out hrawclk on all gen3+ platforms Ville Syrjala
2020-05-16 13:28 ` Chris Wilson
2020-05-14 13:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v2,1/3] drm/i915: Fix 400 MHz FSB readout on elk Patchwork
2020-05-14 17:54 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-05-16 13:27 ` [Intel-gfx] [PATCH v2 1/3] " Chris Wilson
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=158963569526.29850.12146935623702308405@build.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--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 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.