drm-tip/drm-tip boot: 129 boots: 4 failed, 125 passed
(v4.11-rc6-1875-ga2de738b139a)
Full Boot Summary:
https://kernelci.org/boot/all/job/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1875-ga2de738b139a/
Full Build Summary:
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #8 from at...@t-online.de ---
I have no idea how to start the game in valgrind because I have to start the
game through steam. For gdb I used the --pid option to take over the process of
the game after starting it through steam but
Hi Bjorn,
first of all sorry for the delay, had been busy with other stuff in the
last few weeks.
Am 24.03.2017 um 22:34 schrieb Bjorn Helgaas:
+ release_child_resources(res);
Doesn't this recursively release *all* child resources? There could
be BARs from several
On Tue, Apr 11, 2017 at 3:31 AM, Pekka Paalanen wrote:
> On Mon, 10 Apr 2017 12:10:14 -0400
> Ilia Mirkin wrote:
>
>> On Mon, Apr 10, 2017 at 11:09 AM, Pekka Paalanen wrote:
>
>> > I also wonder if a real BE machine could have
On Tue, Apr 11, 2017 at 04:58:51PM +0300, Jani Nikula wrote:
> On Tue, 11 Apr 2017, Luc Verhaegen wrote:
> > On Tue, Apr 11, 2017 at 03:36:32PM +0200, Daniel Vetter wrote:
> >> On Tue, Apr 11, 2017 at 3:30 PM, Luc Verhaegen wrote:
> >> > On Tue, Apr 11, 2017 at
On Tue, Apr 11, 2017 at 03:36:32PM +0200, Daniel Vetter wrote:
> On Tue, Apr 11, 2017 at 3:30 PM, Luc Verhaegen wrote:
> > On Tue, Apr 11, 2017 at 03:24:04PM +0200, Daniel Vetter wrote:
> >> On Tue, Apr 11, 2017 at 3:12 PM, Luc Verhaegen wrote:
> >> > On Tue, Apr
On Tue, Apr 11, 2017 at 08:48:15AM +0200, Daniel Vetter wrote:
> freedesktop.org has adopted a formal code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think this
On 04/10/2017 12:32 PM, Jason Ekstrand wrote:
On April 10, 2017 12:29:12 PM Chad Versace
wrote:
On Tue 04 Apr 2017, Keith Packard wrote:
Jason Ekstrand writes:
> Interesting question. To my knowledge, no one has actually
implemented the
>
On Tue, Apr 11, 2017 at 5:14 PM, Luc Verhaegen wrote:
> On Tue, Apr 11, 2017 at 04:58:51PM +0300, Jani Nikula wrote:
>> On Tue, 11 Apr 2017, Luc Verhaegen wrote:
>> > On Tue, Apr 11, 2017 at 03:36:32PM +0200, Daniel Vetter wrote:
>> >> On Tue, Apr 11, 2017 at 3:30
drm-tip/drm-tip build: 207 builds: 1 failed, 206 passed, 45 warnings
(v4.11-rc6-1889-g328f79e8c2dc)
Full Build Summary:
https://kernelci.org/build/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1889-g328f79e8c2dc/
Tree: drm-tip
Branch: drm-tip
Git Describe: v4.11-rc6-1889-g328f79e8c2dc
Git Commit:
On 2017-04-11 02:48 AM, Daniel Vetter wrote:
freedesktop.org has adopted a formal code of conduct:
https://www.fooishbar.org/blog/fdo-contributor-covenant/
https://www.freedesktop.org/wiki/CodeOfConduct/
Besides formalizing things a bit more I don't think this changes
anything for us, we've
On Tue, 11 Apr 2017, Luc Verhaegen wrote:
> On Tue, Apr 11, 2017 at 03:36:32PM +0200, Daniel Vetter wrote:
>> On Tue, Apr 11, 2017 at 3:30 PM, Luc Verhaegen wrote:
>> > On Tue, Apr 11, 2017 at 03:24:04PM +0200, Daniel Vetter wrote:
>> >> On Tue, Apr 11, 2017 at
On 04/10/2017 11:20 PM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 7:52 AM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 6:14 AM, Nikhil Mahale wrote:
My name is Nikhil Mahale, and I work at NVIDIA in the Linux drivers
team.
I have been working on
On Fri, Apr 7, 2017 at 12:33 PM, Thierry Reding wrote:
> On Fri, Apr 07, 2017 at 05:44:15AM +1000, Dave Airlie wrote:
>> On 5 April 2017 at 16:51, Laurent Pinchart
>> wrote:
>> > As the DRM LVDS panel driver uses a different approach
On Tue, Apr 11, 2017 at 11:14 AM, Luc Verhaegen wrote:
> On Tue, Apr 11, 2017 at 04:58:51PM +0300, Jani Nikula wrote:
>> On Tue, 11 Apr 2017, Luc Verhaegen wrote:
>> > On Tue, Apr 11, 2017 at 03:36:32PM +0200, Daniel Vetter wrote:
>> >> On Tue, Apr 11, 2017 at
drm-tip/drm-tip build: 207 builds: 1 failed, 206 passed, 45 warnings
(v4.11-rc6-1898-g1a8653e657e1)
Full Build Summary:
https://kernelci.org/build/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1898-g1a8653e657e1/
Tree: drm-tip
Branch: drm-tip
Git Describe: v4.11-rc6-1898-g1a8653e657e1
Git Commit:
On Sat, Apr 8, 2017 at 3:45 PM, Fabio Estevam wrote:
> Thierry/Rob,
>
> On Tue, Feb 7, 2017 at 10:48 PM, Fabio Estevam wrote:
>> On Tue, Feb 7, 2017 at 9:36 PM, Rob Herring wrote:
>>
>>> Except I have no way of knowing whether: a) you
On 04/11/2017 09:09 AM, Harry Wentland wrote:
On 2017-04-11 11:15 AM, James Jones wrote:
On 04/10/2017 11:20 PM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 7:52 AM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 6:14 AM, Nikhil Mahale
wrote:
My name is
On Tue, Apr 11, 2017 at 2:48 AM, Daniel Vetter wrote:
> freedesktop.org has adopted a formal code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't
On 2017-04-11 11:15 AM, James Jones wrote:
On 04/10/2017 11:20 PM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 7:52 AM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 6:14 AM, Nikhil Mahale
wrote:
My name is Nikhil Mahale, and I work at NVIDIA in the
Daniel Vetter writes:
> freedesktop.org has adopted a formal code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think this changes
> anything for
drm-tip/drm-tip boot: 135 boots: 5 failed, 129 passed with 1 offline
(v4.11-rc6-1880-g52e53d64fa4a)
Full Boot Summary:
https://kernelci.org/boot/all/job/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1880-g52e53d64fa4a/
Full Build Summary:
On Tue, Apr 11, 2017 at 12:09 PM, Daniel Vetter wrote:
> On Tue, Apr 11, 2017 at 5:50 PM, Alex Deucher wrote:
>> On Tue, Apr 11, 2017 at 2:48 AM, Daniel Vetter
>> wrote:
>>> freedesktop.org has adopted a formal code of
On Tue, Apr 11, 2017 at 1:11 PM, Alastair Bridgewater
wrote:
> Enable stereoscopic output for HDMI and DisplayPort connectors on
> NV50+ (G80+) hardware. We do not enable stereoscopy on older
> hardware in case there is some older board that still has HDMI
>
Linus Walleij writes:
> On Tue, Apr 11, 2017 at 3:18 AM, Eric Anholt wrote:
>
>> From: Tom Cooksey
>
> Well that can be debated at this point. I think it should have
> your Author: tag and just Tom in the Signed-off-by, then
On Tue, Apr 11, 2017 at 5:50 PM, Alex Deucher wrote:
> On Tue, Apr 11, 2017 at 2:48 AM, Daniel Vetter wrote:
>> freedesktop.org has adopted a formal code of conduct:
>>
>> https://www.fooishbar.org/blog/fdo-contributor-covenant/
>>
On 04/10/2017 11:47 PM, Laurent Pinchart wrote:
> Hi Laura,
>
> Thank you for the patch.
>
> On Monday 03 Apr 2017 11:57:55 Laura Abbott wrote:
>> When CMA was first introduced, its primary use was for DMA allocation
>> and the only way to get CMA memory was to call dma_alloc_coherent. This
>>
On Mon, Apr 10, 2017 at 2:27 PM, Dave Airlie wrote:
> On 10 April 2017 at 19:03, Laurent Pinchart
> wrote:
>> Hi Thierry,
>>
>> On Monday 10 Apr 2017 09:17:59 Thierry Reding wrote:
>>> On Sun, Apr 09, 2017 at 01:31:40PM +0100, Emil Velikov
GPU cores with the DYNAMIC_FREQUENCY_SCALING feature bit set expect the
platform to provide the clock scaling and ignore any requests to use the
internal FSCALE divider. Writes to this register still work, but don't
have any effect on the GPU clock frequency.
Save the initial core and shader
The HDMI driver is currently enabling all clks and probe time and keep
the power-domain connected to the HDMI encoder enabled.
Move all activation code to vc4_hdmi_encoder_enable() and make sure
the clks and power domain are released when the HDMI encoder is not used
by adding deactivation steps
drm-tip/drm-tip boot: 128 boots: 5 failed, 121 passed with 2 offline
(v4.11-rc6-1886-g20c20ad1f78a)
Full Boot Summary:
https://kernelci.org/boot/all/job/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1886-g20c20ad1f78a/
Full Build Summary:
Am 24.03.2017 um 16:47 schrieb Bjorn Helgaas:
On Mon, Mar 13, 2017 at 01:41:35PM +0100, Christian König wrote:
From: Christian König
Most BIOS don't enable this because of compatibility reasons.
Can you give any more details here? Without more hints, it's hard to
Russell King - ARM Linux writes:
> On Mon, Apr 10, 2017 at 06:18:01PM -0700, Eric Anholt wrote:
>> v5: Move register definitions inside the driver directory, fix build
>> in COMPILE_TEST and !AMBA mode.
>
> Why is it necessary to move the register definitions there,
2017-04-11 Daniel Vetter :
> freedesktop.org has adopted a formal code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think this changes
>
On Mon, Apr 10, 2017 at 01:06:46PM -0700, Eric Anholt wrote:
> Gustavo Padovan writes:
>
> > From: Gustavo Padovan
> >
> > Add support to async updates of cursors by using the new atomic
> > interface for that. Basically what this commit does
Yannick Fertre writes:
> This controller provides output signals to interface directly a variety
> of LCD and TFT panels. These output signals are: RGB signals
> (up to 24bpp), vertical & horizontal synchronisations, data enable and
> the pixel clock.
>
> Signed-off-by:
On Tue, Apr 11, 2017 at 01:45:01PM -0700, Eric Anholt wrote:
> Yannick Fertre writes:
> > +static void ltdc_crtc_disable(struct drm_crtc *crtc)
> > +{
> > + struct ltdc_device *ldev = crtc_to_ltdc(crtc);
> > + struct drm_pending_vblank_event *event = crtc->state->event;
Russell King - ARM Linux writes:
> On Tue, Apr 11, 2017 at 09:06:31AM -0700, Eric Anholt wrote:
>> Russell King - ARM Linux writes:
>>
>> > On Mon, Apr 10, 2017 at 06:18:01PM -0700, Eric Anholt wrote:
>> >> v5: Move register definitions inside the
https://bugzilla.kernel.org/show_bug.cgi?id=195295
--- Comment #3 from Eugene Shalygin (eugene.shaly...@gmail.com) ---
Tried 4.10.6, which was free of this bug at the time I used it, but now it show
the same behaviour. Here is a part from dmesg:
[ 21.074717] usb 3-1: new high-speed USB device
On Wed, Apr 12, 2017 at 04:57:54AM +0800, Jeffy Chen wrote:
> My previous patch (c5d8fac2bf drm: Unplug drm device when unregistering
> it) calls drm_unplug_dev when unregistering drm dev. But if open_count
> is 0, the unplug will try to unregister the drm dev again and cause
> deadlock.
>
> Fix
drm-tip/drm-tip boot: 122 boots: 4 failed, 117 passed with 1 offline
(v4.11-rc6-1898-g1a8653e657e1)
Full Boot Summary:
https://kernelci.org/boot/all/job/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1898-g1a8653e657e1/
Full Build Summary:
Hi Dave,
I have a lonely pull request for you. Just the patch you asked me to pick up
this morning.
drm-misc-fixes-2017-04-11:
Core changes:
- None
Driver changes
- udl: Fix unaligned memory access on SPARC (Jonathan)
Cheers, Sean
The following changes since commit
On Mon, Apr 10, 2017 at 12:55:33PM -0700, Eric Anholt wrote:
> Gustavo Padovan writes:
>
> > From: Gustavo Padovan
> >
> > In some cases, like cursor updates, it is interesting to update the
> > plane in an asynchronous fashion to avoid big
drm-tip/drm-tip boot: 120 boots: 3 failed, 117 passed
(v4.11-rc6-1889-g328f79e8c2dc)
Full Boot Summary:
https://kernelci.org/boot/all/job/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1889-g328f79e8c2dc/
Full Build Summary:
Chris Wilson writes:
> On Mon, Apr 10, 2017 at 06:44:14PM -0700, Eric Anholt wrote:
>> This is needed for proper synchronization with display on another DRM
>> device (pl111 or tinydrm) with buffers produced by vc4 V3D. Fixes the
>> new igt vc4_dmabuf_poll testcase,
On 2017-04-11 12:37 PM, James Jones wrote:
On 04/11/2017 09:09 AM, Harry Wentland wrote:
On 2017-04-11 11:15 AM, James Jones wrote:
On 04/10/2017 11:20 PM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 7:52 AM, Daniel Vetter wrote:
On Tue, Apr 11, 2017 at 6:14 AM, Nikhil
https://bugs.freedesktop.org/show_bug.cgi?id=98996
--- Comment #2 from Christoph Haag ---
Created attachment 130804
--> https://bugs.freedesktop.org/attachment.cgi?id=130804=edit
performance with amd-staging-4.9 and mesa git
Screenshot with out of the box performance on
drm-tip/drm-tip build: 207 builds: 1 failed, 206 passed, 45 warnings
(v4.11-rc6-1901-gf27f076a9b50)
Full Build Summary:
https://kernelci.org/build/drm-tip/branch/drm-tip/kernel/v4.11-rc6-1901-gf27f076a9b50/
Tree: drm-tip
Branch: drm-tip
Git Describe: v4.11-rc6-1901-gf27f076a9b50
Git Commit:
On 11 April 2017 at 22:42, Chris Wilson wrote:
> On Tue, Apr 11, 2017 at 01:22:20PM +1000, Dave Airlie wrote:
>> +static int amdgpu_sem_lookup_and_sync(struct amdgpu_cs_parser *p,
>> + uint32_t handle)
>> +{
>> + int r;
>> +
On 12 April 2017 at 12:49, Mao, David wrote:
> But how to handle the semaphore wait in the vkQueuePresentkHR?
The problem here is that really we'd want the presenting process to
do the signal once it submits the work for actual presentations (be
that the X server DDX or
https://bugs.freedesktop.org/show_bug.cgi?id=93341
--- Comment #26 from Jean-François Fortin Tam ---
OK, I've got good news... Julien, thanks to the crazy furry donut "torture
test" you suggested, I was able to finally pinpoint the real trigger for this
bug.
My understanding
On 12 April 2017 at 12:36, Mao, David wrote:
> Does it means we have to submit command to trigger the semaphore wait/signal?
Yes, but I think that should be fine, we need to submit a job to the
scheduler to
get the waits to happen or to have a fence to fill into the signals.
Hi Lucas,
[auto build test ERROR on drm/drm-next]
[also build test ERROR on next-20170411]
[cannot apply to v4.11-rc6]
[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/linux/commits/Lucas-Stach/drm-etnaviv
On Wed, Apr 12, 2017 at 09:37:02AM +1000, Dave Airlie wrote:
> From: Dave Airlie
>
> sync_file uses the reference count of the file, the internal
> kref was never getting moved past 1.
>
> We can reintroduce this if we decide we need it later.
>
> Signed-off-by: Dave Airlie
Few parts of kernel define their own macro for aligning down so provide
a common define for this, with the same usage and assumptions as existing
ALIGN.
Convert also three existing implementations to this one.
Signed-off-by: Krzysztof Kozlowski
---
The metag change was not
Replace existing hw_ranndom/exynos-rng driver with a new, reworked one.
This is a driver for pseudo random number generator block which on
Exynos4 chipsets must be seeded with some value. On newer Exynos5420
chipsets it might seed itself from true random number generator block
but this is not
thanks for the work, but could you please split that patch?
It looks like you are doing several things at once and it isn't really
easy to review like this. And it isn't bisectable.
If there are clean ups here, please do it in a seperate patch. I
highly doubt that it all has to be done within one
Now that we have the InfoFrame data being provided, for the most
part, program the hardware to use it.
While we're here, and since the functionality will come in handy
for supporting 3D stereoscopy, implement setting the Vendor
("generic") InfoFrame.
Also don't enable any AVI or Vendor InfoFrame
Hi,
This is a follow up of my questions around exynos-rng [1].
Changes since v4:
=
1. Patch 2/2: Use "stdrng" name, as suggested by Herbert.
2. Patch 2/2: Add Bartlomiej's reviewed-by.
Changes since v3:
=
1. New patch: 1/2 for ALIGN_DOWN macro. The change in
Now that we have mechanism by which to pass mode-dependent HDMI
InfoFrames to the low-level hardware driver, it is incumbent upon
us to do so.
Signed-off-by: Alastair Bridgewater
---
drivers/gpu/drm/nouveau/nv50_display.c | 30 +-
1
Now that we have the InfoFrame data being provided, for the most
part, program the hardware to use it.
While we're here, and since the functionality will come in handy
for supporting 3D stereoscopy, implement setting the Vendor
("generic"?) InfoFrame.
Also don't enable any AVI or Vendor
commit e7e11f995642 ("drm/vmwgfx: fix integer overflow in
vmw_surface_define_ioctl()")
ensures that each req->mip_levels[i] <= DRM_VMW_MAX_MIP_LEVELS, It would be
easy to
conclude that the sum of req->mip_levels[i] (i = 0, ...,
DRM_VMW_MAX_SURFACE_FACES - 1)
is less than or equal to
Hello Tobias,
2017년 04월 11일 19:52에 Tobias Jakobi 이(가) 쓴 글:
> Hello Inki,
>
> please don't forget to review this series.
Thanks for your contribution, and don't worry about that. Will review this
series.
Just sharing a plan for -next,
I plan to have pull-request after reviewing a patch set[1]
On 11 April 2017 at 17:50, Chris Wilson wrote:
> On Tue, Apr 11, 2017 at 01:22:17PM +1000, Dave Airlie wrote:
>> From: Dave Airlie
>>
>> This object can be used to implement the Vulkan semaphores.
>>
>> The object behaviour differs from fence, in
From: Dave Airlie
sync_file uses the reference count of the file, the internal
kref was never getting moved past 1.
We can reintroduce this if we decide we need it later.
Signed-off-by: Dave Airlie
---
drivers/dma-buf/sync_file.c | 13 ++---
But how to handle the semaphore wait in the vkQueuePresentkHR?
Thanks.
Best Regards,
David
-Original Message-
From: Dave Airlie [mailto:airl...@gmail.com]
Sent: Wednesday, April 12, 2017 10:44 AM
To: Mao, David
Cc: amd-...@lists.freedesktop.org;
https://bugzilla.kernel.org/show_bug.cgi?id=195295
--- Comment #4 from Michel Dänzer (mic...@daenzer.net) ---
It could be Mesa, there was an intermittent regression there which caused it to
unnecessarily power up GPUs.
--
You are receiving this mail because:
You are watching the assignee of the
https://bugs.freedesktop.org/show_bug.cgi?id=98996
--- Comment #3 from Michel Dänzer ---
Might be worth investigating the buffer waits, e.g. 80 ms corresponds to almost
5 display refresh cycles.
--
You are receiving this mail because:
You are the assignee for the
On 12 April 2017 at 13:34, Mao, David wrote:
> My point is it is reasonable to split the semaphore signal/wait with the
> command submission.
> For the signal ioctl, we could just pick the last fence in the same schedule
> context, and we don't need to ask for a explicit
=> we'd really want to pass a semaphore between the X server and client to do
this perfectly.
Do you means that you want X to signal the semaphore that waited by client,
through special version of xsync?
We use pretty complex tricks to build synchronization logic upon the event and
shm fence.
https://bugs.freedesktop.org/show_bug.cgi?id=100618
--- Comment #9 from Michel Dänzer ---
Something like
valgrind %command%
in the game's Properties -> Launch Options should work.
--
You are receiving this mail because:
You are the assignee for the
2017년 04월 11일 17:17에 Tobias Jakobi 이(가) 쓴 글:
> Another thing that I noticed. Why wasn't the v2 that ended up in your
> git ever submitted to the mailing list? Because it should have, in
> particular to spot these obvious errors.
Only comment about this.
This patch cleans up description of
https://bugs.freedesktop.org/show_bug.cgi?id=97861
--- Comment #10 from James Wagner ---
Same purple line on my R9 280X
Debian 9.0 (Testing)
Linux 4.10.6 with amdgpu for SI and CIK enabled (From kernel.org)
X.Org 1.19.2, from Debian.
`xrandr --output HDMI-A-0 --auto
My point is it is reasonable to split the semaphore signal/wait with the
command submission.
For the signal ioctl, we could just pick the last fence in the same schedule
context, and we don't need to ask for a explicit flush or a dummy submission
trick.
The spec guarantee the signal always
After unbinding drm, the user space may still owns the drm dev fd,
and may still be able to call drm ioctl.
We're using an unplugged state to prevent something like that, so
let's reuse it here.
Signed-off-by: Jeffy Chen
Reviewed-by: Sean Paul
Now that we have the InfoFrame data being provided, for the most
part, program the hardware to use it.
While we're here, and since the functionality will come in handy
for supporting 3D stereoscopy, implement setting the Vendor
("generic"?) InfoFrame.
Also don't enable any InfoFrame that is not
drm_mode_set_crtcinfo() does compensation for interlace and
doublescan timing effects already, so do it first and use the
compensated figures instead of the constant "vscan / ilace" terms
that we had before.
And then it turns out that the hardware model for how the timing
parameters are
On Tue, Apr 11, 2017 at 09:30:53AM -0400, Sean Paul wrote:
> On Fri, Apr 07, 2017 at 10:02:29PM +0200, Jonathan Neuschäfer wrote:
> > On SPARC, the udl driver filled my kernel log with these messages:
> >
> > [186668.910612] Kernel unaligned access at TPC[76609c]
> > udl_render_hline+0x13c/0x3a0
From: Wei Yongjun
Add the missing unlock before return from function etnaviv_gpu_submit()
in the error handling case.
Fixes: f3cd1b064f11 ("drm/etnaviv: (re-)protect fence allocation with
GPU mutex")
Signed-off-by: Wei Yongjun
---
On Tue, Apr 11, 2017 at 09:06:31AM -0700, Eric Anholt wrote:
> Russell King - ARM Linux writes:
>
> > On Mon, Apr 10, 2017 at 06:18:01PM -0700, Eric Anholt wrote:
> >> v5: Move register definitions inside the driver directory, fix build
> >> in COMPILE_TEST and !AMBA
My previous patch (c5d8fac2bf drm: Unplug drm device when unregistering
it) calls drm_unplug_dev when unregistering drm dev. But if open_count
is 0, the unplug will try to unregister the drm dev again and cause
deadlock.
Fix it by dropping drm_unplug_dev and use drm_device_set_plug_state
Hi Emil,
Really sorry for late. Forgot this for a long time.
2016년 05월 12일 06:39에 Emil Velikov 이(가) 쓴 글:
> Hi Inki, all,
>
> On 10 May 2016 at 08:18, Inki Dae wrote:
>> This patch changes GPL license to X11/MIT.
>>
> As mentioned by Tobias, the commit messages should
Hi,
this patch replaces the old hwmon_device_register with the new
hwmon_device_register_with_info.
I've tested it on my laptop with a GeForceGT 425M and it doesn't break anything.
--- linux/drivers/gpu/drm/nouveau/nouveau_hwmon.c.orig 2017-04-11
18:27:15.477623009 +0200
+++
HDMI 3D mode support, round three. Rebased to drm-next as it was on
Sunday morning. Overall structure is the same as v2.
Substantially rewrote the first patch (nv50_head_atomic_check_mode())
since a recent change to the calculation of m->v.blankus caused a
merge conflict and problems with
Now that we have the InfoFrame data being provided, for the most
part, program the hardware to use it.
While we're here, and since the functionality will come in handy
for supporting 3D stereoscopy, implement setting the Vendor
("generic"?) InfoFrame.
Also don't enable any InfoFrame that is not
Frame-packing modes add an extra vtotal raster lines to each frame
above and beyond what the basic mode description calls for.
Account for this during scaler configuration (possibly a bit of a
hack), during CRTC configuration (clearly not a hack), and when
checking that a mode is valid for a given
Sent from my iPhone
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On Mon, Apr 10, 2017 at 12:55 PM, Herbert Xu
wrote:
> On Sat, Apr 08, 2017 at 03:32:45PM +0200, Krzysztof Kozlowski wrote:
>>
>> +static struct rng_alg exynos_rng_alg = {
>> + .generate = exynos_rng_generate,
>> + .seed =
On 10.04.2017 23:29, Christophe JAILLET wrote:
If 'devm_reset_control_get' returns an error, then we erroneously return
success because error code is taken from 'host->clk' instead of
'host->rst'.
Fixes: b386c6b73ac6 ("gpu: host1x: Support module reset")
Signed-off-by: Christophe JAILLET
On Mon, Apr 10, 2017 at 06:18:01PM -0700, Eric Anholt wrote:
> v5: Move register definitions inside the driver directory, fix build
> in COMPILE_TEST and !AMBA mode.
Why is it necessary to move the register definitions there, when
they're already available in linux/amba/clcd.h and are
Enable stereoscopic output for HDMI and DisplayPort connectors on
NV50+ (G80+) hardware. We do not enable stereoscopy on older
hardware in case there is some older board that still has HDMI
output but for which we have no logic for setting the Vendor
InfoFrame.
With this, I get an obvious 3D
Hi Sean,
On 04/11/2017 03:26 AM, Sean Paul wrote:
On Mon, Apr 10, 2017 at 06:00:43PM +0800, Jeffy Chen wrote:
Hi Jeffy,
Thanks for sending this up again.
Verified on rk3399 chromebook kevin, no more crashes during unbind/bind drm.
I'm assuming this is on the chromeos-4.4 kernel? If so,
Verified on rk3399 chromebook kevin(with cros 4.4 kernel), no more crashes
during unbind/bind drm.
Changes in v7:
Address Sean Paul 's comments.
Update commit message.
Changes in v6:
Address Daniel Vetter 's comments.
Changes in v5:
Fix wrong git
We are freeing all framebuffers in drm_mode_config_cleanup without
sync the drm_file's fbs list.
So if someone try to unbind drm before release drm dev fd, the fbs
list would remain some invalid fb references. And that would cause
crash later in drm_fb_release.
Add a sanity check to prevent
The nouveau driver, in the Linux 3.7 days, used to try and set the
AVI InfoFrame based on the selected display mode. These days, it
uses a fixed set of InfoFrames. Start to correct that, by
providing a mechanism whereby InfoFrame data may be passed to the
NVKM functions that do the actual
Hi Sean,
On 04/11/2017 04:31 AM, Sean Paul wrote:
On Mon, Apr 10, 2017 at 06:00:45PM +0800, Jeffy Chen wrote:
After unbinding drm, the user space may still owns the drm dev fd,
and may trigger fb release after cleanup mode config.
Add a sanity check to prevent that.
Signed-off-by: Jeffy Chen
While highly unlikely, this makes sure that the string built from
engine names won't be processed as a format string.
Signed-off-by: Kees Cook
---
drivers/gpu/drm/i915/intel_hangcheck.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
HDMI InfoFrames are passed to NVKM as bags of bytes, but the
hardware needs them to be packed into words. Rather than having
four (or more) copies of the packing logic introduce a single copy
now, in a central place.
We currently need these for AVI and Vendor InfoFrames, but we may
also expect
2017년 04월 11일 17:01에 Tobias Jakobi 이(가) 쓴 글:
> Inki Dae wrote:
>>
>>
>> 2017년 04월 10일 19:27에 Tobias Jakobi 이(가) 쓴 글:
>>> Inki Dae wrote:
2017-03-29 20:56 GMT+09:00 Tobias Jakobi :
> Hello Daniel,
>
> same question here. Patch doesn't introduce any
Hi Dave,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.11-rc6 next-20170411]
[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/linux/commits/Dave-Airlie/sync_file-get-rid-of-internal
1 - 100 of 172 matches
Mail list logo