From: Thierry Reding
The IOVA API uses a memory cache to allocate IOVA nodes from. To make
sure that this cache is available, obtain a reference to it and release
the reference when the cache is no longer needed.
On 64-bit ARM this is hidden by the fact that the DMA mapping API gets
that referen
From: Thierry Reding
The original code works fine, this is merely a cosmetic change to make
the teardown order the reverse of the setup order.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/drm.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/d
> This table is seriously deprecated, because it's unreadable and
> unmaintainable. Quoting from the docs:
> "Because this table is very unwieldy, do not add any new properties here.
> Instead document them in a section above."
> We haven't yet moved all the existing properties over to the new l
On 4/20/2018 7:52 PM, Ville Syrjälä wrote:
On Fri, Apr 20, 2018 at 07:01:49PM +0530, Nautiyal, Ankit K wrote:
From: Ankit Nautiyal
We parse the EDID and add all the modes in the connector's modelist.
This adds CEA modes with aspect ratio information too, regardless of
whether user space requ
On 4/20/2018 7:42 PM, Ville Syrjälä wrote:
On Fri, Apr 20, 2018 at 07:01:47PM +0530, Nautiyal, Ankit K wrote:
From: Ankit Nautiyal
This patch adds helper functions for determining if aspect-ratio is
expected in user-mode and for allowing/disallowing the aspect-ratio,
if its not expected.
Si
On 4/20/2018 7:37 PM, Ville Syrjälä wrote:
On Fri, Apr 20, 2018 at 07:01:46PM +0530, Nautiyal, Ankit K wrote:
From: Ankit Nautiyal
To enable aspect-ratio support in DRM, blindly exposing the aspect
ratio information along with mode, can break things in existing
user-spaces which have no inte
On 20 April 2018 at 17:22, Gerd Hoffmann wrote:
> On Tue, Apr 03, 2018 at 11:59:04AM +0200, Gerd Hoffmann wrote:
>> Wait until we have enough space in the virt queue to actually queue up
>> our request. Avoids the guest spinning in case we have a non-zero
>> amount of free entries but not enough
On 20 April 2018 at 17:22, Gerd Hoffmann wrote:
>> Gerd Hoffmann (2):
>> qxl: fix qxl_release_{map,unmap}
>> qxl: keep separate release_bo pointer
>
> Ping airlied, can you please either pick it up or review so I can commit
> myself?
Sorry, been on holidays,
Both of these are
Reviewed-by: Da
Andrzej/Archit,
Any comments?
On Thu, Mar 15, 2018 at 3:04 PM, Fabio Estevam wrote:
> From: Fabio Estevam
>
> platform_driver does not need to set the owner field, as this will
> be populated by the driver core.
>
> Generated by scripts/coccinelle/api/platform_no_drv_owner.cocci.
>
> Signed-off
2018년 04월 20일 21:44에 Andrzej Hajda 이(가) 쓴 글:
> On 12.03.2018 08:12, Andrzej Hajda wrote:
>> On 20.02.2018 07:45, Andrzej Hajda wrote:
>>> Hi Inki,
>>>
>>> On 02.02.2018 16:11, Andrzej Hajda wrote:
Hi Inki, Tobias,
This is reviewed/updated/tested Tobias's patch addressing page-fault
Hi Linus,
Just back at work today, I've pulled all the rc2 fixes pulls that were
outstanding, and pushed them out. If I missed rc2, no worries they
should all be fine for rc3.
i915 has an oops fix, and two race fixes, along with some gvt fixes
amdgpu has a dark screen fix, clk/voltage fix and veg
Implement CRC computation configuration and reporting through the DRM
debugfs-based CRC API. The CRC source can be configured to any input
plane or the pipeline output.
Signed-off-by: Laurent Pinchart
---
Changes since v1:
- Format the source names using plane IDs instead of plane indices
---
d
The structure is used in the API that the VSP1 driver exposes to the DU
driver. Documenting it is thus important.
Signed-off-by: Laurent Pinchart
---
Changes since v1:
- Fixed typo
---
include/media/vsp1.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/include/media/vsp1.h b/in
The DISCOM calculates a CRC on a configurable window of the frame. It
interfaces to the VSP through the UIF glue, hence the name used in the
code.
The module supports configuration of the CRC window through the crop
rectangle on the ink pad of the corresponding entity. However, unlike
the traditio
The implementation of the set_fmt pad operation is identical in the
three modules. Move it to a generic helper function.
Signed-off-by: Laurent Pinchart
---
drivers/media/platform/vsp1/vsp1_clu.c| 65 +--
drivers/media/platform/vsp1/vsp1_entity.c | 75
To make vsp1_subdev_set_pad_format() usable by entities that support
selection rectangles, we need to reset the crop and compose rectangles
when setting the format on the sink pad. Do so and replace the custom
set_fmt implementation of the histogram code by a call to
vsp1_subdev_set_pad_format().
The DISCOM is used to compute CRCs on display frames. Integrate it in
the display pipeline at the output of the blending unit to process
output frames.
Computing CRCs on input frames is possible by positioning the DISCOM at
a different point in the pipeline. This use case isn't supported at the
mo
Add a parameter (in the form of a structure to ease future API
extensions) to the VSP atomic flush handler to pass CRC source
configuration, and pass the CRC value to the completion callback.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/rcar-du/rcar_du_vsp.c | 6 --
drivers/media/pl
Adopt the SPDX license identifier headers to ease license compliance
management. All files in the driver are licensed under the GPLv2+ except
for the vsp1_regs.h file which is licensed under the GPLv2. This is
likely an oversight, but fixing this requires contacting the copyright
owners and is out
Hello,
This patch series adds support for CRC calculation to the rcar-du-drm driver.
CRC calculation is supported starting at the Renesas R-Car Gen3 SoCs, as
earlier versions don't have the necessary hardware. On Gen3 SoCs, the CRC is
computed by the DISCOM module part of the VSP-D and VSP-DL.
T
A NV34 GPU was seeing temp and pwm entries in hwmon, which would error
out when read. These should not have been visible, but also the whole
hwmon object should just not have been registered in the first place.
Signed-off-by: Ilia Mirkin
---
drivers/gpu/drm/nouveau/nouveau_hwmon.c | 16 +
Hi Stefan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v4.17-rc1]
[also build test ERROR on next-20180420]
[cannot apply to anholt/for-next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://githu
https://bugs.freedesktop.org/show_bug.cgi?id=106177
Bug ID: 106177
Summary: overclocking doesn't work with 4.17-rc1
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: a0c072e23e6f2543a12009d312387356c870f14f
commit: ace1073bfa90b6ccc9c2d9959c3603008d656b3d [226/251] drm/amdgpu: add save
restore list cntl gpm and srm firmware support
reproduce:
# apt-get install sparse
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #28 from Justin Mitzel ---
I'm not sure what the status of this bug is, but it's only gotten worse with
kernel 4.16 and the amd-staging-drm-next branch.
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #13 from Joshua Lee ---
To be clear, the Furmark was being run in his host system, not within a VM.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #12 from Joshua Lee ---
Someone on the /r/VFIO discord with a Ryzen APU (he usually boots his VM from
the console, rather than having a graphical host) confirmed the crashiness by
running Furmark, which crashed his GPU driver in ten
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #1 from tempel.jul...@gmail.com ---
Created attachment 138988
--> https://bugs.freedesktop.org/attachment.cgi?id=138988&action=edit
xorg log
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=106175
Bug ID: 106175
Summary: amdgpu.dc=1 shows performance issues with Xorg
compositors when moving windows
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #42 from Stratos Zolotas ---
I can confirm that I'm getting the backtraces on Opensuse Tumbleweed with
4.16.2 kernel installed. They appear fewer times now but every time I have a
flickering on my monitors (using a 3 monitor setup).
30 matches
Mail list logo
