do I also need to push to our local tree ?
No, I only push to the master branch all the time as well.
AMD local trees are only cherry picked from upstream as far as I know.
Regards,
Christian.
Am 16.11.2017 um 06:06 schrieb Andrey Grodzovsky:
Pushed to master branch of git.freedesktop.org/git/
On Wed, Nov 15, 2017 at 03:19:39PM +0100, Noralf Trønnes wrote:
> This patchset adds drm_fb_cma_fbdev_init/fini() functions that replaces
> drm_fbdev_cma_init/fini(). The reason for doing so is to get rid of
> struct drm_fbdev_cma and it's wrapper functions. The final piece will
> happen when tinyd
On 15.11.2017 21:26, Eric Anholt wrote:
> I'm happy to have the DSI panel finally working on VC4 (just waiting on
> https://lists.freedesktop.org/archives/dri-devel/2017-October/156407.html),
> but now I've got another problem to solve. It would be great if I could
> include the DSI panel in our u
Hi Inki,
On 2017-11-14 00:46, Inki Dae wrote:
2017년 11월 13일 23:28에 Marek Szyprowski 이(가) 쓴 글:
On 2017-11-13 02:24, Inki Dae wrote:
2017년 11월 10일 16:35에 Marek Szyprowski 이(가) 쓴 글:
On 2017-11-10 04:04, Inki Dae wrote:
2017년 11월 01일 01:28에 Marek Szyprowski 이(가) 쓴 글:
When no IOMMU is available,
On Wed, 15 Nov 2017, Tuncer Ayaz wrote:
> I don't follow why you think it's a different platform and how I might
> have "more" definitely shown v4.1 to be good, but I'll trust your
> judgement as a drm dev and not argue :).
You apparently have Sandy Bridge, the referenced reports are about
Broadw
pushed to drm-misc-next.
在 2017/11/14 19:27, Sandy Huang 写道:
The following patch add support RK3126 vop support, there is only one
VOP at RK3126, and the RK3126 VOP register layout is similar with RK3036,
so some feature can reuse with RK3036.
Sandy Huang (2):
dt-bindings: add document for r
On 16/11/17 10:50, 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
> ---
> -MODULE_ALIAS("spi:toppoly,td028ttec1");
> +MODULE_ALIAS("spi:t
On 09.11.2017 11:28, Marek Szyprowski wrote:
> The maximum pixel clock depends on the version of the connected MHL
> adapter. Add mode_valid callback to filter out modes with too high pixel
> clock to avoid failure in mode_fixup later.
>
> Signed-off-by: Marek Szyprowski
Queued to drm-misc-next.
On 09.11.2017 11:53, Maciej Purski wrote:
> If the sink device is in HDMI mode, enable infoframe interrupt in scdt
> irq handle function else call start_video function immediately, because
> in DVI mode, there is no infoframe interrupt provided.
>
> Rename start_hdmi function to start_video and get
On Wed, Nov 15, 2017 at 11:59 PM, Linus Torvalds
wrote:
> On Wed, Nov 15, 2017 at 6:34 PM, Dave Airlie wrote:
>>
>> There is some code touched on sound/soc, but I think the sound tree
>> should have the same commits from the same base,so this may luck different
>> if you pulled it as I generated
Hi!
Here's a port of the PowerVR Rogue GPU driver for the Acer Chromebook R13,
taken from the Chrome OS 3.18 vendor kernel. It does not really work ATM,
but it's not completely dysfunctional either. Run
https://github.com/uli/bogocube twenty times, and it will work correctly
once or twice. The mos
Signed-off-by: Ulrich Hecht
---
drivers/gpu/drm/img-rogue/1.6/osfunc.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/img-rogue/1.6/osfunc.c
b/drivers/gpu/drm/img-rogue/1.6/osfunc.c
index 2631357..7a9255b0 100644
--- a/drivers/gpu/drm/img-rogue/1.6/osfunc.c
Required for sched_clock()
Signed-off-by: Ulrich Hecht
---
drivers/gpu/drm/img-rogue/1.6/osfunc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/img-rogue/1.6/osfunc.c
b/drivers/gpu/drm/img-rogue/1.6/osfunc.c
index 7a9255b0..4481381 100644
--- a/drivers/gpu/drm/img-rogue/1.
Signed-off-by: Ulrich Hecht
---
drivers/gpu/drm/Kconfig | 2 ++
drivers/gpu/drm/Makefile | 2 ++
drivers/gpu/drm/img-rogue/Kconfig | 1 +
3 files changed, 5 insertions(+)
diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
index 83cb2a8..492188f 100644
--- a/drivers
In the case where the bind gets deferred we would end up with a
un-balanced runtime PM enable call.
Fix this by simply moving the pm_runtime_enable call to the end of
the bind function when all paths have succeeded.
Signed-off-by: Mirza Krak
---
Changes in v2:
- typos in commit message
driver
Signed-off-by: Ulrich Hecht
---
drivers/gpu/drm/img-rogue/1.6/osfunc_arm64.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/img-rogue/1.6/osfunc_arm64.c
b/drivers/gpu/drm/img-rogue/1.6/osfunc_arm64.c
index 84ae224..091806d 100644
--- a/drivers/gpu/drm
Hi Lucas,
As we discussed on ELCE last month in Prague we have Vivante GPU
built-in our new ARC HSDK development board.
And even though [thanks to your suggestions] I got Etnaviv driver
working perfectly fine on our board I faced one quite a tricky
situation [which I dirty worked-around for now].
Has a struct devfreq pointer now.
Signed-off-by: Ulrich Hecht
---
drivers/gpu/drm/img-rogue/1.6/mt8173/mt8173_sysconfig.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/img-rogue/1.6/mt8173/mt8173_sysconfig.c
b/drivers/gpu/drm/img-rogue/1.6/mt8173/mt81
V2:
* replaced patch to fix DSI VDDS for OMAP3 by equivalent patch from Laurent
Pinchart
* keep previous compatibility option in panel driver to handle older device
tree binaries
2017-11-08 22:09:36:
This patch set fixes vendor names of the panels
and fixes a problem on omapdrm with enabling
VDD
Vendor string is "tpo" and not "toppoly".
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap3-gta04.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi
b/arch/arm/boot/dts/omap3-gta04.dtsi
index 4504908c23fe..ec27ed67a22a 10064
> Am 16.11.2017 um 13:32 schrieb Tomi Valkeinen :
>
> On 16/11/17 10:50, 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
>> ---
>
>
Signed-off-by: Ulrich Hecht
---
drivers/gpu/drm/img-rogue/1.6/pmr_os.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/img-rogue/1.6/pmr_os.c
b/drivers/gpu/drm/img-rogue/1.6/pmr_os.c
index 595f772..9526359 100644
--- a/drivers/gpu/drm/img-rogue/1.6/pmr_os.c
++
On Tue, Nov 14, 2017 at 07:48:09PM +, Daniel Thompson wrote:
> On 14/11/17 18:05, Johan Hovold wrote:
> > On Mon, Nov 13, 2017 at 02:16:09PM +, Daniel Thompson wrote:
> >> On 13/11/17 10:20, Johan Hovold wrote:
> >>> Fix child-node lookup during probe, which ended up searching the whole
> >
From: Laurent Pinchart
Commit d178e034d565 ("drm: omapdrm: Move FEAT_DPI_USES_VDDS_DSI feature
to dpi code") replaced usage of platform data version with SoC matching
to configure DPI VDDS. The SoC match entries were incorrect, they should
have matched on the machine name instead of the SoC famil
On 11/15/17, Jani Nikula wrote:
> The freedesktop.org bugs you reference are for rather different
> platforms than yours. There's nothing there to indicate v4.1 being
> the last known good kernel like for you. There is no exact same
> report.
I don't follow why you think it's a different platfor
Fixes "BUG: sleeping function called from invalid context".
Signed-off-by: Ulrich Hecht
---
drivers/gpu/drm/img-rogue/1.6/pvr_dvfs_device.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/gpu/drm/img-rogue/1.6/pvr_dvfs_device.c
b/drivers/gpu/drm/img-rogue/1.6/pvr_dvfs_device.c
Signed-off-by: Ulrich Hecht
---
drivers/gpu/drm/img-rogue/1.6/pvr_uaccess.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/img-rogue/1.6/pvr_uaccess.h
b/drivers/gpu/drm/img-rogue/1.6/pvr_uaccess.h
index 53c8f0a..aab7eba 100644
--- a/drivers/gpu/drm/img-rogue/
Hi,
Any ideas on this issue? Are there any additional tests I can perform
to help debug this?
On 2017-11-05 11:41 -0500, Nick Bowler wrote:
> I completed bisecting this issue. See below.
>
> On 2017-11-02, Nick Bowler wrote:
> > ~50% of the time after a hotplug, there is a vertical pink bar o
Use drm_dev_alloc(), drm_dev_register() and remove the .load and .unload
methods from drm_driver.
Signed-off-by: Ulrich Hecht
---
drivers/gpu/drm/img-rogue/1.6/mt8173/mtk_module.c | 14 +++--
drivers/gpu/drm/img-rogue/1.6/pvr_drm.c | 24 +--
2 files changed,
Includes regulator and operating points definitions.
Signed-off-by: Ulrich Hecht
---
arch/arm64/boot/dts/mediatek/mt8173-oak.dtsi | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173-oak.dtsi
b/arch/arm64/boot/dts/mediatek/mt8173-oak.dtsi
index
We can remove the "omapdss," prefix because the
omapdrm driver takes care of it.
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap3-pandora-common.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-pandora-common.dtsi
b/arch/arm/boot/dt
Signed-off-by: Ulrich Hecht
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 41
1 file changed, 41 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
index f454efa33..43775a6 100644
--- a/arch/arm64/boot
Hi Lucas,
On Wed, 2017-11-15 at 17:44 +0100, Lucas Stach wrote:
> Hi Alexey,
>
> Am Mittwoch, den 15.11.2017, 16:24 + schrieb Alexey Brodkin:
> >
> > Hi Lucas,
> >
> > As we discussed on ELCE last month in Prague we have Vivante GPU
> > built-in our new ARC HSDK development board.
> >
> >
Signed-off-by: Ulrich Hecht
---
drivers/gpu/drm/img-rogue/1.6/physmem_osmem_linux.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/img-rogue/1.6/physmem_osmem_linux.c
b/drivers/gpu/drm/img-rogue/1.6/physmem_osmem_linux.c
index f5353e3..7b55904 100644
--- a/dr
On Wed, Nov 15, 2017 at 02:32:11PM +, Lee Jones wrote:
> On Wed, 15 Nov 2017, Johan Hovold wrote:
>
> > On Tue, Nov 14, 2017 at 07:48:09PM +, Daniel Thompson wrote:
> > > On 14/11/17 18:05, Johan Hovold wrote:
> > > > On Mon, Nov 13, 2017 at 02:16:09PM +, Daniel Thompson wrote:
> > > >
2017-11-15 9:17 GMT+01:00 Mirza Krak :
> In the case of the the binds gets defered we would end up with a
> un-balanced runtime PM enable call.
>
> Fix this by simply moving the pm_runtime_enable call to the end of
> the bind function when all paths have succeeded.
>
> Signed-off-by: Mirza Krak
>
Adds CPU OPP tables for use with the generic cpufreq driver.
Signed-off-by: Ulrich Hecht
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 90
1 file changed, 90 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
b/arch/arm64/boot/dts/mediatek/mt8
No longer required.
Signed-off-by: Ulrich Hecht
---
drivers/gpu/drm/img-rogue/1.6/pvr_drm.c | 10 --
1 file changed, 10 deletions(-)
diff --git a/drivers/gpu/drm/img-rogue/1.6/pvr_drm.c
b/drivers/gpu/drm/img-rogue/1.6/pvr_drm.c
index f72d382..7439a6f 100644
--- a/drivers/gpu/drm/img-ro
https://bugs.freedesktop.org/show_bug.cgi?id=101473
--- Comment #2 from denisgolo...@yandex.ru ---
Same error in dmesg for me. Except that I can boot in graphic mode.
My hardware is XFX Radeon RX580.
desktop64 denis # lspci | grep VG
06:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
Everything "fence..." is now "dma_fence...".
Signed-off-by: Ulrich Hecht
---
drivers/gpu/drm/img-rogue/1.6/pvr_buffer_sync.c | 36 ++---
drivers/gpu/drm/img-rogue/1.6/pvr_fence.c | 70 -
drivers/gpu/drm/img-rogue/1.6/pvr_fence.h | 20 +++
3 files c
Signed-off-by: Ulrich Hecht
---
drivers/gpu/drm/img-rogue/1.6/physmem_dmabuf.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/img-rogue/1.6/physmem_dmabuf.c
b/drivers/gpu/drm/img-rogue/1.6/physmem_dmabuf.c
index 406886f..4fb813f 100644
--- a/drivers/gpu/d
https://bugs.freedesktop.org/show_bug.cgi?id=101473
--- Comment #3 from denisgolo...@yandex.ru ---
Created attachment 135516
--> https://bugs.freedesktop.org/attachment.cgi?id=135516&action=edit
XFX Radeon RX580 dmesg
--
You are receiving this mail because:
You are the assignee for the bug.___
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
---
.../display/panel/{toppoly,td028ttec1.txt => tpo,td028ttec1.txt} | 4 ++--
drivers/gpu/drm/omapdrm/displays/panel-tpo-
https://bugs.freedesktop.org/show_bug.cgi?id=101473
--- Comment #4 from denisgolo...@yandex.ru ---
Tested under Linux 4.13.9 + ck1 patch, Mesa 17.2.5, xf64-video-amdgpu (git
875339c1064f666a2391b4a5a495eddda9407ab6), libdrm-2.4.88.
--
You are receiving this mail because:
You are the assignee for
I think this snuck in when I applied the patch for f97decac5f4c (didn't
apply cleanly, required some manual applying + git-add). It is unused
and shouldn't be here. My bad.
Fixes: f97decac5f4c "drm/msm: Support multiple ringbuffers"
Signed-off-by: Rob Clark
---
include/dt-bindings/msm/msm-bus-
2017-10-30 10:19 GMT+01:00 Daniel Vetter :
> On Tue, Oct 24, 2017 at 11:01:32AM +0200, Benjamin Gaignard wrote:
>> 2017-10-23 17:25 GMT+02:00 Ville Syrjala :
>> > From: Ville Syrjälä
>> >
>> > Since commit 632c6e4edef1 ("drm/vblank: Fix flip event vblank count")
>> > even drivers that don't implem
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä
HDMI 2.0 Appendix F suggest that we should keep sending the infoframe
when switching from 3D to 2D mode, even if the infoframe isn't strictly
necessary (ie. not needed to transmit the VIC or stereo information)
https://bugs.freedesktop.org/show_bug.cgi?id=101473
Alex Deucher changed:
What|Removed |Added
Summary|(SI) latest stable & cant |(SI) latest stable & cant
https://bugs.freedesktop.org/show_bug.cgi?id=101473
--- Comment #5 from Alex Deucher ---
The message:
Invalid PCI ROM header structure: expecting 0xaa55, got 0x
is harmless and can be ignored.
--
You are receiving this mail because:
You are the assignee for the bug.
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä
Appedix F of HDMI 2.0 says that some HDMI sink may fail to switch from
3D to 2D mode in a timely fashion if the source simply stops sending the
HDMI infoframe. The suggested workaround is to keep sending the
in
https://bugs.freedesktop.org/show_bug.cgi?id=101473
--- Comment #6 from denisgolo...@yandex.ru ---
(In reply to Alex Deucher from comment #5)
> The message:
> Invalid PCI ROM header structure: expecting 0xaa55, got 0x
> is harmless and can be ignored.
Ok. Thanks
--
You are receiving this m
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä
commit 6dffd431e229 ("drm: Add aspect ratio parsing in DRM layer")
cause us to not send out any VICs in the AVI infoframes. That commit
was since reverted, but if and when we add aspect ratio handing back
we ne
The hardware has enums for altering the Cr and Cb order,
so use this instead of having a flag which swaps the
order the pointers are presented to the hardware
(that only worked for 3 plane formats anyway).
Explicitly sets .pixel_order in each case, rather than
relying on then default XYCBCR order
These are relatively trivial patches that just expand the
list of formats that the vc4 DRM driver will accept.
RGB888, BGR888, NV21, and NV61 tested with the modetest app from the libdrm
repo. YUV422 and YVU422 can't be as they aren't supported.
Dave Stevenson (3):
drm/vc4: Add support for DRM_F
NV12 (YUV420 2 plane) and NV16 (YUV422 2 plane) were
supported, but NV21 and NV61 (same but with Cb and Cr
swapped) weren't. Add them.
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/vc4_plane.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_plane.c
Filling out the list of supported formats based on those the
hardware can support.
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/vc4_plane.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_plane.c b/drivers/gpu/drm/vc4/vc4_plane.c
index 423a23e..513b4b
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä
If the user mode would specify an aspect ratio other than 4:3 or 16:9
we now silently ignore it. Maybe a better apporoach is to return an
error? Let's try that.
Also we must be careful that we don't try to sen
Line continuations with excess spacing causes unexpected output.
Miscellanea:
o Added missing '\n' to a few of the coalesced pr_ formats
Signed-off-by: Joe Perches
---
drivers/gpu/drm/amd/display/dc/core/dc_link_dp.c | 11 -
.../amd/powerplay/hwmgr/process_pptables_v1_0.c| 6 ++-
Avoid using line continations in formats as that causes unexpected
output.
Joe Perches (4):
rk3399_dmc: Fix line continuation format
drm: amd: Fix line continuation formats
[media] dibx000_common: Fix line continuation format
ima: Fix line continuation format
drivers/devfreq/rk3399_dmc.c
https://bugs.freedesktop.org/show_bug.cgi?id=103175
--- Comment #8 from Andy Furniss ---
It's not OK, I don't know what happened there, maybe I wasn't in the kernel I
thought, though I am not convinced.
Whatever the reason, I can't get it to work now.
--
You are receiving this mail because:
You
On 2017-11-16 10:27 AM, Joe Perches wrote:
> Line continuations with excess spacing causes unexpected output.
>
> Miscellanea:
>
> o Added missing '\n' to a few of the coalesced pr_ formats
>
> Signed-off-by: Joe Perches
> ---
> drivers/gpu/drm/amd/display/dc/core/dc_link_dp.c | 11 ---
On 15 November 2017 at 21:25, Sharma, Deepak wrote:
>>
>> I'd still recommend updating the two functions' documentation, ideally
>> coupled with enforcing for *parent to be non NULL.
>> Could be code as follow-up though.
>>
> If I got it correctly you are referring "Note that for purely virtua
On Thu, 2017-11-16 at 10:38 -0500, Harry Wentland wrote:
> On 2017-11-16 10:27 AM, Joe Perches wrote:
> > Line continuations with excess spacing causes unexpected output.
[]
> > @@ -872,9 +870,8 @@ static bool perform_clock_recovery_sequence(
> > if (retry_count >= LINK_TRAINING_MAX_CR_RETRY) {
On Thu, Nov 16, 2017 at 8:05 AM, Rob Clark wrote:
> I think this snuck in when I applied the patch for f97decac5f4c (didn't
> apply cleanly, required some manual applying + git-add). It is unused
> and shouldn't be here. My bad.
>
> Fixes: f97decac5f4c "drm/msm: Support multiple ringbuffers"
> S
On Thu, Nov 16, 2017 at 03:19:35PM +0100, Benjamin Gaignard wrote:
> 2017-10-30 10:19 GMT+01:00 Daniel Vetter :
> > On Tue, Oct 24, 2017 at 11:01:32AM +0200, Benjamin Gaignard wrote:
> >> 2017-10-23 17:25 GMT+02:00 Ville Syrjala :
> >> > From: Ville Syrjälä
> >> >
> >> > Since commit 632c6e4edef1
On Thu, Nov 16, 2017 at 08:06:18PM +0530, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 11/13/2017 10:34 PM, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > HDMI 2.0 Appendix F suggest that we should keep sending the infoframe
> > when switching from 3D to 2D mode, even if the in
On Thu, Nov 16, 2017 at 08:21:44PM +0530, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 11/13/2017 10:34 PM, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > commit 6dffd431e229 ("drm: Add aspect ratio parsing in DRM layer")
> > cause us to not send out any VICs in the AVI infofra
On Thu, Nov 16, 2017 at 08:31:36PM +0530, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 11/13/2017 10:34 PM, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > If the user mode would specify an aspect ratio other than 4:3 or 16:9
> > we now silently ignore it. Maybe a better apporoa
On Thu, Nov 16, 2017 at 08:10:55PM +0530, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 11/13/2017 10:34 PM, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Appedix F of HDMI 2.0 says that some HDMI sink may fail to switch from
> > 3D to 2D mode in a timely fashion if the source
On Wed, Nov 15, 2017 at 04:44:54PM +, alexander.le...@verizon.com wrote:
> On Wed, Nov 15, 2017 at 01:08:05PM +0200, Ville Syrjälä wrote:
> >On Wed, Nov 15, 2017 at 02:45:43AM +, alexander.le...@verizon.com wrote:
> >> From: Ville Syrjälä
> >>
> >> [ Upstream commit 1be4d3793d5a93daddcd9
On Wed, Nov 15, 2017 at 06:02:59PM +, Jose Abreu wrote:
> Hi Ville,
>
> On 15-11-2017 15:49, Ville Syrjala wrote:
> >
> > +#define DRM_MODE_FLAG_ALL (DRM_MODE_FLAG_PHSYNC | \
> > +DRM_MODE_FLAG_NHSYNC | \
> > +DRM_MODE_
On Mon, Nov 13, 2017 at 10:47:00AM +0200, Laurent Pinchart wrote:
> Unlike the KMS API, the hardware doesn't support planes exceeding the
> screen boundaries or planes being located fully off-screen. We need to
> clip plane coordinates to support the use case.
>
> Fortunately the DRM core offers t
On 16/11/17 05:59 AM, Linus Torvalds wrote:
>
> There's something odd about drm people. You guys like these completely
> insane generated header files, and you seem to be populating the whole
> tree with this odd and diseased notion of "generated header files are
> cool".
>
> Is somebody getting
On Thu, 2017-11-16 at 12:11 -0500, Mimi Zohar wrote:
> On Thu, 2017-11-16 at 07:27 -0800, Joe Perches wrote:
> > Avoid using line continations in formats as that causes unexpected
> > output.
>
> Is having lines greater than 80 characters the preferred method?
yes.
> Could you add quotes before
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: be1e8b7c9bbedf5963f9573bcd9cb9ba5046c50d
commit: 1cfd8e237f0318e330190ac21d63c58ae6a1f66c [1458/1474] drm/amdgpu:cleanup
GMC & gart garbage function
config: i386-randconfig-s0-201746 (attached as .config)
compiler:
https://bugs.freedesktop.org/show_bug.cgi?id=103783
Bug ID: 103783
Summary: atombios stuck in loop for more than 5secs
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=103783
--- Comment #1 from Rene Barbosa ---
Created attachment 135525
--> https://bugs.freedesktop.org/attachment.cgi?id=135525&action=edit
lspci
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=103783
--- Comment #2 from Rene Barbosa ---
Created attachment 135526
--> https://bugs.freedesktop.org/attachment.cgi?id=135526&action=edit
modules
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=103783
Alex Deucher changed:
What|Removed |Added
Attachment #135524|application/x-desktop |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=103783
--- Comment #3 from Alex Deucher ---
(In reply to Rene Barbosa from comment #0)
> Created attachment 135524 [details]
> dmesg
Looks like you attached the wrong file. Please attach your full dmesg output.
--
You are receiving this mail becaus
https://bugs.freedesktop.org/show_bug.cgi?id=103783
Rene Barbosa changed:
What|Removed |Added
Attachment #135524|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=103783
--- Comment #5 from Rene Barbosa ---
Err. Sorry about that.
I've uploaded the correct file now.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri
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
https://bugs.freedesktop.org/show_bug.cgi?id=103783
--- Comment #6 from Rene Barbosa ---
An interesting information: It's only with open source amdgpu driver. With
amdgpu-pro it's not happening but this driver isn't compatible with Ubuntu
17.10.
--
You are receiving this mail because:
You are t
Den 16.11.2017 09.14, skrev Shawn Guo:
On Wed, Nov 15, 2017 at 03:19:39PM +0100, Noralf Trønnes wrote:
This patchset adds drm_fb_cma_fbdev_init/fini() functions that replaces
drm_fbdev_cma_init/fini(). The reason for doing so is to get rid of
struct drm_fbdev_cma and it's wrapper functions. The
Andrzej Hajda writes:
> On 15.11.2017 21:26, Eric Anholt wrote:
>> I'm happy to have the DSI panel finally working on VC4 (just waiting on
>> https://lists.freedesktop.org/archives/dri-devel/2017-October/156407.html),
>> but now I've got another problem to solve. It would be great if I could
>>
On 16 November 2017 at 14:59, Linus Torvalds
wrote:
> On Wed, Nov 15, 2017 at 6:34 PM, Dave Airlie wrote:
>>
>> There is some code touched on sound/soc, but I think the sound tree
>> should have the same commits from the same base,so this may luck different
>> if you pulled it as I generated my p
On Thu, Nov 16, 2017 at 12:57 PM, Dave Airlie wrote:
>
> This sounds more like a Monty Python sketch than a serious question.
It's a serious question when the files start appearing in random
places where they don't belong.
There's a place for automatically generated files.
But that "there is a
https://bugs.freedesktop.org/show_bug.cgi?id=102985
--- Comment #3 from invergo ---
I'm now on drm-next-amd-dc-staging commit 4479ed411cf4. I can see in my logs
that all of the modes in my TV's EDID are being detected. GDM launches at
1920x1080 as usual, but when I try to log in, all video outpu
Signed-off-by: Jan Vesely
---
drivers/gpu/drm/amd/amdkfd/kfd_kernel_queue_vi.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_kernel_queue_vi.c
b/drivers/gpu/drm/amd/amdkfd/kfd_kernel_queue_vi.c
index f1d48281e322..b3bee39661ab 100644
---
On Wed, Nov 15, 2017 at 10:45 AM, Colin King wrote:
> From: Colin Ian King
>
> Use kcalloc instead of kzalloc and the cast on the return from kzalloc is
> unnecessary and can be removed.
>
> Signed-off-by: Colin Ian King
Reviewed and pushed.
Thanks!
Alex
> ---
> drivers/gpu/drm/amd/display/
https://bugs.freedesktop.org/show_bug.cgi?id=102985
--- Comment #4 from invergo ---
Sorry, I should have attached that in a file.
Just before those kernel errors were these:
Nov 16 21:23:21 jackalope gnome-shell[1020]: JS WARNING:
[resource:///org/gnome/shell/ui/modalDialog.js 218]: reference t
On Wed, Nov 15, 2017 at 4:37 AM, Arnd Bergmann wrote:
> An otherwise correct cleanup patch from Dan Carpenter turned a broken
> failure handling from a feature patch by Hans Verkuil into a kernel
> Oops, so bisection points to commit 7af35b0addbc ("drm/kirin: Checking
> for IS_ERR() instead of NUL
On Thu, Nov 16, 2017 at 1:50 PM, John Stultz wrote:
> On Wed, Nov 15, 2017 at 4:37 AM, Arnd Bergmann wrote:
>> An otherwise correct cleanup patch from Dan Carpenter turned a broken
>> failure handling from a feature patch by Hans Verkuil into a kernel
>> Oops, so bisection points to commit 7af35b
On Thu, Nov 16, 2017 at 2:20 PM, John Stultz wrote:
> On Thu, Nov 16, 2017 at 1:50 PM, John Stultz wrote:
>> On Wed, Nov 15, 2017 at 4:37 AM, Arnd Bergmann wrote:
>>> An otherwise correct cleanup patch from Dan Carpenter turned a broken
>>> failure handling from a feature patch by Hans Verkuil i
From: Arnd Bergmann
An otherwise correct cleanup patch from Dan Carpenter turned a broken
failure handling from a feature patch by Hans Verkuil into a kernel
Oops, so bisection points to commit 7af35b0addbc ("drm/kirin: Checking
for IS_ERR() instead of NULL") rather than 3b1b975003e4 ("drm:
adv75
https://bugs.freedesktop.org/show_bug.cgi?id=102800
--- Comment #13 from higu...@gmx.net ---
Can you give me any pointer how to "call the ACPI _PR3 method"?
i already install acpi_call, but have no idea how to use it
--
You are receiving this mail because:
You are the assignee for the bug._
Regards
Shashank
On 11/16/2017 9:46 PM, Ville Syrjälä wrote:
On Thu, Nov 16, 2017 at 08:06:18PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä
HDMI 2.0 Appendix F suggest that we should keep sending the infoframe
when swi
Regards
Shashank
On 11/16/2017 9:51 PM, Ville Syrjälä wrote:
On Thu, Nov 16, 2017 at 08:10:55PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä
Appedix F of HDMI 2.0 says that some HDMI sink may fail to switch from
3D to 2
Regards
Shashank
On 11/16/2017 9:53 PM, Ville Syrjälä wrote:
On Thu, Nov 16, 2017 at 08:21:44PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä
commit 6dffd431e229 ("drm: Add aspect ratio parsing in DRM layer")
cause us to
1 - 100 of 112 matches
Mail list logo
