On Sat, 3 Jun 2017 01:53:04 +, "Bridgman, John"
wrote:
> OK, no powerplay messages that time. Was performance back to what you
> expected ?
Yes, performance on 4.10.12 is what i call normal
higuita
--
Naturally the common people don't want war... but after all it is the
leaders of a
Looks ok. I won't get around to testing this until maybe mid next week though.
On Wed, May 24, 2017 at 04:52:10PM +0200, Daniel Vetter wrote:
> Again stopping the vblank before uninstalling the irq handler is kinda
> the wrong way round, but the fb_off stuff should take care of
> disabling the ds
On 06/03/2017 12:24 AM, Daniel Drake wrote:
On Fri, Jun 2, 2017 at 4:01 AM, Chris Chiu wrote:
We are working with new desktop that have the NVIDIA NV118
chipset.
During boot, the display becomes unusable at the point where the
nouveau driver loads. We have reproduced on 4.8, 4.11 and linux
mas
https://bugs.freedesktop.org/show_bug.cgi?id=100101
Jason Ekstrand changed:
What|Removed |Added
QA Contact|dri-devel@lists.freedesktop |intel-3d-bugs@lists.freedes
If src_x/y were nonzero, we failed to shift them down by 16 to get the
pixel offset. The recent CMA helper function gets it right.
Signed-off-by: Eric Anholt
Fixes: bed41005e617 ("drm/pl111: Initial drm/kms driver for pl111")
Reported-by: Mircea Carausu
---
drivers/gpu/drm/pl111/pl111_display.
>-Original Message-
>From: Daniel Mota Leite [mailto:dan...@motaleite.net]
>Sent: Friday, June 02, 2017 9:47 PM
>To: Bridgman, John
>Cc: Alex Deucher; DRI Development
>Subject: Re: Slower 3D with kernel 4.11.x
>
>On Thu, 1 Jun 2017 21:09:03 +, "Bridgman, John"
> wrote:
>> Hmm... more p
On Thu, 1 Jun 2017 21:09:03 +, "Bridgman, John"
wrote:
> Hmm... more powerplay error messages than I am used to seeing, plus a
> bunch of GPUVM faults, plus a stack trace.
>
> My first thought would be to ask if you could go back to the previous
> kernel, boot up and send a dmesg from that t
On 2 June 2017 at 18:48, Tomi Valkeinen wrote:
> Hi Dave,
>
> Here's second attempt for omapdrm changes for v4.13. The first version
> conflicts
> with the latest drm-next due to the DRM_ROTATE flag changes. This one is
> rebased
> on top of the latest drm-next.
As much as I dislike rebases (ho
https://bugs.freedesktop.org/show_bug.cgi?id=99851
erhar...@mailbox.org changed:
What|Removed |Added
Attachment #131537|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #46 from erhar...@mailbox.org ---
Created attachment 131685
--> https://bugs.freedesktop.org/attachment.cgi?id=131685&action=edit
pgtable fix bisect.log
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=99851
erhar...@mailbox.org changed:
What|Removed |Added
Attachment #131536|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #44 from erhar...@mailbox.org ---
Finally I was able to finish the bisect with some help from slyfox from
#gentoo-powerpc. At last...
I made a second bisect in search of the fix for the "Couldn't allocate pmd
pagetable caches" error,
On Thu, Jun 01, 2017 at 10:11:14PM +0800, icen...@aosc.io wrote:
> 在 2017-06-01 02:43，Maxime Ripard 写道：
> > On Wed, May 24, 2017 at 04:25:46PM +0800, Icenowy Zheng wrote:
> > >
> > >
> > > 于 2017年5月24日 GMT+08:00 下午3:30:19, Maxime Ripard
> > > 写到:
> > > >On Tue, May 23, 2017 at 09:00:59PM +0800,
Hans Verkuil writes:
> The bo->resv pointer could be NULL, leading to kernel oopses like the one
> below.
> It looks like .fb_probe -> drm_fbdev_cma_create() -> drm_gem_cma_create()
> would
> end up not initializing resv, because we're doing that in vc4_bo_create(), not
> vc4_create_object().
>
The bo->resv pointer could be NULL, leading to kernel oopses like the one below.
It looks like .fb_probe -> drm_fbdev_cma_create() -> drm_gem_cma_create() would
end up not initializing resv, because we're doing that in vc4_bo_create(), not
vc4_create_object().
This patch ensures that bo->resv is
Hi Dave,
Smallish (by series count) -next pull request here comprised of a few moderately
sized series'. We gained mode_valid() hooks for crtc/encoder/bridge, and now
have
a clearer seperation between irq and vblank. Additionally we cleaned up some
legacy
code by turfing drm_for_each_connector an
Philippe CORNU writes:
> Add the panel-bridge support for both panels & bridges (used by DSI host &
> HDMI/LVDS bridges).
This looks like a great cleanup. Just a couple of things I noticed, and
hopefully once the DT is reviewed we can merge it. I've also
resubmitted the panel-bridge patch so t
https://bugzilla.kernel.org/show_bug.cgi?id=194761
--- Comment #35 from Alex Deucher (alexdeuc...@gmail.com) ---
Created attachment 256845
--> https://bugzilla.kernel.org/attachment.cgi?id=256845&action=edit
another possible fix
This sets mc_arb_ramcfg properly for userspace.
--
You are recei
https://bugzilla.kernel.org/show_bug.cgi?id=194761
--- Comment #34 from Marek Olšák (mar...@gmail.com) ---
BTW, adev->gfx.config.mc_arb_ramcfg is not set for SI. That might cause addrlib
to do something incorrect.
--
You are receiving this mail because:
You are watching the assignee of the bug.
Many DRM drivers have common code to make a stub connector
implementation that wraps a drm_panel. By wrapping the panel in a DRM
bridge, all of the connector code (including calls during encoder
enable/disable) goes away.
v2: Fix build with CONFIG_DRM=m, drop "dev" argument that should just
b
Jose Abreu writes:
> Now that we have a callback to check if crtc and encoder supports a
> given mode we can use it in vc4 so that we restrict the number of
> probbed modes to the ones we can actually display.
"probed"
>
> Also, remove the mode_fixup() calls as these are no longer needed
> beca
On Fri, Jun 02, 2017 at 06:10:24PM +0800, Chen-Yu Tsai wrote:
> The MSI Primo81 tablet has a micro HDMI connector at the bottom.
> This is connected to the SoCs HDMI output.
>
> Enable the display pipeline and the HDMI output.
>
> Signed-off-by: Chen-Yu Tsai
> ---
> arch/arm/boot/dts/sun6i-a31s
On Fri, Jun 02, 2017 at 06:10:19PM +0800, Chen-Yu Tsai wrote:
> The HDMI controller found in the A31 SoCs is slightly different
> from the one already supported, which is found in the A10s:
>
> - Need different initial values for the PLL related registers
>
> - Different behavior of the DDC a
On Fri, Jun 02, 2017 at 06:10:18PM +0800, Chen-Yu Tsai wrote:
> The HDMI controller found in earlier Allwinner SoCs have slight
> differences:
>
> - Need different initial values for the PLL related registers
>
> - Different behavior of the DDC and TMDS clocks
>
> - Different register layo
On Fri, Jun 02, 2017 at 06:10:17PM +0800, Chen-Yu Tsai wrote:
> On the A31, the HDMI DDC block is different from the one in the
> other SoCs. As far as the DDC clock goes, it has no pre-divider,
> as it is clocked from a slower parent clock, not the TMDS clock.
> The divider offset from the registe
On Fri, Jun 02, 2017 at 06:10:15PM +0800, Chen-Yu Tsai wrote:
> The DDC parent clock on the A31 SoC is also conveniently named
> "hdmi-ddc", which results in a name collision when the hdmi driver
> registers its internal DDC divider clock.
>
> Rename the internal clock to "hdmi-ddc-divider".
>
>
On Fri, Jun 02, 2017 at 06:10:07PM +0800, Chen-Yu Tsai wrote:
> The encoder drivers use drm_of_find_possible_crtcs to get upstream
> crtcs from the device tree using of_graph. For the results to be
> correct, encoders must be probed/bound after _all_ crtcs have been
> created. The existing code use
Hi Dave,
Here's this week's fixes pull. Most noteworthy is the drm_unplug_dev change.
We've previously had discussion around cleanup on unplug for rockchip, but that
was mostly an academic issue (they wanted to unbind/bind at runtime). At the
time, this usecase was determined not to warrant the com
From: Jani Nikula
Date: Wed, 31 May 2017 18:50:43 +0300
> From: Chris Wilson
>
> An error during suspend (e100e_pm_suspend),
...
> lead to complete failure:
...
> The unwind failures stems from commit 2800209994f8 ("e1000e: Refactor PM
> flows"), but it may be a later patch that introduced th
https://bugs.freedesktop.org/show_bug.cgi?id=99349
--- Comment #12 from Gert Wollny ---
Created attachment 131683
--> https://bugs.freedesktop.org/attachment.cgi?id=131683&action=edit
Patch proposed on mesa-dev to work around too many temporaries
--
You are receiving this mail because:
You ar
On Fri, Jun 02, 2017 at 01:25:10PM +0200, Corentin Labbe wrote:
> Instead of rewriting write/readq, use linux/io-64-nonatomic-lo-hi.h which
> already have them.
>
> Signed-off-by: Corentin Labbe
Applied to drm-misc-next
Thanks,
Sean
> ---
> include/drm/drm_os_linux.h | 14 +-
> 1
On Thu, Jun 01, 2017 at 01:14:56PM +0100, Chris Wilson wrote:
> On Thu, Jun 01, 2017 at 01:54:30PM +0200, Hans de Goede wrote:
> > commit a39be606f99d ("drm: Do a full device unregister when unplugging")
> > causes backtraces like this one when unplugging an usb drm device while
> > it is in use:
>
https://bugs.freedesktop.org/show_bug.cgi?id=101189
--- Comment #14 from Emil Velikov ---
For anyone wondering why patches have not been merged, yet.
Patch 2/5 neuters the partial Opencl support in r600, in an attempt to untangle
the convoluted dependencies. A few people are unhappy about it (un
On 31 May 2017 at 16:10, Eric Engestrom wrote:
> Adds the C++ extern guards from
> ebbb0e5cfd2ceb1150b1 drm: add extern C guard for the UAPI headers
>
> Generated using `make headers_install` from airlied/drm-next
> at commit 2a1720376adda5ecf8e636fbfb05339c7dad1c55
>
> Signed-off-by: Eric Engestr
https://bugzilla.kernel.org/show_bug.cgi?id=194761
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
Attachment #256727|0 |1
is obsole
Hi Marco,
Disclaimer: I'm mostly lurking around, barring the occasional patch so
please take my input with a grain of salt.
On 1 June 2017 at 23:46, Marco Diego Aurélio Mesquita
wrote:
> Hi Devs!
>
> On Thu, Jun 1, 2017 at 8:59 AM, Hans de Goede wrote:
>> Hi All,
>>
>> This is a resend of a pat
https://bugs.freedesktop.org/show_bug.cgi?id=100979
--- Comment #6 from Daniel ---
The situation over here is maybe related:
Hibernating/suspend-to-disk/s4 on my new AMD Carrizo box fails.
Upon hibernate, the system just reboots. No hints in the logs.
Suspend-to-RAM/S3 works fine.
When I disa
On Fri, Jun 2, 2017 at 3:35 AM, Florian Echtler wrote:
> On 01.06.2017 19:53, Alex Deucher wrote:
>> On Thu, Jun 1, 2017 at 4:27 AM, Florian Echtler wrote:
>>> On 31.05.2017 14:57, Alex Deucher wrote:
On Wed, May 31, 2017 at 5:21 AM, Lukas Wunner wrote:
>>>
>>> Here's the (substantial) dmes
On Fri, Jun 2, 2017 at 4:01 AM, Chris Chiu wrote:
> We are working with new desktop that have the NVIDIA NV118
> chipset.
>
> During boot, the display becomes unusable at the point where the
> nouveau driver loads. We have reproduced on 4.8, 4.11 and linux
> master (4.12-rc3).
To save digging int
https://bugs.freedesktop.org/show_bug.cgi?id=101274
Alexandr changed:
What|Removed |Added
Summary|[DC] Native display |[DC] Native display
|resol
On 06/02/17 14:07, Russell King - ARM Linux wrote:
> On Thu, Jun 01, 2017 at 10:31:10AM +0200, Hans Verkuil wrote:
>> This will change. Patches to fix the config handling are pending for 4.12.
>>
>> Here you can see the pending patches:
>> https://git.linuxtv.org/hverkuil/media_tree.git/log/?h=drm-
https://bugs.freedesktop.org/show_bug.cgi?id=101262
--- Comment #3 from Emil Velikov ---
(In reply to Anthony Jagers from comment #2)
> My guess is I need help in tracing this.
> How would you trace a steam game?
See https://wiki.archlinux.org/index.php/Steam/Troubleshooting#Debugging_Steam
No i
Add a driver for Cadence DPI -> DSI bridge.
Signed-off-by: Boris Brezillon
---
Changes in v2:
- rebase on v4.12-rc1 and adapt to driver to the drm_bridge API changes
- return the correct error when devm_clk_get(sysclk) fails
- add missing depends on OF and select DRM_PANEL in the Kconfig entry
--
Document the bindings used for the Cadence DSI bridge.
Signed-off-by: Boris Brezillon
---
.../bindings/display/bridge/cdns,dsi.txt | 55 ++
1 file changed, 55 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/bridge/cdns,dsi.txt
diff --gi
On Fri, 2 Jun 2017 19:07:28 +0800
kbuild test robot wrote:
> Hi Boris,
>
> [auto build test ERROR on robh/for-next]
> [also build test ERROR on v4.12-rc3 next-20170602]
> [cannot apply to drm/drm-next drm-intel/for-linux-next]
> [if your patch is applied to the wrong git tree
This adds support for the Pervasive Displays RePaper branded displays.
The controller code is taken from the userspace driver available
through repaper.org. Only the V231 film is supported since the others
are EOL.
Signed-off-by: Noralf Trønnes
---
MAINTAINERS |6 +
dri
This adds support for the 1.44", 1.9", 2.0" and 2.7" Pervasive Diplays
monochrome e-ink panels. The code was taken from the userspace driver
available through repaper.org.
Monochrome
Since drm doesn't have support for monochrome, I have added a helper to
convert XRGB to greyscale8. XRGB is
Add device-tree binding documentation for the 1.44", 1.9", 2.0" and 2.7"
display panels.
Signed-off-by: Noralf Trønnes
---
.../devicetree/bindings/display/repaper.txt| 52 ++
1 file changed, 52 insertions(+)
create mode 100644 Documentation/devicetree/bindings/displa
Drm has no monochrome or greyscale support so add a conversion
from the common format XR24.
Also reorder includes into the common order.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/tinydrm/core/tinydrm-helpers.c | 74 +-
include/drm/tinydrm/tinydrm-helpers.h
Pervasive Displays Inc. designs, develops, and manufactures low-power
electrophoretic (e-ink) display modules and supporting electronics for
commercial and industrial display applications.
Signed-off-by: Noralf Trønnes
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file chang
Instead of rewriting write/readq, use linux/io-64-nonatomic-lo-hi.h which
already have them.
Signed-off-by: Corentin Labbe
---
include/drm/drm_os_linux.h | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/include/drm/drm_os_linux.h b/include/drm/drm_os_linux.h
ind
drivers/gpu/drm/bridge/cdns-dsi.c:980:5-11: inconsistent IS_ERR and PTR_ERR on
line 981.
PTR_ERR should access the value just tested by IS_ERR
Semantic patch information:
There can be false positives in the patch case, where it is the call to
IS_ERR that is wrong.
Generated by: scripts/cocci
Hi Boris,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.12-rc3 next-20170602]
[cannot apply to drm/drm-next drm-intel/for-linux-next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
https://bugs.freedesktop.org/show_bug.cgi?id=101278
--- Comment #1 from nagrigoria...@gmail.com ---
Apologies, I forgot some important related details:
I'm on kernel 4.11.1-gentoo right now, but observed the same on 4.10.8
libdrm-2.4.80
llvm-4.0.0-r2
xorg-server-1.19.3
xf86-video-ati-7.9.0
using
https://bugs.freedesktop.org/show_bug.cgi?id=101278
Bug ID: 101278
Summary: Severe slowdown on Shadow of Mordor between 17.1.0 and
17.1.1
Product: Mesa
Version: 17.1
Hardware: x86-64 (AMD64)
OS: Linux (All)
On Thu, 25 May 2017 15:19:21 +0100
Jose Abreu wrote:
> Now that we have a callback to check if crtc supports a given mode
> we can use it in atmel-hlcdc so that we restrict the number of probbed
> modes to the ones we can actually display.
>
> Also, remove the mode_fixup() callback as this is no
Hi Bjorn,
sorry for not responding earlier and thanks for picking this thread up
again.
Am 01.06.2017 um 22:14 schrieb Bjorn Helgaas:
[+cc ADMGPU, DRM folks]
On Tue, May 09, 2017 at 06:49:07PM +0200, Christian König wrote:
[SNIP]
+/**
+ * amdgpu_resize_bar0 - try to resize BAR0
+ *
+ * @ade
On 06/02/17 11:15, Russell King - ARM Linux wrote:
> On Fri, Jun 02, 2017 at 06:02:28AM +0100, Jose Abreu wrote:
>> You should check that CEC is: not in standy, acknowledges
>> broadcast messages, signal free time is 5bit period, and not lost
>> arbitration, which basically means CEC_CTRL must be 0
On Fri, Jun 02, 2017 at 10:34:26AM +0200, Boris Brezillon wrote:
> On Mon, 15 May 2017 18:23:59 +0100
> Liviu Dudau wrote:
>
> > Hi,
> >
> > This series introduces support for Mali DP's memory writeback engine
> > using the generic writeback connector support introduced in the
> > "[PATCH v5 0/2
On 06/02/17 08:43, Jose Abreu wrote:
> Hi Hans,
>
>
> On 02-06-2017 07:31, Hans Verkuil wrote:
>> On 06/01/2017 03:47 PM, Neil Armstrong wrote:
>>> On 05/30/2017 04:23 PM, Russell King wrote:
Add a CEC driver for the dw-hdmi hardware.
Signed-off-by: Russell King
---
dr
Hi Dave,
Here's second attempt for omapdrm changes for v4.13. The first version conflicts
with the latest drm-next due to the DRM_ROTATE flag changes. This one is rebased
on top of the latest drm-next.
Tomi
The following changes since commit 2a1720376adda5ecf8e636fbfb05339c7dad1c55:
Backmer
On Mon, 15 May 2017 18:23:59 +0100
Liviu Dudau wrote:
> Hi,
>
> This series introduces support for Mali DP's memory writeback engine
> using the generic writeback connector support introduced in the
> "[PATCH v5 0/2] drm: Introduce writeback connectors" series [1]
>
> This version updates the M
Hello,
This series adds a driver for the TXP (transposer) block which is
providing writeback support.
Note that adding support for this IP required reworking a bit how the
VC4 driver handles commits (vc4_kms.c). I also had to support a new use
case in vc4_crtc.c because the TXP IP is completely b
The transposer block is allowing one to write the result of the VC4
composition back to memory.
Signed-off-by: Boris Brezillon
---
arch/arm/boot/dts/bcm283x.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/bcm283x.dtsi b/arch/arm/boot/dts/bcm283x.dtsi
index 35cea3
Replace the drm_atomic_helper_wait_for_vblanks() with a call to
drm_atomic_helper_wait_for_flip_done(). This allows better detection of
page flip done events which what we are really waiting for in
vc4_atomic_complete_commit().
With this approach, we also addresse the 'missed single vblank event'
The VC4 KMS driver is implementing its own ->atomic_commit() but there
are a few generic helpers we can use instead of open-coding the logic.
Signed-off-by: Boris Brezillon
---
drivers/gpu/drm/vc4/vc4_kms.c | 38 --
1 file changed, 12 insertions(+), 26 deletio
These are part of the vc4 display pipeline.
Signed-off-by: Boris Brezillon
---
Documentation/devicetree/bindings/display/brcm,bcm-vc4.txt | 12
1 file changed, 12 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/brcm,bcm-vc4.txt
b/Documentation/devicetree/bindi
Add an helper to wait for all page flips of an atomic state to be done.
Signed-off-by: Boris Brezillon
---
drivers/gpu/drm/drm_atomic_helper.c | 30 ++
include/drm/drm_atomic_helper.h | 3 +++
2 files changed, 33 insertions(+)
diff --git a/drivers/gpu/drm/drm_at
The TXP block is providing writeback support. Add a driver to expose this
feature.
Supporting this engine requires reworking the CRTC because it's not using
the usual 'HVS -> PV -> VC4 Encoder' scheme. Instead, the TXP block is
directly connected to HVS FIFO2, and the PV is completely bypassed.
I
There are two problems related to VBLANK handling in the current CRTC
driver:
* VBLANK events are missed when the CRTC is being disabled because the
driver does not wait till the end of the frame before stopping the
HVS and PV blocks. In this case, we should explicitly issue a VBLANK
event i
On 01.06.2017 19:53, Alex Deucher wrote:
> On Thu, Jun 1, 2017 at 4:27 AM, Florian Echtler wrote:
>> On 31.05.2017 14:57, Alex Deucher wrote:
>>> On Wed, May 31, 2017 at 5:21 AM, Lukas Wunner wrote:
>>
>> Here's the (substantial) dmesg output, with drm.debug=0xf:
>> http://floe.butterbrot.org/ext
Hi Hans,
On 02-06-2017 07:31, Hans Verkuil wrote:
> On 06/01/2017 03:47 PM, Neil Armstrong wrote:
>> On 05/30/2017 04:23 PM, Russell King wrote:
>>> Add a CEC driver for the dw-hdmi hardware.
>>>
>>> Signed-off-by: Russell King
>>> ---
>>> drivers/gpu/drm/bridge/synopsys/Kconfig | 8 +
On 01-06-2017 23:30, Russell King - ARM Linux wrote:
> On Thu, Jun 01, 2017 at 01:53:21AM +0100, Jose Abreu wrote:
>> Hi Russell,
>>
>>
>> On 30-05-2017 15:23, Russell King wrote:
>>> +static int dw_hdmi_cec_transmit(struct cec_adapter *adap, u8 attempts,
>>> + u32 signa
Add a driver for Cadence DPI -> DSI bridge.
Signed-off-by: Boris Brezillon
---
drivers/gpu/drm/bridge/Kconfig|7 +
drivers/gpu/drm/bridge/Makefile |1 +
drivers/gpu/drm/bridge/cdns-dsi.c | 1087 +
3 files changed, 1095 insertions(+)
create mode
Document the bindings used for the Cadence DSI bridge.
Signed-off-by: Boris Brezillon
---
.../bindings/display/bridge/cdns,dsi.txt | 55 ++
1 file changed, 55 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/bridge/cdns,dsi.txt
diff --gi
A simpler variant of cec_transmit_done to be used where the HW does
just a single attempt at a transmit. So if the status indicates an
error, then the corresponding error count will always be 1 and this
function figures that out based on the status argument.
Signed-off-by: Hans Verkuil
---
Russe
On Mon, 15 May 2017 10:16:15 -0700
Eric Anholt wrote:
> Failing to do so meant that we got a resume() callback on first use of
> the device, so we would leak the bin BO that we allocated during
> probe.
>
> Signed-off-by: Eric Anholt
> Fixes: 553c942f8b2c ("drm/vc4: Allow using more than 256MB
77 matches
Mail list logo
