17 Dec, 2011
2 commits
-
We were checking whether the supplied edid matched the connector it was
read from. We do this in case a DDC read returns an EDID for another
device on a multifunction or otherwise interesting card. However, we
failed to include LVDS as a digital device and so rejecting an otherwise
valid EDID.Fixes the detection of the secondary SDVO LVDS panel on the Libretto
W105.Signed-off-by: Chris Wilson
Reviewed-by: Adam Jackson
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=39216
Signed-off-by: Keith Packard -
v2: add a CPT-specific macro, make code cleaner
v3: fix commit messageBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=41272
Cc: stable@kernel.org
Signed-off-by: Paulo Zanoni
Reviewed-by: Chris Wilson
Signed-off-by: Keith Packard
01 Nov, 2011
1 commit
-
They need this to get all the EXPORT_SYMBOL variants and THIS_MODULE
Signed-off-by: Paul Gortmaker
21 Oct, 2011
5 commits
-
Well almost anyway. IVB has 3 planes, pipes, transcoders, and FDI
interfaces, but only 2 pipe PLLs. So two of the pipes must use the same
pipe timings (e.g. 2 DP plus one other, or two HDMI with the same mode
and one other, etc.).Signed-off-by: Jesse Barnes
Tested-By: Eugeni Dodonov
Reviewed-By: Eugeni Dodonov
Signed-off-by: Keith Packard -
Signed-off-by: Adam Jackson
Reviewed-by: Chris Wilson
Signed-off-by: Keith Packard -
This is general TMDS detect, not HDMI specifically.
Signed-off-by: Adam Jackson
Reviewed-by: Chris Wilson
Signed-off-by: Keith Packard -
I can't think of any sensible reason to limit this to a mask of 0x0f,
ie, SDVO_OUTPUT_{TMDS,RGB,CVBS,SVID}0.Signed-off-by: Adam Jackson
Reviewed-by: Chris Wilson
Signed-off-by: Keith Packard -
I have no evidence for this byte being used this way, and lots of
counterexamples. Restore the struct to its empirical definition and
patch up gmbus setup to match.Signed-off-by: Adam Jackson
Acked-by: Chris Wilson
Signed-off-by: Keith Packard
29 Sep, 2011
1 commit
22 Sep, 2011
1 commit
-
I was seeing a nasty 5 frame glitch every 10 seconds, caused by the
poll for connection on DVI attached by SDVO.As my SDVO DVI supports hotplug detect interrupts, the fix is to
enable them, and hook them in to the various bits of driver
infrastructure so that they work reliably.Note that this is only tested on single-function DVI-D SDVOs, on two
platforms (965GME and 945GSE), and has not been checked against a
specification document.With lots of help from Adam Jackson on IRC.
Signed-off-by: Simon Farnsworth
Reviewed-by: Keith Packard
Signed-off-by: Keith Packard
20 Sep, 2011
1 commit
-
Various issues involved with the space character were generating
warnings in the checkpatch.pl file. This patch removes most of those
warnings.Signed-off-by: Akshay Joshi
Signed-off-by: Keith Packard
05 Jun, 2011
1 commit
-
Make the audio property creation routine common and share the single
property between the connectors.Signed-off-by: Chris Wilson
Reviewed-by: Keith Packard
Signed-off-by: Keith Packard
18 May, 2011
1 commit
-
The ddc proxy depends upon the underlying i2c bus being selected. Under
certain configurations, the i2c-adapter functionality is queried during
initialisation and so may trigger an OOPS during boot. Hence, we need to
reorder the initialisation of the ddc proxy until after we hook up the i2c
adapter for the SDVO device.The condition under which it fails is when the i2c_add_adapter calls
into i2c_detect which will attempt to probe all valid addresses on the
adapter iff there is a pre-existing i2c_driver with the same class as
the freshly added i2c_adapter.So it appears to depend upon having compiled in (or loaded such a
module before i915.ko) an i2c-driver that likes to futz over the
i2c_adapters claiming DDC support.Reported-by: Mihai Moldovan
Signed-off-by: Chris Wilson
Reviewed-by: Keith Packard
Signed-off-by: Keith Packard
14 Mar, 2011
1 commit
-
* 'intel/drm-intel-next' of ../drm-next: (755 commits)
drm/i915: Only wait on a pending flip if we intend to write to the buffer
drm/i915/dp: Sanity check eDP existence
drm/i915: Rebind the buffer if its alignment constraints changes with tiling
drm/i915: Disable GPU semaphores by default
drm/i915: Do not overflow the MMADDR write FIFO
Revert "drm/i915: fix corruptions on i8xx due to relaxed fencing"
drm/i915: Don't save/restore hardware status page address register
drm/i915: don't store the reg value for HWS_PGA
drm/i915: fix memory corruption with GM965 and >4GB RAM
Linux 2.6.38-rc7
Revert "TPM: Long default timeout fix"
drm/i915: Re-enable GPU semaphores for SandyBridge mobile
drm/i915: Replace vblank PM QoS with "Interrupt-Based AGPBUSY#"
Revert "drm/i915: Use PM QoS to prevent C-State starvation of gen3 GPU"
drm/i915: Allow relocation deltas outside of target bo
drm/i915: Silence an innocuous compiler warning for an unused variable
fs/block_dev.c: fix new kernel-doc warning
ACPI: Fix build for CONFIG_NET unset
mm: must include
x86: Use u32 instead of long to set reset vector back to 0
...Conflicts:
drivers/gpu/drm/i915/i915_gem.c
23 Feb, 2011
1 commit
-
... and fixup some methods to accept the constant argument.
Now that constant module arrays are loaded into read-only memory, using
const appropriately has some benefits beyond warning the programmer
about likely mistakes.Signed-off-by: Chris Wilson
Signed-off-by: Dave Airlie
22 Feb, 2011
1 commit
-
In order to prevent "crushed blacks" on TVs, the range of the RGB output
may be limited to 16-235. This used to be available through Xorg under
the "Broadcast RGB" option, so reintroduce support for KMS.Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=34543
Signed-off-by: Chris Wilson
16 Feb, 2011
1 commit
-
Grab the latest stabilisation bits from -fixes and some suspend and
resume fixes from linus.Conflicts:
drivers/gpu/drm/i915/i915_drv.h
drivers/gpu/drm/i915/i915_irq.c
11 Feb, 2011
1 commit
-
If the user changes the force-audio property and it no longer reflects
the current configuration, then we need to trigger a mode set in order
to update the registers.Signed-off-by: Chris Wilson
10 Feb, 2011
1 commit
-
If we have an EDID for a digital panel, but we are probing a non-TMDS
connector then we know that this is a false detection, and vice versa.
This should reduce the number of bogus outputs on multi-function
adapters that report the same output on multiple connectors.Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=34101
Reported-by: Sebastien Caty
Tested-by: Sebastien Caty
Signed-off-by: Chris Wilson
Cc: stable@kernel.org
01 Feb, 2011
1 commit
-
Merge resume fixes from -fixes and an important fix for SDVO GMBUS.
26 Jan, 2011
3 commits
-
Signed-off-by: Chris Wilson
-
Signed-off-by: Chris Wilson
-
We were not pausing after detecting the response was pending and so did
not allow the hardware sufficient time to complete before aborting. This
lead to transient failures whilst probing SDVO devices.Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=30235
Reported-by: Knut Petersen
Signed-off-by: Chris Wilson
12 Jan, 2011
1 commit
-
Alex Fiestas reported an issue with his HDMI connector being misdetected
as DVI unless he had something connected upon boot. By moving the
decision as to whether to use HDMI or DVI encoding for the HDMI capable
output until we probe the monitor means that we should avoid sending a
HDMI signal to a DVI monitor and also correctly detect hardware like
Alex's.However, to really determine what connector is soldered onto the wire we
need to inspect the VBT sdvo child devices - but can we trust it?Reported-by: Alex Fiestas
Tested-by: Alex Fiestas
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=32828
Signed-off-by: Chris Wilson
Cc: stable@kernel.org
05 Jan, 2011
1 commit
23 Dec, 2010
1 commit
-
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=25012
Reported-by: Tõnu Raitviir
Signed-off-by: Chris Wilson
17 Dec, 2010
1 commit
-
This is even more important as those bits will be moved in future.
Signed-off-by: Chris Wilson
10 Dec, 2010
1 commit
-
BIOSes. Can't live without them (apparently), definitely can't live with
them.Reported-by: Ben Gamari
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=24312
Signed-off-by: Chris Wilson
25 Nov, 2010
1 commit
-
Commit d09c23de intended to add a 30ms delay to give the ADD time to
detect any TVs connected. However, it used the sdvo->is_tv flag to do so
which is dependent upon the previous detection result and not whether the
output supports TVs.Signed-off-by: Chris Wilson
Cc: stable@kernel.org
24 Nov, 2010
1 commit
-
On a few devices, like the Mac Mini, the CRT DDC pins are shared between
the analog connector and the digital connector. In this scenario, rely
on the EDID to determine if a digital panel is connected to the digital
connector.Reported-and-tested-by: Tino Keitel
Signed-off-by: Chris Wilson
22 Nov, 2010
1 commit
-
As we conflated intel_sdvo->is_hdmi with both having HDMI support on the
ADD along with having HDMI support on the monitor, we would attempt to
use HDMI encodings even if the interface did not support those commands.Reported-by: Simon Farnsworth
Signed-off-by: Chris Wilson
Tested-by: Simon Farnsworth
Reviewed-by: Simon Farnsworth
22 Oct, 2010
2 commits
-
This block is only used when detecting whether the connector is HDMI and
never again, so scope the variable to the detection routine.Signed-off-by: Chris Wilson
-
This patch enables the sending of AVI infoframes in
drivers/gpu/drm/i915/intel_hdmi.c.My receiver currently loses sync when the HDMI output on my computer
(DG45FC motherboard) is switched from 800x600 (the BIOS resolution) to
1920x1080 as part of the boot. Fixable by switching inputs on the receiver
a couple of times.With this patch, my receiver has not lost sync yet (> 40 tries).
Fourth version, now based on drm-intel-next from:
git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.gitTwo questions still remain:
I'm assuming that the sdvo hardware also stores a header ECC byte in
the MSB of the first dword - is this correct?Does the SDVOB and SDVOC handling in intel_hdmi_set_avi_infoframe()
look correct?Signed-off-by: David Härdeman
Signed-off-by: Chris Wilson
19 Oct, 2010
1 commit
-
Allow the user to override the detection of the sink's audio capabilities
from EDID. Not all sinks support the required EDID level to specify
whether they handle audio over the display connection, so allow the user
to enable it manually.Signed-off-by: Chris Wilson
28 Sep, 2010
2 commits
-
Besides a couple of bugs when writing more than a single byte along the
GMBUS, SDVO was completely failing whilst trying to use GMBUS, so use
bit banging instead.Signed-off-by: Chris Wilson
24 Sep, 2010
2 commits
-
In the event that the external chipset doesn't implement the
GET_SUPPORTED_ENHANCEMENTS commands, gracefully treat it as having no
enhancments rather than bailing.Reported-and-tested-by: Woody Suwalski
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=18342
Signed-off-by: Chris Wilson -
We weren't unlinking the freed connector from the drm lists, and so
hit some use-after-free if we failed to initialise the connector.Reported-and-tested-by: Woody Suwalski
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=18342
Signed-off-by: Chris Wilson
21 Sep, 2010
2 commits
-
Avoid confusion between i965g meaning broadwater and the gen4+ chipset
families.Signed-off-by: Chris Wilson
-
Conflicts:
drivers/char/agp/intel-agp.c
drivers/gpu/drm/i915/intel_crt.c