Eric Lee / smarc-fsl-linux-kernel

22 May, 2011

3 commits

20 May, 2011

19 commits

19 May, 2011

1 commit

18 May, 2011

4 commits

  • 56184e3da   drm/i915/sdvo: Reorder i2c initialisation before ddc proxy ... Browse Code »

    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

    Chris Wilson
     
  • 61e499bf0   drm/i915: FDI link training broken on Ironlake by Ivybridge integration ... Browse Code »

    Commit 357555c00f8414057f0c12ee3f479f197264123d split out IVB-specific
    register definitions for FDI link training, but a piece of that commit
    stopped executing some critical code on Ironlake systems while leaving
    it running on Sandybridge.

    Turn that code back on both Ironlake and Sandybridge

    Signed-off-by: Keith Packard
    Acked-by: Jesse Barnes

    Keith Packard
     
  • a51f7a66f   drm/i915: enable rc6 by default ... Browse Code »

    With FBC disabled by default, it should be safe to enable RC6. So let's
    give it a try.

    Signed-off-by: Jesse Barnes
    Reviewed-by: Ben Widawsky
    Signed-off-by: Keith Packard

    Jesse Barnes
     
  • c1a9f0476   drm/i915: add fbc enable flag, but disable by default ... Browse Code »

    FBC has too many corner cases that we don't currently deal with, so
    disable it by default so we can enable more important features like RC6,
    which conflicts in some configurations.

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=31742
    Signed-off-by: Jesse Barnes
    Reviewed-by: Ben Widawsky
    Signed-off-by: Keith Packard

    Jesse Barnes
     

17 May, 2011

2 commits

  • 8547920fc   drm/i915: clean up unused ring_get_irq/ring_put_irq functions ... Browse Code »

    This patch depends on patch "drm/i915: fix user irq miss in BSD ring on
    g4x".
    Once the previous patch apply, ring_get_irq/ring_put_irq become unused.
    So simply remove them.

    Signed-off-by: Feng, Boqun
    Reviewed-by: Xiang, Haihao
    Signed-off-by: Keith Packard

    Feng, Boqun
     
  • 5bfa1063a   drm/i915: fix user irq miss in BSD ring on g4x ... Browse Code »

    On g4x, user interrupt in BSD ring is missed.
    This is because though g4x and ironlake share the same bsd_ring,
    their interrupt control interfaces have _two_ differences.

    1.different irq enable/disable functions:
    On g4x are i915_enable_irq and i915_disable_irq.
    On ironlake are ironlake_enable_irq and ironlake_disable_irq.
    2.different irq flag:
    On g4x user interrupt flag in BSD ring on is I915_BSD_USER_INTERRUPT.
    On ironlake is GT_BSD_USER_INTERRUPT

    Old bsd_ring_get/put_irq call ring_get_irq and ring_get_irq.
    ring_get_irq and ring_put_irq only call ironlake_enable/disable_irq.
    So comes the irq miss on g4x.

    To fix this, as other rings' code do, conditionally call different
    functions(i915_enable/disable_irq and ironlake_enable/disable_irq)
    and use different interrupt flags in bsd_ring_get/put_irq.

    Signed-off-by: Feng, Boqun
    Reviewed-by: Xiang, Haihao
    Cc: stable@kernel.org
    Signed-off-by: Keith Packard

    Feng, Boqun
     

16 May, 2011

11 commits