[PATCH 1/2] drm: exynos: Perform initialization/cleanup at probe/remove time

Hi Daniel, On Tuesday 13 Dec 2016 22:49:51 Daniel Vetter wrote: > On Tue, Dec 13, 2016 at 04:32:30PM -0500, Sean Paul wrote: > > On Tue, Dec 13, 2016 at 4:30 PM, Laurent Pinchart wrote: > >> On Tuesday 13 Dec 2016 22:10:58 Daniel Vetter wrote: > >>> On Tue, Dec 13, 2016 at 09:34:05PM +0200,

[PATCH 08/13] drm: prevent double-(un)registration for connectors

On Wed, Dec 14, 2016 at 12:08:09AM +0100, Daniel Vetter wrote: > If we're unlucky then the registration from a hotplugged connector > might race with the final registration step on driver load. And since > MST topology discover is asynchronous that's even somewhat likely. > > v2: Also update the

[PATCH 2/2] drm: omapdrm: Perform initialization/cleanup at probe/remove time

Hi Daniel, On Tuesday 13 Dec 2016 22:21:10 Daniel Vetter wrote: > On Tue, Dec 13, 2016 at 05:21:43PM +0200, Laurent Pinchart wrote: > > The drm driver .load() operation is prone to race conditions as it > > initializes the driver after registering the device nodes. Its usage is > > deprecated,

[PATCH 1/2] drm: exynos: Perform initialization/cleanup at probe/remove time

On Tuesday 13 Dec 2016 22:10:58 Daniel Vetter wrote: > On Tue, Dec 13, 2016 at 09:34:05PM +0200, Laurent Pinchart wrote: > > From: Laurent Pinchart > > > > The drm driver .load() operation is prone to race conditions as it > > initializes the driver after registering the device nodes. Its usage

[PATCH v2] drm: shmobile: Perform initialization/cleanup at probe/remove time

Hi Daniel, On Tuesday 13 Dec 2016 22:01:36 Daniel Vetter wrote: > On Tue, Dec 13, 2016 at 07:19:15PM +0200, Laurent Pinchart wrote: > > On Tuesday 13 Dec 2016 18:11:34 Daniel Vetter wrote: > >> On Tue, Dec 13, 2016 at 02:59:48PM +0200, Laurent Pinchart wrote: > >>> From: Laurent Pinchart > >>>

[PATCH 1/2] drm: omapdrm: Use sizeof(*var) instead of sizeof(type) for structures

On Tuesday 13 Dec 2016 22:12:12 Daniel Vetter wrote: > On Tue, Dec 13, 2016 at 05:21:42PM +0200, Laurent Pinchart wrote: > > By linking the sizeof to a variable type the code will be less prone to > > bugs due to future type changes of variables. > > > > Signed-off-by: Laurent Pinchart > >

[PATCH] drm: Use atomic state for FB in legacy ioctls

On Tue, Dec 13, 2016 at 07:02:53PM +, Daniel Stone wrote: > Hi, > > > On 13 Dec 2016, at 6:48 pm, Ville Syrjälä > linux.intel.com> wrote: > > > >> On Tue, Dec 13, 2016 at 06:19:12PM +, Daniel Stone wrote: > >> @@ -357,7 +357,10 @@ int drm_mode_getcrtc(struct drm_device *dev, > >> >

[PATCH 2/2] ASoC: hdmi-codec: add channel mapping control

On 2016年12月13日 22:23, Takashi Sakamoto wrote: > Hi Arnaud, >>> This table is invariant in lifetime of the storage object, as well. >>> Let's put into .rodata section, too. >>> >> This table is updated in hdmi_codec_cea_init_channel_alloc so can not be >> constant. In theory i could declare

[PATCH 1/2] drm: exynos: Perform initialization/cleanup at probe/remove time

On Tue, Dec 13, 2016 at 04:32:30PM -0500, Sean Paul wrote: > On Tue, Dec 13, 2016 at 4:30 PM, Laurent Pinchart > wrote: > > On Tuesday 13 Dec 2016 22:10:58 Daniel Vetter wrote: > >> On Tue, Dec 13, 2016 at 09:34:05PM +0200, Laurent Pinchart wrote: > >> > From: Laurent Pinchart > >> > > >> > The

[PATCH 2/2] drm: omapdrm: Perform initialization/cleanup at probe/remove time

On Tue, Dec 13, 2016 at 11:41:09PM +0200, Laurent Pinchart wrote: > On Tuesday 13 Dec 2016 22:21:10 Daniel Vetter wrote: > > On Tue, Dec 13, 2016 at 05:21:43PM +0200, Laurent Pinchart wrote: > > > + > > > + /* Allocate and initialize the DRM device. */ > > > + ddev = drm_dev_alloc(_drm_driver,

[PATCH 26/34] drm: Rename prev_node to hole in drm_mm_scan_add_block()

On Tue, Dec 13, 2016 at 05:23:54PM +0200, Joonas Lahtinen wrote: > On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > > Acknowledging that we were building up the hole was more useful to me > > when reading the code, than knowing the relationship between this node > > and the previous node. >

[PATCH] drm/fsl: don't use drm_put_dev

On Tue, Dec 13, 2016 at 06:57:59PM +0100, Lucas Stach wrote: > Am Dienstag, den 13.12.2016, 18:54 +0100 schrieb Daniel Vetter: > > fsl is already fully demidlayered in the probe function, but for > > convenience stuck with drm_put_dev. Call the unregister/unref parts > > separately, to make sure

[patch] drm: mxsfb: drm_dev_alloc() returns error pointers

On Tue, Dec 13, 2016 at 03:23:32PM +0300, Dan Carpenter wrote: > We should be checking for IS_ERR() instead of NULL because > drm_dev_alloc() returns error pointers. > > Fixes: 45d59d704080 ("drm: Add new driver for MXSFB controller") > Signed-off-by: Dan Carpenter Queued up in drm-misc for

[PATCH 2/2] ASoC: hdmi-codec: add channel mapping control

Hi Arnaud, On Dec 12 2016 22:46, Arnaud Pouliquen wrote: > On 12/12/2016 01:03 PM, Takashi Sakamoto wrote: >> On 2016年12月12日 18:38, Arnaud Pouliquen wrote: > + */ > +static struct hdmi_codec_cea_spk_alloc hdmi_codec_channel_alloc[] = { > +/* channel: 7

[PATCH] drm: Use atomic state for FB in legacy ioctls

On Tue, Dec 13, 2016 at 11:14:47PM +0200, Ville Syrjälä wrote: > On Tue, Dec 13, 2016 at 07:02:53PM +, Daniel Stone wrote: > > Hi, > > > > > On 13 Dec 2016, at 6:48 pm, Ville Syrjälä > > linux.intel.com> wrote: > > > > > >> On Tue, Dec 13, 2016 at 06:19:12PM +, Daniel Stone wrote: >

[PATCH 2/2] drm: omapdrm: Perform initialization/cleanup at probe/remove time

On Tue, Dec 13, 2016 at 05:21:43PM +0200, Laurent Pinchart wrote: > The drm driver .load() operation is prone to race conditions as it > initializes the driver after registering the device nodes. Its usage is > deprecated, inline it in the probe function and call drm_dev_alloc() and >

[PATCH 1/2] drm: omapdrm: Use sizeof(*var) instead of sizeof(type) for structures

On Tue, Dec 13, 2016 at 05:21:42PM +0200, Laurent Pinchart wrote: > By linking the sizeof to a variable type the code will be less prone to > bugs due to future type changes of variables. > > Signed-off-by: Laurent Pinchart Reviewed-by: Daniel Vetter Isn't there some cocci magic that does

[PATCH 1/2] drm: exynos: Perform initialization/cleanup at probe/remove time

On Tue, Dec 13, 2016 at 09:34:05PM +0200, Laurent Pinchart wrote: > From: Laurent Pinchart > > The drm driver .load() operation is prone to race conditions as it > initializes the driver after registering the device nodes. Its usage is > deprecated, inline it in the probe function and call

[PATCH 2/2] drm: Remove unused drm_platform midlayer

On Tue, Dec 13, 2016 at 09:34:06PM +0200, Laurent Pinchart wrote: > Now that the last driver has been converted, the drm_platform midlayer > is unused. Remove it. > > Signed-off-by: Laurent Pinchart > --- > drivers/gpu/drm/Makefile | 2 +- >

[PATCH] drm_fourcc: Fix DRM_FORMAT_MOD_LINEAR #define

On Tue, Dec 13, 2016 at 11:27:52AM -0800, Kristian H. Kristensen wrote: > We need to define DRM_FORMAT_MOD_VENDOR_NONE for the fourcc_mod_code() > macro to work correctly. > > Signed-off-by: Kristian H. Kristensen Oopsies. Applied to drm-misc, thx for spotting. -Daniel > --- >

[PATCH v2] drm: shmobile: Perform initialization/cleanup at probe/remove time

On Tue, Dec 13, 2016 at 07:19:15PM +0200, Laurent Pinchart wrote: > Hi Daniel, > > On Tuesday 13 Dec 2016 18:11:34 Daniel Vetter wrote: > > On Tue, Dec 13, 2016 at 02:59:48PM +0200, Laurent Pinchart wrote: > > > From: Laurent Pinchart > > > > > > The drm driver .load() operation is prone to

[PATCH 06/34] drm: Add a simple linear congruent generator PRNG

Hello, On Tuesday 13 Dec 2016 16:16:41 David Herrmann wrote: > On Mon, Dec 12, 2016 at 12:53 PM, Chris Wilson wrote: > > For testing, we want a reproducible PRNG, a plain linear congruent > > generator is suitable for our very limited selftests. > > > > Signed-off-by: Chris Wilson This doesn't

[PATCH 2/2] drm: Remove unused drm_platform midlayer

Now that the last driver has been converted, the drm_platform midlayer is unused. Remove it. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/Makefile | 2 +- drivers/gpu/drm/drm_platform.c | 91 --

[PATCH 1/2] drm: exynos: Perform initialization/cleanup at probe/remove time

From: Laurent Pinchart The drm driver .load() operation is prone to race conditions as it initializes the driver after registering the device nodes. Its usage is deprecated, inline it in the probe function and call drm_dev_alloc() and drm_dev_register()

[PATCH 0/2] exynosdrm: Remove .load/.unload midlayer

Hello, Patch 1/2 removes the .load and .unload operations from the exynosdrm driver and moves the code to the probe/remove handlers. As I don't have access to exynos hardware the patch has been compile-tested only. As an added bonus, patch 2/2 removes the now unused drm_platform midlayer. It

Passing multi-screen layout to KMS driver

Hello, I'm afraid I'm not subscribed to the list, so I would greatly appreciate a CC on replies (if any). I have been fiddling with our (not-upstreamed) VirtualBox guest drm driver to make it work better with the Wayland version of GNOME Shell in Fedora 25. One problem that I have run into

[PATCH 06/34] drm: Add a simple linear congruent generator PRNG

On Tue, Dec 13, 2016 at 09:39:06PM +0200, Laurent Pinchart wrote: > Hello, > > On Tuesday 13 Dec 2016 16:16:41 David Herrmann wrote: > > On Mon, Dec 12, 2016 at 12:53 PM, Chris Wilson wrote: > > > For testing, we want a reproducible PRNG, a plain linear congruent > > > generator is suitable for

[PATCH] drm: Use atomic state for FB in legacy ioctls

On Tue, Dec 13, 2016 at 06:19:12PM +, Daniel Stone wrote: > If atomic state is available, use this to read the current plane in > GetCrtc/GetPlane, rather than the legacy points. > > Signed-off-by: Daniel Stone > Cc: Daniel Vetter > --- > drivers/gpu/drm/drm_crtc.c | 5 - >

Fwd: kvmgt-vfio-mdev-for-v4.10 pull request content

e: 169 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161213/7b8901a7/attachment.sig>

[PATCH libdrm] xf86drm: fix null termination of string buffer

From: Taro Yamada The string written to the buffer by read() is not null-terminated, but currently drmParsePciBusInfo() places null character only at the end of the buffer, not at the end of the string. As a result, the string passed to sscanf() contains an uninitialized

Patch to fix null termination of string buffer

This is my first time to sending a patch to the mailing list. So, I'm sorry if I did something wrong. The function drmParsePciBusInfo() in xf86drm.c reads the contents of the file "/sys/dev/char/x:y/device/uevent" into the buffer. The string written to the buffer by read() is not

[PATCH 12/23] drm: omapdrm: plane: update fifo size on atomic update

Hi Sebastian, Thank you for the patch. On Tuesday 08 Mar 2016 17:39:44 Sebastian Reichel wrote: > This is a workaround for a hardware bug occuring > on OMAP3 with manually updated panels. Could you please explain what the bug is and how the workaround operates ? Do you have a reference to an

[PATCH v2] drm: shmobile: Perform initialization/cleanup at probe/remove time

Hi Daniel, On Tuesday 13 Dec 2016 18:11:34 Daniel Vetter wrote: > On Tue, Dec 13, 2016 at 02:59:48PM +0200, Laurent Pinchart wrote: > > From: Laurent Pinchart > > > > The drm driver .load() operation is prone to race conditions as it > > initializes the driver after registering the device

[PATCH] drm: Use atomic state for FB in legacy ioctls

Hi, > On 13 Dec 2016, at 6:48 pm, Ville Syrjälä linux.intel.com> wrote: > >> On Tue, Dec 13, 2016 at 06:19:12PM +, Daniel Stone wrote: >> @@ -357,7 +357,10 @@ int drm_mode_getcrtc(struct drm_device *dev, >> >>drm_modeset_lock_crtc(crtc, crtc->primary); >>crtc_resp->gamma_size =

[PATCH] drm/fsl: don't use drm_put_dev

Am Dienstag, den 13.12.2016, 18:54 +0100 schrieb Daniel Vetter: > fsl is already fully demidlayered in the probe function, but for > convenience stuck with drm_put_dev. Call the unregister/unref parts > separately, to make sure this driver works correct. > > v2: Rebase. > > Cc: Lucas Stach >

[PATCH] drm/fsl: don't use drm_put_dev

fsl is already fully demidlayered in the probe function, but for convenience stuck with drm_put_dev. Call the unregister/unref parts separately, to make sure this driver works correct. v2: Rebase. Cc: Lucas Stach Cc: Stefan Agner Signed-off-by: Daniel Vetter ---

[git pull] vmwgfx-fixes

Hi Dave, The following changes since commit ab7cd8d83e5dba13027de66f1b008b08b30b71a4: Merge tag 'drm-intel-fixes-2016-12-01' of git://anongit.freedesktop.org/git/drm-intel into drm-fixes (2016-12-04 06:31:26 +1000) are available in the git repository at:

[PATCH 1/4] drm: Protect master->unique with dev->master_mutex

On 13/12/16 05:35 PM, Daniel Vetter wrote: > On Mon, Dec 12, 2016 at 01:23:46PM +, Emil Velikov wrote: >> On 10 December 2016 at 21:52, Daniel Vetter >> wrote: >>> No one looks at the major/minor versions except the unique/busid >>> stuff. If we protect that with the master_mutex (since it

[PATCH v2 6/6] drm/i915: Add a cursor hack to allow converting legacy page flip to atomic, v3.

Hi, On 12/12/2016 4:04 PM, Maarten Lankhorst wrote: > Do something similar to vc4, only allow updating the cursor state > in-place through a fastpath when the watermarks are unaffected. This > will allow cursor movement to be smooth, but changing cursor size or > showing/hiding cursor will still

[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

ext part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161213/af7fd04f/attachment.html>

[PATCH] drm: Use atomic state for FB in legacy ioctls

If atomic state is available, use this to read the current plane in GetCrtc/GetPlane, rather than the legacy points. Signed-off-by: Daniel Stone Cc: Daniel Vetter --- drivers/gpu/drm/drm_crtc.c | 5 - drivers/gpu/drm/drm_plane.c | 8 ++-- 2 files changed, 10 insertions(+), 3

[PATCH 3/4] drm/mediatek: don't use drm_put_dev

On Tue, Dec 13, 2016 at 11:55:32AM +0100, Lucas Stach wrote: > Am Donnerstag, den 08.12.2016, 12:07 +0100 schrieb Daniel Vetter: > > fsl is already fully demidlayered in the probe function, but for > ^ mediatek not fsl-dcu > > > convenience stuck with drm_put_dev. Call the unregister/unref

[PATCH 2/4] drm/fsl: don't use drm_put_dev

On Tue, Dec 13, 2016 at 11:53:53AM +0100, Lucas Stach wrote: > Am Donnerstag, den 08.12.2016, 12:07 +0100 schrieb Daniel Vetter: > > fsl is already fully demidlayered in the probe function, but for > > convenience stuck with drm_put_dev. Call the unregister/unref parts > > separately, to make sure

[PATCH v2] drm: shmobile: Perform initialization/cleanup at probe/remove time

On Tue, Dec 13, 2016 at 02:59:48PM +0200, Laurent Pinchart wrote: > From: Laurent Pinchart > > The drm driver .load() operation is prone to race conditions as it > initializes the driver after registering the device nodes. Its usage is > deprecated, inline it in the probe function and call

[Intel-gfx] [PATCH 2/6] drm/atomic: Unconditionally call prepare_fb.

On Tue, Dec 13, 2016 at 03:13:54PM +0100, Maarten Lankhorst wrote: > Op 09-12-16 om 09:25 schreef Daniel Vetter: > > On Fri, Dec 09, 2016 at 12:42:19AM +0200, Laurent Pinchart wrote: > >> Hi Daniel, > >> > >> On Thursday 08 Dec 2016 16:41:04 Daniel Vetter wrote: > >>> On Thu, Dec 08, 2016 at

[PATCH 0/5] sphinxification for dma-buf docs

Thanks Jonathan! On 12 December 2016 at 01:14, Jonathan Corbet wrote: > On Sun, 11 Dec 2016 18:35:42 +0100 > Daniel Vetter wrote: > >> > Here's a thought, though: how about if we slip in a little version of >> > dma-buf.rst now with a "coming soon, don't miss it!!" message? Then the >> > rest

[PATCH 32/34] drm: Apply tight eviction scanning to color_adjust

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > Using mm->color_adjust makes the eviction scanner much tricker since we > don't know the actual neighbours of the target hole until after it is > created (after scanning is complete). To work out whether we need to > evict the neighbours

[PATCH 30/34] drm: Optimise power-of-two alignments in drm_mm_scan_add_block()

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > For power-of-two alignments, we can avoid the 64bit divide and do a > simple bitwise add instead. > > Signed-off-by: Chris Wilson > --- >  drivers/gpu/drm/drm_mm.c | 9 - >  include/drm/drm_mm.h     | 1 + >  2 files changed,

[PATCH libdrm] xf86drm: fix null termination of string buffer

From: Taro Yamada The string written to the buffer by read() is not null-terminated, but currently drmParsePciBusInfo() places null character only at the end of the buffer, not at the end of the string. As a result, the string passed to sscanf() contains an uninitialized

Patch to fix null termination of string buffer

This is my first time to sending a patch to the mailing list. So, I'm sorry if I did something wrong. The function drmParsePciBusInfo() in xf86drm.c reads the contents of the file "/sys/dev/char/x:y/device/uevent" into the buffer. The string written to the buffer by read() is not

[PATCH 29/34] drm: Compute tight evictions for drm_mm_scan

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > Compute the minimal required hole during scan and only evict those nodes > that overlap. This enables us to reduce the number of nodes we need to > evict to the bare minimum. > > Signed-off-by: Chris Wilson Definitely for the better.

[Intel-gfx] [PATCH] drm: Fix for invalid pruning of modes in dual display cases

On Tue, Dec 13, 2016 at 04:52:01PM +0200, Jani Nikula wrote: > On Tue, 13 Dec 2016, Chris Wilson wrote: > > On Tue, Dec 13, 2016 at 03:46:54PM +0530, Vidya Srinivas wrote: > >> Currently in dual display connected boot scenarios, minimum of the > >> resolutions > >> is taken for fb width and

[RFC] Using DC in amdgpu for upcoming GPU

(hit send too early) > We would love to upstream DC for all supported asic! We made enough change > to make Sea Island work but it's really not validate to the extend we > validate Polaris on linux and no where close to what we do for 2017 ASICs. > With DC the display hardware programming,

[PATCH 27/34] drm: Unconditionally do the range check in drm_mm_scan_add_block()

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > Doing the check is trivial (low cost in comparison to overall eviction) > and helps simplify the code. > > Signed-off-by: Chris Wilson I now see that the other function gets eliminated, so no biggie. Reviewed-by: Joonas Lahtinen

[PATCH 26/34] drm: Rename prev_node to hole in drm_mm_scan_add_block()

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > Acknowledging that we were building up the hole was more useful to me > when reading the code, than knowing the relationship between this node > and the previous node. > I don't really agree. I see that we have nodes and there are holes

[PATCH 06/34] drm: Add a simple linear congruent generator PRNG

Hey Chris On Tue, Dec 13, 2016 at 4:40 PM, Chris Wilson wrote: > On Tue, Dec 13, 2016 at 04:18:35PM +0100, David Herrmann wrote: >> On Tue, Dec 13, 2016 at 4:16 PM, David Herrmann >> wrote: >> > On Mon, Dec 12, 2016 at 12:53 PM, Chris Wilson > > chris-wilson.co.uk> wrote: >> > for (i = 0; i <

[PATCH 2/2] drm: omapdrm: Perform initialization/cleanup at probe/remove time

The drm driver .load() operation is prone to race conditions as it initializes the driver after registering the device nodes. Its usage is deprecated, inline it in the probe function and call drm_dev_alloc() and drm_dev_register() explicitly. For consistency inline the .unload() handler in the

[PATCH 1/2] drm: omapdrm: Use sizeof(*var) instead of sizeof(type) for structures

By linking the sizeof to a variable type the code will be less prone to bugs due to future type changes of variables. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/displays/panel-dsi-cm.c | 2 +- drivers/gpu/drm/omapdrm/dss/omapdss-boot-init.c | 3 +--

[PATCH 0/2] omapdrm: Remove .load/.unload midlayer

Hello, This small patch series removes the .load and .unload operations from the omapdrm driver and moves the code to the probe/remove handlers. The patches are based on top of my pending omapdrm stack, and have been pushed for convenience to git://linuxtv.org/pinchartl/media.git

[PATCH 25/34] drm: Extract struct drm_mm_scan from struct drm_mm

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > The scan state occupies a large proportion of the struct drm_mm and is > rarely used and only contains temporary state. That makes it suitable to > moving to its struct and onto the stack of the callers. > > Signed-off-by: Chris Wilson >

[RFC PATCH 0/3] staging: remove fbdev drivers

Hi Daniel, On Thursday 08 Dec 2016 11:10:05 Daniel Vetter wrote: > On Thu, Dec 08, 2016 at 12:01:19PM +1100, Benjamin Herrenschmidt wrote: > > On Wed, 2016-11-23 at 10:03 +0200, Tomi Valkeinen wrote: > > > Hi, > > > > > > Since the fbdev framework is in maintenance mode and all new display > > >

[RFC] Using DC in amdgpu for upcoming GPU

> We would love to upstream DC for all supported asic! We made enough change > to make Sea Island work but it's really not validate to the extend we > validate Polaris on linux and no where close to what we do for 2017 ASICs. > With DC the display hardware programming, resource optimization,

[PATCH 24/34] drm: Compile time enabling for asserts in drm_mm

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > Use CONFIG_DRM_DEBUG_MM to conditionally enable the internal and > validation checking using BUG_ON. Ideally these paths should all be > exercised by CI selftests (with the asserts enabled). > > Signed-off-by: Chris Wilson Reviewed-by:

[PATCH 04/34] drm: Add some kselftests for the DRM range manager (struct drm_mm)

On ti, 2016-12-13 at 10:21 +, Chris Wilson wrote: > On Tue, Dec 13, 2016 at 11:58:54AM +0200, Joonas Lahtinen wrote: > > > > This could be build time, depending on the intended use. > > I was thinking module param for the seed, just in case we want different > patterns. As discussed in IRC,

[PATCH v2] drm/mxsfb: use bus_format to determine LCD bus width

The LCD bus width does not need to align with the pixel format. The LCDIF controller automatically converts between pixel formats and bus width by padding or dropping LSBs. The DRM subsystem has the notion of bus_format which allows to determine what bus_formats are supported by the display.

[RFC] Using DC in amdgpu for upcoming GPU

On Tue, Dec 13, 2016 at 10:03:58AM -0500, Cheng, Tony wrote: > On 12/13/2016 4:40 AM, Lukas Wunner wrote: > > If the Linux community contributes to DC, I guess those contributions > > can generally be assumed to be GPLv2 licensed. Yet a future version > > of the macOS driver would incorporate

[Intel-gfx] [PATCH] drm: Fix for invalid pruning of modes in dual display cases

On Tue, 13 Dec 2016, Chris Wilson wrote: > On Tue, Dec 13, 2016 at 03:46:54PM +0530, Vidya Srinivas wrote: >> Currently in dual display connected boot scenarios, minimum of the >> resolutions >> is taken for fb width and height as reference. Based on this resolution, >> other >> modes are

[PATCH v7 3/4] drm/i915: Find fallback link rate/lane count

On Fri, 09 Dec 2016, Jani Nikula wrote: > On Fri, 09 Dec 2016, Manasi Navare wrote: >> If link training fails, then we need to fallback to lower >> link rate first and if link training fails at RBR, then >> fallback to lower lane count. >> This function finds the next lower link rate/lane count

[PATCH 1/2] drm: exynos: Perform initialization/cleanup at probe/remove time

On Tue, Dec 13, 2016 at 4:30 PM, Laurent Pinchart wrote: > On Tuesday 13 Dec 2016 22:10:58 Daniel Vetter wrote: >> On Tue, Dec 13, 2016 at 09:34:05PM +0200, Laurent Pinchart wrote: >> > From: Laurent Pinchart >> > >> > The drm driver .load() operation is prone to race conditions as it >> >

[RFC] Using DC in amdgpu for upcoming GPU

On 10/12/16 01:32 AM, Jan Ziak wrote: > Hello Dave > > Let's cool down the discussion a bit and try to work out a solution. > > To summarize the facts, your decision implies that the probability of > merging DAL/DC into the mainline Linux kernel the next year (2017) has > become extremely low. >

[PATCH 2/4] drm/i915: Compute sink's max lane count/link BW at Hotplug

On Thu, 08 Dec 2016, Manasi Navare wrote: > Daniel, can we merge this patch? Pushed this one to dinq, thanks for the patch. BR, Jani. > It has no dependency on other link train patches, > it is just a clean up for the existing driver code that > uses max link rate and lane count values. >

[RFC PATCH 0/3] staging: remove fbdev drivers

On 10/12/16 05:27 AM, Benjamin Herrenschmidt wrote: > On Fri, 2016-12-09 at 14:35 +0100, Daniel Vetter wrote: >>> As for multi userspace client, well, swapping an mmap between HW and >>> memory backing store is a somewhat solved problem already. >> >> Hm, I didn't know that, but then all existing

[PATCH 06/34] drm: Add a simple linear congruent generator PRNG

On Tue, Dec 13, 2016 at 4:16 PM, David Herrmann wrote: > On Mon, Dec 12, 2016 at 12:53 PM, Chris Wilson > wrote: > for (i = 0; i < count; ++i) > swap(order[i], order[drm_lcg_random(state) % count]); > > Much simpler and I cannot see why it wouldn't work. Hint: swap() does multiple

[PATCH libdrm] autogen.sh: set format.subjectPrefix and sendemail.to if needed

On Tue, 13 Dec 2016, Emil Velikov wrote: > Just set the rules automatically rather than asking each contributor to > update thing locally. > > Signed-off-by: Emil Velikov > --- > autogen.sh | 6 ++ > 1 file changed, 6 insertions(+) > > diff --git a/autogen.sh b/autogen.sh > index

[PATCH 06/34] drm: Add a simple linear congruent generator PRNG

Hey Chris On Mon, Dec 12, 2016 at 12:53 PM, Chris Wilson wrote: > For testing, we want a reproducible PRNG, a plain linear congruent > generator is suitable for our very limited selftests. > > Signed-off-by: Chris Wilson > --- > drivers/gpu/drm/Kconfig| 5 + >

[RFC] Using DC in amdgpu for upcoming GPU

___ dri-devel mailing list dri-devel at lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161213/c8d4357c/attachment.html>

Issue with DRM and "reimplement IDR and IDA using the radix tree"

t IDR and IDA using the radix tree" on 20161213's next fixes the issue for me, suggesting a bug may have slipped in there. Not sure how this could be fixed, so reporting the issue for now in case it is not known yet. Cheers, Alex.

[PATCH 4/4] s5p-cec: add hdmi-notifier support, move out of staging

From: Hans Verkuil By using the HDMI notifier framework there is no longer any reason to manually set the physical address. This was the one blocking issue that prevented this driver from going out of staging, so do this move as well. Update the bindings documenting the

[PATCH 3/4] cec: integrate HDMI notifier support

From: Hans Verkuil Support the HDMI notifier framework, simplifying drivers that depend on this. Signed-off-by: Hans Verkuil --- drivers/media/cec/cec-core.c | 50 include/media/cec.h | 15 + 2 files

[PATCH 2/4] exynos_hdmi: add HDMI notifier support

From: Hans Verkuil Implement the HDMI notifier support to allow CEC drivers to be informed when there is a new EDID and when a connect or disconnect happens. Signed-off-by: Hans Verkuil --- drivers/gpu/drm/exynos/Kconfig | 1 +

[PATCH 1/4] video: add HDMI state notifier support

From: Hans Verkuil Add support for HDMI hotplug and EDID notifiers, which is used to convey information from HDMI drivers to their CEC and audio counterparts. Based on an earlier version from Russell King: https://patchwork.kernel.org/patch/9277043/ The hdmi_notifier

[PATCH 0/4] video/exynos/cec: add HDMI state notifier & use in s5p-cec

From: Hans Verkuil This patch series adds the HDMI notifier code, based on Russell's code: https://patchwork.kernel.org/patch/9277043/ It adds support for it to the exynos_hdmi drm driver, adds support for it to the CEC framework and finally adds support to the s5p-cec

[PATCH] drm: tilcdc: simplify the recovery from sync lost error on rev1

Revision 2 of LCDC suffers from an issue where a SYNC_LOST error caused by limited memory bandwidth may leave the picture shifted a couple pixels to the right. This issue has not been observed on revision 1, while the recovery mechanism introduces a different issue, where the END_OF_FRAME

[PATCH 2/2] drm: Remove unused drm_platform midlayer

On Tue, Dec 13, 2016 at 4:03 PM, Daniel Vetter wrote: > On Tue, Dec 13, 2016 at 09:34:06PM +0200, Laurent Pinchart wrote: >> Now that the last driver has been converted, the drm_platform midlayer >> is unused. Remove it. >> >> Signed-off-by: Laurent Pinchart >

[PATCH 1/2] drm: exynos: Perform initialization/cleanup at probe/remove time

On Tue, Dec 13, 2016 at 2:34 PM, Laurent Pinchart wrote: > From: Laurent Pinchart > > The drm driver .load() operation is prone to race conditions as it > initializes the driver after registering the device nodes. Its usage is > deprecated, inline it

[PATCH] drm/mxsfb: fix pixel clock polarity

On 2016-12-08 15:38, Marek Vasut wrote: > On 12/08/2016 09:46 PM, Stefan Agner wrote: >> On 2016-12-07 18:37, Marek Vasut wrote: >>> On 12/08/2016 02:26 AM, Stefan Agner wrote: On 2016-12-07 16:59, Stefan Agner wrote: > On 2016-12-07 16:49, Marek Vasut wrote: >> On 12/08/2016 01:27

[PATCH libdrm] autogen.sh: set format.subjectPrefix and sendemail.to if needed

On 13 December 2016 at 15:42, Eric Engestrom wrote: > On Tuesday, 2016-12-13 16:16:50 +0200, Jani Nikula wrote: >> On Tue, 13 Dec 2016, Emil Velikov wrote: >> > Just set the rules automatically rather than asking each contributor to >> > update thing locally. >> > >> > Signed-off-by: Emil

[PATCH] drm/mxsfb: use bus_format to determine LCD bus width

On 2016-12-08 20:24, Marek Vasut wrote: > On 12/09/2016 04:44 AM, Stefan Agner wrote: >> On 2016-12-08 15:33, Marek Vasut wrote: >>> On 12/08/2016 11:52 PM, Stefan Agner wrote: The LCD bus width does not need to align with the pixel format. The LCDIF controller automatically converts

[PATCH 2/2] ASoC: hdmi-codec: add channel mapping control

On 12/13/2016 02:58 PM, Takashi Sakamoto wrote: > On 2016年12月13日 22:23, Takashi Sakamoto wrote: >> Hi Arnaud, This table is invariant in lifetime of the storage object, as well. Let's put into .rodata section, too. >>> This table is updated in

[PATCH] drm: Fix for invalid pruning of modes in dual display cases

Currently in dual display connected boot scenarios, minimum of the resolutions is taken for fb width and height as reference. Based on this resolution, other modes are pruned. Example Scenario: If DSI mode is 2560x1440 and HDMI is 1920x1080, during the probing the fb width and height is set to

[PATCH libdrm] autogen.sh: set format.subjectPrefix and sendemail.to if needed

On Tuesday, 2016-12-13 16:16:50 +0200, Jani Nikula wrote: > On Tue, 13 Dec 2016, Emil Velikov wrote: > > Just set the rules automatically rather than asking each contributor to > > update thing locally. > > > > Signed-off-by: Emil Velikov > > --- > > autogen.sh | 6 ++ > > 1 file changed, 6

[PATCH 06/34] drm: Add a simple linear congruent generator PRNG

On Tue, Dec 13, 2016 at 04:18:35PM +0100, David Herrmann wrote: > On Tue, Dec 13, 2016 at 4:16 PM, David Herrmann > wrote: > > On Mon, Dec 12, 2016 at 12:53 PM, Chris Wilson > chris-wilson.co.uk> wrote: > > for (i = 0; i < count; ++i) > > swap(order[i], order[drm_lcg_random(state) %

[PATCH] drm/fsl: don't use drm_put_dev

On 2016-12-13 13:26, Daniel Vetter wrote: > On Tue, Dec 13, 2016 at 06:57:59PM +0100, Lucas Stach wrote: >> Am Dienstag, den 13.12.2016, 18:54 +0100 schrieb Daniel Vetter: >> > fsl is already fully demidlayered in the probe function, but for >> > convenience stuck with drm_put_dev. Call the

[PATCH 06/34] drm: Add a simple linear congruent generator PRNG

On Tue, Dec 13, 2016 at 04:16:41PM +0100, David Herrmann wrote: > Hey Chris > > On Mon, Dec 12, 2016 at 12:53 PM, Chris Wilson > wrote: > > For testing, we want a reproducible PRNG, a plain linear congruent > > generator is suitable for our very limited selftests. > > > > Signed-off-by: Chris

[patch] drm: mxsfb: drm_dev_alloc() returns error pointers

We should be checking for IS_ERR() instead of NULL because drm_dev_alloc() returns error pointers. Fixes: 45d59d704080 ("drm: Add new driver for MXSFB controller") Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm/mxsfb/mxsfb_drv.c b/drivers/gpu/drm/mxsfb/mxsfb_drv.c index

[PATCH 1/4] drm: Protect master->unique with dev->master_mutex

On 13 December 2016 at 09:46, Daniel Vetter wrote: > On Tue, Dec 13, 2016 at 10:42 AM, Michel Dänzer > wrote: >>> Hm, I thought the grand plan is to use -modesetting almost everywhere and >>> forget about all the others? >> >> Maybe if you mean s/grand plan/pipe dream/ ... > > I said "almost

[git pull] drm tree for 4.10

Hi Linus, This is the main drm pull request for the 4.10. Posting it early as I'm probably on holidays for next few days. Items of note: There is a big chunk of AMD register headers in here that bumps the size quite a bit. Renaming the dma-buf fence to dma_fence which is a more apt naming.

[Intel-gfx] [PATCH 2/6] drm/atomic: Unconditionally call prepare_fb.

Op 09-12-16 om 09:25 schreef Daniel Vetter: > On Fri, Dec 09, 2016 at 12:42:19AM +0200, Laurent Pinchart wrote: >> Hi Daniel, >> >> On Thursday 08 Dec 2016 16:41:04 Daniel Vetter wrote: >>> On Thu, Dec 08, 2016 at 02:45:25PM +0100, Maarten Lankhorst wrote: Atomic drivers may set properties

[PATCH v3 10/20] drm: omapdrm: Only commit planes on active CRTCs

Hi Tomi, On Tuesday 13 Dec 2016 09:58:34 Tomi Valkeinen wrote: > On 13/12/16 00:53, Laurent Pinchart wrote: > > On Tuesday 20 Sep 2016 16:51:11 Tomi Valkeinen wrote: > >> On 19/09/16 15:27, Laurent Pinchart wrote: > >>> The DRM core supports skipping plane update for inactive CRTCs for > >>>

[RFC] Using DC in amdgpu for upcoming GPU

all changes and "rewrite" our own version of clean up patch community want to see? Thanks, Lukas -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161213/9cb9eae2/attachment.html>

  1   2   >