Skip to content

K
Kernel

openeuler / Kernel
接近 2 年 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 07 3月, 2017 1 次提交
  3. 01 3月, 2017 12 次提交
  5. 22 2月, 2017 1 次提交
  7. 02 2月, 2017 1 次提交
  9. 17 1月, 2017 1 次提交
  11. 15 12月, 2016 2 次提交
  13. 15 11月, 2016 3 次提交
  15. 20 9月, 2016 1 次提交
  17. 22 7月, 2016 1 次提交
  19. 07 6月, 2016 2 次提交
  21. 31 5月, 2016 1 次提交
  23. 17 5月, 2016 1 次提交
  25. 02 5月, 2016 1 次提交
  27. 31 3月, 2016 1 次提交
  29. 16 2月, 2016 1 次提交
  31. 11 12月, 2015 2 次提交
    • V
      drm: Drop drm_helper_probe_single_connector_modes_nomerge() · 6af3e656
      由 Ville Syrjälä 提交于 
      Now that the mode type bit merge logic is fixed to only merge
between new probed modes, hopefully we can eliminat the special
case for qxl and virtio. That is make the merge the mode type
bits from all matching new probed modes, just like every other
driver.

qxl and virtio got excluded from the merging in
commit 3fbd6439 ("drm: copy mode type in drm_mode_connector_list_update()")
commit abce1ec9 ("Revert "drm: copy mode type in drm_mode_connector_list_update()"")
commit b87577b7 ("drm: try harder to avoid regression when merging mode bits")

Cc: Marc-André Lureau <marcandre.lureau@redhat.com>
Cc: Dave Airlie <airlied@redhat.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Adam Jackson <ajax@redhat.com>
Signed-off-by: NVille Syrjälä <ville.syrjala@linux.intel.com>
[danvet: Resolve conflicts with doc updates.]
Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      6af3e656
    • V
      drm: Pass 'name' to drm_encoder_init() · 13a3d91f
      由 Ville Syrjälä 提交于 
      Done with coccinelle for the most part. However, it thinks '...' is
part of the semantic patch, so I put an 'int DOTDOTDOT' placeholder
in its place and got rid of it with sed afterwards.

@@
identifier dev, encoder, funcs;
@@
 int drm_encoder_init(struct drm_device *dev,
                      struct drm_encoder *encoder,
                      const struct drm_encoder_funcs *funcs,
                      int encoder_type
+                     ,const char *name, int DOTDOTDOT
                      )
{ ... }

@@
identifier dev, encoder, funcs;
@@
 int drm_encoder_init(struct drm_device *dev,
                      struct drm_encoder *encoder,
                      const struct drm_encoder_funcs *funcs,
                      int encoder_type
+                     ,const char *name, int DOTDOTDOT
                      );

@@
expression E1, E2, E3, E4;
@@
 drm_encoder_init(E1, E2, E3, E4
+                 ,NULL
                  )

v2: Add ', or NULL...' to @name kernel doc (Jani)
    Annotate the function with __printf() attribute (Jani)
Signed-off-by: NVille Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
Link: http://patchwork.freedesktop.org/patch/msgid/1449670818-2966-1-git-send-email-ville.syrjala@linux.intel.com
      13a3d91f
  33. 08 12月, 2015 1 次提交
  35. 24 11月, 2015 1 次提交
  37. 07 10月, 2015 1 次提交
  39. 01 10月, 2015 1 次提交
  41. 24 9月, 2015 1 次提交
  43. 11 9月, 2015 1 次提交
    • J
      drm/qxl: validate monitors config modes · bd3e1c7c
      由 Jonathon Jongsma 提交于 
      Due to some recent changes in
drm_helper_probe_single_connector_modes_merge_bits(), old custom modes
were not being pruned properly. In current kernels,
drm_mode_validate_basic() is called to sanity-check each mode in the
list. If the sanity-check passes, the mode's status gets set to to
MODE_OK. In older kernels this check was not done, so old custom modes
would still have a status of MODE_UNVERIFIED at this point, and would
therefore be pruned later in the function.

As a result of this new behavior, the list of modes for a device always
includes every custom mode ever configured for the device, with the
largest one listed first. Since desktop environments usually choose the
first preferred mode when a hotplug event is emitted, this had the
result of making it very difficult for the user to reduce the size of
the display.

The qxl driver did implement the mode_valid connector function, but it
was empty. In order to restore the old behavior where old custom modes
are pruned, we implement a proper mode_valid function for the qxl
driver. This function now checks each mode against the last configured
custom mode and the list of standard modes. If the mode doesn't match
any of these, its status is set to MODE_BAD so that it will be pruned as
expected.
Signed-off-by: NJonathon Jongsma <jjongsma@redhat.com>
Cc: stable@vger.kernel.org
Signed-off-by: NDave Airlie <airlied@redhat.com>
      bd3e1c7c
  45. 05 6月, 2015 1 次提交
  47. 15 11月, 2014 1 次提交