https://bugs.freedesktop.org/show_bug.cgi?id=102885
--- Comment #9 from Samuel Pitoiset ---
No, the bug should be fixed. I just didn't have much time to work on it to be
honest.
--
You are receiving this mail because:
You are the assignee for the bug.
Patch #4 is Reviewed-by: Christian König .
The rest is Acked-by: Christian König .
Regards,
Christian.
Am 02.11.2017 um 21:03 schrieb Ville Syrjala:
From: Ville Syrjälä
When building drm+i915 I get around 150 lines of sparse noise from
dma_fence __rcu warnings. This series eliminates all of
From: Aleksandar Markovic
Add documentation for DT binding of Goldfish FB driver. The compatible
string used by OS for binding the driver is "google,goldfish-fb".
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran Ferenc
Signed-off-by: Aleksandar Markovic
Acked-by: Rob Herring
---
.../device
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 114735
Addresses-Coverity-ID: 114736
Addresses-Coverity-ID: 114737
Addresses-Coverity-ID: 114738
Signed-off-by: Gustavo A. R. Silva
---
drivers/gpu/drm/savage/savag
From: John Stultz
commit 651e4769ba2a9f20c4b8a823ae2727bf7fa9c9f0 upstream.
In chasing down issues with EDID probing, I found some
duplicated but incomplete logic used to power the chip on and
off.
This patch refactors the adv7511_power_on/off functions, so
they can be used for internal needs.
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 114740
Addresses-Coverity-ID: 114741
Addresses-Coverity-ID: 114742
Addresses-Coverity-ID: 114743
Signed-off-by: Gustavo A. R. Silva
---
drivers/gpu/drm/via/via_dmab
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1260018
Addresses-Coverity-ID: 1260019
Addresses-Coverity-ID: 1260022
Signed-off-by: Gustavo A. R. Silva
---
drivers/gpu/drm/nouveau/nvkm/subdev/bios/timing.c | 5 +
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 143119
Addresses-Coverity-ID: 143120
Addresses-Coverity-ID: 143121
Addresses-Coverity-ID: 143122
Addresses-Coverity-ID: 143123
Addresses-Coverity-ID: 143124
Signed-of
From: John Stultz
commit 3587c856675c45809010c2cee5b21096f6e8e938 upstream.
I've found that by just turning the chip on and off via the
POWER_DOWN register, I end up getting i2c_transfer errors on
HiKey.
Investigating further, it turns out that some of the register
state in hardware is getting
From: John Stultz
commit 4226d9b127cf4758ba0e07931b3f0d59f1b1a50c upstream.
Thus this patch changes the EDID probing logic so that we
re-use the __adv7511_power_on/off() calls instead of duplciating
logic.
This does change behavior slightly as it adds the HPD signal
pulse to the EDID probe path
Den 02.11.2017 21.09, skrev Noralf Trønnes:
These helpers take care of output polling, fbdev and atomic state.
Cc: Stefan Agner
Cc: Alison Wang
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 23 +--
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv
https://bugzilla.kernel.org/show_bug.cgi?id=196197
--- Comment #12 from Michel Dänzer (mic...@daenzer.net) ---
(In reply to Andreas Brogle from comment #7)
> The last 7 turns caused a kernel panic, all the 4.10.0-rc1 versions. I
> declared them as bad with git bisect.
In cases like this, where it
Reviewed-By: Xiangliang Yu
Thanks!
> -Original Message-
> From: Arnd Bergmann [mailto:a...@arndb.de]
> Sent: Thursday, November 02, 2017 7:26 PM
> To: Deucher, Alexander ; Koenig, Christian
>
> Cc: Arnd Bergmann ; David Airlie ; Liu,
> Monk ; Yu, Xiangliang ;
> Chen, Horace ; amd-...@li
On 2017-11-01 02:13, Inki Dae wrote:
Hi Marek,
Thanks for your effort and sorry for late. Below are trivial my comments,
2017년 10월 23일 16:54에 Marek Szyprowski 이(가) 쓴 글:
This patch adds Exynos IPP v2 subsystem and userspace API.
New userspace API is focused ONLY on memory-to-memory image pro
Dear dri-devel, spec. Dear i.MX folks,
I would like to display a splash screen on an i.MX6 based board from the
kernel as soon as the display hardware is initialized. But I'm having
trouble finding some kind of 'take this buffer and display it' function
within the IPU driver. (And I see no way
Hi Inki,
On 2017-11-01 07:26, Inki Dae wrote:
2017년 10월 23일 16:54에 Marek Szyprowski 이(가) 쓴 글:
Some hardware modules, like FIMC in Exynos4 series are shared between
V4L2 (camera support) and DRM (memory-to-memory processing) subsystems.
This patch provides a simple check to let such drivers to b
On Thu, Nov 2, 2017 at 11:45 PM, Chih-Wei Huang wrote:
> The file contains rules that are executed on incremental builds.
> Since commit 4f7dc9b6 the library was moved to /vendor so
> the old file must be removed.
>
> Signed-off-by: Chih-Wei Huang
> ---
> CleanSpec.mk | 1 +
> 1 file changed, 1
https://bugs.freedesktop.org/show_bug.cgi?id=103550
Daniel Stone changed:
What|Removed |Added
Product|Wayland |DRI
Component|wayland
Hi,
On 3 November 2017 at 16:56, Stephan Bauroth wrote:
> Dear dri-devel, spec. Dear i.MX folks,
>
> I would like to display a splash screen on an i.MX6 based board from the
> kernel as soon as the display hardware is initialized. But I'm having
> trouble finding some kind of 'take this buffer an
On 03.11.2017 13:57, PrasannaKumar Muralidharan wrote:
Hi,
On 3 November 2017 at 16:56, Stephan Bauroth wrote:
Dear dri-devel, spec. Dear i.MX folks,
I would like to display a splash screen on an i.MX6 based board from the
kernel as soon as the display hardware is initialized. But I'm having
Just add the extra PCI-ID to the existing fixup.
Signed-off-by: Christian König
---
arch/x86/pci/fixup.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/x86/pci/fixup.c b/arch/x86/pci/fixup.c
index 7b6bd76..1d2238d 100644
--- a/arch/x86/pci/fixup.c
+++ b/arch/x86/pci/f
Just add the extra PCI-ID to the existing fixup.
Signed-off-by: Christian König
---
arch/x86/pci/fixup.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/x86/pci/fixup.c b/arch/x86/pci/fixup.c
index 3eebb0e..894d73d 100644
--- a/arch/x86/pci/fixup.c
+++ b/arch/x86/pci/f
Just add the extra PCI-ID to the existing fixup.
Signed-off-by: Christian König
---
arch/x86/pci/fixup.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/x86/pci/fixup.c b/arch/x86/pci/fixup.c
index 1d2238d..aa8b20e 100644
--- a/arch/x86/pci/fixup.c
+++ b/arch/x86/pci/f
Just add the extra PCI-ID to the existing fixup.
Signed-off-by: Christian König
---
arch/x86/pci/fixup.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/x86/pci/fixup.c b/arch/x86/pci/fixup.c
index aa8b20e..3eebb0e 100644
--- a/arch/x86/pci/fixup.c
+++ b/arch/x86/pci/
From: Christian König
Just add the extra PCI-ID to the existing fixup.
Signed-off-by: Christian König
---
arch/x86/pci/fixup.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/x86/pci/fixup.c b/arch/x86/pci/fixup.c
index 7b6bd76..1d2238d 100644
--- a/arch/x86/pci/fixu
Inki Dae wrote:
> Hi Email,
>
> Since I posted this patch, much time has been passed.
> But no answer. We got already many Acked-by so could you merge this patch?
I think you need Acked-by by all authors. And it looks like you ignored my
comments.
- Tobias
>
> Thanks,
> Inki Dae
>
>
> 2017년
https://bugs.freedesktop.org/show_bug.cgi?id=102358
--- Comment #32 from Thomas Hellström ---
Slightly polished patch available here...
https://lists.freedesktop.org/archives/mesa-dev/2017-November/175373.html
--
You are receiving this mail because:
You are the assignee for the bug.__
On 3 November 2017 at 13:59, Tobias Jakobi
wrote:
> Inki Dae wrote:
>> Hi Email,
>>
>> Since I posted this patch, much time has been passed.
>> But no answer. We got already many Acked-by so could you merge this patch?
> I think you need Acked-by by all authors. And it looks like you ignored my
>
Hello Arnd,
I guess you could coordinate the IPP changes with Marek, who is rewriting the
IPP subsystem anyway (added Marek to Cc).
Here is the most recent IPPv2 series:
https://www.spinics.net/lists/linux-samsung-soc/msg61066.html
Concerning the G2D changes, I don't think anything in userspace
https://bugs.freedesktop.org/show_bug.cgi?id=103562
Bug ID: 103562
Summary: QXL driver disables IRQ and locks up when starting
multihead weston, kernel 4.13
Product: DRI
Version: XOrg git
Hardware: Other
OS:
https://bugs.freedesktop.org/show_bug.cgi?id=103562
Vasilis LIaskovitis changed:
What|Removed |Added
Version|XOrg git|unspecified
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=102885
--- Comment #10 from Thomas J. Moore ---
(In reply to Samuel Pitoiset from comment #9)
> No, the bug should be fixed. I just didn't have much time to work on it to
> be honest.
OK, no hurry. It's not like it's corrupting memory or anything, an
https://bugs.freedesktop.org/show_bug.cgi?id=103544
--- Comment #4 from Roland Scheidegger ---
(In reply to Vitalii from comment #3)
> (In reply to Emil Velikov from comment #1)
> > Vitalii can you bisect Mesa to the commit that broke the game? There aren't
> > many developer working on r600 - so
https://bugs.freedesktop.org/show_bug.cgi?id=92790
--- Comment #5 from Adrian ---
It still doesn't work on Ubuntu 17.10 (4.13.0-16-lowlatency).
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-dev
https://bugs.freedesktop.org/show_bug.cgi?id=29322
--- Comment #4 from mirh ---
Would say this is a duplicate of bug 42117 ?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedeskto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
libdrm 2.4.88 has been released.
Andrey Grodzovsky (1):
amdgpu: Fix wrappers for AMDGPU_VM IOCTL.
Marek Olšák (1):
configure.ac: bump version for release
git tag: libdrm-2.4.88
https://dri.freedesktop.org/libdrm/libdrm-2.4.88.tar.bz2
This set of patches fixes several issues that was found during testing
tc358767 with desktop DisplayPort displays.
Changes in V2:
- fixed maximum pixelclock frequency
- copyright patch added
Andrey Gusakov (7):
drm/bridge: tc358767: do no fail on hi-res displays
drm/bridge: tc
Use drm_dp_channel_eq_ok helper
---
drivers/gpu/drm/bridge/tc358767.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/bridge/tc358767.c
b/drivers/gpu/drm/bridge/tc358767.c
index 4394131..1e677be 100644
--- a/drivers/gpu/drm/bridge/tc358767.c
++
Minimum pixel clock period is 6.5 nS for DPI. Do not accept modes
with lower pixel clock period.
---
drivers/gpu/drm/bridge/tc358767.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/bridge/tc358767.c
b/drivers/gpu/drm/bridge/tc358767.c
index d52cd41..7
Remove shift from TU_SIZE_RECOMMENDED define as it used to
calculate max_tu_symbols.
---
drivers/gpu/drm/bridge/tc358767.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/bridge/tc358767.c
b/drivers/gpu/drm/bridge/tc358767.c
index 7f9c2e0..90d6b49 10064
Add copyright lines for Zodiac who paid for driver development.
Signed-off-by: Andrey Gusakov
---
drivers/gpu/drm/bridge/tc358767.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/bridge/tc358767.c
b/drivers/gpu/drm/bridge/tc358767.c
index 1e677be..d98d717 100644
--- a/
First four bytes should go to DP0_AUXWDATA0. Due to bug if
len > 4 first four bytes was writen to DP0_AUXWDATA1 and all
data get shifted by 4 bytes. Fix it.
---
drivers/gpu/drm/bridge/tc358767.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/bridge/tc358767.
Fields in HTIM01 and HTIM02 regs should be even.
Recomended thresh_dly value is max_tu_symbol.
---
drivers/gpu/drm/bridge/tc358767.c | 34 --
1 file changed, 20 insertions(+), 14 deletions(-)
diff --git a/drivers/gpu/drm/bridge/tc358767.c
b/drivers/gpu/drm/bridg
Do not fail data rates higher than 2.7 and more than 2 lanes.
Try to fall back to 2.7Gbps and 2 lanes.
---
drivers/gpu/drm/bridge/tc358767.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/bridge/tc358767.c
b/drivers/gpu/drm/bridge/tc358767.c
i
https://bugs.freedesktop.org/show_bug.cgi?id=42117
--- Comment #17 from mirh ---
xf86-video-ati 6.14.4 supposedly added KMS tiling
https://wiki.freedesktop.org/xorg/radeon/
Could this get performance back to a satisfactorily enough level that we can
consider this nonetheless fixed?
Or.. Why her
struct timeval is deprecated because it cannot represent times
past 2038. In this driver, the only use of this structure is
to capture debug information. This is easily changed to ktime_t,
which we then format as needed when printing it later.
Signed-off-by: Arnd Bergmann
---
drivers/gpu/drm/i91
https://bugs.freedesktop.org/show_bug.cgi?id=102358
--- Comment #33 from har...@gmx.de ---
No freezes, works great for me.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.o
Hi Dave,
The following changes since commit 25dd1aa3b4cf0c361147aa45ff4dd1d335259ac1:
Merge branch 'linux-4.14' of git://github.com/skeggsb/linux into drm-fixes
(2017-11-01 10:05:03 +1000)
are available in the git repository at:
git://people.freedesktop.org/~syeh/repos_linux drm-vmwgfx-fix
r()
>>> to pass the timer pointer explicitly.
>>
>> Reviewed and applied to drm-misc-next. Thanks!
>
> Thanks!
>
> I happened to notice that this was in next-20171102, but missing in
> next-20171103. Did it get removed, or am I misunderstanding something?
I don'
From: Vijendar Mukunda
Using hw register to read transmitted byte count and report
accordingly the hw pointer.
BUG=b:63121716
TEST=
modprobe snd-soc-acp-pcm.ko
modprobe snd-soc-acp-rt5645.ko
aplay
Signed-off-by: Vijendar Mukunda
Signed-off-by: Akshu Agrawal
Reviewed-on: https://chromium-revi
From: Akshu Agrawal
This fixes the issue of driver not getting auto loaded with
MODULE_ALIAS.
find /sys/devices -name modalias -print0 | xargs -0 grep 'audio'
/sys/devices/pci:00/:00:01.0/acp_audio_dma.0.auto/modalias:platform:acp_audio_dma
BUG=b:62103837
TEST=boot and check for device i
This patch set is just a couple fixes for the Audio CoProcessor (ACP)
on AMD Stoney platforms and a small general fix for the rt5645
codec driver.
The entire patch set can also be viewed here:
https://cgit.freedesktop.org/~agd5f/linux/log/?h=sound-for-next-stoney
Thanks!
Alex
Akshu Agrawal (2):
From: Akshu Agrawal
Minimum time required between power On of codec and read
of RT5645_VENDOR_ID2 is 400msec. We should wait and attempt
before erroring out.
BUG=b:66978383
TEST=Cold boot the device and check for sound device.
Signed-off-by: Akshu Agrawal
Signed-off-by: Bard Liao
Signed-off-b
https://bugs.freedesktop.org/show_bug.cgi?id=102358
--- Comment #34 from Thomas Hellström ---
(In reply to haro41 from comment #33)
> No freezes, works great for me.
Want to add a Tested-by: tag?
/Thomas
--
You are receiving this mail because:
You are the assignee for the bug.
tree: git://people.freedesktop.org/~agd5f/linux.git sound-for-next-stoney
head: d01a736c0b1595c5e65b2f2b16fe2da87ec3bc4c
commit: d22c814cbe57c05d8b21b83840dc5537f3b3ccff [2/3] ASoC: AMD: Make the
driver name consistent across files
config: i386-randconfig-s0-201744 (attached as .config)
compil
https://bugs.freedesktop.org/show_bug.cgi?id=103316
Vedran Miletić changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=103316
Vedran Miletić changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=102507
--- Comment #5 from Vedran Miletić ---
Fixed for me with Nov 2 commits.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop
tree: git://people.freedesktop.org/~agd5f/linux.git sound-for-next-stoney
head: d01a736c0b1595c5e65b2f2b16fe2da87ec3bc4c
commit: 41f9cb7a4d2aaf31aad6a87278f028add9d2d1a6 [1/3] ASoC: amd: Report
accurate hw_ptr during dma
config: i386-allyesconfig (attached as .config)
compiler: gcc-6 (Debian 6
https://bugs.freedesktop.org/show_bug.cgi?id=103544
--- Comment #5 from Roland Scheidegger ---
I've actually got that game myself here.
So I did the bisect and the winner is:
ce7a045feeef8cad155f1c9aa07f166e146e3d00 is the first bad commit
commit ce7a045feeef8cad155f1c9aa07f166e146e3d00
Author: I
https://bugs.freedesktop.org/show_bug.cgi?id=103544
--- Comment #6 from Ilia Mirkin ---
(In reply to Roland Scheidegger from comment #5)
> I've actually got that game myself here.
> So I did the bisect and the winner is:
> ce7a045feeef8cad155f1c9aa07f166e146e3d00 is the first bad commit
> commit
https://bugs.freedesktop.org/show_bug.cgi?id=103544
--- Comment #7 from Roland Scheidegger ---
(In reply to Ilia Mirkin from comment #6)
> The main difference between IEEE and non-IEEE is whether 0 * infinity = 0 or
> NaN. IEEE makes it mean NaN. DX9 behavior is 0. I added a flag to be used by
>
The if statement wasn't indented so it makes static analysis tools and
probably very recent GCC versions complain.
Signed-off-by: Dan Carpenter
---
I went over 80 characters because other lines do already and it seemed
like the cleanest thing here.
diff --git a/drivers/gpu/drm/amd/display/dc/dcn
63 matches
Mail list logo
