Hi Dave,
Three small fixes to the CIK SDMA code in amdkfd
Thanks,
Oded
The following changes since commit d65d31388a23b14df9494135ad6c6549a59a3caa:
Merge tag 'drm-misc-next-fixes-2017-11-07' of
git://anongit.freedesktop.org/drm/drm-misc into drm-next (2017-11-08 05:22:49
+1000)
are availab
Thanks for the pointer, I did that (these patches will be sent for
next merge window)
On Mon, Nov 6, 2017 at 6:35 PM, Felix Kuehling wrote:
> I messed up while rebasing patches and didn't test every intermediate
> patch as I should have. The next patch in the series fixes this.
>
> If anyone want
On 11/07/2017 04:57 PM, Russell King wrote:
Parsing the EDID for HDMI and audio information in the get_modes()
callback is incorrect - this only parses the EDID read from the
connector, not any override or firmware provided EDID.
The correct place to parse the EDID for these parameters is the
Hi Nikolaus,
On Thursday, 9 November 2017 08:05:15 EET H. Nikolaus Schaller wrote:
> > Am 09.11.2017 um 04:33 schrieb Laurent Pinchart:
> > On Wednesday, 8 November 2017 23:09:29 EET H. Nikolaus Schaller wrote:
> >> The vendor name was "toppoly" but other panels and the vendor list
> >> have defin
Warnigs,
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#110:
new file mode 100644
WARNING: please write a paragraph that describes the config symbol fully
#150: FILE: drivers/gpu/drm/exynos/Kconfig:112:
+config DRM_EXYNOS_SCALER
WARNING: Prefer 'unsigned int' to bare
Also warnigs,
WARNING: line over 80 characters
#145: FILE: drivers/gpu/drm/exynos/exynos_drm_drv.c:299:
+ component_match_add(dev, &match, compare_dev,
d);
WARNING: please, no spaces at the start of a line
#2702: FILE: drivers/gpu/drm/exynos/exynos_drm_fimc.c:730:
+
Also warnings,
WARNING: please, no spaces at the start of a line
#2667: FILE: drivers/gpu/drm/exynos/exynos_drm_gsc.c:727:
+ struct drm_exynos_ipp_task_rect *src, struct drm_exynos_ipp_task_rect
*dst)$
WARNING: line over 80 characters
#3098: FILE: drivers/gpu/drm/exynos/exynos_drm_gsc.c:1158
https://bugs.freedesktop.org/show_bug.cgi?id=103634
--- Comment #1 from Roland Scheidegger ---
Created attachment 135335
--> https://bugs.freedesktop.org/attachment.cgi?id=135335&action=edit
trace file captured with R600_TRACE
Here's the output of R600_TRACE when running
./nv_conditional_rende
Many warings,
WARNING: line over 80 characters
#181: FILE: drivers/gpu/drm/exynos/exynos_drm_drv.c:118:
+ DRM_IOCTL_DEF_DRV(EXYNOS_IPP_GET_RESOURCES,
exynos_drm_ipp_get_res_ioctl,
WARNING: line over 80 characters
#185: FILE: drivers/gpu/drm/exynos/exynos_drm_drv.c:122:
+ DRM_IOCTL_DE
Hi Marek,
I checked style warning of this patch series using checkpatch.pl before merging
them but the script says many warnings.
I will comment this.
Thanks,
Inki Dae
2017년 11월 08일 18:41에 Marek Szyprowski 이(가) 쓴 글:
> Dear all,
>
> This patchset performs complete rewrite of Exynos DRM IPP subs
Hi Nikolaus,
Thank you for the patch.
On Wednesday, 8 November 2017 23:09:32 EET H. Nikolaus Schaller wrote:
> commit d178e034d565 ("drm: omapdrm: Move FEAT_DPI_USES_VDDS_DSI feature to
> dpi code")
>
> introduced a new match table which turned out to be wrong, at least
> for the 600 MHz OpenPan
Hi Nikolaus,
Thank you for the patch.
On Wednesday, 8 November 2017 23:09:31 EET H. Nikolaus Schaller wrote:
> We can remove the "omapdss," prefix.
I agree but you should explain why.
> Signed-off-by: H. Nikolaus Schaller
> ---
> arch/arm/boot/dts/omap3-pandora-common.dtsi | 2 +-
> 1 file ch
Hi Nikolaus,
Thank you for the patch.
On Wednesday, 8 November 2017 23:09:29 EET H. Nikolaus Schaller wrote:
> The vendor name was "toppoly" but other panels and the vendor list
> have defined it as "tpo". So let's fix it in driver and bindings.
>
> Signed-off-by: H. Nikolaus Schaller
> ---
>
https://bugs.freedesktop.org/show_bug.cgi?id=103634
Bug ID: 103634
Summary: nv_conditional_render tests hang the gpu (HD 5750)
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: c64efcaed73726bd3cfaa46c27768d3331a1ad35
commit: 0bd599b1f523598c05f13a4a562884e82a378c2c [2064/2165] ASoC: AMD: enable
ACP3x drivers build
config: tile-allmodconfig (attached as .config)
compiler: tilegx-linux-gcc
Hi Dave,
I know it is time to wrap-up, but we have 2 fixes still
that seems important for a stable 4.14.
drm-intel-fixes-2017-11-08:
- Fix possible NULL dereference (Chris).
- Avoid miss usage of syncobj by rejecting unknown flags (Tvrtko).
Thanks,
Rodrigo.
The following changes since commit 39
From: Dave Airlie
The lease updates missed a few bits of docs, fixed up
the wrong name on the property lookup fn as well.
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/drm_framebuffer.c | 1 +
drivers/gpu/drm/drm_mode_object.c | 1 +
include/drm/drm_connector.h | 1 +
include/drm/drm_cr
Hi Dave,
A few more fixes for 4.15.
The following changes since commit d65d31388a23b14df9494135ad6c6549a59a3caa:
Merge tag 'drm-misc-next-fixes-2017-11-07' of
git://anongit.freedesktop.org/drm/drm-misc into drm-next (2017-11-08 05:22:49
+1000)
are available in the git repository at:
git:
Hi Dave,
A bunch of smatch fixes for the dc code.
The following changes since commit 26c860d5579684528114c3875ef88f7796330eb5:
Merge branch 'drm-next-4.15-dc' of git://people.freedesktop.org/~agd5f/linux
into drm-next (2017-11-03 05:32:08 +1000)
are available in the git repository at:
git
Ville Syrjälä writes:
> On Wed, Nov 08, 2017 at 12:17:28PM -0800, Eric Anholt wrote:
>> Ville Syrjala writes:
>>
>> > From: Ville Syrjälä
>> >
>> > Apparently some sinks look at the YQ bits even when receiving RGB,
>> > and they get somehow confused when they see a non-zero YQ value.
>> > So w
The patch
ASoC: amd: use do_div rather than 64 bit division to fix 32 bit builds
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the n
https://bugs.freedesktop.org/show_bug.cgi?id=103630
--- Comment #2 from cosiek...@o2.pl ---
Created attachment 135321
--> https://bugs.freedesktop.org/attachment.cgi?id=135321&action=edit
Hacker Evolution Duality trace
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=103630
--- Comment #1 from cosiek...@o2.pl ---
Created attachment 135320
--> https://bugs.freedesktop.org/attachment.cgi?id=135320&action=edit
Hacker Evolution Untold trace
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=103630
Bug ID: 103630
Summary: [regression] Hacker Evolution(1,2,3) crash on startup
Product: Mesa
Version: 17.2
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
On Wed, Nov 08, 2017 at 09:30:07PM +0100, Daniel Vetter wrote:
> Point at the equivalent atomic state and explain that atomic drivers
> shouldn't really depend upon legacy state.
>
> Motivated by questions from Manasi about how this all is supposed to
> work.
>
> Cc: Manasi Navare
> Signed-off-b
On Wed, Nov 08, 2017 at 10:09:32AM -0800, Manasi Navare wrote:
> On Wed, Nov 08, 2017 at 02:28:23PM +0100, Daniel Vetter wrote:
> > On Wed, Nov 08, 2017 at 03:26:15PM +0200, Ville Syrjälä wrote:
> > > On Wed, Nov 08, 2017 at 02:11:46PM +0100, Daniel Vetter wrote:
> > > > On Wed, Nov 08, 2017 at 03:
> -Original Message-
> From: Mark Brown [mailto:broo...@kernel.org]
> Sent: Wednesday, November 08, 2017 1:48 PM
> To: Alex Deucher
> Cc: amd-gfx list; alsa-de...@alsa-project.org; Maling list - DRI developers;
> Mukunda, Vijendar; Liam Girdwood; Takashi Iwai; Guenter Roeck; Deucher,
> Alex
On Wed, Nov 08, 2017 at 02:35:05PM -0500, Alex Deucher wrote:
> On Wed, Nov 8, 2017 at 2:30 PM, Guenter Roeck wrote:
> > On Wed, Nov 8, 2017 at 11:18 AM, Deucher, Alexander
> >> > Is this different to "ASoC: amd: Report accurate hw_ptr during dma"
> >> > which was applied at 16:07?
> >> Yes, thi
On Wed, Nov 08, 2017 at 12:17:28PM -0800, Eric Anholt wrote:
> Ville Syrjala writes:
>
> > From: Ville Syrjälä
> >
> > Apparently some sinks look at the YQ bits even when receiving RGB,
> > and they get somehow confused when they see a non-zero YQ value.
> > So we can't just blindly follow CEA-8
On Wed, Nov 8, 2017 at 2:53 PM, Ernst Sjöstrand wrote:
> Can't find these anywhere yet, errors still there.
>
> https://patchwork.freedesktop.org/series/31220/
Applied. thanks for the reminder.
Alex
>
> Regards
> //Ernst
>
> 2017-09-30 10:25 GMT+02:00 Christian König :
>> Am 30.09.2017 um 10:1
Point at the equivalent atomic state and explain that atomic drivers
shouldn't really depend upon legacy state.
Motivated by questions from Manasi about how this all is supposed to
work.
Cc: Manasi Navare
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/drm_atomic_helper.c | 6 ++
include
Ville Syrjala writes:
> From: Ville Syrjälä
>
> Apparently some sinks look at the YQ bits even when receiving RGB,
> and they get somehow confused when they see a non-zero YQ value.
> So we can't just blindly follow CEA-861-F and set YQ to match the
> RGB range.
>
> Unfortunately there is no goo
On Wed, Nov 08, 2017 at 05:21:04PM +0200, Ville Syrjälä wrote:
> On Wed, Nov 08, 2017 at 11:54:49AM +0100, Daniel Vetter wrote:
> > It's useful for syncing async connector work like link retraining.
> >
> > Cc: Manasi Navare
> > Cc: Maarten Lankhorst
> > Cc: Ville Syrjälä
> > Signed-off-by: Dan
On Wed, Nov 8, 2017 at 2:49 PM, Mark Brown wrote:
> On Wed, Nov 08, 2017 at 11:13:50AM -0800, Guenter Roeck wrote:
>> On Wed, Nov 8, 2017 at 10:47 AM, Mark Brown wrote:
>
>> > Is this different to "ASoC: amd: Report accurate hw_ptr during dma"
>> > which was applied at 16:07?
>
>> I suspect we ma
https://bugs.freedesktop.org/show_bug.cgi?id=101382
cosiek...@o2.pl changed:
What|Removed |Added
Severity|normal |major
Version|17.1
https://bugs.freedesktop.org/show_bug.cgi?id=101382
--- Comment #7 from cosiek...@o2.pl ---
17.2.4-1 crash
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists
https://bugs.freedesktop.org/show_bug.cgi?id=103625
Chris Wilson changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
On Wed, Nov 08, 2017 at 11:13:50AM -0800, Guenter Roeck wrote:
> On Wed, Nov 8, 2017 at 10:47 AM, Mark Brown wrote:
> > Is this different to "ASoC: amd: Report accurate hw_ptr during dma"
> > which was applied at 16:07?
> I suspect we may be getting hit by chromeos-isms again. In Chrome OS, we
>
On Wed, Nov 8, 2017 at 2:30 PM, Guenter Roeck wrote:
> On Wed, Nov 8, 2017 at 11:18 AM, Deucher, Alexander
> wrote:
>>
>> > -Original Message-
>> > From: Mark Brown [mailto:broo...@kernel.org]
>> > Sent: Wednesday, November 08, 2017 1:48 PM
>> > To: Alex Deucher
>> > Cc: amd-gfx list; als
This pulls in pieces of drm-next d65d31388a23 ("Merge tag
'drm-misc-next-fixes-2017-11-07' of
git://anongit.freedesktop.org/drm/drm-misc into drm-next")
Signed-off-by: Eric Anholt
---
include/drm/README| 9 +---
include/drm/nouveau_drm.h | 84 +++---
include/dr
The kernel started using the struct from drm.h instead of the typedef.
Signed-off-by: Eric Anholt
---
include/drm/README| 4
include/drm/mga_drm.h | 2 +-
2 files changed, 1 insertion(+), 5 deletions(-)
diff --git a/include/drm/README b/include/drm/README
index 47d80929a8f1..6e12ca4d81
I wanted to update the vc4 header so that I could land some igt
testcases (though I'd much rather just be importing the header into
igt and ditching libdrm). In the process, I cleaned up some other
header deltas to the kernel so that there's less diff for the next
person to look at.
I skipped the
This pulls in pieces of drm-next d65d31388a23
("Merge tag 'drm-misc-next-fixes-2017-11-07' of
git://anongit.freedesktop.org/drm/drm-misc into drm-next")
Signed-off-by: Eric Anholt
---
include/drm/README| 4
include/drm/mga_drm.h | 8
include/drm/nouveau_drm.h | 10 +++
This pulls in pieces of drm-next d65d31388a23
("Merge tag 'drm-misc-next-fixes-2017-11-07' of
git://anongit.freedesktop.org/drm/drm-misc into drm-next")
Signed-off-by: Eric Anholt
---
include/drm/mga_drm.h| 2 +-
include/drm/qxl_drm.h| 2 +-
include/drm/savage_drm.h | 10 +-
3
This updates the header with the contents from drm-next d65d31388a23
("Merge tag 'drm-misc-next-fixes-2017-11-07' of
git://anongit.freedesktop.org/drm/drm-misc into drm-next")
Signed-off-by: Eric Anholt
---
include/drm/vc4_drm.h | 47 ---
1 file change
Fixed in 9433b702fc16 ("headers: Sync drm{,_mode}.h with the kernel")
Signed-off-by: Eric Anholt
---
include/drm/README | 5 -
1 file changed, 5 deletions(-)
diff --git a/include/drm/README b/include/drm/README
index 042cfb1786f2..5b518ddf8f03 100644
--- a/include/drm/README
+++ b/include/d
On Wed, Nov 08, 2017 at 01:40:32PM -0500, Alex Deucher wrote:
> On Wed, Nov 8, 2017 at 1:22 PM, Mark Brown wrote:
> > Like I said in reply to your other mail please don't resubmit already
> > applied patches. The current tip of my topic/amd branch appears to be
> > this very patch, if there's an
On Wed, Nov 8, 2017 at 1:22 PM, Mark Brown wrote:
> On Wed, Nov 08, 2017 at 01:18:41PM -0500, Alex Deucher wrote:
>> From: Guenter Roeck
>>
>> ERROR: "__aeabi_uldivmod" [sound/soc/amd/snd-soc-acp-pcm.ko] undefined!
>>
>> 64-bit divides require special operations to avoid build errors on 32-bit
>>
The patch
ASoC: amd: Make the driver name consistent across files
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) a
On Wed, Nov 08, 2017 at 06:12:34PM +, Deucher, Alexander wrote:
> This didn't not appear to be in your tree yet and I never got any
> confirmation it being
> applied. Apologies.
Ah, sorry - my bad. This was one that I tried to apply but which didn't
apply.
signature.asc
Description: PGP
Am 08.11.2017 um 18:37 schrieb Michel Dänzer:
On 08/11/17 05:41 PM, Christian König wrote:
Am 08.11.2017 um 17:36 schrieb Michel Dänzer:
On 08/11/17 03:59 PM, Christian König wrote:
Instead of having a pointless wrapper or call the underlying ww_mutex
function directly.
Not sure I can agree i
On Wed, Nov 08, 2017 at 01:18:41PM -0500, Alex Deucher wrote:
> From: Guenter Roeck
>
> ERROR: "__aeabi_uldivmod" [sound/soc/amd/snd-soc-acp-pcm.ko] undefined!
>
> 64-bit divides require special operations to avoid build errors on 32-bit
> systems.
Like I said in reply to your other mail please
From: Guenter Roeck
ERROR: "__aeabi_uldivmod" [sound/soc/amd/snd-soc-acp-pcm.ko] undefined!
64-bit divides require special operations to avoid build errors on 32-bit
systems.
fixes: 61add8147942 (ASoC: amd: Report accurate hw_ptr during dma)
Signed-off-by: Guenter Roeck
Reviewed-on: https://ch
Lothar Waßmann writes:
> Hi,
>
> drivers/gpu/drm/bridge/lvds-encoder.c driver is currently
> dysfunctional due to:
> |commit 13dfc0540a575b47b2d640b093ac16e9e09474f6
> |Author: Eric Anholt
> |Date: Fri Jun 2 13:25:14 2017 -0700
> |
> |drm/bridge: Refactor out the panel wrapper from the lvd
> -Original Message-
> From: Mark Brown [mailto:broo...@kernel.org]
> Sent: Wednesday, November 08, 2017 1:09 PM
> To: Alex Deucher
> Cc: amd-...@lists.freedesktop.org; alsa-de...@alsa-project.org; dri-
> de...@lists.freedesktop.org; Mukunda, Vijendar; lgirdw...@gmail.com;
> ti...@suse.de;
On Wed, Nov 08, 2017 at 12:24:03PM -0500, Alex Deucher wrote:
> regmap_read(regmap, RT5645_VENDOR_ID2, &val);
>
> + /*
> + * Read after 400msec, as it is the interval required between
> + * read and power On.
> + */
> + msleep(TIME_TO_POWER_MS);
> + regmap_read(r
On Wed, Nov 08, 2017 at 12:24:02PM -0500, Alex Deucher wrote:
> From: Akshu Agrawal
>
> This fixes the issue of driver not getting auto loaded with
> MODULE_ALIAS.
Please don't resubmit patches that have already been applied, you should
submit patches against current code in the tree you're expe
On Wed, Nov 08, 2017 at 02:28:23PM +0100, Daniel Vetter wrote:
> On Wed, Nov 08, 2017 at 03:26:15PM +0200, Ville Syrjälä wrote:
> > On Wed, Nov 08, 2017 at 02:11:46PM +0100, Daniel Vetter wrote:
> > > On Wed, Nov 08, 2017 at 03:04:58PM +0200, Ville Syrjälä wrote:
> > > > On Wed, Nov 08, 2017 at 01:
On Wed, Nov 08, 2017 at 12:45:16PM -0500, Alex Deucher wrote:
> On Wed, Nov 8, 2017 at 12:42 PM, Alex Deucher wrote:
> > I'm not familiar with which are chromium specific (TEST, BUG, FIXUP,
> > FROMLIST I guess?). The info seems useful to have in the bug, but I
> > can respin if it's a big deal.
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #297 from Nicola Mori ---
@Mihai I'm using dpm since years on my Mobility 3470 and I only experience
random freezes very rarely. The only thing that's really annoying for me is
this:
https://bugs.freedesktop.org/show_bug.cgi?id=949
On Wed, Nov 8, 2017 at 12:42 PM, Alex Deucher wrote:
> On Wed, Nov 8, 2017 at 12:29 PM, Guenter Roeck wrote:
>> On Wed, Nov 8, 2017 at 9:24 AM, Alex Deucher wrote:
>>>
>>> From: Guenter Roeck
>>>
>>> ERROR: "__aeabi_uldivmod" [sound/soc/amd/snd-soc-acp-pcm.ko] undefined!
>>>
>>> 64-bit divides
https://bugs.freedesktop.org/show_bug.cgi?id=103519
--- Comment #6 from Emil Velikov ---
Send Derek's patch to the list with some ack/rb tags. Modulo any objections
I'll push it in a day or two.
[1] https://patchwork.freedesktop.org/patch/187092/
--
You are receiving this mail because:
You are
On Wed, Nov 8, 2017 at 12:29 PM, Guenter Roeck wrote:
> On Wed, Nov 8, 2017 at 9:24 AM, Alex Deucher wrote:
>>
>> From: Guenter Roeck
>>
>> ERROR: "__aeabi_uldivmod" [sound/soc/amd/snd-soc-acp-pcm.ko] undefined!
>>
>> 64-bit divides require special operations to avoid build errors on 32-bit
>> s
On 08/11/17 05:41 PM, Christian König wrote:
> Am 08.11.2017 um 17:36 schrieb Michel Dänzer:
>> On 08/11/17 03:59 PM, Christian König wrote:
>>> Instead of having a pointless wrapper or call the underlying ww_mutex
>>> function directly.
>> Not sure I can agree it's pointless, since it recently too
From: Guenter Roeck
ERROR: "__aeabi_uldivmod" [sound/soc/amd/snd-soc-acp-pcm.ko] undefined!
64-bit divides require special operations to avoid build errors on 32-bit
systems.
BUG=b:63121716
TEST="Build i386:allmodconfig"
Signed-off-by: Guenter Roeck
Reviewed-on: https://chromium-review.google
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
From: Akshu Agrawal
Minimum time required between power On of codec and read
of RT5645_VENDOR_ID2 is 400msec. We should wait that long
before reading the value.
TEST=Cold boot the device and check for sound device.
Signed-off-by: Akshu Agrawal
Signed-off-by: Bard Liao
Signed-off-by: Alex Deuc
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-stoney2
Thanks!
Alex
v2: - Add a fix f
Am 08.11.2017 um 17:36 schrieb Michel Dänzer:
On 08/11/17 03:59 PM, Christian König wrote:
Instead of having a pointless wrapper or call the underlying ww_mutex
function directly.
Not sure I can agree it's pointless, since it recently took me a while
to realize that unlocking bo->resv is essent
On 08/11/17 03:59 PM, Christian König wrote:
> Instead of having a pointless wrapper or call the underlying ww_mutex
> function directly.
Not sure I can agree it's pointless, since it recently took me a while
to realize that unlocking bo->resv is essentially the same as
unreserving the BO.
Anywa
On Tue, Nov 7, 2017 at 3:13 PM, Arnd Bergmann wrote:
> do_gettimeofday() is deprecated because it is not y2038 safe, so I'm
> changing the calculation for the diagnostic output over to using
> 'timespec64'.
>
> We really only print time deltas here, so changing it to monotonic
> time makes this mo
https://bugs.freedesktop.org/show_bug.cgi?id=103625
--- Comment #5 from Lars Taubert ---
Created attachment 135310
--> https://bugs.freedesktop.org/attachment.cgi?id=135310&action=edit
detailed version of used drm, mesa & xorg software
--
You are receiving this mail because:
You are the assig
https://bugs.freedesktop.org/show_bug.cgi?id=103625
--- Comment #4 from Lars Taubert ---
Created attachment 135309
--> https://bugs.freedesktop.org/attachment.cgi?id=135309&action=edit
xrandr --verbose output
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=103625
--- Comment #3 from Lars Taubert ---
Created attachment 135308
--> https://bugs.freedesktop.org/attachment.cgi?id=135308&action=edit
/etc/X11/xorg.conf.d/01-intel-graphics.conf
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=103625
--- Comment #2 from Lars Taubert ---
Created attachment 135307
--> https://bugs.freedesktop.org/attachment.cgi?id=135307&action=edit
/var/log/Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=103625
--- Comment #1 from Lars Taubert ---
Created attachment 135306
--> https://bugs.freedesktop.org/attachment.cgi?id=135306&action=edit
dmesg output
--
You are receiving this mail because:
You are the assignee for the bug.__
The patch
ASoC: amd: Report accurate hw_ptr during dma
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
https://bugs.freedesktop.org/show_bug.cgi?id=103625
Bug ID: 103625
Summary: Sporadic GPU HANG issue while Java is rendering via
OpenGL
Product: Mesa
Version: 17.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
On Tue, Nov 07, 2017 at 09:34:35PM +0530, Agrawal, Akshu wrote:
> On 11/7/2017 5:07 PM, Mark Brown wrote:
> > > > These two URLs are different, what was being reviewed here? What is
> > > > Commit-Ready supposed to mean?
> Same patch is reviewed, once on 4.4 kernel (659699) and then on 4.12 kern
From: Ville Syrjälä
Apparently some sinks look at the YQ bits even when receiving RGB,
and they get somehow confused when they see a non-zero YQ value.
So we can't just blindly follow CEA-861-F and set YQ to match the
RGB range.
Unfortunately there is no good way to tell whether the sink
designe
Den 06.11.2017 18.32, skrev Philippe CORNU:
Hi Noralf,
On 11/04/2017 02:04 PM, Noralf Trønnes wrote:
Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on
the fact that drm_device holds a pointer to the drm_fb_helper structure.
This means that the driver doesn't have to keep
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Jan Vesely changed:
What|Removed |Added
Depends on||103586
Referenced Bugs:
https://bugs.free
On Wed, Nov 08, 2017 at 11:54:49AM +0100, Daniel Vetter wrote:
> It's useful for syncing async connector work like link retraining.
>
> Cc: Manasi Navare
> Cc: Maarten Lankhorst
> Cc: Ville Syrjälä
> Signed-off-by: Daniel Vetter
> ---
> drivers/gpu/drm/drm_atomic_helper.c | 8 +++-
> 1 fi
Den 08.11.2017 13.21, skrev Benjamin Gaignard:
2017-11-04 14:04 GMT+01:00 Noralf Trønnes :
Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on
the fact that drm_device holds a pointer to the drm_fb_helper structure.
This means that the driver doesn't have to keep track of th
Deleted BOs with the same reservation object can be reaped even if they
can't be reserved.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 35 +++
1 file changed, 27 insertions(+), 8 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drive
Needed for the next patch.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 52
1 file changed, 28 insertions(+), 24 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
index 6f55310a9d09..d23592cfe4
Instead of having a pointless wrapper or call the underlying ww_mutex
function directly.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 13 +++--
drivers/gpu/drm/ttm/ttm_execbuf_util.c | 8
include/drm/ttm/ttm_bo_driver.h| 14 +-
Needed for the next patch and makes the code quite a bit easier to
understand.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
index c088703777e2..9
https://bugs.freedesktop.org/show_bug.cgi?id=92248
--- Comment #44 from Hector Velazquez
---
This test continue failing on CFL QA
igt@kms_plane_scaling
This is my configuration:
==
Graphic stack
==
Component: drm
2017-11-08 14:04 GMT+01:00 Benjamin Gaignard :
> Drivers are registered on platform bus so the private list
> could be replace by a call to of_find_device_by_node().
> Changing this also makes dev, np and link fields useless
> in vtg structure.
>
> Signed-off-by: Benjamin Gaignard
Merge in drm-mi
2017-11-08 14:06 GMT+01:00 Benjamin Gaignard :
> vtg_remove does nothing just remove it
>
> Signed-off-by: Benjamin Gaignard
Merge in drm-misc-next with Daniel's irc ack
> ---
> drivers/gpu/drm/sti/sti_vtg.c | 6 --
> 1 file changed, 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/sti/sti_v
On Wed, Nov 08, 2017 at 03:26:15PM +0200, Ville Syrjälä wrote:
> On Wed, Nov 08, 2017 at 02:11:46PM +0100, Daniel Vetter wrote:
> > On Wed, Nov 08, 2017 at 03:04:58PM +0200, Ville Syrjälä wrote:
> > > On Wed, Nov 08, 2017 at 01:57:50PM +0100, Daniel Vetter wrote:
> > > > Two bits:
> > > > - check a
On Wed, Nov 08, 2017 at 02:11:46PM +0100, Daniel Vetter wrote:
> On Wed, Nov 08, 2017 at 03:04:58PM +0200, Ville Syrjälä wrote:
> > On Wed, Nov 08, 2017 at 01:57:50PM +0100, Daniel Vetter wrote:
> > > Two bits:
> > > - check actual atomic state, the legacy stuff can only be looked at
> > > from w
Op 08-11-17 om 14:04 schreef Ville Syrjälä:
> On Wed, Nov 08, 2017 at 01:57:50PM +0100, Daniel Vetter wrote:
>> Two bits:
>> - check actual atomic state, the legacy stuff can only be looked at
>> from within the atomic_commit_tail function, since it's only
>> protected by ordering and not by an
On Wed, Nov 08, 2017 at 03:04:58PM +0200, Ville Syrjälä wrote:
> On Wed, Nov 08, 2017 at 01:57:50PM +0100, Daniel Vetter wrote:
> > Two bits:
> > - check actual atomic state, the legacy stuff can only be looked at
> > from within the atomic_commit_tail function, since it's only
> > protected by
vtg_remove does nothing just remove it
Signed-off-by: Benjamin Gaignard
---
drivers/gpu/drm/sti/sti_vtg.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/gpu/drm/sti/sti_vtg.c b/drivers/gpu/drm/sti/sti_vtg.c
index 5f75aea..3aa2fa6 100644
--- a/drivers/gpu/drm/sti/sti_vtg.c
+++ b
Drivers are registered on platform bus so the private list
could be replace by a call to of_find_device_by_node().
Changing this also makes dev, np and link fields useless
in vtg structure.
Signed-off-by: Benjamin Gaignard
---
drivers/gpu/drm/sti/Kconfig | 1 +
drivers/gpu/drm/sti/sti_vtg.c |
On Wed, Nov 08, 2017 at 01:57:50PM +0100, Daniel Vetter wrote:
> Two bits:
> - check actual atomic state, the legacy stuff can only be looked at
> from within the atomic_commit_tail function, since it's only
> protected by ordering and not by any locks.
>
> - Make sure we don't wreak the work
Hi Dave,
drm-misc-next-fixes-2017-11-08:
4.15 merge window fixes, round 2:
randconfig fix from Arnd, plus the vblank WARN_ON fix from Ville.
Right away a new pull request because somehow Ville's fix was stuck for a
bit too long and everyone forgot :-( And I didn't notice because i915
isn't affec
Two bits:
- check actual atomic state, the legacy stuff can only be looked at
from within the atomic_commit_tail function, since it's only
protected by ordering and not by any locks.
- Make sure we don't wreak the work an ongoing nonblocking commit is
doing.
v2: We need the crtc lock too, b
1 - 100 of 131 matches
Mail list logo
