18 Apr, 2019

1 commit

  • Enable Dynamic Range and Mastering Infoframe for HDR
    content, which is defined in CEA 861.3 spec.

    The metadata will be computed based on blending
    policy in userspace compositors and passed as a connector
    property blob to driver. The same will be sent as infoframe
    to panel which support HDR.

    Signed-off-by: Uma Shankar

    Uma Shankar
     

16 Oct, 2018

1 commit

  • HDMI Forum VSDB YCBCR420 deep color capability bits are 2:0. Correct
    definitions in the header for the mask to work correctly.

    Fixes: e6a9a2c3dc43 ("drm/edid: parse ycbcr 420 deep color information")
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107893
    Cc: # v4.14+
    Signed-off-by: Clint Taylor
    Reviewed-by: Jani Nikula
    Reviewed-by: Shashank Sharma
    Signed-off-by: Jani Nikula
    Link: https://patchwork.freedesktop.org/patch/msgid/1538776335-12569-1-git-send-email-clinton.a.taylor@intel.com

    Clint Taylor
     

25 Apr, 2018

1 commit


13 Dec, 2017

1 commit

  • There are a set of values in the drm_display_info structure for each
    connector which hold information derived from EDID. These are computed
    in drm_add_display_info. Before this patch, that was only called in
    drm_add_edid_modes. This meant that they were only set when EDID was
    present and never reset when EDID was not, as happened when the
    display was disconnected.

    One of these fields, non_desktop, is used from
    drm_mode_connector_update_edid_property, the function responsible for
    assigning the new edid value to the application-visible property.

    Various drivers call these two functions (drm_add_edid_modes and
    drm_mode_connector_update_edid_property) in different orders. This
    means that even when EDID is present, the drm_display_info fields may
    not have been computed at the time that
    drm_mode_connector_update_edid_property used the non_desktop value to
    set the non_desktop property.

    I've added a public function (drm_reset_display_info) that resets the
    drm_display_info field values to default values and then made the
    drm_add_display_info function public. These two functions are now
    called directly from drm_mode_connector_update_edid_property so that
    the drm_display_info fields are always computed from the current EDID
    information before being used in that function.

    This means that the drm_display_info values are often computed twice,
    once when the EDID property it set and a second time when EDID is used
    to compute modes for the device. The alternative would be to uniformly
    ensure that the values were computed once before being used, which
    would require that all drivers reliably invoke the two paths in the
    same order. The computation is inexpensive enough that it seems more
    maintainable in the long term to simply compute them in both paths.

    The API to drm_add_display_info has been changed so that it no longer
    takes the set of edid-based quirks as a parameter. Rather, it now
    computes those quirks itself and returns them for further use by
    drm_add_edid_modes.

    This patch also includes a number of 'const' additions caused by
    drm_mode_connector_update_edid_property taking a 'const struct edid *'
    parameter and wanting to pass that along to drm_add_display_info.

    v2: after review by Daniel Vetter

    Removed EXPORT_SYMBOL_GPL for drm_reset_display_info and
    drm_add_display_info.

    Added FIXME in drm_mode_connector_update_edid_property about
    potentially merging that with drm_add_edid_modes to avoid
    the need for two driver calls.

    Signed-off-by: Keith Packard
    Reviewed-by: Daniel Vetter
    Signed-off-by: Daniel Vetter
    Link: https://patchwork.freedesktop.org/patch/msgid/20171213084427.31199-1-keithp@keithp.com

    Keith Packard
     

04 Dec, 2017

1 commit

  • Cross-subsystem Changes:

    - device tree doc for the Mitsubishi AA070MC01 and Tianma TM070RVHG71
    panels (Lukasz Majewski) and for a 2nd endpoint on stm32 (Philippe Cornu)

    Core Changes:

    The most important changes are:

    - Add drm_driver .last_close and .output_poll_changed helpers to reduce
    fbdev emulation footprint in drivers (Noralf)
    - Fix plane clipping in core and for vmwgfx (Ville)

    Then we have a bunch of of improvement for print and debug such as the
    addition of a framebuffer debugfs file. ELD connector, HDMI and
    improvements. And a bunch of misc improvements, clean ups and style
    changes and doc updates

    [airlied: drop eld bits from amdgpu_dm]

    Driver Changes:

    - sii8620: filter unsupported modes and add DVI mode support (Maciej Purski)
    - rockchip: analogix_dp: Remove unnecessary init code (Jeffy Chen)
    - virtio, cirrus: add fb create_handle support to enable screenshots(Lepton Wu)
    - virtio: replace reference/unreference with get/put (Aastha Gupta)
    - vc4, gma500: Convert timers to use timer_setup() (Kees Cook)
    - vc4: Reject HDMI modes with too high of clocks (Eric)
    - vc4: Add support for more pixel formats (Dave Stevenson)
    - stm: dsi: Rename driver name to "stm32-display-dsi" (Philippe Cornu)
    - stm: ltdc: add a 2nd endpoint (Philippe Cornu)
    - via: use monotonic time for VIA_WAIT_IRQ (Arnd Bergmann)

    * tag 'drm-misc-next-2017-11-30' of git://anongit.freedesktop.org/drm/drm-misc: (96 commits)
    drm/bridge: tc358767: add copyright lines
    MAINTAINERS: change maintainer for Rockchip drm drivers
    drm/vblank: Fix vblank timestamp debugs
    drm/via: use monotonic time for VIA_WAIT_IRQ
    dma-buf: Fix ifnullfree.cocci warnings
    drm/printer: Add drm_vprintf()
    drm/edid: Allow HDMI infoframe without VIC or S3D
    video/hdmi: Allow "empty" HDMI infoframes
    dma-buf/fence: Fix lock inversion within dma-fence-array
    drm/sti: Handle return value of platform_get_irq_byname
    drm/vc4: Add support for NV21 and NV61.
    drm/vc4: Use .pixel_order instead of custom .flip_cbcr
    drm/vc4: Add support for DRM_FORMAT_RGB888 and DRM_FORMAT_BGR888
    drm: Move drm_plane_helper_check_state() into drm_atomic_helper.c
    drm: Check crtc_state->enable rather than crtc->enabled in drm_plane_helper_check_state()
    drm/vmwgfx: Try to fix plane clipping
    drm/vmwgfx: Use drm_plane_helper_check_state()
    drm/vmwgfx: Remove bogus crtc coords vs fb size check
    gpu: gma500: remove unneeded DRIVER_LICENSE #define
    drm: don't link DP aux i2c adapter to the hardware device node
    ...

    Dave Airlie
     

24 Nov, 2017

1 commit


23 Nov, 2017

1 commit

  • Appedix F of HDMI 2.0 says that some HDMI sink may fail to switch from
    3D to 2D mode in a timely fashion if the source simply stops sending the
    HDMI infoframe. The suggested workaround is to keep sending the
    infoframe even when strictly not necessary (ie. no VIC and no S3D).
    HDMI 1.4 does allow for this behaviour, stating that sending the
    infoframe is optional in this case.

    The infoframe was first specified in HDMI 1.4, so in theory sinks
    predating that may not appreciate us sending an uknown infoframe
    their way. To avoid regressions let's try to determine if the sink
    supports the infoframe or not. Unfortunately there's no direct way
    to do that, so instead we'll just check if we managed to parse any
    HDMI 1.4 4k or stereo modes from the EDID, and if so we assume the
    sink will accept the infoframe. Also if the EDID contains the HDMI
    2.0 HDMI Forum VSDB we can assume the sink is prepared to receive
    the infoframe.

    v2: Fix getting has_hdmi_infoframe from display_info
    Always fail constructing the infoframe if the display
    possibly can't handle it

    Cc: Shashank Sharma
    Cc: Andrzej Hajda
    Cc: Laurent Pinchart
    Signed-off-by: Ville Syrjälä
    Reviewed-by: Shashank Sharma
    Link: https://patchwork.freedesktop.org/patch/msgid/20171113170427.4150-3-ville.syrjala@linux.intel.com

    Ville Syrjälä
     

15 Nov, 2017

1 commit

  • Apparently some sinks look at the YQ bits even when receiving RGB,
    and they get somehow confused when they see a non-zero YQ value.
    So we can't just blindly follow CEA-861-F and set YQ to match the
    RGB range.

    Unfortunately there is no good way to tell whether the sink
    designer claims to have read CEA-861-F. The CEA extension block
    revision number has generally been stuck at 3 since forever,
    and even a very recently manufactured sink might be based on
    an old design so the manufacturing date doesn't seem like
    something we can use. In lieu of better information let's
    follow CEA-861-F only for HDMI 2.0 sinks, since HDMI 2.0 is
    based on CEA-861-F. For HDMI 1.x sinks we'll always set YQ=0.

    The alternative would of course be to always set YQ=0. And if
    we ever encounter a HDMI 2.0+ sink with this bug that's what
    we'll probably have to do.

    Cc: stable@vger.kernel.org
    Cc: Jani Nikula
    Cc: Eric Anholt
    Cc: Neil Kownacki
    Reported-by: Neil Kownacki
    Tested-by: Neil Kownacki
    Fixes: fcc8a22cc905 ("drm/edid: Set YQ bits in the AVI infoframe according to CEA-861-F")
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101639
    Signed-off-by: Ville Syrjälä
    Link: https://patchwork.freedesktop.org/patch/msgid/20171108152504.12596-1-ville.syrjala@linux.intel.com
    Acked-by: Eric Anholt

    Ville Syrjälä
     

07 Nov, 2017

1 commit

  • This is no longer needed outside of drm_edid.c.

    Reviewed-by: Ville Syrjälä
    Reviewed-by: Alex Deucher
    Acked-by: Thierry Reding
    Signed-off-by: Jani Nikula
    Link: https://patchwork.freedesktop.org/patch/msgid/9c0be7b97d0144ed0419c87ac42b30f5835ca7e6.1509545641.git.jani.nikula@intel.com

    Jani Nikula
     

19 Sep, 2017

1 commit

  • Add drm_kms_helper.edid_firmware module parameter with param ops hooks
    to set drm.edid_firmware instead, for backwards compatibility.

    Suggested-by: Ville Syrjälä
    Cc: Abdiel Janulgue
    Cc: Daniel Vetter
    Cc: Ville Syrjälä
    Reviewed-by: Ville Syrjälä
    Acked-by: Dave Airlie
    Signed-off-by: Jani Nikula
    Link: https://patchwork.freedesktop.org/patch/msgid/20170918182003.22238-2-jani.nikula@intel.com

    Jani Nikula
     

15 Jul, 2017

2 commits

  • CEA-861-F spec adds ycbcr420 deep color support information
    in hf-vsdb block. This patch extends the existing hf-vsdb parsing
    function by adding parsing of ycbcr420 deep color support from the
    EDID and adding it into display information stored.

    V2: Rebase
    V3: Rebase
    V4: Moved definition of y420_dc_modes into this patch, where its used
    (Ville)
    V5: Optimize function, if(conditions) not reqd (Ville)
    V6: Rebase
    V7: Rebase

    Cc: Ville Syrjälä
    Cc: Jose Abreu
    Signed-off-by: Shashank Sharma
    Link: http://patchwork.freedesktop.org/patch/msgid/1499960000-9232-8-git-send-email-shashank.sharma@intel.com
    [vsyrjala: Fix sparse indentation warn]
    Signed-off-by: Ville Syrjälä

    Shashank Sharma
     
  • HDMI 1.4b support the CEA video modes as per range of CEA-861-D (VIC 1-64).
    For any other mode, the VIC filed in AVI infoframes should be 0.
    HDMI 2.0 sinks, support video modes range as per CEA-861-F spec, which is
    extended to (VIC 1-107).

    This patch adds a bool input variable, which indicates if the connected
    sink is a HDMI 2.0 sink or not. This will make sure that we don't pass a
    HDMI 2.0 VIC to a HDMI 1.4 sink.

    This patch touches all drm drivers, who are callers of this function
    drm_hdmi_avi_infoframe_from_display_mode but to make sure there is
    no change in current behavior, is_hdmi2 is kept as false.

    In case of I915 driver, this patch:
    - checks if the connected display is HDMI 2.0.
    - HDMI infoframes carry one of this two type of information:
    - VIC for 4K modes for HDMI 1.4 sinks
    - S3D information for S3D modes
    As CEA-861-F has already defined VICs for 4K videomodes, this
    patch doesn't allow sending HDMI infoframes for HDMI 2.0 sinks,
    until the mode is 3D.

    Cc: Ville Syrjala
    Cc: Jose Abreu
    Cc: Andrzej Hajda
    Cc: Alex Deucher
    Cc: Daniel Vetter

    PS: This patch touches a few lines in few files, which were
    already above 80 char, so checkpatch gives 80 char warning again.
    - gpu/drm/omapdrm/omap_encoder.c
    - gpu/drm/i915/intel_sdvo.c

    V2: Rebase, Added r-b from Andrzej
    V3: Addressed review comment from Ville:
    - Do not send VICs in both AVI-IF and HDMI-IF
    send only one of it.
    V4: Rebase
    V5: Added r-b from Neil.
    Addressed review comments from Ville
    - Do not block HDMI vendor IF, instead check for VIC while
    handling AVI infoframes
    V6: Rebase
    V7: Rebase

    Reviewed-by: Andrzej Hajda
    Reviewed-by: Neil Armstrong
    Signed-off-by: Shashank Sharma
    Link: http://patchwork.freedesktop.org/patch/msgid/1499960000-9232-2-git-send-email-shashank.sharma@intel.com
    Signed-off-by: Ville Syrjälä

    Shashank Sharma
     

21 Mar, 2017

1 commit

  • This patch does following:
    - Adds a new structure (drm_hdmi_info) in drm_display_info.
    This structure will be used to save and indicate if sink
    supports advanced HDMI 2.0 features
    - Adds another structure drm_scdc within drm_hdmi_info, to
    reflect scdc support and capabilities in connected HDMI 2.0 sink.
    - Checks the HF-VSDB block for presence of SCDC, and marks it
    in scdc structure
    - If SCDC is present, checks if sink is capable of generating
    SCDC read request, and marks it in scdc structure.

    V2: Addressed review comments
    Thierry:
    - Fix typos in commit message and make abbreviation consistent
    across the commit message.
    - Change structure object name from hdmi_info -> hdmi
    - Fix typos and abbreviations in description of structure drm_hdmi_info
    end the description with a full stop.
    - Create a structure drm_scdc, and keep all information related to SCDC
    register set (supported, read request supported) etc in it.

    Ville:
    - Change rr -> read_request
    - Call drm_detect_scrambling function drm_parse_hf_vsdb so that all
    of HF-VSDB parsing can be kept in same function, in incremental
    patches.

    V3: Rebase.
    V4: Rebase.
    V5: Rebase.
    V6: Addressed review comments from Ville
    - Add clock rate calculations for 1/10 and 1/40 ratios
    - Remove leftovers from old patchset
    V7: Added R-B from Jose.
    V8: Rebase.
    V9: Rebase.
    V10: Rebase.

    Signed-off-by: Shashank Sharma
    Reviewed-by: Thierry Reding
    Reviewed-by: Jose Abreu
    Signed-off-by: Jani Nikula
    Link: http://patchwork.freedesktop.org/patch/msgid/1489404244-16608-5-git-send-email-shashank.sharma@intel.com

    Shashank Sharma
     

14 Mar, 2017

1 commit


24 Feb, 2017

1 commit

  • Pull drm updates from Dave Airlie:
    "This is the main drm pull request for v4.11.

    Nothing too major, the tinydrm and mmu-less support should make
    writing smaller drivers easier for some of the simpler platforms, and
    there are a bunch of documentation updates.

    Intel grew displayport MST audio support which is hopefully useful to
    people, and FBC is on by default for GEN9+ (so people know where to
    look for regressions). AMDGPU has a lot of fixes that would like new
    firmware files installed for some GPUs.

    Other than that it's pretty scattered all over.

    I may have a follow up pull request as I know BenH has a bunch of AST
    rework and fixes and I'd like to get those in once they've been tested
    by AST, and I've got at least one pull request I'm just trying to get
    the author to fix up.

    Core:
    - drm_mm reworked
    - Connector list locking and iterators
    - Documentation updates
    - Format handling rework
    - MMU-less support for fbdev helpers
    - drm_crtc_from_index helper
    - Core CRC API
    - Remove drm_framebuffer_unregister_private
    - Debugfs cleanup
    - EDID/Infoframe fixes
    - Release callback
    - Tinydrm support (smaller drivers for simple hw)

    panel:
    - Add support for some new simple panels

    i915:
    - FBC by default for gen9+
    - Shared dpll cleanups and docs
    - GEN8 powerdomain cleanup
    - DMC support on GLK
    - DP MST audio support
    - HuC loading support
    - GVT init ordering fixes
    - GVT IOMMU workaround fix

    amdgpu/radeon:
    - Power/clockgating improvements
    - Preliminary SR-IOV support
    - TTM buffer priority and eviction fixes
    - SI DPM quirks removed due to firmware fixes
    - Powerplay improvements
    - VCE/UVD powergating fixes
    - Cleanup SI GFX code to match CI/VI
    - Support for > 2 displays on 3/5 crtc asics
    - SI headless fixes

    nouveau:
    - Rework securre boot code in prep for GP10x secure boot
    - Channel recovery improvements
    - Initial power budget code
    - MMU rework preperation

    vmwgfx:
    - Bunch of fixes and cleanups

    exynos:
    - Runtime PM support for MIC driver
    - Cleanups to use atomic helpers
    - UHD Support for TM2/TM2E boards
    - Trigger mode fix for Rinato board

    etnaviv:
    - Shader performance fix
    - Command stream validator fixes
    - Command buffer suballocator

    rockchip:
    - CDN DisplayPort support
    - IOMMU support for arm64 platform

    imx-drm:
    - Fix i.MX5 TV encoder probing
    - Remove lower fb size limits

    msm:
    - Support for HW cursor on MDP5 devices
    - DSI encoder cleanup
    - GPU DT bindings cleanup

    sti:
    - stih410 cleanups
    - Create fbdev at binding
    - HQVDP fixes
    - Remove stih416 chip functionality
    - DVI/HDMI mode selection fixes
    - FPS statistic reporting

    omapdrm:
    - IRQ code cleanup

    dwi-hdmi bridge:
    - Cleanups and fixes

    adv-bridge:
    - Updates for nexus

    sii8520 bridge:
    - Add interlace mode support
    - Rework HDMI and lots of fixes

    qxl:
    - probing/teardown cleanups

    ZTE drm:
    - HDMI audio via SPDIF interface
    - Video Layer overlay plane support
    - Add TV encoder output device

    atmel-hlcdc:
    - Rework fbdev creation logic

    tegra:
    - OF node fix

    fsl-dcu:
    - Minor fixes

    mali-dp:
    - Assorted fixes

    sunxi:
    - Minor fix"

    [ This was the "fixed" pull, that still had build warnings due to people
    not even having build tested the result. I'm not a happy camper

    I've fixed the things I noticed up in this merge. - Linus ]

    * tag 'drm-for-v4.11-less-shouty' of git://people.freedesktop.org/~airlied/linux: (1177 commits)
    lib/Kconfig: make PRIME_NUMBERS not user selectable
    drm/tinydrm: helpers: Properly fix backlight dependency
    drm/tinydrm: mipi-dbi: Fix field width specifier warning
    drm/tinydrm: mipi-dbi: Silence: ‘cmd’ may be used uninitialized
    drm/sti: fix build warnings in sti_drv.c and sti_vtg.c files
    drm/amd/powerplay: fix PSI feature on Polars12
    drm/amdgpu: refuse to reserve io mem for split VRAM buffers
    drm/ttm: fix use-after-free races in vm fault handling
    drm/tinydrm: Add support for Multi-Inno MI0283QT display
    dt-bindings: Add Multi-Inno MI0283QT binding
    dt-bindings: display/panel: Add common rotation property
    of: Add vendor prefix for Multi-Inno
    drm/tinydrm: Add MIPI DBI support
    drm/tinydrm: Add helper functions
    drm: Add DRM support for tiny LCD displays
    drm/amd/amdgpu: post card if there is real hw resetting performed
    drm/nouveau/tmr: provide backtrace when a timeout is hit
    drm/nouveau/pci/g92: Fix rearm
    drm/nouveau/drm/therm/fan: add a fallback if no fan control is specified in the vbios
    drm/nouveau/hwmon: expose power_max and power_crit
    ..

    Linus Torvalds
     

21 Feb, 2017

1 commit


20 Feb, 2017

1 commit


27 Jan, 2017

4 commits

  • HDMI 2.0 recommends that we set the Q bits in the AVI infoframe
    even when the sink does not support quantization range selection (QS=0).
    According to CEA-861 we can do that as long as the Q we send matches
    the default quantization range for the mode.

    Previously I think I had misread the spec as saying that you can't
    send a non-zero Q at all when QS=0. But that's not what the spec
    actually says.

    v2: Fix typo in commit message (Jani)

    Signed-off-by: Ville Syrjälä
    Link: http://patchwork.freedesktop.org/patch/msgid/20170111125725.8086-5-ville.syrjala@linux.intel.com
    Reviewed-by: Jani Nikula
    Acked-by: Eric Anholt

    Ville Syrjälä
     
  • Pull the logic to populate the quantization range information
    in the AVI infoframe into a small helper. We'll be adding a bit
    more logic to it, and having it in a central place seems like a
    good idea since it's based on the CEA-861 spec.

    Signed-off-by: Ville Syrjälä
    Link: http://patchwork.freedesktop.org/patch/msgid/20170111125725.8086-4-ville.syrjala@linux.intel.com
    Reviewed-by: Jani Nikula
    Acked-by: Eric Anholt

    Ville Syrjälä
     
  • Make the code selecting the RGB quantization range a little less magicy
    by wrapping it up in a small helper.

    v2: s/adjusted_mode/mode in vc4 to make it actually compile
    v3: Add a comment proposed by Eric

    Signed-off-by: Ville Syrjälä
    Link: http://patchwork.freedesktop.org/patch/msgid/20170111141835.25369-1-ville.syrjala@linux.intel.com
    Reviewed-by: Jani Nikula
    Acked-by: Eric Anholt

    Ville Syrjälä
     
  • drm_edid.h depends on hdmi.h on account of enum hdmi_picture_aspect,
    so let's just include hdmi.h and drop some useless struct declarations.

    Signed-off-by: Ville Syrjälä
    Link: http://patchwork.freedesktop.org/patch/msgid/20170111125725.8086-2-ville.syrjala@linux.intel.com
    Reviewed-by: Jani Nikula
    Acked-by: Eric Anholt

    Ville Syrjälä
     

20 Jan, 2017

1 commit


09 Nov, 2016

1 commit

  • The only user was i915, which is now gone.

    Signed-off-by: Maarten Lankhorst
    Reviewed-by: Ville Syrjälä
    Acked-by: Dave Airlie #irc
    Cc: dri-devel@lists.freedesktop.org
    Link: http://patchwork.freedesktop.org/patch/msgid/1478609742-13603-9-git-send-email-maarten.lankhorst@linux.intel.com

    Maarten Lankhorst
     

19 Sep, 2016

1 commit


20 Apr, 2016

1 commit

  • Push the ifdef to the drm_edid.h and create a stub, for the
    DRM_LOAD_EDID_FIRMWARE=n case. This removes some clutter in
    the code, making it more readable.

    Signed-off-by: Ezequiel Garcia
    Reviewed-by: Jani Nikula
    Signed-off-by: Daniel Vetter
    Link: http://patchwork.freedesktop.org/patch/msgid/1461087638-16959-1-git-send-email-ezequiel@vanguardiasur.com.ar

    Ezequiel Garcia
     

16 Feb, 2016

1 commit

  • To fill the audio infoframe it is required to identify the
    connection type as DP or HDMI. This patch adds an API which
    parses ELD and returns the display type connected.

    Signed-off-by: Subhransu S. Prusty
    Signed-off-by: Vinod Koul
    Reviewed-by: Jani Nikula
    Cc: David Airlie
    Cc: dri-devel@lists.freedesktop.org
    Cc: Daniel Vetter
    Signed-off-by: Mark Brown

    Subhransu S. Prusty
     

09 Sep, 2015

2 commits


20 Aug, 2015

1 commit

  • Add a function to find the start of the SADs in the ELD. This
    complements the helper to retrieve the SAD count.

    [airlied: this fixes a build problem with the alsa eld helper
    which required this].

    Signed-off-by: Russell King
    Signed-off-by: Dave Airlie

    Russell King
     

13 Apr, 2015

1 commit

  • Add ELD versions according to HDA Specification v1.0a.

    2 indicates version 2, which supports CEA_Ver 861D or below. Maximum
    Baseline ELD size of 80 bytes (15 SAD count).

    31 indicates an ELD that has been partially populated through
    implementation specific mean of default programming before an external
    graphics driver is loaded. Only the field that is called out as "canned"
    field will be populated, and audio driver should ignore the non "canned"
    field.

    Signed-off-by: Jani Nikula
    Reviewed-by: Ville Syrjälä
    Signed-off-by: Daniel Vetter

    Jani Nikula
     

09 Dec, 2014

1 commit


27 Nov, 2014

1 commit

  • The drm_get_edid() function performs direct I2C accesses to read EDID
    blocks, assuming that the monitor DDC interface is directly connected to
    the I2C bus. It can't thus be used with HDMI encoders that control the
    DDC bus and expose EDID blocks through a different interface.

    Refactor drm_do_get_edid() to take a block read callback function
    instead of an I2C adapter, and export it for direct use by drivers.

    As in the general case the DDC bus is accessible by the kernel at the
    I2C level, drivers must make all reasonable efforts to expose it as an
    I2C adapter and use drm_get_edid() instead of abusing this function.

    Signed-off-by: Lars-Peter Clausen
    Signed-off-by: Laurent Pinchart
    Reviewed-by: Rob Clark
    Reviewed-by: Daniel Vetter

    Lars-Peter Clausen
     

05 Nov, 2014

1 commit


03 Jun, 2014

1 commit


02 Sep, 2013

1 commit

  • Alex writes:
    This is the radeon drm-next request. Big changes include:
    - support for dpm on CIK parts
    - support for ASPM on CIK parts
    - support for berlin GPUs
    - major ring handling cleanup
    - remove the old 3D blit code for bo moves in favor of CP DMA or sDMA
    - lots of bug fixes

    [airlied: fix up a bunch of conflicts from drm_order removal]

    * 'drm-next-3.12' of git://people.freedesktop.org/~agd5f/linux: (898 commits)
    drm/radeon/dpm: make sure dc performance level limits are valid (CI)
    drm/radeon/dpm: make sure dc performance level limits are valid (BTC-SI) (v2)
    drm/radeon: gcc fixes for extended dpm tables
    drm/radeon: gcc fixes for kb/kv dpm
    drm/radeon: gcc fixes for ci dpm
    drm/radeon: gcc fixes for si dpm
    drm/radeon: gcc fixes for ni dpm
    drm/radeon: gcc fixes for trinity dpm
    drm/radeon: gcc fixes for sumo dpm
    drm/radeonn: gcc fixes for rv7xx/eg/btc dpm
    drm/radeon: gcc fixes for rv6xx dpm
    drm/radeon: gcc fixes for radeon_atombios.c
    drm/radeon: enable UVD interrupts on CIK
    drm/radeon: fix init ordering for r600+
    drm/radeon/dpm: only need to reprogram uvd if uvd pg is enabled
    drm/radeon: check the return value of uvd_v1_0_start in uvd_v1_0_init
    drm/radeon: split out radeon_uvd_resume from uvd_v4_2_resume
    radeon kms: fix uninitialised hotplug work usage in r100_irq_process()
    drm/radeon/audio: set up the sads on DCE3.2 asics
    drm/radeon: fix handling of variable sized arrays for router objects
    ...

    Conflicts:
    drivers/gpu/drm/i915/i915_dma.c
    drivers/gpu/drm/i915/i915_gem_dmabuf.c
    drivers/gpu/drm/i915/intel_pm.c
    drivers/gpu/drm/radeon/cik.c
    drivers/gpu/drm/radeon/ni.c
    drivers/gpu/drm/radeon/r600.c

    Dave Airlie
     

31 Aug, 2013

1 commit


30 Aug, 2013

1 commit

  • This can then be used by DRM drivers to setup their vendor infoframes.

    v2: Fix hmdi typo (Simon Farnsworth)
    v3: Adapt to the hdmi_vendor_infoframe rename

    Signed-off-by: Damien Lespiau
    Reviewed-by: Simon Farnsworth
    Reviewed-by: Ville Syrjälä
    Reviewed-by: Thierry Reding
    Signed-off-by: Dave Airlie

    Lespiau, Damien
     

24 Apr, 2013

1 commit

  • Some devices (ATI/AMD cards) don't support passing ELD struct to the
    hardware but just require filling specific registers and then the
    hardware/firmware does the rest. In such cases we need to read the info
    from SAD blocks and put them in the correct registers.

    agd5f: note that the returned pointer needs to be kfreed as per
    Christian's suggestion.

    v2: fix warning

    Signed-off-by: Rafał Miłecki
    Reviewed-by: Christian König
    Signed-off-by: Alex Deucher

    Rafał Miłecki
     

22 Feb, 2013

1 commit


24 Apr, 2012

1 commit

  • The new structs added in struct detailed_data_monitor_range must be
    marked with packed attribute although the outer struct itself is
    already marked as packed. Otherwise these 7-bytes structs may be
    aligned, and give the wrong position and size for the data.

    Signed-off-by: Takashi Iwai
    Acked-by: Adam Jackson
    Signed-off-by: Dave Airlie

    Takashi Iwai