- 30 Mar, 2015 2 commits
-
-
Ander Conselvan de Oliveira authored
Consistently with other free functions, handle the NULL case without oopsing. Cc: dri-devel@lists.freedesktop.org Signed-off-by:
Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com> Signed-off-by:
Daniel Vetter <daniel.vetter@ffwll.ch>
-
Ander Conselvan de Oliveira authored
Users of the atomic state assume that if the pointer to a crtc, plane or connector is not NULL in the respective object vector, than the state for that object in *_states vector also won't be NULL. That assumption was broken by drm_atomic_state_clear(), which would clear the state pointer but leave the pointer to the object still set. This fixes a NULL pointer dereference in i915 caused by the use of drm_atomic_state_clear(). Cc: dri-devel@lists.freedesktop.org Signed-off-by:
-
- 27 Mar, 2015 6 commits
-
-
Ville Syrjälä authored
Use the same logic when checking for valid ioctl range in drm_ioctl_flags() that is used in drm_ioctl() to avoid confusion. Signed-off-by:
Ville Syrjälä <ville.syrjala@linux.intel.com> Signed-off-by:
-
Ville Syrjälä authored
Use max() to make the code to determine the allocation size for the ioctl data easier to read. Signed-off-by:
-
Ville Syrjälä authored
Now that cmd_drv is gone the handling for core and driver ioctls is mostly identical, so eliminate the duplication. Also take the opportunity to simplify the range checks to be less cluttered. Signed-off-by:
-
Ville Syrjälä authored
ioctl->cmd_drv is pointless and we can just as well stick the full ioctl definition into ioctl->cmd. Cc: Jakob Bornecrantz <jakob@vmware.com> Cc: Thomas Hellstrom <thellstrom@vmware.com> Signed-off-by:
-
Ville Syrjälä authored
Currently DRM_IOCTL_DEF_DRV does '[DRM_IOCTL_NR(DRM_##ioctl)]' which doesn't make much sense since DRM_##ioctl is already a the raw ioctl number. So change it to 'DRM_IOCTL_NR(DRM_IOCTL_##ioctl) - DRM_COMMAND_BASE' which means the DRM_IOCTL_NR() now makes sense, and also this also means if there's a mistake in the DRM_IOCTL_##ioctl macros we might get a warning about it (eg. we would have gotten a sparse warning about the i915 colorkey get/set ioctl being defined to be the same thing). Signed-off-by:
-
Daniel Vetter authored
Legacy setCrtc has a nice fastpath for just updating the frontbuffer when the output routing doesn't change. Which I of course tried to keep working, except that I fumbled the job: The helpers correctly compute ->mode_changed, CRTC updates get correctly skipped but connector functions are called unconditionally. Fix this. v2: For the disable sided connector->state->crtc might be NULL. Instead look at the old_connector_state->crtc, but still use the new crtc state for that old crtc. Reported by Thierry. Reported-and-Tested-by:
Gustavo Padovan <gustavo.padovan@collabora.co.uk> Reviewed-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk> (v1) Cc: Thierry Reding <thierry.reding@gmail.com> Cc: Gustavo Padovan <gustavo.padovan@collabora.co.uk> (v1) Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
- 23 Mar, 2015 7 commits
-
-
Daniel Stone authored
Before, we would set the property, but also return -EINVAL because of a broken fallthrough. Signed-off-by:
Daniel Stone <daniels@collabora.com> Signed-off-by:
-
Daniel Stone authored
Active was here, and we allowed users to set it, but not to get it as well. Signed-off-by:
-
Daniel Stone authored
Just as we provide crtc->mode pre-populated with the requested mode, move adjusted_mode into hwmode before we call the crtc's mode_set, making sure to restore it on failure. Allows drivers which thoughtlessly discard adjusted_mode in their mode_set hooks (e.g. Exynos) to use hwmode directly, and also provides some neat symmetry with crtc->mode. Signed-off-by:
-
Daniel Stone authored
Since we're now using mode == NULL to represent disabled, it's not wholly surprising that we'd want to compare NULL modes. Signed-off-by:
-
Daniel Stone authored
mode is always NULL at this point in the function, so make our intention clear. Signed-off-by:
-
Daniel Stone authored
Signed-off-by:
-
Ville Syrjälä authored
When doing a native or i2c aux write the sink will indicate the number of bytes written even if it the nacks the transfer. When we receive a nack we just return an error upwards, but it might still be interesting to see how many bytes made it before the nack. So include that information in the debug messages. v2: Also print the message size (Jani) Signed-off-by:
Jani Nikula <jani.nikula@intel.com> Signed-off-by:
-
- 22 Mar, 2015 3 commits
-
-
git://linuxtv.org/pinchartl/fbdevDave Airlie authored
rcar-du fixes * 'drm/next/rcar-du' of git://linuxtv.org/pinchartl/fbdev: drm: rcar-du: Enable the atomic updates API drm: rcar-du: Don't initialize event->pipe field drm: rcar-du: Fix framebuffer reference leak through plane state MAINTAINERS: Remove rcar-du.h entry
-
git://linuxtv.org/pinchartl/fbdevDave Airlie authored
adv7511 fixes. * 'drm/next/adv7511' of git://linuxtv.org/pinchartl/fbdev: drm: adv7511: Refactor power management drm: adv7511: Fix nested sleep when reading EDID drm: adv7511: Fix DDC error interrupt handling
-
git://people.freedesktop.org/~agd5f/linuxDave Airlie authored
- DP MST support (disabled by default) - non-ATOM aux support (DCE5+) - output csc support for clamped RGB - Lots of new queries for profiling, Gallium HUD, etc. - Misc fixes * 'drm-next-4.1' of git://people.freedesktop.org/~agd5f/linux: (40 commits) drm/radeon: add DisplayPort MST support (v2) drm/radeon: improve encoder picking functions (v2) drm/radeon: export max link rate calculation drm/radeon: add new atombios encoder/transmitter interfaces drm/radeon: add some MST registers radeon/fb: add wrapper functions around fb connector add/remove radeon/cik: add support for short HPD irqs radeon/si: add support for short HPD irqs radeon/evergreen: add support for short HPD irqs radeon: introduce a dp_work handler drm/dp_mst: add a function to retrieve vcpi slots drm/radeon: program auxch directly (v2) drm/radeon: fix doublescan modes (v2) drm/radeon: typo in parameter description drm/radeon: add support for read reg query from radeon info ioctl drm/radeon: add get_allowed_info_register for CIK drm/radeon: add get_allowed_info_register for SI drm/radeon: add get_allowed_info_register for cayman/TN drm/radeon: add get_allowed_info_register for EG/BTC drm/radeon: add get_allowed_info_register for r6xx/r7xx ...
-
- 19 Mar, 2015 22 commits
-
-
Dave Airlie authored
This adds initial DP 1.2 MST support to radeon, on CAYMAN and up in theory. This is off by default. v2: agd5f: - add UNIPHY3 offsets - move atom cmd table code into atombios_encoders.c - whitespace cleanup - replace some magic numbers with proper defines Signed-off-by:
Dave Airlie <airlied@redhat.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Dave Airlie authored
For MST we need to be able to pick front end encoders separate from backend, but only for MST, so we need to make the encoder picking interface smarter. v2: agd5f: squash in: drm/radeon: release digital encoder before asking for new one Reported-by:
Dieter Nützel <Dieter@nuetzel-hh.de> Signed-off-by:
-
Dave Airlie authored
We need this in the MST code later. Signed-off-by:
-
Dave Airlie authored
These allow overriding the encoder id with the frontend, we need this for setting up MST. Signed-off-by:
-
Dave Airlie authored
These registers will be used later to setup Signed-off-by:
-
Dave Airlie authored
These are just two wrappers to be used in the MST code later. Signed-off-by:
-
Alex Deucher authored
This adds support to process short HPD irqs on CIK gpus. Signed-off-by: -
Dave Airlie authored
This adds support to process short HPD irqs on SI gpus. Signed-off-by:
-
Dave Airlie authored
This adds support for processing short irqs, and triggering the dp_work. Signed-off-by:
-
Dave Airlie authored
This is to be called on short HPD irqs, just introduce the basic infrastructure for it. Signed-off-by:
-
Dave Airlie authored
radeon requires this to get the slots for later filling out a table on every transition. Signed-off-by:
-
Dave Airlie authored
The atombios tables have an unfortunate restriction on only being able to write 12 bytes, MST really wants 16-bytes here, and since the hw can do it, we should just write directly to it. This uses a module option to allow for it now, and maybe we should provide the old code as a fallback for a while. v2: (agd5f) - move registers to a proper register header - only enable on DCE5+ - enable by default on DCE5+ - Switch pad to aux mode before using it - reformat instance handling to better match the rest of the driver Signed-off-by:
-
Alex Deucher authored
Use the correct flags for atom. v2: handle DRM_MODE_FLAG_DBLCLK Signed-off-by: -
Vincent Batts authored
"defaul" -> "default" Signed-off-by:
Vincent Batts <vbatts@hashbangbash.com> Signed-off-by:
-
Alex Deucher authored
This allows us to query certain registers from userspace for profiling and harvest configuration. E.g., it can be used by the GALLIUM_HUD for profiling the status of various gfx blocks. Tested-by:
Marek Olšák <marek.olsak@amd.com> Signed-off-by:
-
Alex Deucher authored
Registers that can be fetched from the info ioctl. Tested-by:
-
Alex Deucher authored
Registers that can be fetched from the info ioctl. Tested-by:
-
Alex Deucher authored
Registers that can be fetched from the info ioctl. Tested-by:
-
Alex Deucher authored
Registers that can be fetched from the info ioctl. Tested-by:
-
Alex Deucher authored
Registers that can be fetched from the info ioctl. Tested-by:
-
Alex Deucher authored
Just a stub. Tested-by:
-
Alex Deucher authored
This adds a callback for each asic family to determine what registers are allowed to be read back via the info ioctl. The idea here is to allow usermode to query things like GPU status registers or GPU harvest registers for profiling and determining the gfx config. Tested-by:
-
