ping
On 05/22/2018 05:13 PM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
When unplugging a hotpluggable DRM device we first unregister it
with drm_dev_unregister and then set drm_device.unplugged flag which
is used to mark device critical sections with drm_dev_enter()/
Am 29.05.2018 um 07:53 schrieb Nayan Deshmukh:
convert existing raw comments into kernel-doc format as well
as add new documentation
v2: reword the overview
Signed-off-by: Alex Deucher
Signed-off-by: Nayan Deshmukh
Reviewed-by: Alex Deucher
Reviewed-by: Christian König
Going to push
On 24.05.2018 18:41, Sandeep Panda wrote:
> Document the bindings used for the sn65dsi86 DSI to eDP bridge.
>
> Changes in v1:
> - Rephrase the dt-binding descriptions to be more inline with existing
>bindings (Andrzej Hajda).
> - Add missing dt-binding that are parsed by corresponding
On Mon, May 28, 2018 at 02:44:28PM +0300, Tomi Valkeinen wrote:
> Hi,
>
> On 28/05/18 13:55, Pekka Paalanen wrote:
>
> >> The series adds support for changing the order of the displays defined by
> >> DT
> >> display aliases.
> >>
> >> The motivation to do such a thing is that for example the
On Thu, May 24, 2018 at 07:51:40PM +0530, Souptick Joarder wrote:
> On Thu, May 24, 2018 at 6:27 PM, Daniel Vetter wrote:
> > On Wed, May 23, 2018 at 03:05:35PM +0530, Souptick Joarder wrote:
> >> On Mon, May 14, 2018 at 9:56 PM, Daniel Vetter wrote:
> >> > On Thu, May 10, 2018 at 02:51:38PM
On Mon, May 28, 2018 at 04:27:11PM +0200, Emil Lundmark wrote:
> This fixes a NULL pointer dereference that can happen if the UDL
> driver is unloaded before the framebuffer is initialized. This can
> happen e.g. if the USB device is unplugged right after it was plugged
> in.
>
> As explained by
Hi Morimoto-san,
On Tue, May 29, 2018 at 3:44 AM, Kuninori Morimoto
wrote:
>> > +_con {
>> > + remote-endpoint = <_dw_hdmi0_out>;
>> > +};
>>
>> I think the hdmi0 and hdmi0_con parts can be moved to salvator-common.dtsi.
>> Can we do that now (with stubs?), or does this have to wait until
On 05/29/2018 09:04 PM, Boris Ostrovsky wrote:
On 05/25/2018 11:33 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Memory {increase|decrease}_reservation and VA mappings update/reset
code used in balloon driver can be made common, so other drivers can
also re-use the same
On 05/29/2018 09:24 PM, Boris Ostrovsky wrote:
On 05/25/2018 11:33 AM, Oleksandr Andrushchenko wrote:
+
+void xenmem_reservation_va_mapping_update(unsigned long count,
+ struct page **pages,
+ xen_pfn_t *frames)
On 29/05/18 13:17, Heiko Stübner wrote:
Am Dienstag, 29. Mai 2018, 13:59:42 CEST schrieb Robin Murphy:
On 28/05/18 14:20, Heiko Stuebner wrote:
From: Sandy Huang
The vop irq is shared between vop and iommu and irq probing in the
iommu driver moved to the probe function recently. This can in
Hi Dave,
One last fix for 4.17. Fix a suspend regression in DC.
The following changes since commit 72777fe79768ec30ac2163d26de68a89edc9849f:
Merge branch 'drm-fixes-4.17' of git://people.freedesktop.org/~agd5f/linux
into drm-fixes (2018-05-11 10:37:17 +1000)
are available in the git
https://bugs.freedesktop.org/show_bug.cgi?id=104391
Roman Li changed:
What|Removed |Added
CC||roman...@amd.com
--- Comment #7 from Roman
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Jan Vesely changed:
What|Removed |Added
Depends on||106619
Referenced Bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Bug 99553 depends on bug 106619, which changed state.
Bug 106619 Summary: [OpenCL][llvm-svn]build failure addPassesToEmitFile
candidate expects 6 arguments, 3 provided
https://bugs.freedesktop.org/show_bug.cgi?id=106619
What
https://bugs.freedesktop.org/show_bug.cgi?id=106670
--- Comment #4 from JerryD ---
Extended renderer info (GLX_MESA_query_renderer):
Vendor: X.Org (0x1002)
Device: AMD RAVEN (DRM 3.23.0 / 4.16.12-300.fc28.x86_64, LLVM 6.0.0)
(0x15dd)
Version: 18.0.2
Accelerated: yes
Video
On Sat, May 26, 2018 at 06:56:22PM +0300, Dmitry Osipenko wrote:
> Color keying is the action of replacing pixels matching a given color
> (or range of colors) with transparent pixels in an overlay when
> performing blitting. Depending on the hardware capabilities, the
> matching pixel can either
On 24.05.2018 18:41, Sandeep Panda wrote:
> Add support for TI's sn65dsi86 dsi2edp bridge chip.
> The chip converts DSI transmitted signal to eDP signal,
> which is fed to the connected eDP panel.
>
> This chip can be controlled via either i2c interface or
> dsi interface. Currently in driver all
On Tue, May 29, 2018 at 10:23:27AM +0200, Daniel Vetter wrote:
> On Fri, May 25, 2018 at 04:08:08PM +0200, Gerd Hoffmann wrote:
> > A driver to let userspace turn memfd regions into dma-bufs.
> >
> > Use case: Allows qemu create dmabufs for the vga framebuffer or
> > virtio-gpu ressources. Then
On Fri, May 25, 2018 at 03:42:54PM +0200, Lucas Stach wrote:
> The intention of the existing code was to deflect the actual work
> of mmaping a dma-buf to the exporter, as that one probably knows best
> how to handle the buffer. Unfortunately the call to drm_gem_mmap did
> more than what etnaviv
On Fri, May 25, 2018 at 04:42:52PM +0530, Ramalingam C wrote:
>
>
> On Thursday 24 May 2018 01:36 PM, Daniel Vetter wrote:
> > On Mon, May 21, 2018 at 06:23:49PM +0530, Ramalingam C wrote:
> > > Initialize HDCP2.2 support. This includes the mei interface
> > > initialization along with required
On Mon, May 21, 2018 at 06:23:19PM +0530, Ramalingam C wrote:
> The sequence for HDCP2.2 authentication and encryption is implemented
> in I915. Encoder specific implementations are moved into hdcp_shim.
>
> Intel HWs supports HDCP2.2 through ME FW. Hence this series
> introduces a client driver
On Fri, May 25, 2018 at 02:00:33AM +0530, Souptick Joarder wrote:
> On Wed, May 16, 2018 at 10:09 AM, Souptick Joarder
> wrote:
> > On Thu, May 10, 2018 at 7:12 PM, Souptick Joarder
> > wrote:
> >> Use new return type vm_fault_t for fault handler. For
> >> now, this is just documenting that
On Tue, May 22, 2018 at 05:13:04PM +0300, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> When unplugging a hotpluggable DRM device we first unregister it
> with drm_dev_unregister and then set drm_device.unplugged flag which
> is used to mark device critical sections with
On 05/29/2018 10:02 AM, Daniel Vetter wrote:
On Tue, May 22, 2018 at 05:13:04PM +0300, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
When unplugging a hotpluggable DRM device we first unregister it
with drm_dev_unregister and then set drm_device.unplugged flag which
is used to
On 29/05/18 09:42, Daniel Vetter wrote:
Thus far the rules has been that we try to put the integrated panel first,
and that's it. See drm_helper_move_panel_connectors_to_head(). If there's
Ok. But we may also have multiple integrated panels.
any standard, then imo that's it. Not a more
On Tue, May 29, 2018 at 10:16:20AM +0300, Tomi Valkeinen wrote:
> On 29/05/18 09:42, Daniel Vetter wrote:
>
> > Thus far the rules has been that we try to put the integrated panel first,
> > and that's it. See drm_helper_move_panel_connectors_to_head(). If there's
>
> Ok. But we may also have
On Fri, May 25, 2018 at 05:20:08AM +0300, Haneen Mohammed wrote:
> This patch add checks for NULL drm_[connector/crtc/plane]_helper_funcs
> pointers before derefrencing the variable to avoid NULL pointer
> dereference and make the helper functions as optional as possible.
>
> Signed-off-by:
On Tue, May 29, 2018 at 10:09:57AM +0300, Oleksandr Andrushchenko wrote:
> On 05/29/2018 10:02 AM, Daniel Vetter wrote:
> > On Tue, May 22, 2018 at 05:13:04PM +0300, Oleksandr Andrushchenko wrote:
> > > From: Oleksandr Andrushchenko
> > >
> > > When unplugging a hotpluggable DRM device we first
On Mon, May 28, 2018 at 02:01:49PM +0530, Nayan Deshmukh wrote:
> I have done that already, sent a patch with this one. The last patch
> of this series. I have tried to take care of all the hyperlinks.
Oh great, was jumping to conclusions. Usually I do that first, so that I
can see mistakes while
On Tue, May 29, 2018 at 08:53:37AM +0200, Daniel Vetter wrote:
> On Fri, May 25, 2018 at 04:42:52PM +0530, Ramalingam C wrote:
> >
> >
> > On Thursday 24 May 2018 01:36 PM, Daniel Vetter wrote:
> > > On Mon, May 21, 2018 at 06:23:49PM +0530, Ramalingam C wrote:
> > > > Initialize HDCP2.2
On Fri, May 25, 2018 at 02:42:02PM +0200, Noralf Trønnes wrote:
>
> Den 24.05.2018 11.16, skrev Daniel Vetter:
> > On Wed, May 23, 2018 at 04:34:07PM +0200, Noralf Trønnes wrote:
> > > This is the first step in getting generic fbdev emulation.
> > > A drm_fb_helper_funcs.fb_probe function is
On Thu, May 24, 2018 at 09:43:50PM -0400, Sean Paul wrote:
> On Thu, May 24, 2018, 9:26 PM Haneen Mohammed
> wrote:
>
> > This patch add checks for atomic_[duplicate/destroy]_state of
> > drm_[connector/crtc/plane]_funcs for atomic drivers in the relevant
> > drm_*_init functions since these
On Tue, May 29, 2018 at 7:58 AM, Oleksandr Andrushchenko
wrote:
> On 05/25/2018 06:50 PM, Arnd Bergmann wrote:
>> b/drivers/gpu/drm/xen/xen_drm_front_shbuf.c
>> index 8099cb343ae3..d333b67cc1a0 100644
>> --- a/drivers/gpu/drm/xen/xen_drm_front_shbuf.c
>> +++
On Tue, May 29, 2018 at 07:51:56AM +, C, Ramalingam wrote:
> > -Original Message-
> > From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel
> > Vetter
> > Sent: Tuesday, May 29, 2018 12:27 PM
> > To: C, Ramalingam
> > Cc: intel-...@lists.freedesktop.org;
This fixes a NULL pointer dereference that can happen if the UDL
driver is unloaded before the framebuffer is initialized. This can
happen e.g. if the USB device is unplugged right after it was plugged
in.
As explained by Stéphane Marchesin:
It happens when fbdev is disabled (which is the case
On 29.05.2018 02:48, Dmitry Osipenko wrote:
> inversion=true" if mask has form of 0x11000111, though this could be not
For clarity: I meant s/0x11000111/0xFF000FFF/.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
Fixes a stringop-truncation warning from gcc-8.
Signed-off-by: Nick Desaulniers
---
drivers/video/hdmi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/video/hdmi.c b/drivers/video/hdmi.c
index 111a0ab..46c184c 100644
--- a/drivers/video/hdmi.c
+++
On 28.05.2018 16:15, Ville Syrjälä wrote:
> On Sat, May 26, 2018 at 06:56:22PM +0300, Dmitry Osipenko wrote:
>> Color keying is the action of replacing pixels matching a given color
>> (or range of colors) with transparent pixels in an overlay when
>> performing blitting. Depending on the hardware
On Mon, May 28, 2018 at 6:20 PM, Lucas Stach wrote:
> Hi Souptick,
>
> Am Montag, den 21.05.2018, 22:42 +0530 schrieb Souptick Joarder:
>> Use new return type vm_fault_t for fault handler. For
>> now, this is just documenting that the function returns
>> a VM_FAULT value rather than an errno.
On Tue, May 29, 2018 at 02:48:22AM +0300, Dmitry Osipenko wrote:
> On 28.05.2018 16:15, Ville Syrjälä wrote:
> > On Sat, May 26, 2018 at 06:56:22PM +0300, Dmitry Osipenko wrote:
> >> Color keying is the action of replacing pixels matching a given color
> >> (or range of colors) with transparent
On 05/28/2018 02:47 AM, Maciej Purski wrote:
> diff --git a/drivers/gpu/drm/bridge/Kconfig b/drivers/gpu/drm/bridge/Kconfig
> index fa2c799..58e19af 100644
> --- a/drivers/gpu/drm/bridge/Kconfig
> +++ b/drivers/gpu/drm/bridge/Kconfig
> @@ -110,6 +110,13 @@ config DRM_THINE_THC63LVD1024
>
Hi Geert
> > +_con {
> > + remote-endpoint = <_dw_hdmi0_out>;
> > +};
>
> I think the hdmi0 and hdmi0_con parts can be moved to salvator-common.dtsi.
> Can we do that now (with stubs?), or does this have to wait until r8a77965 has
> received HDMI sound support?
HDMI sound doesn't use
To make suspend and resume work on msm8916 platforms, call into the generic
helpers and preserve the state across suspends.
Signed-off-by: Daniel Mack
---
drivers/gpu/drm/msm/msm_drv.c | 9 +
drivers/gpu/drm/msm/msm_drv.h | 1 +
2 files changed, 10 insertions(+)
diff --git
When a msm8016 based system is woken up from suspend, the firmware in
the adreno device hangs.
[ 83.903416] qcom-iommu-ctx 1f09000.iommu-ctx: Unhandled context fault:
fsr=0x202, iova=0x, fsynr=0x2, cb=1
[ 85.853633] msm 1a0.mdss: A306: hangcheck detected gpu lockup rb 0!
> -Original Message-
> From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
> Sent: Tuesday, May 29, 2018 12:27 PM
> To: C, Ramalingam
> Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
> seanp...@chromium.org; dan...@ffwll.ch;
On Mon, May 28, 2018 at 03:26:48PM +0200, Noralf Trønnes wrote:
>
> Den 24.05.2018 10.42, skrev Daniel Vetter:
> > On Wed, May 23, 2018 at 04:34:06PM +0200, Noralf Trønnes wrote:
> > > This the beginning of an API for in-kernel clients.
> > > First out is a way to get a framebuffer backed by a
On Fri, May 25, 2018 at 04:08:08PM +0200, Gerd Hoffmann wrote:
> A driver to let userspace turn memfd regions into dma-bufs.
>
> Use case: Allows qemu create dmabufs for the vga framebuffer or
> virtio-gpu ressources. Then they can be passed around to display
> those guest things on the host.
On 05/30/2018 07:24 AM, Juergen Gross wrote:
On 25/05/18 17:33, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Make set/clear page private code shared and accessible to
other kernel modules which can re-use these instead of open-coding.
Signed-off-by: Oleksandr Andrushchenko
Change-Id: I412f5783e2839c53841e6ab665f939236bdc5bf1
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c
index
In per-vm-bo case, there could be no bo list.
But gds bo created from user space must be passed to bo list.
So adding a check to prevent creat per-vm gds bo.
Change-Id: Idfa58c40447df0db2883413f9f7ccf56b47579f5
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c | 7
Reviewed-by: Emily Deng
> -Original Message-
> From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf
> Of Chunming Zhou
> Sent: Wednesday, May 30, 2018 11:15 AM
> To: dri-devel@lists.freedesktop.org; amd-...@lists.freedesktop.org
> Cc: Deng, Emily ; Zhou, David(ChunMing)
https://bugs.freedesktop.org/show_bug.cgi?id=106639
--- Comment #5 from jian-h...@endlessm.com ---
Hi Michel,
The patch which you mentioned works better than before.
Will it be back ported to Linux kernel 4.16 or 4.17?
Thanks
--
You are receiving this mail because:
You are the assignee for
Higher values of pclk can exceed 32 bits when multiplied
by a factor.
Make the pclk_rate u64 to accommodate higher pixel clock
rates.
Signed-off-by: Abhinav Kumar
---
drivers/gpu/drm/msm/dsi/dsi_host.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On 05/25/2018 05:08 PM, Gerd Hoffmann wrote:
A driver to let userspace turn memfd regions into dma-bufs.
Use case: Allows qemu create dmabufs for the vga framebuffer or
virtio-gpu ressources. Then they can be passed around to display
those guest things on the host. To spice client for
Hi,
> > > qemu test branch:
> > > https://git.kraxel.org/cgit/qemu/log/?h=sirius/udmabuf
^^
> > > + if (!shmem_mapping(file_inode(ubuf->filp)->i_mapping))
> > > + goto err_free_ubuf;
>
> Can/should we test here that the
Hi all,
After merging the drm-intel-fixes tree, today's linux-next build (i386
defconfig) failed like this:
In file included from include/asm-generic/barrier.h:20:0,
from arch/x86/include/asm/barrier.h:86,
from include/linux/nospec.h:8,
from
On Tuesday 29 May 2018 02:12 PM, Daniel Vetter wrote:
On Tue, May 29, 2018 at 08:53:37AM +0200, Daniel Vetter wrote:
On Fri, May 25, 2018 at 04:42:52PM +0530, Ramalingam C wrote:
On Thursday 24 May 2018 01:36 PM, Daniel Vetter wrote:
On Mon, May 21, 2018 at 06:23:49PM +0530, Ramalingam C
Hi Linus,
On Fri, May 11, 2018 at 05:54:27PM +0200, Linus Walleij wrote:
> Hi Maxime,
>
> sorry that noone had much time to look at the driver.
> But I can help out, hopefully.
Thanks for your feedback :)
> On Fri, May 4, 2018 at 5:23 PM, Maxime Ripard
> wrote:
>
> > The LHR050H41 panel is
On 05/29/2018 01:50 PM, Gerd Hoffmann wrote:
Hi,
+config UDMABUF
+ bool "userspace dmabuf misc driver"
+ default n
+ depends on DMA_SHARED_BUFFER
Don't you want "select DMA_SHARED_BUFFER" here instead?
Why do you think so?
After thinking a bit more your code looks ok,
Am Dienstag, den 29.05.2018, 10:20 +0200 schrieb Daniel Vetter:
> On Fri, May 25, 2018 at 03:42:54PM +0200, Lucas Stach wrote:
> > The intention of the existing code was to deflect the actual work
> > of mmaping a dma-buf to the exporter, as that one probably knows best
> > how to handle the
Hi Geert,
On 28/05/18 10:06, Geert Uytterhoeven wrote:
> Hi Kieran, Morimoto-san,
>
> On Fri, Apr 27, 2018 at 6:57 PM, Kieran Bingham
> wrote:
>> The DU1 external dot clock is provided by the fixed frequency clock
>> generator X21, while the DU0 and DU3 clocks are provided by the
>>
Hi Kieran,
On Tue, May 29, 2018 at 11:08 AM, Kieran Bingham
wrote:
> On 28/05/18 10:06, Geert Uytterhoeven wrote:
>> On Fri, Apr 27, 2018 at 6:57 PM, Kieran Bingham
>> wrote:
>>> The DU1 external dot clock is provided by the fixed frequency clock
>>> generator X21, while the DU0 and DU3 clocks
The LHR050H41 from BananaPi is a 1280x700 4-lanes DSI panel based on the
ILI9881c from Ilitek.
Acked-by: Rob Herring
Signed-off-by: Maxime Ripard
---
Documentation/devicetree/bindings/display/panel/ilitek,ili9881c.txt | 20
1 file changed, 20 insertions(+)
create mode
The BananaPi M2M has an optional 1280x720 DSI panel. Since that panel is
optional, we can only show a DT patch that would show how to enable it.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun8i-r16-bananapi-m2m.dts | 48 +-
1 file changed, 48 insertions(+)
diff
Hi,
Here is the next version of the patches to add the support for the Ilitek
ILI9881c panel controller.
This used to be a part of the larger DSI support series for the Allwinner
SoCs whose patches have been since merged and are obviously not part of
this series anymore.
Let me know what you
The LHR050H41 panel is the panel shipped with the BananaPi M2-Magic, and is
based on the Ilitek ILI9881c Controller. Add a driver for it, modelled
after the other Ilitek controller drivers.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/panel/Kconfig | 9 +-
Hi,
> > +config UDMABUF
> > + bool "userspace dmabuf misc driver"
> > + default n
> > + depends on DMA_SHARED_BUFFER
> Don't you want "select DMA_SHARED_BUFFER" here instead?
Why do you think so?
cheers,
Gerd
___
dri-devel mailing list
Hi,
> > +static void *kmap_atomic_udmabuf(struct dma_buf *buf, unsigned long
> > page_num)
> > +{
> > + struct udmabuf *ubuf = buf->priv;
> > + struct page *page = ubuf->pages[page_num];
> > +
> > + return kmap_atomic(page);
> > +}
> > +
> > +static void *kmap_udmabuf(struct dma_buf
On 25/05/18 19:39, Laurent Pinchart wrote:
> Hello,
>
> This patch series removes the usage of struct_mutex from the omapdrm driver in
> order to switch to gem_free_object_unlocked(). The series is inspired by
> Daniel Vetter's recent gem_free_object_unlocked() patches (starting with
> "[PATCH
> -Original Message-
> From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
> Sent: Tuesday, May 29, 2018 2:01 PM
> To: C, Ramalingam
> Cc: Daniel Vetter ; intel-...@lists.freedesktop.org; dri-
> de...@lists.freedesktop.org; seanp...@chromium.org; chris@chris-
>
https://bugs.freedesktop.org/show_bug.cgi?id=106709
Bug ID: 106709
Summary: Requesting new account for IGT
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
On 28/05/18 14:20, Heiko Stuebner wrote:
From: Sandy Huang
The vop irq is shared between vop and iommu and irq probing in the
iommu driver moved to the probe function recently. This can in some
cases lead to a stall if the irq is triggered while the vop driver
still has it disabled, but the
On Tue, May 29, 2018 at 12:48 PM, Gerd Hoffmann wrote:
> Hi,
>
>> > > qemu test branch:
>> > > https://git.kraxel.org/cgit/qemu/log/?h=sirius/udmabuf
> ^^
>
>> > > + if (!shmem_mapping(file_inode(ubuf->filp)->i_mapping))
>> > > +
On Tue, May 29, 2018 at 10:48 AM, Gerd Hoffmann wrote:
> Hi,
>
>> > +static void *kmap_atomic_udmabuf(struct dma_buf *buf, unsigned long
>> > page_num)
>> > +{
>> > + struct udmabuf *ubuf = buf->priv;
>> > + struct page *page = ubuf->pages[page_num];
>> > +
>> > + return
On Tue, May 29, 2018 at 11:08 AM, Lucas Stach wrote:
> Am Dienstag, den 29.05.2018, 10:20 +0200 schrieb Daniel Vetter:
>> On Fri, May 25, 2018 at 03:42:54PM +0200, Lucas Stach wrote:
>> > The intention of the existing code was to deflect the actual work
>> > of mmaping a dma-buf to the exporter,
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #71 from MirceaKitsune ---
The Mesa 18.1.0 update, which was supposed to fix several GPU crashes, seems to
have managed to expand this freeze instead: I now get it even when playing
simple 3D games with low-poly models and low-res
On Tue, May 29, 2018 at 11:49 AM, Maxime Ripard
wrote:
> The LHR050H41 panel is the panel shipped with the BananaPi M2-Magic, and is
> based on the Ilitek ILI9881c Controller. Add a driver for it, modelled
> after the other Ilitek controller drivers.
>
> Signed-off-by: Maxime Ripard
https://bugs.freedesktop.org/show_bug.cgi?id=106631
--- Comment #11 from Ricardo Ribalda ---
Seems that it is in release mode
root@qt5022:~# llvm-config --assertion-mode
OFF
root@qt5022:~# llvm-config --build-mode
Release
--
You are receiving this mail because:
You are the assignee for
Quoting Stephen Rothwell (2018-05-29 12:26:05)
> Hi all,
>
> After merging the drm-intel-fixes tree, today's linux-next build (i386
> defconfig) failed like this:
Thanks for reporting. I've added a patch to fix the issue now.
I'll talk with our CI team about testing 32-bit building to try to
On Tue, May 29, 2018 at 11:49 AM, Maxime Ripard
wrote:
> The LHR050H41 from BananaPi is a 1280x700 4-lanes DSI panel based on the
> ILI9881c from Ilitek.
>
> Acked-by: Rob Herring
> Signed-off-by: Maxime Ripard
Looks good to me.
Reviewed-by: Linus Walleij
Yours,
Linus Walleij
On Tue, May 29, 2018 at 11:25 AM, Sudeep Holla wrote:
> On 28/05/18 13:26, Linus Walleij wrote:
>> This is a purely syntactic change that result in the same
>> DTB files from the DTS/DTSI files.
> Is it different from v1/earlier version you had posted ?
Don't think so. Just resent it as part
On Tue, May 29, 2018 at 11:49 AM, Maxime Ripard
wrote:
> The BananaPi M2M has an optional 1280x720 DSI panel. Since that panel is
> optional, we can only show a DT patch that would show how to enable it.
>
> Signed-off-by: Maxime Ripard
This looks very nice.
Reviewed-by: Linus Walleij
Yours,
This adds the Vive Pro's EDID information and
sets EDID_QUIRK_NON_DESKTOP.
Signed-off-by: Lubosz Sarnecki
---
drivers/gpu/drm/drm_edid.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index 39f1db4acda4..2697ff51f1ac
Am Dienstag, 29. Mai 2018, 13:59:42 CEST schrieb Robin Murphy:
> On 28/05/18 14:20, Heiko Stuebner wrote:
> > From: Sandy Huang
> >
> > The vop irq is shared between vop and iommu and irq probing in the
> > iommu driver moved to the probe function recently. This can in some
> > cases lead to a
https://bugzilla.kernel.org/show_bug.cgi?id=199653
James Le Cuirot (ch...@gentoo.org) changed:
What|Removed |Added
CC||ch...@gentoo.org
So drivers don't need dummy functions just returning NULL.
Cc: Daniel Vetter
Signed-off-by: Gerd Hoffmann
---
include/linux/dma-buf.h | 4 ++--
drivers/dma-buf/dma-buf.c | 4
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/include/linux/dma-buf.h b/include/linux/dma-buf.h
On Mon, May 28, 2018 at 04:32:43PM +0200, Boris Brezillon wrote:
> +Thierry
>
> Hi Arnd,
>
> On Fri, 25 May 2018 17:50:15 +0200
> Arnd Bergmann wrote:
>
> > These two functions are unused in some configurations, and using
> > __maybe_unused
> > is the easiest way to shut up the harmless
On Mon, May 14, 2018 at 09:08:49PM +0200, Lukasz Majewski wrote:
> This commit adds support for AUO's 7.0" display.
>
> Signed-off-by: Lukasz Majewski
> Reviewed-by: Rob Herring
>
> ---
> Changes for v3:
> - Remove not used 'bus-format-override = "rgb565";' property
>
> Changes for v2:
> -
Replace version checks with the helper functions bound to
cfg_handler for DSI v2, DSI 6G 1.x and DSI 6G v2.0+ controllers
Signed-off-by: Sibi Sankar
---
drivers/gpu/drm/msm/dsi/dsi_host.c | 241 -
1 file changed, 29 insertions(+), 212 deletions(-)
diff --git
This patch series aims to create and bind dsi host controller helper
functions to functionalities that vary across DSI v2, DSI 6G 1.x and
DSI 6G v2.0+ controllers. These functionalities are currently under
excessive version checks which is now replaced with the corresponding
helper function.
V4:
Add dsi host helper functions support for DSI v2 and DSI 6G 1.x
controllers that are under version checks
Signed-off-by: Sibi Sankar
---
drivers/gpu/drm/msm/dsi/dsi.h | 1 +
drivers/gpu/drm/msm/dsi/dsi_cfg.h | 12
2 files changed, 13 insertions(+)
diff --git
Add dsi host helper function implementation for DSI v2
DSI 6G 1.x and DSI 6G v2.0+ controllers
Signed-off-by: Sibi Sankar
---
drivers/gpu/drm/msm/dsi/dsi.h | 15 ++
drivers/gpu/drm/msm/dsi/dsi_cfg.c | 56 ++--
drivers/gpu/drm/msm/dsi/dsi_host.c | 218 -
3
On Mon, May 28, 2018 at 09:55:19AM +0200, Lukasz Majewski wrote:
> Hi,
>
> > Hi Thierry,
> >
> > > This commit adds support for KOE's 5.7" display.
> > >
> >
> > Thierry, shall I perform some more work on this code, or is it
> > eligible for applying to your tree?
>
> Gentle ping. If
On Tue, May 29, 2018 at 05:33:38PM +0200, Lukasz Majewski wrote:
> Hi Thierry,
>
> > On Tue, May 29, 2018 at 05:01:48PM +0200, Lukasz Majewski wrote:
> > > Hi Thierry,
> > >
> > > > On Mon, May 28, 2018 at 09:55:19AM +0200, Lukasz Majewski wrote:
> > > > > Hi,
> > > > >
> > > > > > Hi
Hi Dave,
Although we didn't have anything for you last week, we have a couple of
one-liners this week. Tomi is fixing a regression introduced in 4.17, and
Dhinakaran added a previously unsupported psr setup time which could be
affecting displays in the wild.
drm-misc-fixes-2018-05-29:
core: Add
On Tue, May 29, 2018 at 05:01:48PM +0200, Lukasz Majewski wrote:
> Hi Thierry,
>
> > On Mon, May 28, 2018 at 09:55:19AM +0200, Lukasz Majewski wrote:
> > > Hi,
> > >
> > > > Hi Thierry,
> > > >
> > > > > This commit adds support for KOE's 5.7" display.
> > > > >
> > > >
> > > >
On Sat, May 26, 2018 at 11:36:29AM +0100, Mark Brown wrote:
> Currently -next is failing to boot on Jetson TK1. The problem looks to
> be the Nouveau driver, during initialization it reports an address
> decode error then starts printing error messages saying "nouveau
> 5700.gpu: fifo:
Hi Dave,
One potential Spectre vector plugging patch, a NULL deref fix and
a DMI info fix reported by user.
This is still based on -rc6 as my flight was delayed last week to
the extent I missed possibility of sending the PR.
For 4.19, Rodrigo will be picking up drm-next after Jani is done
with
98 matches
Mail list logo
