On Mon, Jun 3, 2019 at 4:40 AM Rob Clark wrote:
>
> On Fri, May 10, 2019 at 7:35 AM Rob Clark wrote:
> >
> > On Tue, Dec 4, 2018 at 2:29 PM Rob Herring wrote:
> > >
> > > On Sat, Dec 1, 2018 at 10:54 AM Rob Clark wrote:
> > > >
> > > > This solves a problem we see with drm/msm, caused by
Hi,
This serie aims at adding the support for slave pipeline on Komeda
driver. Also adds drop_master to shutdown the device and make sure
all the komeda resources shared between crtcs have been released.
This patch series depends on:
- https://patchwork.freedesktop.org/series/58710/
-
The komeda internal resources (pipelines) are shared between crtcs,
and resources release by disable_crtc. This commit is working for once
user forgot disabling crtc like app quit abnomally, and then the
resources can not be used by another crtc. Adds drop_master to
shutdown the device and make
One crtc can use two komeda_pipeline, and one works as master and as
slave. the slave pipeline doesn't have its own output and timing
ctrlr, but pre-composite the input layer data flow and then feed the
result to master. the pipeline configuration like:
slave-layer-0 \
...slave->CU
On Sat, Jun 1, 2019 at 9:26 AM Jitao Shi wrote:
> --- a/drivers/gpu/drm/mediatek/mtk_dsi.c
> +++ b/drivers/gpu/drm/mediatek/mtk_dsi.c
> @@ -1045,12 +1045,6 @@ static int mtk_dsi_bind(struct device *dev, struct
> device *master, void *data)
> return ret;
> }
>
> -
On Thu, May 30, 2019 at 03:31:05PM +0200, Janusz Krzysztofik wrote:
> In order to support driver hot unbind, some cleanup operations, now
> performed on PCI driver remove, must be called later, after all device
> file descriptors are closed.
>
> Split out those operations from the tail of
On Mon, Jun 3, 2019 at 3:59 PM Amadeusz Sławiński
wrote:
>
> On Mon, 3 Jun 2019 12:32:46 +0800
> Cheng-Yi Chiang wrote:
>
> > From: Philipp Zabel
> >
> > Use HDMI connection / disconnection notifications to update an ALSA
> > jack object. Also make a copy of the ELD block after every change.
>
https://bugs.freedesktop.org/show_bug.cgi?id=110822
Bug ID: 110822
Summary: booting with kernel version 5.1.0 or higher on RX 580
hangs
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux
https://bugs.freedesktop.org/show_bug.cgi?id=110813
Yury Zhuravlev changed:
What|Removed |Added
Summary|Vega hung on Surviving Mars |Vega hang on Surviving Mars
On Sun, Jun 2, 2019 at 11:25 PM Tomasz Figa wrote:
>
> On Mon, Jun 3, 2019 at 4:40 AM Rob Clark wrote:
> >
> > On Fri, May 10, 2019 at 7:35 AM Rob Clark wrote:
> > >
> > > On Tue, Dec 4, 2018 at 2:29 PM Rob Herring wrote:
> > > >
> > > > On Sat, Dec 1, 2018 at 10:54 AM Rob Clark wrote:
> > >
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #33 from Tom B ---
is this likely to be fixed in 5.2 or before? It's a showstopping bug for those
affected.
--
You are receiving this mail because:
You are the assignee for the bug.___
On 2019-05-21 9:52 a.m., Daniel Vetter wrote:
> On Tue, May 21, 2019 at 8:55 AM Pekka Paalanen wrote:
>> On Mon, 20 May 2019 18:11:07 +0200
>> Daniel Vetter wrote:
>>
>>> There's also a fairly easy fix for that -modesetting issue: We don't
>>> expose atomic if the compositor has a process name
https://bugs.freedesktop.org/show_bug.cgi?id=110823
--- Comment #1 from CI Bug Log ---
The CI Bug Log issue associated to this bug has been updated.
### New filters associated
* VEGA M: igt@amdgpu/amd_basic@userptr - fail - Failed assertion: r == 0
-
https://bugs.freedesktop.org/show_bug.cgi?id=110781
--- Comment #11 from Richard Thier ---
Slowdown cause is found when bisecting:
8b3a257851905ff444d981e52938cbf2b36ba830 is the first bad commit
commit 8b3a257851905ff444d981e52938cbf2b36ba830
Author: Marek Olšák
Date: Tue Jul 18 16:08:44
https://bugs.freedesktop.org/show_bug.cgi?id=110823
Martin Peres changed:
What|Removed |Added
Assignee|intel-gfx-bugs@lists.freede |dri-devel@lists.freedesktop
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Daniel
>Vetter
>Sent: Monday, June 3, 2019 1:53 PM
>To: Shankar, Uma
>Cc: Sean Paul ; linux-fb...@vger.kernel.org;
>dcasta...@chromium.org; jo...@kwiboo.se; Maxime Ripard
>;
On Thu, May 30, 2019 at 10:40:09AM +0100, Chris Wilson wrote:
> Quoting Janusz Krzysztofik (2019-05-30 10:24:26)
> > In order to support driver hot unbind, some cleanup operations, now
> > performed on PCI driver remove, must be called later, after all device
> > file descriptors are closed.
> >
On Thu, May 30, 2019 at 01:29:02AM +0530, Uma Shankar wrote:
> Fixes the following warnings:
> ./include/drm/drm_mode_config.h:841: warning: Incorrect use of
> kernel-doc format: * hdr_output_metadata_property: Connector
> property containing hdr
> ./include/drm/drm_mode_config.h:918:
On Thu, May 30, 2019 at 01:29:04AM +0530, Uma Shankar wrote:
> Dropped static functions from kernel documentation.
>
> Suggested-by: Daniel Vetter
> Signed-off-by: Uma Shankar
> ---
> drivers/video/hdmi.c | 32
> 1 file changed, 16 insertions(+), 16
Print display controller hardware version in debug mode only.
Signed-off-by: Yannick Fertré
---
drivers/gpu/drm/stm/ltdc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/stm/ltdc.c b/drivers/gpu/drm/stm/ltdc.c
index a40870b..2fe6c4a 100644
---
On 6/3/19 10:09 AM, Daniel Vetter wrote:
> On Mon, Jun 03, 2019 at 09:45:49AM +0200, Hans Verkuil wrote:
>> On 6/3/19 6:32 AM, Cheng-Yi Chiang wrote:
>>> From: Hans Verkuil
>>>
>>> Add support for HDMI hotplug and EDID notifiers, which is used to convey
>>> information from HDMI drivers to their
On Mon, Jun 3, 2019 at 4:47 PM Christoph Hellwig wrote:
>
> If you (and a few others actors in the thread) want people to actually
> read what you wrote please follow proper mailing list ettiquette. I've
> given up on reading all the recent mails after scrolling through two
> pages of full
On Thu, May 30, 2019 at 05:04:20PM +0200, Christian König wrote:
> Am 29.05.19 um 21:36 schrieb Daniel Vetter:
> > On Wed, May 29, 2019 at 04:43:45PM +, Grodzovsky, Andrey wrote:
> > > I don't, sorry.
> > Should we fix that? Seems like you do plenty of scheduler stuff, so would
> > make sense
On Tue, May 21, 2019 at 12:07:12PM +0300, Pekka Paalanen wrote:
> On Tue, 21 May 2019 10:48:49 +0200
> Daniel Vetter wrote:
>
> > With Eric's patch
> >
> > commit ba6e798ecf320716780bb6a6088a8d17dcba1d49
> > Author: Eric Anholt
> > Date: Wed Apr 24 11:56:17 2019 -0700
> >
> > drm/doc:
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #25 from Matt Coffin ---
(In reply to Mauro Gaspari from comment #24)
> Hi, a bit frustrating eh? :)
> I have been asking around and it seems that RadeonVII and RX590 do not
> suffer those issues. Probably related to default clock
pick the series up in any case, and I'll test it
> > when I get the kernel booting.
>
> Great good to have these merged finally :)
>
> Hmm I wonder if some x15 models are affected by the SoC variant
> changes queued in my fixes branc
https://bugzilla.kernel.org/show_bug.cgi?id=202445
jaapbuur...@gmail.com changed:
What|Removed |Added
CC||jaapbuur...@gmail.com
---
On 03/06/2019 11:47, Rob Clark wrote:
On Sun, Jun 2, 2019 at 11:25 PM Tomasz Figa wrote:
On Mon, Jun 3, 2019 at 4:40 AM Rob Clark wrote:
On Fri, May 10, 2019 at 7:35 AM Rob Clark wrote:
On Tue, Dec 4, 2018 at 2:29 PM Rob Herring wrote:
On Sat, Dec 1, 2018 at 10:54 AM Rob Clark
On Fri, May 31, 2019 at 08:46:58AM -0700, Eric Anholt wrote:
> Boris Brezillon writes:
>
> > Right now, the BO is mapped as a cached region when ->vmap() is called
> > and the underlying object is not a dmabuf.
> > Doing that makes cache management a bit more complicated (you'd need
> > to call
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index be768afa..64f0d5b1 100644
--- a/meson.build
+++ b/meson.build
@@ -248,7 +248,7 @@ if prog_xslt.found()
endif
with_man_pages = with_man_pages != 'false' and prog_xslt.found() and
On Mon, 3 Jun 2019 12:32:46 +0800
Cheng-Yi Chiang wrote:
> From: Philipp Zabel
>
> Use HDMI connection / disconnection notifications to update an ALSA
> jack object. Also make a copy of the ELD block after every change.
>
> This was posted by Philipp Zabel at
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=110803
diplosa...@gmail.com changed:
What|Removed |Added
CC||mezin.alexan...@gmail.com
---
On Thu, May 30, 2019 at 01:29:01AM +0530, Uma Shankar wrote:
> Drop a redundant and unused variable "hdr_output_metadata" from
> drm_connector.
>
> Suggested-by: Daniel Vetter
> Signed-off-by: Uma Shankar
For next time around: Please add Fixes: lines to indicate which already
merged commit
https://bugs.freedesktop.org/show_bug.cgi?id=110807
diplosa...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Thu, May 30, 2019 at 01:29:03AM +0530, Uma Shankar wrote:
> Fixed doc warnings in drm uapi header. All the UAPI
> structures are now documented in kernel doc.
>
> Signed-off-by: Uma Shankar
Applied, thanks for the patch.
Long-term there's obviously a lot more to do here, but this at least
https://bugs.freedesktop.org/show_bug.cgi?id=110822
--- Comment #1 from Gobinda Joy ---
I've tested kernel version from 5.1.0 to the latest git all shows similar
problems.
For the 5.2 git versions when using amdgpu.dpm=0 command line the following
error occurs:
kernel: [drm] amdgpu kernel
Hi Daniel,
On Mon, 3 Jun 2019 09:31:03 +0200 Daniel Vetter wrote:
>
> drm.git too I guess?
No, I fetch that from git://git.freedesktop.org/ which seems to answer.
> But yeah fd.o anongit keeled over over the w/e :-( Admins not yet awake,
> so can't tell you what's up.
No worries, I will just
On Sunday, 2 June 2019 20:44:53 CEST Sam Ravnborg wrote:
> > Signed-off-by: Paul Cercueil
>
> This driver is authored by Maarten ter Huurne
> as well as you.
> Could you get a s-o-b or at least some other formal
> attribution of Maarten in the changelog.
This is based on a driver I wrote for
On Tue, May 28, 2019 at 05:12:32PM +0300, Laurent Pinchart wrote:
> Add the new renesas,companion property to the LVDS0 node to point to the
> companion LVDS encoder LVDS1.
>
> Signed-off-by: Laurent Pinchart
> Reviewed-by: Jacopo Mondi
> Tested-by: Jacopo Mondi
Hi Laurent,
is this patch
Le 30/05/2019 à 01:23, Mauro Carvalho Chehab a écrit :
Sphinx doesn't like orphan documents:
Documentation/accelerators/ocxl.rst: WARNING: document isn't included in
any toctree
Documentation/arm/stm32/overview.rst: WARNING: document isn't included in
any toctree
On Mon, Jun 03, 2019 at 11:04:03AM +1000, Stephen Rothwell wrote:
> Hi Stephen,
>
> On Mon, 3 Jun 2019 08:20:51 +1000 Stephen Rothwell
> wrote:
> >
> > Hi all,
> >
> > Trying to fetch the drm-intel-fixes tree today gives me this error:
> >
> >
On 6/3/19 6:32 AM, Cheng-Yi Chiang wrote:
> From: Hans Verkuil
>
> Add support for HDMI hotplug and EDID notifiers, which is used to convey
> information from HDMI drivers to their CEC and audio counterparts.
>
> Based on an earlier version from Russell King:
>
>
On 6/3/2019 11:50 AM, Tomasz Figa wrote:
On Mon, Jun 3, 2019 at 4:40 AM Rob Clark wrote:
On Fri, May 10, 2019 at 7:35 AM Rob Clark wrote:
On Tue, Dec 4, 2018 at 2:29 PM Rob Herring wrote:
On Sat, Dec 1, 2018 at 10:54 AM Rob Clark wrote:
This solves a problem we see with drm/msm,
https://bugs.freedesktop.org/show_bug.cgi?id=110781
--- Comment #12 from Richard Thier ---
My friend "Googling" at the commit hash we found that my problem might possibly
relate to this other bug report already existing:
https://bugs.freedesktop.org/show_bug.cgi?id=105171
They also report a
>-Original Message-
>From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
>Sent: Monday, June 3, 2019 1:55 PM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>maarten.lankho...@linux.intel.com;
There are a few small nits needed to make the meson build script work
properly on FreeBSD. In short: sys/sysctl.h needs sys/types.h Use sh
if bash isn't around.
Also fix a typo while I'm here.
[ please CC me, I'm not subscribed to dri-devel@ ]
Niclas Zeising (2):
meson.build: Fix typo
When looking up the connector type make sure the index
is valid. Avoids a later crash if we read past the end
of the array.
This bug is similar to the issue which was fixed in
commit e1718d97aa88 ("drm/amdgpu: avoid a possible
array overflow").
Signed-off-by: Young Xiao <92siuy...@gmail.com>
FreeBSD requires sys/types.h for sys/sysctl.h, add it as part of the
includes when checking for headers.
Instead of splitting out the check for sys/sysctl.h from the other
header checks, just add sys/types.h to all header checks.
FreeBSD doesn't normally ship bash, try regular sh instead if we
This patch enables runtime power management (runtime PM) support for
the display controller. pm_runtime_enable() and pm_runtime_disable()
are added during ltdc load and unload respectively.
pm_runtime_get_sync() and pm_runtime_put_sync() are added for ltdc
register access.
Signed-off-by: Yannick
https://bugs.freedesktop.org/show_bug.cgi?id=109345
--- Comment #48 from Michel Dänzer ---
(In reply to Allan Cairns from comment #47)
> My Amigone x5000 would only boot to a black screen. No ability to input.
Please attach the corresponding Xorg log file. If you can't log into the system
https://bugs.freedesktop.org/show_bug.cgi?id=110781
--- Comment #10 from Richard Thier ---
I am getting really close to bisecting the bigger identified problem.
bad: b672c3833b7
good: aff1ad0798
Now at this point:
Bisecting: 9 revisions left to test after this (roughly 3 steps)
If you (and a few others actors in the thread) want people to actually
read what you wrote please follow proper mailing list ettiquette. I've
given up on reading all the recent mails after scrolling through two
pages of full quotes.
This patch updates mhdp8546 firmware from v1.2.12 to v1.2.15.
Added support for performing arbitrary I2C-over-AUX transactions.
Corrected handling of erroneous requests for reading/writing 0 bytes over DPCD.
Add mailbox message to force uCPU fatal error.
Signed-off-by: Damian Kos
---
WHENCE
On Sat, Jun 1, 2019 at 5:39 PM Shobhit Kukreti wrote:
>
> drivers/video/fbdev/controlfb.c: WARNING comparing pointer to 0
> drivers/video/fbdev/controlfb.c: WARNING comparing pointer to 0
> drivers/video/fbdev/controlfb.c: WARNING comparing pointer to 0
>
> Signed-off-by: Shobhit Kukreti
> ---
>
On Mon, Jun 3, 2019 at 4:14 PM Rob Clark wrote:
>
> On Mon, Jun 3, 2019 at 12:57 AM Vivek Gautam
> wrote:
> >
> >
> >
> > On 6/3/2019 11:50 AM, Tomasz Figa wrote:
> > > On Mon, Jun 3, 2019 at 4:40 AM Rob Clark wrote:
> > >> On Fri, May 10, 2019 at 7:35 AM Rob Clark wrote:
> > >>> On Tue, Dec
From: Shobhit Kukreti
Fixed Warning Comparing Pointer to 0. Changed return value to -ENOMEM to
report kzalloc failure
drivers/video/fbdev/controlfb.c: WARNING comparing pointer to 0
drivers/video/fbdev/controlfb.c: WARNING comparing pointer to 0
drivers/video/fbdev/controlfb.c: WARNING
On Sun, Jun 02, 2019 at 08:40:08PM -0400, Ilia Mirkin wrote:
> This series improves the pattern generation logic to support additional
> formats, as well as a new "gradient" pattern (see patch comments on why
> I found it useful).
>
> Furthermore, these formats are piped through to modetest,
On Mon, Jun 03, 2019 at 09:45:49AM +0200, Hans Verkuil wrote:
> On 6/3/19 6:32 AM, Cheng-Yi Chiang wrote:
> > From: Hans Verkuil
> >
> > Add support for HDMI hotplug and EDID notifiers, which is used to convey
> > information from HDMI drivers to their CEC and audio counterparts.
> >
> > Based
On Monday, June 3, 2019 9:28:18 AM CEST Daniel Vetter wrote:
> On Thu, May 30, 2019 at 10:40:09AM +0100, Chris Wilson wrote:
> > Quoting Janusz Krzysztofik (2019-05-30 10:24:26)
> > > In order to support driver hot unbind, some cleanup operations, now
> > > performed on PCI driver remove, must be
On Mon, Jun 3, 2019 at 12:57 AM Vivek Gautam
wrote:
>
>
>
> On 6/3/2019 11:50 AM, Tomasz Figa wrote:
> > On Mon, Jun 3, 2019 at 4:40 AM Rob Clark wrote:
> >> On Fri, May 10, 2019 at 7:35 AM Rob Clark wrote:
> >>> On Tue, Dec 4, 2018 at 2:29 PM Rob Herring wrote:
> On Sat, Dec 1, 2018 at
>-Original Message-
>From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
>Sent: Monday, June 3, 2019 1:42 PM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>maarten.lankho...@linux.intel.com;
>-Original Message-
>From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
>Sent: Monday, June 3, 2019 1:56 PM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>maarten.lankho...@linux.intel.com;
On Mon, Jun 3, 2019 at 3:32 AM Daniel Vetter wrote:
>
> On Sun, Jun 02, 2019 at 08:40:08PM -0400, Ilia Mirkin wrote:
> > This series improves the pattern generation logic to support additional
> > formats, as well as a new "gradient" pattern (see patch comments on why
> > I found it useful).
> >
https://bugs.freedesktop.org/show_bug.cgi?id=110823
--- Comment #3 from Chris Wilson ---
(In reply to Martin Peres from comment #0)
> Hi, it looks like amdgpu's userptrs are now broken:
>
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6179/fi-kbl-8809g/
> igt@amdgpu_amd_ba...@userptr.html
>
On Mon, Jun 03, 2019 at 06:20:57AM -0700, Rob Clark wrote:
> On Mon, Jun 3, 2019 at 4:14 AM Robin Murphy wrote:
> >
> > On 03/06/2019 11:47, Rob Clark wrote:
> > > On Sun, Jun 2, 2019 at 11:25 PM Tomasz Figa wrote:
> > >>
> > >> On Mon, Jun 3, 2019 at 4:40 AM Rob Clark wrote:
> > >>>
> > >>>
On Mon, Jun 3, 2019 at 6:54 AM Thierry Reding wrote:
>
> On Mon, Jun 03, 2019 at 06:20:57AM -0700, Rob Clark wrote:
> > On Mon, Jun 3, 2019 at 4:14 AM Robin Murphy wrote:
> > >
> > > On 03/06/2019 11:47, Rob Clark wrote:
> > > > On Sun, Jun 2, 2019 at 11:25 PM Tomasz Figa wrote:
> > > >>
> > >
From: Colin Ian King
The less than check for the variable num_lanes is always going to be
false because the variable is a u32. Fix this by making num_lanes an
int and also make loop index i an int too.
Addresses-Coverity: ("Unsigned compared against 0")
Fixes: ff5781634c41 ("drm/bridge:
On Mon, 3 Jun 2019 16:28:48 +0200
Daniel Vetter wrote:
> drm_atomic_set_fence_for_plane() contains the main discussion from a
> driver pov, link to that from more places.
>
> Cc: Pekka Paalanen
> Signed-off-by: Daniel Vetter
> Cc: Maarten Lankhorst
> Cc: Maxime Ripard
> Cc: Sean Paul
>
Hi Dave & Daniel,
Missed last week's window of opportunity due to trouble getting
CI results for Icelake. So this is against -rc2 still to avoid
re-doing the GVT pull third time.
Just a single Icelake W/A for i915. For GVT a fix for recently
seen arbitrary DMA map fault and more enforcement
On Mon, Jun 03, 2019 at 12:14:27PM +0100, Robin Murphy wrote:
> On 03/06/2019 11:47, Rob Clark wrote:
> > On Sun, Jun 2, 2019 at 11:25 PM Tomasz Figa wrote:
> > >
> > > On Mon, Jun 3, 2019 at 4:40 AM Rob Clark wrote:
> > > >
> > > > On Fri, May 10, 2019 at 7:35 AM Rob Clark wrote:
> > > > >
https://bugs.freedesktop.org/show_bug.cgi?id=109835
rtent...@yandex.ru changed:
What|Removed |Added
Version|unspecified |19.1
--- Comment #4 from
> It shouldn't be a problem to hook something else up to the IOMMU
> subsystem. Hopefully it's something that people are going to standardize
> on.
>
> > 3) The automatic attach of DMA domain is also causing a different
> >problem for us on the GPU side, preventing us from supporting per-
> >
Add a new section for UAPI structure and helper definitions
in kernel docbook.
Suggested-by: Daniel Vetter
Signed-off-by: Uma Shankar
---
Documentation/gpu/drm-uapi.rst | 9 +
1 file changed, 9 insertions(+)
diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
This series adds DRM UAPI header structure documentation to kernel
docs. Fixes issues with existing structure documentation in drm
uapi header.
This also fixes warnings in HDR doc and addresses suggestions from
Daniel Vetter.
v2: 2 patches from v1 are merged. This series version adds remaining
Fixes the following warnings:
./include/drm/drm_mode_config.h:841: warning: Incorrect use of
kernel-doc format: * hdr_output_metadata_property: Connector
property containing hdr
./include/drm/drm_mode_config.h:918: warning: Function parameter or member
'hdr_output_metadata_property' not
Dropped static functions from kernel documentation.
v2: Dropped the comments altogether for static functions,
as the definitions seems self explanatory.
Suggested-by: Daniel Vetter
Signed-off-by: Uma Shankar
---
drivers/video/hdmi.c | 30 --
1 file changed, 30
On 6/3/19 3:24 AM, Daniel Vetter wrote:
> On Thu, May 30, 2019 at 05:04:20PM +0200, Christian König wrote:
>> Am 29.05.19 um 21:36 schrieb Daniel Vetter:
>>> On Wed, May 29, 2019 at 04:43:45PM +, Grodzovsky, Andrey wrote:
I don't, sorry.
>>> Should we fix that? Seems like you do plenty
On Fri, May 31, 2019 at 4:09 PM Jordan Crouse wrote:
>
> Before loading the zap shader we should ensure that the reserved memory
> region is big enough to hold the loaded file.
>
> Signed-off-by: Jordan Crouse
Reviewed-by: Jeffrey Hugo
> ---
>
> drivers/gpu/drm/msm/adreno/adreno_gpu.c | 8
On Mon, Jun 03, 2019 at 05:34:11PM +0300, Pekka Paalanen wrote:
> On Mon, 3 Jun 2019 16:28:48 +0200
> Daniel Vetter wrote:
>
> > drm_atomic_set_fence_for_plane() contains the main discussion from a
> > driver pov, link to that from more places.
> >
> > Cc: Pekka Paalanen
> > Signed-off-by:
On Mon, 2019-06-03 at 17:08 +0200, Daniel Vetter wrote:
> On Mon, Jun 03, 2019 at 11:50:53AM +0200, Michel Dänzer wrote:
> > On 2019-05-21 9:52 a.m., Daniel Vetter wrote:
> > > On Tue, May 21, 2019 at 8:55 AM Pekka Paalanen
> > > wrote:
> > > > On Mon, 20 May 2019 18:11:07 +0200
> > > > Daniel
Add support for display panels built around the Novatek NT39016 display
controller, as found on e.g. the King Display KD035G6-54NT 24-bit
320x240 3.5" LCD panel which equips the GCW Zero open-source handheld
gaming console.
Signed-off-by: Paul Cercueil
Signed-off-by: Maarten ter Huurne
---
The KD035G6-54NT is a 3.5" 320x240 24-bit TFT LCD panel.
Signed-off-by: Paul Cercueil
---
Notes:
v2: - Add an address to the panel node
- Add information about SPI properties
- Add information about the 'port' sub-node
.../panel/kingdisplay,kd035g6-54nt.txt| 42
On Thu, May 30, 2019 at 12:09 AM Alex Deucher wrote:
>
> Hi Dave, Daniel,
>
> New stuff for 5.3:
> - Add new thermal sensors for vega asics
> - Various RAS fixes
> - Add sysfs interface for memory interface utilization
> - Use HMM rather than mmu notifier for user pages
> - Expose xgmi topology
https://bugs.freedesktop.org/show_bug.cgi?id=110781
--- Comment #16 from Richard Thier ---
Created attachment 144427
--> https://bugs.freedesktop.org/attachment.cgi?id=144427=edit
Simple diff/patch to test the issue
See attached diff/patch for what I am trying as a quickfix and testing what
drm_atomic_set_fence_for_plane() contains the main discussion from a
driver pov, link to that from more places.
Cc: Pekka Paalanen
Signed-off-by: Daniel Vetter
Cc: Maarten Lankhorst
Cc: Maxime Ripard
Cc: Sean Paul
Cc: David Airlie
Cc: Daniel Vetter
---
On Mon, Jun 03, 2019 at 07:20:14AM -0700, Rob Clark wrote:
> On Mon, Jun 3, 2019 at 6:54 AM Thierry Reding
> wrote:
> >
> > On Mon, Jun 03, 2019 at 06:20:57AM -0700, Rob Clark wrote:
> > > On Mon, Jun 3, 2019 at 4:14 AM Robin Murphy wrote:
> > > >
> > > > On 03/06/2019 11:47, Rob Clark wrote:
>
On Fri, May 31, 2019 at 3:46 AM Brian Masney wrote:
>
> The mdp5 drm/kms driver currently does not work on command-mode DSI
> panels due to 'vblank wait timed out' errors. This causes a latency
> of seconds, or tens of seconds in some cases, before content is shown
> on the panel. This hardware
On Mon, Jun 03, 2019 at 11:50:53AM +0200, Michel Dänzer wrote:
> On 2019-05-21 9:52 a.m., Daniel Vetter wrote:
> > On Tue, May 21, 2019 at 8:55 AM Pekka Paalanen wrote:
> >> On Mon, 20 May 2019 18:11:07 +0200
> >> Daniel Vetter wrote:
> >>
> >>> There's also a fairly easy fix for that
Add a KMS driver for the Ingenic JZ47xx family of SoCs.
This driver is meant to replace the aging jz4740-fb driver.
This driver does not make use of the simple pipe helper, for the reason
that it will soon be updated to support more advanced features like
multiple planes, IPU integration for
Add documentation for the devicetree bindings of the LCD controller present in
the JZ47xx family of SoCs from Ingenic.
Signed-off-by: Paul Cercueil
Tested-by: Artur Rojek
---
Notes:
v2: Remove ingenic,panel property.
v3: - Rename compatible strings from ingenic,jz47XX-drm to
The LS020B1DD01D is a 2.0" 240x160 16-bit TFT LCD panel.
Signed-off-by: Paul Cercueil
Reviewed-by: Rob Herring
---
Notes:
v2: New patch
v3: Add Rob's Reviewed-by
v4: Rebase on drm-misc-next (b232d4ed92ea)
.../bindings/display/panel/sharp,ls020b1dd01d.txt| 12
The Sharp LS020B1DD01D is a simple 2.0" 240x160 16-bit TFT panel.
Signed-off-by: Paul Cercueil
Tested-by: Artur Rojek
---
Notes:
v2: No change
v3: Add DRM_BUS_FLAG_SHARP_SIGNALS to the bus flags
v4: Rebase on drm-misc-next (b232d4ed92ea)
Add the DRM_BUS_FLAG_SHARP_SIGNALS to the drm_bus_flags enum.
This flags can be used when the display must be driven with the
Sharp-specific signals SPL, CLS, REV, PS.
Signed-off-by: Paul Cercueil
---
Notes:
v3: New patch
v4: Rebase on drm-misc-next (b232d4ed92ea)
https://bugs.freedesktop.org/show_bug.cgi?id=110823
Chris Wilson changed:
What|Removed |Added
Component|DRM/AMDgpu |IGT
--- Comment #2 from Chris Wilson
On Mon, May 20, 2019 at 02:33:16PM +0530, Jagan Teki wrote:
> Allwinner MIPI DSI controllers are supplied with SoC
> DSI power rails via VCC-DSI pin.
>
> Add support for this supply pin by adding voltage
> regulator handling code to MIPI DSI driver.
>
> Tested-by: Merlijn Wajer
> Signed-off-by:
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #34 from ant...@gmx.de ---
I think this is not just affecting Vega 20 but also Vega 10 is now stuck on
memclock pstate 0 (167MHz) since kernel 5.1.
I assume this is related to fclk and defclk
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=110781
--- Comment #13 from Rui Salvaterra ---
This is interesting. I have the exact same problem on an old Turion X2 laptop
I've been given. I attributed it to memory controller contention (since the GPU
resides in the northbridge and the memory
On Mon, Jun 3, 2019 at 4:14 AM Robin Murphy wrote:
>
> On 03/06/2019 11:47, Rob Clark wrote:
> > On Sun, Jun 2, 2019 at 11:25 PM Tomasz Figa wrote:
> >>
> >> On Mon, Jun 3, 2019 at 4:40 AM Rob Clark wrote:
> >>>
> >>> So, another case I've come across, on the display side.. I'm working
> >>> on
The GiantPlus GPM940B0 is a simple 3.0" 320x240 24-bit TFT panel.
Signed-off-by: Paul Cercueil
Tested-by: Artur Rojek
---
Notes:
v2: Change bus format to MEDIA_BUS_FMT_RGB888_3X8_BE
v3: No change
v4: Change bus format to MEDIA_BUS_FMT_RGB888_3X8
https://bugs.freedesktop.org/show_bug.cgi?id=110781
--- Comment #14 from Richard Thier ---
Now seeing that the commit diff is actually small, I can put some printf logs
in place to see what is going on and where the code ends up.
--
You are receiving this mail because:
You are the assignee for
1 - 100 of 156 matches
Mail list logo
