Permalink
Commits on Aug 7, 2014
  1. sw/nv50: add an interface to control perfmon

    This will be used to monitor global performance counters (PCOUNTER) from
    the userspace with a set of software methods.
    committed Aug 1, 2014
  2. abi16: expose NV_PERFEVENT_CLASS using a ioctl

    This allows the userspace to allocate perfevent objects in order to
    monitor performance counters through the perfmon engine.
    committed Aug 1, 2014
  3. perfmon: do not forget to destroy the engine context

    This fixes a crash when we reload Nouveau DRM.
    committed Aug 1, 2014
  4. perfmon: expose domain ID and number of counters used by events

    This will be used to improve scheduling.
    committed Aug 1, 2014
  5. perfmon: introduce the new interface PERFEVENT

    This will be used to monitor complex hardware events.
    committed Jul 31, 2014
  6. perfmon/a3: add more 8-bits signals

    These signals will be used to build complex hardware events.
    committed Jul 25, 2014
Commits on Jul 25, 2014
  1. perfmon: remove PDAEMON signals

    These signals will be exposed through sysfs.
    committed Jul 25, 2014
Commits on Jul 1, 2014
  1. disp/dp: fix required link bandwidth calculations

    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jul 1, 2014
Commits on Jun 30, 2014
  1. drm: support for probing platform devices

    Add a platform driver for Nouveau devices declared using the device tree
    or platform data. This driver currently supports GK20A on Tegra
    platforms and is only compiled for these platforms if Nouveau is
    enabled.
    
    Nouveau will probe the chip type itself using the BOOT0 register, so all
    this driver really needs to do is to make sure the module is powered and
    its clocks active before calling nouveau_drm_platform_probe().
    
    Heavily based on work done by Thierry Reding.
    
    Signed-off-by: Thierry Reding <treding@nvidia.com>
    Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    Gnurou committed with skeggsb Jun 26, 2014
  2. drm: pull in some missing bits from kernel tree

    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 30, 2014
  3. kms: restore acceleration before fb_set_suspend() resumes

    This *should* be safe these days.
    
    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 30, 2014
  4. kms: take more care when pulling down accelerated fbcon

    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 28, 2014
  5. kms: restore fbcon after display has been resumed

    Under some complicated circumstances (boot, suspend, resume, attach
    second display, suspend, resume, suspend, detach second display,
    resume, suspend, attach second display, resume), the fb_set_suspend()
    call can somehow result in a modeset being attempted before we're
    ready for it and things blow up in fun ways.
    
    Running display init first fixes the issue.
    
    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 30, 2014
  6. kms/nv50-: pass a non-zero value for head to sor dpms methods

    There's Apple machines out there which (probably completely arbitrarily)
    restrict each output path to a particular head.  This causes us to not
    be able to locate the output data needed to power on/off the DP output
    correctly.
    
    We fix this by passing in a head index we know is valid (as opposed to
    "head 0").
    
    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 30, 2014
Commits on Jun 28, 2014
  1. fb: Prevent inlining of ramfuc_reg

    When gcc 4.8 inlines this function, it eats up 16 bytes on the stack
    every time. Eventually we hit warnings because our stack grew too
    much:
    
    ramnve0.c:1383:1: error: the frame size of 1496 bytes is larger than
    1024 bytes
    
    We fix this by preventing inlining for this function.
    
    Signed-off-by: Stéphane Marchesin <marcheu@chromium.org>
    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    Stéphane Marchesin committed with skeggsb Jun 27, 2014
Commits on Jun 18, 2014
  1. drm: expose pstate selection per-power source in sysfs

    echo ac:id >> pstate # select mode when on mains power
    echo dc:id >> pstate # select mode when on battery
    echo id >> pstate # select mode for both
    
    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 13, 2014
  2. clk: allow selection of different power state for ac vs battery

    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 13, 2014
  3. clk: schedule pstate changes through a workqueue

    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 13, 2014
  4. device: register for acpi events

    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 13, 2014
  5. gr/gk208-: stop touching 0x260 inappropriately

    As a side note.. It's a bit hard to figure out how to name this commit..
    GK20A is NVEA, which is before NV108 (GK208).. Confusing.
    
    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 12, 2014
  6. gr/gk110b: initvals differ from gk110

    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 12, 2014
  7. gr/gk104: disable PGOB at init time

    This removes the previous hack that worked on some boards.
    
    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 12, 2014
  8. pwr/gk104: implement PGOB disable method

    As documented at:
    
    ftp://download.nvidia.com/open-gpu-doc/gk104-disable-graphics-power-gating/1/gk104-disable-graphics-power-gating.txt
    
    NVIDIA were not able document the steps necessary to detect whether this
    is required or not at this time.  However, they did confirm that this
    procedure is safe to perform unconditionally on GK104/6.  GK107 does not
    have the power gating feature, and it was recommended that we do not
    perform these steps there as the effects were not verified.
    
    The disable path is from observing the binary driver, and not
    documented in the link above.
    
    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 12, 2014
  9. pwr: tidy

    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 12, 2014
  10. fb/ram/gk104: bash mpll bit 31 on

    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 12, 2014
  11. disp: fix oops in destructor with headless cards

    If init doesn't run then disp->outp might not be initialized, resulting
    in an oops.
    
    Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    Maarten Lankhorst committed with skeggsb Jun 17, 2014
  12. i2c/gf117: no aux channels on this chipset

    Reported-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 18, 2014
Commits on Jun 17, 2014
  1. pwr: fix typo in fifo wrap handling

    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 17, 2014
  2. disp/nv50: fix a potential oops in supervisor handling

    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 16, 2014
  3. disp/dp: don't touch link config after success

    I don't know of anything this fixes, but it seems wrong anyway.
    
    Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
    skeggsb committed Jun 16, 2014