Re: [PATCH 3/6] drm: fourcc byteorder: add bigendian support to drm_mode_legacy_fb_format

On Di, 2017-04-25 at 12:18 +0900, Michel Dänzer wrote: > On 24/04/17 03:25 PM, Gerd Hoffmann wrote: > > Return correct fourcc codes on bigendian. Drivers must be adapted to > > this change. > > > > Signed-off-by: Gerd Hoffmann > > Just to reiterate, this won't work for the

[PATCH 5/5] amdgpu: use drm sync objects for shared semaphores (v4)

From: Dave Airlie This creates a new command submission chunk for amdgpu to add in and out sync objects around the submission. Sync objects are managed via the drm syncobj ioctls. The command submission interface is enhanced with two new chunks, one for syncobj pre

[PATCH 1/5] drm: introduce sync objects

From: Dave Airlie Sync objects are new toplevel drm object, that contain a pointer to a fence. This fence can be updated via command submission ioctls via drivers. There is also a generic wait obj API modelled on the vulkan wait API (with code modelled on some amdgpu code).

[PATCH 2/5] drm/syncobj: add sync obj wait interface.

From: Dave Airlie This interface will allow sync object to be used to back Vulkan fences. This API is pretty much the vulkan fence waiting API, and I've ported the code from amdgpu. Signed-off-by: Dave Airlie --- drivers/gpu/drm/drm_internal.h | 2 +

[rfc] drm sync objects (search for spock)

Okay I've gone around the sun with these a few times, and pretty much implemented what I said last week. This is pretty much a complete revamp. 1. sync objects are self contained drm objects, they have a file reference so can be passed between processes. 2. Added a sync object wait interface

[PATCH 4/5] amdgpu/cs: split out fence dependency checking

From: Dave Airlie This just splits out the fence depenency checking into it's own function to make it easier to add semaphore dependencies. Reviewed-by: Christian König Signed-off-by: Dave Airlie ---

[PATCH 3/5] drm/syncobj: add sync_file interaction.

From: Dave Airlie This interface allows importing the fence from a sync_file into an existing drm sync object, or exporting the fence attached to an existing drm sync object into a new sync file object. This should only be used to interact with sync files where necessary.

Re: [PATCH] dma-buf: avoid scheduling on fence status query

CC a few extra lists I missed. Regards, Andres On 2017-04-25 09:36 PM, Andres Rodriguez wrote: When a timeout of zero is specified, the caller is only interested in the fence status. In the current implementation, dma_fence_default_wait will always call schedule_timeout() at least once for an

Re: [PATCH] drm: fourcc byteorder: brings header file comments in line with reality.

On 25/04/17 07:26 PM, Ville Syrjälä wrote: > On Tue, Apr 25, 2017 at 10:12:37AM +0900, Michel Dänzer wrote: >> On 24/04/17 10:03 PM, Ville Syrjälä wrote: >>> On Mon, Apr 24, 2017 at 03:57:02PM +0900, Michel Dänzer wrote: On 22/04/17 07:05 PM, Ville Syrjälä wrote: > On Fri, Apr 21, 2017 at

Re: [PATCH 3/6] drm: fourcc byteorder: add bigendian support to drm_mode_legacy_fb_format

On 25/04/17 06:52 PM, Ville Syrjälä wrote: > On Tue, Apr 25, 2017 at 12:18:52PM +0900, Michel Dänzer wrote: >> On 24/04/17 03:25 PM, Gerd Hoffmann wrote: >>> +#ifdef __BIG_ENDIAN >>> + switch (bpp) { >>> + case 8: >>> + fmt = DRM_FORMAT_C8; >>> + break; >>> + case 24: >>>

[PATCH] dma-buf: avoid scheduling on fence status query

When a timeout of zero is specified, the caller is only interested in the fence status. In the current implementation, dma_fence_default_wait will always call schedule_timeout() at least once for an unsignaled fence. This adds a significant overhead to a fence status query. Avoid this overhead

[Bug 195581] NULL pointer dereference when amdgpu driver calls drm_load_edid_firmware

https://bugzilla.kernel.org/show_bug.cgi?id=195581 --- Comment #1 from Michel Dänzer (mic...@daenzer.net) --- Looks like https://bugs.freedesktop.org/show_bug.cgi?id=100375 . Is this a regression from older kernel versions? -- You are receiving this mail because: You are watching the assignee

[Bug 100781] "Black Mesa" will not Launch

https://bugs.freedesktop.org/show_bug.cgi?id=100781 Michel Dänzer changed: What|Removed |Added Resolution|FIXED |NOTOURBUG -- You

[PATCH v2 01/21] scatterlist: Introduce sg_map helper functions

This patch introduces functions which kmap the pages inside an sgl. These functions replace a common pattern of kmap(sg_page(sg)) that is used in more than 50 places within the kernel. The motivation for this work is to eventually safely support sgls that contain io memory. In order for that to

[PATCH v2 13/21] scsi: arcmsr, ips, megaraid: Make use of the new sg_map helper function

Very straightforward conversion of three scsi drivers Signed-off-by: Logan Gunthorpe Cc: Adaptec OEM Raid Solutions Cc: Kashyap Desai Cc: Sumit Saxena Cc: Shivasharan S

GPU hangs and X shot down with 4.11-rc6

Hi, I have just experienced X being shut down once with 4.11-rc2 and 2 times with 4.11-rc6 kernel. I do not remember seeing something like this before but it is quite possible I was just lucky to not trigger this issue before. It always happened while I was working on a presentation in

[PATCH v2 20/21] mmc: tifm_sd: Make use of the new sg_map helper function

This conversion is a bit complicated. We modiy the read_fifo, write_fifo and copy_page functions to take a scatterlist instead of a page. Thus we can use sg_map instead of kmap_atomic. There's a bit of accounting that needed to be done for the offset for this to work. (Seeing sg_map takes care of

[PATCH 0/3] drm/sun4i: More cleanups and fixes

Hi Maxime, The subject is probably getting old. Here are a few more cleanups. Patch 1 should have been part of the patch drm/sun4i: Use lists to track registered display backends and TCONs from my multiple pipeline support series. Please squash it in if you can. Patch 2 just moves setting

[PATCH v2 10/21] RDS: Make use of the new sg_map helper function

Straightforward conversion except there's no error path, so we make use of SG_MAP_MUST_NOT_FAIL which may BUG_ON in certain cases in the future. Signed-off-by: Logan Gunthorpe Cc: Santosh Shilimkar Cc: "David S. Miller"

[PATCH v2 03/21] libiscsi: Make use of new the sg_map helper function

Convert the kmap and kmap_atomic uses to the sg_map function. We now store the flags for the kmap instead of a boolean to indicate atomicitiy. We use ISCSI_TCP_INTERNAL_ERR error type that was prepared earlier for this. Signed-off-by: Logan Gunthorpe Cc: Lee Duncan

[PATCH v2 21/21] memstick: Make use of the new sg_map helper function

Straightforward conversion, but we have to make use of SG_MAP_MUST_NOT_FAIL which may BUG_ON in certain cases in the future. Signed-off-by: Logan Gunthorpe Cc: Alex Dubov --- drivers/memstick/host/jmb38x_ms.c | 11 ++-

[PATCH v2 06/21] crypto: hifn_795x: Make use of the new sg_map helper function

Conversion of a couple kmap_atomic instances to the sg_map helper function. However, it looks like there was a bug in the original code: the source scatter lists offset (t->offset) was passed to ablkcipher_get which added it to the destination address. This doesn't make a lot of sense, but

[PATCH v2 15/21] xen-blkfront: Make use of the new sg_map helper function

Straightforward conversion to the new helper, except due to the lack of error path, we have to use SG_MAP_MUST_NOT_FAIL which may BUG_ON in certain cases in the future. Signed-off-by: Logan Gunthorpe Cc: Boris Ostrovsky Cc: Juergen Gross

[PATCH v2 18/21] mmc: tmio: Make use of the new sg_map helper function

Straightforward conversion to sg_map helper. Seeing there is no cleare error path, SG_MAP_MUST_NOT_FAIL which may BUG_ON in certain cases in the future. Signed-off-by: Logan Gunthorpe Cc: Wolfram Sang Cc: Ulf Hansson

[PATCH v2 09/21] staging: unisys: visorbus: Make use of the new sg_map helper function

Straightforward conversion to the new function. Signed-off-by: Logan Gunthorpe Acked-by: David Kershner --- drivers/staging/unisys/visorhba/visorhba_main.c | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git

[PATCH v2 12/21] scsi: hisi_sas, mvsas, gdth: Make use of the new sg_map helper function

Very straightforward conversion of three scsi drivers. Signed-off-by: Logan Gunthorpe Cc: Achim Leubner Cc: John Garry --- drivers/scsi/gdth.c| 9 +++-- drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 14

[PATCH -next] drm/nouveau/secboot/gm20b: fix the error return code in gm20b_secboot_tegra_read_wpr()

From: Wei Yongjun The error return code PTR_ERR(mc) is always 0 since mc is equal to 0 in this error handling case. Signed-off-by: Wei Yongjun --- drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gm20b.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH v2 02/21] libiscsi: Add an internal error code

This is a prep patch to add a new error code to libiscsi. We want to rework some kmap calls to be able to fail. When we do, we'd like to use this error code. This patch simply introduces ISCSI_TCP_INTERNAL_ERR and prints "Internal Error." when it gets hit. Signed-off-by: Logan Gunthorpe

[PATCH 3/3] drm/sun4i: backend: Clarify sun4i_backend_layer_enable debug message

sun4i_backend_layer_enable can be called to enable or disable a layer. However the debug message always says "Enable", which is confusing. This patch makes the debug message vary according to the enable state. Signed-off-by: Chen-Yu Tsai --- drivers/gpu/drm/sun4i/sun4i_backend.c

[PATCH 2/3] drm/sun4i: Set TCON clock inside sun4i_tconX_mode_set

Currently we are configuring the TCON's dot clock or special clock directly from the encoder mode_set functions. Since we already provide mode_set helper functions for the TCON's 2 channels, we can set the respective clock from those helpers, and reduce the exposure of the TCON's internals.

Re: [PATCH] drm/nouveau: Add support for clockgating on Fermi+

Hi Lyude, thanks for the great work. Just a view comments inline. 2017-04-25 20:38 GMT+02:00 Lyude : > This adds support for enabling automatic clockgating on nvidia GPUs for > Fermi and later generations. This saves a little bit of power, bringing > my fermi GPU's power

[PATCH v2 14/21] scsi: libfc, csiostor: Change to sg_copy_buffer in two drivers

These two drivers appear to duplicate the functionality of sg_copy_buffer. So we clean them up to use the common code. This helps us remove a couple of instances that would otherwise be slightly tricky sg_map usages. Signed-off-by: Logan Gunthorpe Cc: Johannes Thumshirn

[PATCH v2 08/21] dm-crypt: Make use of the new sg_map helper in 4 call sites

Very straightforward conversion to the new function in all four spots. Signed-off-by: Logan Gunthorpe Cc: Alasdair Kergon Cc: Mike Snitzer --- drivers/md/dm-crypt.c | 39 ++- 1 file changed, 26

[PATCH v2 16/21] mmc: sdhci: Make use of the new sg_map helper function

Straightforward conversion, except due to the lack of an error path we have to use SG_MAP_MUST_NOT_FAIL which may BUG_ON in certain cases in the future. Signed-off-by: Logan Gunthorpe Cc: Adrian Hunter Cc: Ulf Hansson ---

[PATCH] drm/panel: Add driver for Seiko 43WVF1G panel

Add driver for Seiko Instruments Inc. 4.3" WVGA (800 x RGB x 480) TFT with Touch-Panel. Datasheet available at: http://www.glyn.de/data/glyn/media/doc/43wvf1g-0.pdf Seiko 43WVF1G panel has two power supplies: AVDD and DVDD and they require a specific power on/down sequence. For this reason the

[PATCH v2 11/21] scsi: ipr, pmcraid, isci: Make use of the new sg_map helper

Very straightforward conversion of three scsi drivers. Signed-off-by: Logan Gunthorpe Cc: Brian King Cc: Artur Paszkiewicz --- drivers/scsi/ipr.c | 27 ++- drivers/scsi/isci/request.c | 42

[PATCH v2 07/21] crypto: shash, caam: Make use of the new sg_map helper function

Very straightforward conversion to the new function in the caam driver and shash library. Signed-off-by: Logan Gunthorpe Cc: Herbert Xu Cc: "David S. Miller" --- crypto/shash.c| 9 ++---

[PATCH v2 19/21] mmc: sdricoh_cs: Make use of the new sg_map helper function

This is a straightforward conversion to the new function. Signed-off-by: Logan Gunthorpe Cc: Sascha Sommer Cc: Ulf Hansson --- drivers/mmc/host/sdricoh_cs.c | 14 +- 1 file changed, 9 insertions(+), 5

[PATCH v2 04/21] target: Make use of the new sg_map function at 16 call sites

Fairly straightforward conversions in all spots. In a couple of cases any error gets propogated up should sg_map fail. In other cases a warning is issued if the kmap fails seeing there's no clear error path. This should not be an issue until someone tries to use unmappable memory in the sgl with

[PATCH v2 05/21] drm/i915: Make use of the new sg_map helper function

This is a single straightforward conversion from kmap to sg_map. We also create the i915_gem_object_unmap function to common up the unmap code. Signed-off-by: Logan Gunthorpe Acked-by: Daniel Vetter --- drivers/gpu/drm/i915/i915_gem.c | 27

[PATCH v2 17/21] mmc: spi: Make use of the new sg_map helper function

We use the sg_map helper but it's slightly more complicated as we only check for the error when the mapping actually gets used. Such that if the mapping failed but wasn't needed then no error occurs. Signed-off-by: Logan Gunthorpe Cc: Ulf Hansson ---

[PATCH 1/3] drm/sun4i: Drop unused tcon pointer

The sun4i DRM driver now uses 2 lists to track backends and tcons. During the switch, the original tcon pointer was not removed. As it is now unused, remove it, so other new drivers can't accidentally use it. Signed-off-by: Chen-Yu Tsai --- As mentioned in the cover letter,

[PATCH v2 00/21] Introduce common scatterlist map function

Changes since v1: * Rebased onto next-20170424 * Removed the _offset version of these functions per Christoph's suggestion * Added an SG_MAP_MUST_NOT_FAIL flag which will BUG_ON in future cases that can't gracefully fail. This removes a bunch of the noise added in v1 to a couple of the

[Bug 100785] [regression, bisected] arb_gpu_shader5 piglit fail

https://bugs.freedesktop.org/show_bug.cgi?id=100785 --- Comment #2 from Timothy Arceri --- Does it work if you set: R600_DEBUG=nosb Also it would be helpful if you could attach a before and after shader dump using. R600_DEBUG=vs,ps -- You are receiving this mail

Re: [PATCH libdrm 2/2] Add the DPI encoder/connector types to KMS utils.

Daniel Stone writes: > Hi Eric, > > On 25 April 2017 at 20:33, Eric Anholt wrote: >> Signed-off-by: Eric Anholt > > Both are: > Reviewed-by: Daniel Stone Pushed. Thanks! signature.asc Description: PGP signature

Re: [RFC 0/4] Exynos DRM: add Picture Processor extension

Hi Marek, On Thu, Apr 20, 2017 at 01:23:09PM +0200, Marek Szyprowski wrote: > Hi Laurent, > > On 2017-04-20 12:25, Laurent Pinchart wrote: > >Hi Marek, > > > >(CC'ing Sakari Ailus) > > > >Thank you for the patches. > > > >On Thursday 20 Apr 2017 11:13:36 Marek Szyprowski wrote: > >>Dear all, >

[Bug 100400] Game Valhalla Hills crash on startup

https://bugs.freedesktop.org/show_bug.cgi?id=100400 --- Comment #10 from CraZy bisCuiT --- This problem affects me as well on mesa 17.04 and llvm 4.0.0-1 with AMD RX 480. Any ideas what causes this problem? We can't expect a patch from the developer since the

Re: [PATCH libdrm 2/2] Add the DPI encoder/connector types to KMS utils.

Hi Eric, On 25 April 2017 at 20:33, Eric Anholt wrote: > Signed-off-by: Eric Anholt Both are: Reviewed-by: Daniel Stone Cheers, Daniel ___ dri-devel mailing list

[Bug 100695] Texture artifacts in Deus Ex: Mankind Divided

https://bugs.freedesktop.org/show_bug.cgi?id=100695 Hadrien changed: What|Removed |Added Status|NEW |RESOLVED

Re: [Intel-gfx] GPU hangs and X shot down with 4.11-rc6

On Tue, Apr 25, 2017 at 06:41:20PM +0200, Michal Hocko wrote: > Hi, > I have just experienced X being shut down once with 4.11-rc2 and 2 times > with 4.11-rc6 kernel. I do not remember seeing something like this > before but it is quite possible I was just lucky to not trigger this > issue

[Bug 195577] Oops

https://bugzilla.kernel.org/show_bug.cgi?id=195577 Lutz Vieweg (l...@5t9.de) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 195581] New: NULL pointer dereference when amdgpu driver calls drm_load_edid_firmware

https://bugzilla.kernel.org/show_bug.cgi?id=195581 Bug ID: 195581 Summary: NULL pointer dereference when amdgpu driver calls drm_load_edid_firmware Product: Drivers Version: 2.5 Kernel Version: 4.10.11-1-ARCH Hardware:

[PATCH] drm: mali-dp: use div_u64 for expensive 64-bit divisions

On 32-bit machines, we can't divide 64-bit integers: drivers/gpu/drm/arm/malidp_crtc.o: In function `malidp_crtc_atomic_check': malidp_crtc.c:(.text.malidp_crtc_atomic_check+0x3c0): undefined reference to `__aeabi_uldivmod' malidp_crtc.c:(.text.malidp_crtc_atomic_check+0x3dc): undefined

[Bug 195577] New: Oops

https://bugzilla.kernel.org/show_bug.cgi?id=195577 Bug ID: 195577 Summary: Oops Product: Drivers Version: 2.5 Kernel Version: 4.10.11-1-ARCH Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW

[PATCH] drm/nouveau: Add support for clockgating on Fermi+

This adds support for enabling automatic clockgating on nvidia GPUs for Fermi and later generations. This saves a little bit of power, bringing my fermi GPU's power consumption from ~28.3W on idle to ~27W, and my kepler's idle power consumption from ~23.6W to ~21.65W. Similar to how the nvidia

[PATCH libdrm 2/2] Add the DPI encoder/connector types to KMS utils.

Signed-off-by: Eric Anholt --- tests/util/kms.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tests/util/kms.c b/tests/util/kms.c index c008f78a32e7..028cc8d956df 100644 --- a/tests/util/kms.c +++ b/tests/util/kms.c @@ -79,6 +79,7 @@ static const struct type_name

[PATCH libdrm 1/2] Add pl111 as a KMS driver for utils.

Signed-off-by: Eric Anholt --- tests/util/kms.c | 1 + 1 file changed, 1 insertion(+) diff --git a/tests/util/kms.c b/tests/util/kms.c index 959b688158bd..c008f78a32e7 100644 --- a/tests/util/kms.c +++ b/tests/util/kms.c @@ -145,6 +145,7 @@ static const char * const modules[] =

Re: [PATCH 11/28] drm/qxl: fix include notation and remove -Iinclude/drm flag

Masahiro Yamada writes: > Include instead of relative path from include/drm, then > remove the -Iinclude/drm compiler flag. > > Signed-off-by: Masahiro Yamada Please add Reviewed-by: Gabriel Krisman Bertazi

Re: [PATCH 4/4] drm/amdgpu: resize VRAM BAR for CPU access v2

On Tue, Apr 25, 2017 at 12:22 PM, Christian König wrote: > Am 25.04.2017 um 17:14 schrieb Alex Deucher: >> >> On Tue, Apr 25, 2017 at 11:09 AM, Christian König >> wrote: >>> >>> Am 25.04.2017 um 16:34 schrieb Alex Deucher: On Tue, Apr

Re: [PATCH 4/4] drm/amdgpu: resize VRAM BAR for CPU access v2

Am 25.04.2017 um 17:14 schrieb Alex Deucher: On Tue, Apr 25, 2017 at 11:09 AM, Christian König wrote: Am 25.04.2017 um 16:34 schrieb Alex Deucher: On Tue, Apr 25, 2017 at 9:19 AM, Christian König wrote: From: Christian König

Re: [PATCH v5 02/11] drm/core: Allow attaching custom scaling mode properties

On Tue, Apr 25, 2017 at 01:55:26PM +0200, Maarten Lankhorst wrote: > Some connectors may not allow all scaling mode properties, this function will > allow > creating the scaling mode property with only the supported subset. > > This will make it possible to convert i915 connectors to atomic. >

[Bug 100781] "Black Mesa" will not Launch

https://bugs.freedesktop.org/show_bug.cgi?id=100781 katof...@protonmail.com changed: What|Removed |Added Resolution|NOTOURBUG |FIXED --- Comment #4 from

Re: [PATCH 4/4] drm/amdgpu: resize VRAM BAR for CPU access v2

On Tue, Apr 25, 2017 at 11:09 AM, Christian König wrote: > Am 25.04.2017 um 16:34 schrieb Alex Deucher: >> >> On Tue, Apr 25, 2017 at 9:19 AM, Christian König >> wrote: >>> >>> From: Christian König >>> >>> Try to

Re: [PATCH v5 02/11] drm/core: Allow attaching custom scaling mode properties

On Tue, Apr 25, 2017 at 01:55:26PM +0200, Maarten Lankhorst wrote: > Some connectors may not allow all scaling mode properties, this function will > allow > creating the scaling mode property with only the supported subset. > > This will make it possible to convert i915 connectors to atomic. >

Re: [PATCH 4/4] drm/amdgpu: resize VRAM BAR for CPU access v2

Am 25.04.2017 um 16:34 schrieb Alex Deucher: On Tue, Apr 25, 2017 at 9:19 AM, Christian König wrote: From: Christian König Try to resize BAR0 to let CPU access all of VRAM. v2: rebased, style cleanups, disable mem decode before resize,

Re: [PATCH 1/4] PCI: add resizeable BAR infrastructure v4

On Tue, Apr 25, 2017 at 9:19 AM, Christian König wrote: > From: Christian König > > Just the defines and helper functions to read the possible sizes of a BAR and > update it's size. > > See >

Re: [PATCH 3/4] x86/PCI: Enable a 64bit BAR on AMD Family 15h (Models 30h-3fh) Processors v2

On Tue, Apr 25, 2017 at 9:19 AM, Christian König wrote: > From: Christian König > > Most BIOS don't enable this because of compatibility reasons. > > Manually enable a 64bit BAR of 64GB size so that we have > enough room for PCI devices. > > v2:

Re: [PATCH 4/4] drm/amdgpu: resize VRAM BAR for CPU access v2

On Tue, Apr 25, 2017 at 9:19 AM, Christian König wrote: > From: Christian König > > Try to resize BAR0 to let CPU access all of VRAM. > > v2: rebased, style cleanups, disable mem decode before resize, > handle gmc_v9 as well, round size up

Re: Resizeable PCI BAR support V4

On Tue, Apr 25, 2017 at 4:19 PM, Christian König wrote: > Hi everyone, > > This is the fourth incarnation of this set of patches. It would be nice if you put (next time) version of the series in each patch. Usually it's done quite easy by passing -vX (where X is version

Resizeable PCI BAR support V4

Hi everyone, This is the fourth incarnation of this set of patches. It enables device drivers to resize and most likely also relocate the PCI BAR of devices they manage to allow the CPU to access all of the device local memory at once. This is very useful for GFX device drivers where the

[PATCH 3/4] x86/PCI: Enable a 64bit BAR on AMD Family 15h (Models 30h-3fh) Processors v2

From: Christian König Most BIOS don't enable this because of compatibility reasons. Manually enable a 64bit BAR of 64GB size so that we have enough room for PCI devices. v2: style cleanups, increase size, add resource name, set correct flags, print message that

[PATCH 1/4] PCI: add resizeable BAR infrastructure v4

From: Christian König Just the defines and helper functions to read the possible sizes of a BAR and update it's size. See https://pcisig.com/sites/default/files/specification_documents/ECN_Resizable-BAR_24Apr2008.pdf and PCIe r3.1, sec 7.22. This is useful for

[PATCH 4/4] drm/amdgpu: resize VRAM BAR for CPU access v2

From: Christian König Try to resize BAR0 to let CPU access all of VRAM. v2: rebased, style cleanups, disable mem decode before resize, handle gmc_v9 as well, round size up to power of two. Signed-off-by: Christian König ---

[PATCH 2/4] PCI: add functionality for resizing resources v3

From: Christian König This allows device drivers to request resizing their BARs. The function only tries to reprogram the windows of the bridge directly above the requesting device and only the BAR of the same type (usually mem, 64bit, prefetchable). This is done to

Re: [PATCH 3/4] x86/PCI: Enable a 64bit BAR on AMD Family 15h (Models 30h-3fh) Processors

Am 12.04.2017 um 18:55 schrieb Bjorn Helgaas: [SNIP] I think the specs would envision this being done via an ACPI _SRS method on the PNP0A03 host bridge device. That would be a more generic path that would work on any host bridge. Did you explore that possibility? I would prefer to avoid

[Bug 100784] Fullscreen fade transitions in starsector run at a few frames per second

https://bugs.freedesktop.org/show_bug.cgi?id=100784 --- Comment #1 from Jon --- API trace https://www.dropbox.com/s/i8do4s47w77uaow/java.trace?dl=0 -- You are receiving this mail because: You are the assignee for the bug.___

[PATCH v5 02/11] drm/core: Allow attaching custom scaling mode properties

Some connectors may not allow all scaling mode properties, this function will allow creating the scaling mode property with only the supported subset. This will make it possible to convert i915 connectors to atomic. Signed-off-by: Maarten Lankhorst Cc:

[PATCH v5 01/11] drm/atomic: Handle aspect ratio and scaling mode in core, v3.

This is required to for i915 to convert connector properties to atomic. Changes since v1: - Add docbook info. (danvet) - Change picture_aspect_ratio to enum hdmi_picture_aspect. Changes since v2: - For i915 put the properties in connector_state, to prevent regressions where the property doesn't

[Bug 100785] [regression, bisected] arb_gpu_shader5 piglit fail

https://bugs.freedesktop.org/show_bug.cgi?id=100785 --- Comment #1 from Hi-Angel --- Ah, a fail output: $ LD_LIBRARY_PATH=/home/constantine/Projects/mesa/lib LIBGL_DRIVERS_PATH=/home/constantine/Projects/mesa/lib/gallium

[Bug 100785] [regression, bisected] arb_gpu_shader5 piglit fail

https://bugs.freedesktop.org/show_bug.cgi?id=100785 Bug ID: 100785 Summary: [regression, bisected] arb_gpu_shader5 piglit fail Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity:

[Bug 100784] Fullscreen fade transitions in starsector run at a few frames per second

https://bugs.freedesktop.org/show_bug.cgi?id=100784 Bug ID: 100784 Summary: Fullscreen fade transitions in starsector run at a few frames per second Product: Mesa Version: 17.0 Hardware: x86-64 (AMD64) OS:

Re: [PATCH] drm: fourcc byteorder: brings header file comments in line with reality.

On Tue, Apr 25, 2017 at 10:12:37AM +0900, Michel Dänzer wrote: > On 24/04/17 10:03 PM, Ville Syrjälä wrote: > > On Mon, Apr 24, 2017 at 03:57:02PM +0900, Michel Dänzer wrote: > >> On 22/04/17 07:05 PM, Ville Syrjälä wrote: > >>> On Fri, Apr 21, 2017 at 06:14:31PM +0200, Gerd Hoffmann wrote: >

Re: [PATCH 3/6] drm: fourcc byteorder: add bigendian support to drm_mode_legacy_fb_format

On Tue, Apr 25, 2017 at 12:18:52PM +0900, Michel Dänzer wrote: > On 24/04/17 03:25 PM, Gerd Hoffmann wrote: > > Return correct fourcc codes on bigendian. Drivers must be adapted to > > this change. > > > > Signed-off-by: Gerd Hoffmann > > Just to reiterate, this won't work

Re: [PATCH 0/6] drm: tackle byteorder issues, take two

On Tue, Apr 25, 2017 at 09:49:38AM +0900, Michel Dänzer wrote: > On 24/04/17 11:26 PM, Ville Syrjälä wrote: > > On Mon, Apr 24, 2017 at 04:54:25PM +0900, Michel Dänzer wrote: > >> On 24/04/17 04:36 PM, Gerd Hoffmann wrote: > >>> > > drm: fourcc byteorder: add DRM_FORMAT_CPU_* > > drm:

Re: [PATCH v2 07/10] drm: omapdrm: Fix incorrect usage of the term 'cache coherency'

On 24/04/17 17:25, Laurent Pinchart wrote: > Hi Tomi, > > On Monday 24 Apr 2017 13:44:23 Tomi Valkeinen wrote: >> On 21/04/17 00:33, Laurent Pinchart wrote: >>> The is_cache_coherent() function currently returns true when the mapping >>> is not cache-coherent. This isn't a bug as such as the

[PATCH] drm/i915/gvt: fix typo: "supporte" -> "support"

From: Colin Ian King trivial fix to typo in WARN_ONCE message Signed-off-by: Colin Ian King --- drivers/gpu/drm/i915/gvt/handlers.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/gvt/handlers.c

Re: [PATCH v2 4/5] drm: omapdrm: Store the Z order in the plane state zpos field

On 24/04/17 17:00, Laurent Pinchart wrote: > Hi Tomi, > > On Monday 24 Apr 2017 12:40:10 Tomi Valkeinen wrote: >> On 15/04/17 12:16, Laurent Pinchart wrote: >>> The DRM core implements a standard "zpos" property to control planes >>> ordering. The omapdrm driver implements a similar property

Re: [PATCH v2 5/5] drm: omapdrm: Add zpos property

On 24/04/17 17:05, Laurent Pinchart wrote: > Hi Tomi, > > On Monday 24 Apr 2017 17:00:52 Laurent Pinchart wrote: >> On Monday 24 Apr 2017 12:37:24 Tomi Valkeinen wrote: >>> On 15/04/17 12:16, Laurent Pinchart wrote: Create a standard zpos property for every plane as an alias to the

[Bug 100761] `radeon_ib_ring_tests` takes 0.5 s on resume

https://bugs.freedesktop.org/show_bug.cgi?id=100761 --- Comment #5 from Christian König --- What I've forgot: One thing that could possible help would be an HDP flush directly before we wait for the fence. Just in case the value written for the fence is stuck in the HDP

[Bug 100761] `radeon_ib_ring_tests` takes 0.5 s on resume

https://bugs.freedesktop.org/show_bug.cgi?id=100761 --- Comment #4 from Christian König --- (In reply to Paul Menzel from comment #3) > Interesting. What part is responsible for this? AtomBIOS? No, that is completely unrelated to AtomBIOS. The PLL just needs awfully

Re: [PATCH v7 4/4] drm/dp: Track MST link bandwidth

On 21-04-17 07:51, Dhinakaran Pandiyan wrote: > From: "Pandiyan, Dhinakaran" > > Use the added helpers to track MST link bandwidth for atomic modesets. > Link bw is acquired in the ->atomic_check() phase when CRTCs are being > enabled with

Re: [PATCH v7 1/4] drm: Add driver-private objects to atomic state

On 21-04-17 07:51, Dhinakaran Pandiyan wrote: > From: "Pandiyan, Dhinakaran" > > It is necessary to track states for objects other than connector, crtc > and plane for atomic modesets. But adding objects like DP MST link > bandwidth to drm_atomic_state would mean

Re: [PATCH -next] drm/shmob: fix return value check in shmob_drm_probe()

Hi Wei, Thank you for the patch. On Tuesday 25 Apr 2017 03:08:08 Wei Yongjun wrote: > From: Wei Yongjun > > In case of error, the function devm_ioremap_resource() returns ERR_PTR() > and never returns NULL. The NULL test in the return value check should > be replaced

[Bug 100761] `radeon_ib_ring_tests` takes 0.5 s on resume

https://bugs.freedesktop.org/show_bug.cgi?id=100761 --- Comment #3 from Paul Menzel --- (In reply to Christian König from comment #2) > (In reply to Paul Menzel from comment #0) > > Looking at the generated graph 540 ms is spent in `radeon_ib_ring_tests`, > >

Re: [PATCHv2 2/3] ARM: drm: Intel FPGA VIP Frame Buffer II drm driver

On Tue, 25 Apr 2017, hean.loong@intel.com wrote: > +++ b/drivers/gpu/drm/ivip/Makefile > @@ -0,0 +1,9 @@ > +# > +# Makefile for the drm device driver. This driver provides support for the > +# Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher. > + > +ccflags-y := -Iinclude/drm

Re: [RFC 0/4] Exynos DRM: add Picture Processor extension

Hi Dave, On 2017-04-20 21:02, Dave Airlie wrote: On 20 April 2017 at 19:13, Marek Szyprowski wrote: This is an updated proposal for extending EXYNOS DRM API with generic support for hardware modules, which can be used for processing image data from the one memory

Re: [PATCH 2/2] drm/amd/display: Prevent premature pageflip when comitting in vblank. (v3)

On 25/04/17 01:54 AM, Mario Kleiner wrote: > Make sure we do not program a hw pageflip inside vblank 'n' iff the > atomic flip is comitted while inside the same vblank 'n'. We must > defer such a flip by one refresh cycle to vblank 'n+1', unless this > is a DRM_MODE_PAGE_FLIP_ASYNC async pageflip,