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
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
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
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.
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
https://bugzilla.kernel.org/show_bug.cgi?id=202445
jaapbuur...@gmail.com changed:
What|Removed |Added
CC||jaapbuur...@gmail.com
---
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
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:
> > >
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
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
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=110823
Martin Peres changed:
What|Removed |Added
Assignee|intel-gfx-bugs@lists.freede |dri-devel@lists.freedesktop
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
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 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 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
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
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
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
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 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=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)
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
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
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
---
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
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
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
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: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=110803
diplosa...@gmail.com changed:
What|Removed |Added
CC||mezin.alexan...@gmail.com
---
https://bugs.freedesktop.org/show_bug.cgi?id=110807
diplosa...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
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
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
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
>
>
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,
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:
>
>
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>
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
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
---
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 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:
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,
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 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 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 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 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
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
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
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/
-
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
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;
> }
>
> -
101 - 156 of 156 matches
Mail list logo
