On Sun, 13 Oct 2019, Pavel Machek wrote:
> On Mon 2019-09-30 12:09:07, Kiran Gunda wrote:
> > Restructure the qcom-wled bindings for the better readability.
> >
> > Signed-off-by: Kiran Gunda
> > Reviewed-by: Bjorn Andersson
> > Reviewed-by: Rob Herring
> > Acked-by: Daniel Thompson
> > Acked
On Thu, Oct 10, 2019 at 03:13:33PM +0200, Johan Hovold wrote:
> If a process is interrupted while accessing the crypto device and the
> global ap_perms_mutex is contented, release() could return early and
> fail to free related resources.
>
> Fixes: 00fab2350e6b ("s390/zcrypt: multiple zcrypt devi
Hello,
syzbot found the following crash on:
HEAD commit:8ada228a Add linux-next specific files for 20191011
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1423a87f60
kernel config: https://syzkaller.appspot.com/x/.config?x=7cf4eed5fe42c31a
dashboard
On Thu, Oct 10, 2019 at 7:02 AM Qiang Yu wrote:
>
> By using shared drm helpers:
> 1. drm_gem_(un)lock_reservations
> 2. drm_gem_shmem_helpers
> we can simplify lima driver a lot and benifit from updates to
> these functions.
>
> Patch series is based on drm-misc-next branch
>
> v2:
> Add drm_gem_
On Fri, Oct 11, 2019 at 05:45:45PM +0800, sandy.huang wrote:
> Hi, james, ville syrjala, david,
>
> 在 2019/10/11 下午4:32, james qian wang (Arm Technology China) 写道:
> > On Fri, Oct 11, 2019 at 03:32:17PM +0800, sandy.huang wrote:
> > > 在 2019/10/11 下午3:22, james qian wang (Arm Technology China) 写道:
Hi Laurent Pinchart, please check my comment below.
Thanks,
Xin
On Fri, Oct 11, 2019 at 03:54:18PM +0300, Laurent Pinchart wrote:
> Hi Andrzej,
>
> On Fri, Oct 11, 2019 at 01:21:43PM +0200, Andrzej Hajda wrote:
> > On 11.10.2019 04:21, Xin Ji wrote:
> > > The ANX7625 is an ultra-low power 4K Mob
Hi Andrzej Hajda, please check my comment below.
Thanks,
Xin
On Fri, Oct 11, 2019 at 01:21:43PM +0200, Andrzej Hajda wrote:
> On 11.10.2019 04:21, Xin Ji wrote:
> > The ANX7625 is an ultra-low power 4K Mobile HD Transmitter designed
> > for portable device. It converts MIPI to DisplayPort 1.3 4K.
Hi all,
This is now a conflict between the amdgpu tree and the drm tree.
On Fri, 4 Oct 2019 11:10:22 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the drm-misc tree got a conflict in:
>
> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c
>
> between commit:
>
>
Hi all,
This is now a semantic conflict between the drm and v4l-dvb trees.
On Tue, 8 Oct 2019 10:30:45 +1100 Stephen Rothwell
wrote:
>
> After merging the drm-misc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
drivers/media/platform/cec-gpio/cec-gpio.c: In function '
Am Donnerstag, 10. Oktober 2019, 05:44:52 CEST schrieb Nickey Yang:
> Some VOP's (such as px30) dclk_pol bit is at the last.
> So it is necessary to distinguish dclk_pol and pin_pol.
>
> Signed-off-by: Nickey Yang
applied to drm-misc-next with Sandy's Reviewed-by
Thanks
Heiko
Am Mittwoch, 9. Oktober 2019, 14:10:22 CEST schrieb Ben Dooks:
> The rockchip_gem_alloc_object function is not exported so
> make it static to avoid the following sparse warning:
>
> drivers/gpu/drm/rockchip/rockchip_drm_gem.c:297:28: warning: symbol
> 'rockchip_gem_alloc_object' was not declared
Am Samstag, 21. September 2019, 20:40:16 CEST schrieb Markus Elfring:
> From: Markus Elfring
> Date: Sat, 21 Sep 2019 20:32:25 +0200
>
> Simplify this function implementation by using a known wrapper function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Mark
Am Mittwoch, 9. Oktober 2019, 15:21:34 CEST schrieb Ben Dooks:
> Include rockchip_drm_drv.h for definition of vop_platform_driver
> to avoid the following sparse warning:
>
> drivers/gpu/drm/rockchip/rockchip_vop_reg.c:982:24: warning: symbol
> 'vop_platform_driver' was not declared. Should it be
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #92 from Marko Popovic ---
Ok day recap: been using my PC for like 12 hours today, without using the nodma
variable, no "random" hangs appeared on the desktop, I will make another reply
in a few days if things keep like this, hopeful
(Sorry to CCs for spam, I made an error in my first posting)
Hi,
There were certainly some interesting changes discussed at the allocator
workshop during XDC this year, and I'd like to just summarise my
thoughts on it and make sure everybody is on the same page.
For those who don't know who I a
Am Donnerstag, 10. Oktober 2019, 21:43:51 CEST schrieb Ezequiel Garcia:
> RK3288 SoC VOPs have optional support Gamma LUT setting,
> which requires specifying the Gamma LUT address in the devicetree.
>
> Signed-off-by: Ezequiel Garcia
> Reviewed-by: Douglas Anderson
applied for 5.5
Thanks
Heik
https://bugs.freedesktop.org/show_bug.cgi?id=109887
--- Comment #12 from Stefan Springer ---
Actually, it gets reset to 1200mV every time the resolution changes. I.e. when
launching a fullscreen game or restarting the display manager.
--
You are receiving this mail because:
You are the assignee
Hi Changbin,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[cannot apply to v5.4-rc2 next-20191010]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to
https://bugs.freedesktop.org/show_bug.cgi?id=109887
--- Comment #11 from Stefan Springer ---
Loading a powerplay table only temporarily alleviates the issue. It comes back
after a while of desktop usage.
I think the culprit might be here:
https://github.com/torvalds/linux/blob/master/drivers/gpu
https://bugs.freedesktop.org/show_bug.cgi?id=111986
--- Comment #6 from Daniel Suarez ---
Created attachment 145728
--> https://bugs.freedesktop.org/attachment.cgi?id=145728&action=edit
Xorg log
I switched over to mesa-git (along with all the other packages recommended to
accompany it mentione
https://bugzilla.kernel.org/show_bug.cgi?id=204805
--- Comment #2 from ilkka.pr...@gmail.com ---
System freezing repeated on 5.3.6 (Debian/testing bullseye).
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-deve
On Mon, Oct 7, 2019 at 3:01 PM Maxime Ripard wrote:
>
> On Sat, Oct 05, 2019 at 07:49:08PM +0530, Jagan Teki wrote:
> > The MIPI DSI controller in Allwinner A64 is similar to A33.
> >
> > But unlike A33, A64 doesn't have DSI_SCLK gating so it is valid
> > to with separate compatible for A64 on the
On Wed, Oct 2, 2019 at 7:25 AM Tomi Valkeinen wrote:
>
> The OMAP36xx and AM/DM37x TRMs say that the maximum divider for DSS fclk
> (in CM_CLKSEL_DSS) is 32. Experimentation shows that this is not
> correct, and using divider of 32 breaks DSS with a flood or underflows
> and sync losts. Dividers u
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #91 from Marko Popovic ---
(In reply to Shmerl from comment #90)
> Those hangs are likely shader related, so not the same thing. But desktop
> (Firefox specifically for me) hangs look indeed fixed to me so far.
This might actually a
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #90 from Shmerl ---
Those hangs are likely shader related, so not the same thing. But desktop
(Firefox specifically for me) hangs look indeed fixed to me so far.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #89 from Marko Popovic ---
(In reply to Shmerl from comment #88)
> (In reply to Marko Popovic from comment #87)
> > All of the hangs are still present for me, so this patch changed nothing.
>
> Does Firefox hang for you still?
Actu
https://bugs.freedesktop.org/show_bug.cgi?id=111986
Daniel Suarez changed:
What|Removed |Added
Severity|major |critical
--
You are receiving this mai
https://bugs.freedesktop.org/show_bug.cgi?id=111986
Daniel Suarez changed:
What|Removed |Added
Priority|not set |high
Severity|not set
https://bugs.freedesktop.org/show_bug.cgi?id=111913
--- Comment #11 from Stefan Rehm ---
git bisect shows that commit fb6959ae50176758a073687dbb081d26521f4576 ("Embed
DCN2 SOC bounding box") is the first to to trigger the bug.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111988
Bug ID: 111988
Summary: Kernel WARNING related to Xorg happening in every boot
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity
https://bugs.freedesktop.org/show_bug.cgi?id=111948
Andreas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Hi!
> If the LED is acquired by a consumer device with devm_led_get(), it is
> automatically released when the device is detached.
>
> Signed-off-by: Jean-Jacques Hiblot
> Acked-by: Pavel Machek
> ---
> drivers/leds/led-class.c | 49
> include/linux/led
On Mon 2019-09-30 12:09:07, Kiran Gunda wrote:
> Restructure the qcom-wled bindings for the better readability.
>
> Signed-off-by: Kiran Gunda
> Reviewed-by: Bjorn Andersson
> Reviewed-by: Rob Herring
> Acked-by: Daniel Thompson
> Acked-by: Pavel Machek
I applied 1,2 to my branch, it should
https://bugzilla.kernel.org/show_bug.cgi?id=204241
--- Comment #28 from a...@tutanota.com ---
(In reply to Andreas Jackisch from comment #27)
> In brief - the patch
> "0001-drm-amdgpu-uvd6-fix-allocation-size-in-enc-ring-test.patch" didn't
> work for me. After about 10 suspend/resume cycles the ty
https://bugzilla.kernel.org/show_bug.cgi?id=204609
Witold Baryluk (bary...@smp.if.uj.edu.pl) changed:
What|Removed |Added
CC||bary...@smp.if
https://bugs.freedesktop.org/show_bug.cgi?id=111987
--- Comment #10 from Witold Baryluk ---
Firmware signatures:
user@debian:/lib/firmware/amdgpu$ sha256sum fiji_*
615693b2736f13c4ef3cd9220efe4d55df3c5d82fe128d3f1b34a45edba65fbd fiji_ce.bin
b0d51dc0b361afa07bcefa0f4670c344679b1fcbe1be68c06e727e
https://bugs.freedesktop.org/show_bug.cgi?id=111987
--- Comment #9 from Witold Baryluk ---
Kernel config, nothing special:
$ grep DRM_AMD /boot/config-5.2.0-3-amd64
CONFIG_DRM_AMDGPU=m
CONFIG_DRM_AMDGPU_SI=y
CONFIG_DRM_AMDGPU_CIK=y
CONFIG_DRM_AMDGPU_USERPTR=y
# CONFIG_DRM_AMDGPU_GART_DEBUGFS is
https://bugzilla.kernel.org/show_bug.cgi?id=205169
--- Comment #9 from Dmitri Seletski (drj...@gmail.com) ---
i had a couple of LLVM versions.i removed all. Now I have version 9.0.0
dimko@(none)dimko's Desktop ~ $ ls /boot/ |grep vmlinuz-5.3.
sys-devel/llvm
Latest version available: 9.0.0
https://bugzilla.kernel.org/show_bug.cgi?id=205169
--- Comment #8 from Dmitri Seletski (drj...@gmail.com) ---
(In reply to Pierre-Eric Pelloux-Prayer from comment #7)
> (In reply to Dmitri Seletski from comment #0)
> > I have another problem logged with Navi + AMDGPU drivers. It's triggered
> > in
https://bugs.freedesktop.org/show_bug.cgi?id=111987
--- Comment #8 from Witold Baryluk ---
My random guess is that it is due to some bug in calculating gpu_busy_percent
possibly, or SCLK_{UP,DOWN}_HYST parameters:
Here is a dump of various values, when running Talos:
Sun Oct 13 09:29:46 UTC 201
https://bugzilla.kernel.org/show_bug.cgi?id=205169
Pierre-Eric Pelloux-Prayer (pierre-eric.pelloux-pra...@amd.com) changed:
What|Removed |Added
CC|
41 matches
Mail list logo
