On 4/6/2018 11:14 PM, Ville Syrjälä wrote:
On Fri, Apr 06, 2018 at 10:55:14PM +0530, Nautiyal, Ankit K wrote:
This patch is causing failure of IGT test kms_3d. The kms_3d test
expects the no. of 3d modes to be 13.
(The test has hard-coded value for expected no. of 3d modes as 13)
But due to
On Tue, Apr 17, 2018 at 02:16:59AM +0300, StanLis wrote:
> From: Stanislav Lisovskiy
>
> Added encoding of drm content_type property from
> drm_connector_state within AVI infoframe in order to properly handle
> external HDMI TV content-type setting.
>
>
Noralf,
Thanks for the guidance on how to use the mi0283qt driver to run the
panel included in the Adafruit 2.8" capacitive PiTFT Plus (running on
top of a Raspberry Pi 3).
I am working with 4.16.0 (Fedora 28). I can get the driver to load, and
have console output appearing on it, but I have run
On Fri, Apr 13, 2018 at 01:52:17PM -0700, abhin...@codeaurora.org wrote:
> On 2018-04-13 13:29, Sean Paul wrote:
> > On Tue, Apr 10, 2018 at 06:54:07PM -0700, Abhinav Kumar wrote:
> > > Currently the DSI PHY timings are hard-coded for a specific panel
> > > for the 10nm PHY.
> > >
> > > Replace
Hi Sean
Thanks for reviewing.
Reply inline.
On 2018-04-16 10:07, Sean Paul wrote:
On Fri, Apr 13, 2018 at 03:04:48PM -0700, abhin...@codeaurora.org
wrote:
On 2018-04-13 14:10, abhin...@codeaurora.org wrote:
> Hi Sean
>
> Thanks for the review.
>
> Reply inline.
>
> On 2018-04-13 13:26, Sean
Chris Wilson writes:
> Quoting Jordan Crouse (2018-04-05 23:06:53)
>> On Thu, Apr 05, 2018 at 04:00:47PM -0600, Jordan Crouse wrote:
>> > The i915 DRM driver very cleverly used ascii85 encoding for their
>> > GPU state file. Move the encode functions to a general header
SDM845 DPU driver was talking to dsi-staging driver for its dsi
operations through the customized dpu_connector layer. The following
series of patches removes DPU dependency from various dpu
connector API's before purging the dpu_connector altogether. It
also completes the switch to upstream DSI
Switch DPU from dsi-staging to upstream dsi driver. To make
the switch atomic, this change includes:
- remove dpu connector layers
- clean up dpu connector dependencies in encoder/crtc
- compile out writeback and display port drivers
- compile out dsi-staging driver (separate patch submitted to
Hi Sandy,
On Tue, 10 Apr 2018 20:40:06 +0800, Sandy Huang wrote:
> Reviewed-by: Sandy huang
Thanks for the review, but I don't see this in drm-misc yet. Are you
planning to pick this up?
> 在 2018/3/29 0:03, John Keeping 写道:
> > We have seen a case of a bad reference
On Tue, Apr 03, 2018 at 08:08:32PM +0200, Daniel Vetter wrote:
> I did not mean you should dma_map_sg/page. I just meant that using
> dma_map_resource to fill only the dma address part of the sg table seems
> perfectly sufficient.
But that is not how the interface work, especially facing
On Mon, Apr 16, 2018 at 2:39 PM, Christoph Hellwig wrote:
> On Tue, Apr 03, 2018 at 08:08:32PM +0200, Daniel Vetter wrote:
>> I did not mean you should dma_map_sg/page. I just meant that using
>> dma_map_resource to fill only the dma address part of the sg table seems
>>
https://bugzilla.kernel.org/show_bug.cgi?id=199407
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
Upstream DSI driver doesn't support DSC panels yet. Remove
the support for compression from DPU for now.
Signed-off-by: Jeykumar Sankaran
---
drivers/gpu/drm/msm/Makefile | 1 -
drivers/gpu/drm/msm/disp/dpu1/dpu_connector.c | 4 -
Remove custom ioctl support in SDM845 which allows
user space to register/unregister for hw events.
Signed-off-by: Jeykumar Sankaran
---
drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 218 +--
drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.h | 1 -
Remove autorefresh support for smart panels in SDM845 for now.
It needs more discussion to figure out the user space
communication to set preference for the feature.
Signed-off-by: Jeykumar Sankaran
---
drivers/gpu/drm/msm/disp/dpu1/dpu_connector.c | 7 -
On Mon, Apr 16, 2018 at 12:41 PM Bjorn Andersson
wrote:
> On Sat 14 Apr 00:25 PDT 2018, Abhinav Kumar wrote:
> > Register truly panel as a backlight led device and
> > provide methods to control its backlight operation.
> >
> > Changes in v2:
> > - Removed redundant
On Mon, Apr 16, 2018 at 11:32:50AM +0530, spa...@codeaurora.org wrote:
> On 2018-04-14 00:59, Sean Paul wrote:
> > On Fri, Apr 13, 2018 at 10:53:00AM +0530, Sandeep Panda wrote:
> > > Add support for TI's sn65dsi86 dsi2edp bridge chip.
> > > The chip converts DSI transmitted signal to eDP signal,
On Fri, Apr 13, 2018 at 03:04:48PM -0700, abhin...@codeaurora.org wrote:
> On 2018-04-13 14:10, abhin...@codeaurora.org wrote:
> > Hi Sean
> >
> > Thanks for the review.
> >
> > Reply inline.
> >
> > On 2018-04-13 13:26, Sean Paul wrote:
> > > On Tue, Apr 10, 2018 at 06:54:06PM -0700, Abhinav
Ping pong split topology was meant for low end soc's which
doesn't have enough layer mixers to support split panels.
Considering how uncommon the topology is for current chipset's and
also to simply the driver programming, striping off the support
for SDM845.
Signed-off-by: Jeykumar Sankaran
On Fri, Apr 13, 2018 at 01:59:29PM -0700, abhin...@codeaurora.org wrote:
> Hi Sean
>
> Thanks for the comments.
>
> Some replies inline.
>
> On 2018-04-13 13:46, Sean Paul wrote:
> > On Sat, Apr 07, 2018 at 12:06:53AM -0700, Abhinav Kumar wrote:
> > > Register truly panel as a backlight led
The GPU subsystem node was a workaround to have a central device to
bind V3D and display to. Following the lead of 246774d17fc0
("drm/etnaviv: remove the need for a gpu-subsystem DT node"), remove
the subsystem node usage and just create a platform device for the DRM
device to attach to if any of
https://bugs.freedesktop.org/show_bug.cgi?id=105760
--- Comment #3 from Alex Deucher ---
Is the driver build as a module or built into the kernel?
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugzilla.kernel.org/show_bug.cgi?id=199407
--- Comment #3 from Alex Deucher (alexdeuc...@gmail.com) ---
It's in 4.17 and should show up in 4.16 via stable updates over the next few
weeks.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=199407
--- Comment #4 from Dan (dan...@consultd.de) ---
excellent!! Thank you!!
Dan
On 4/16/2018 5:19 PM, bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=199407
>
> --- Comment #3 from Alex Deucher
LSPCON adapters in low-power state may ignore the first I2C write during
TMDS output buffer enabling, resulting in a blank screen even with an
otherwise enabled pipe. Fix this by reading back and validating the
written value a few times.
The problem was noticed on GLK machines with an onboard
Den 16.04.2018 10.27, skrev Daniel Vetter:
On Sat, Apr 14, 2018 at 01:53:12PM +0200, Noralf Trønnes wrote:
The modesetting code is already present, this adds the rest of the API.
Mentioning the TODO in the commit message would be good. Helps readers
like me who have an attention span measured
On Thu, Apr 5, 2018 at 8:09 AM Ramalingam C wrote:
> In both HDMI and DP, device count is represented by 6:0 bits of a
> register(BInfo/Bstatus)
> So macro for bitmasking the device_count is fixed(0x3F->0x7F).
> v3:
>Retained the Rb-ed.
> v4:
>%s/drm\/i915/drm
https://bugs.freedesktop.org/show_bug.cgi?id=102553
Alex Deucher changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=106054
--- Comment #1 from Alex Deucher ---
Flashing random vbioses is not supported and will likely void your warranty.
--
You are receiving this mail because:
You are the assignee for the
From: Stanislav Lisovskiy
Added encoding of drm content_type property from
drm_connector_state within AVI infoframe in order to properly handle
external HDMI TV content-type setting.
Signed-off-by: Stanislav Lisovskiy
---
From: Stanislav Lisovskiy
Added content_type property to
drm_connector_state in order to properly handle
external HDMI TV content-type setting.
Signed-off-by: Stanislav Lisovskiy
---
Documentation/gpu/kms-properties.csv | 1 +
From: Stanislav Lisovskiy
Added content type setting property to drm_connector(part 1)
and enabled transmitting it with HDMI AVI infoframes
for i915(part 2).
Stanislav Lisovskiy (2):
drm: content-type property for HDMI connector
i915: content-type property for
https://bugs.freedesktop.org/show_bug.cgi?id=106054
--- Comment #2 from Tom Englund ---
oh i know :), just thought it maybe might be useful to know about or look at if
there is something wrong in the driver, but i fully accept its my own fault if
otherwise :D
--
You are
Hi All,
I have implemented a WSEGL plugin library for Imagination's PVR driver
for SGX, which allows using SGX via DRI3. In other words, it is one
piece in the puzzle of using SGX with X11.
The project is not production quality, as I have not had time to perfect
it (and, to be honest, I'm not
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #84 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Hi Andrey
I have removed the GALLIUM_DDEBUG=flush hack and performed around 10 boots. I
have not been able to replicate the bug.
I am porting the patch to my current distro
https://bugzilla.kernel.org/show_bug.cgi?id=199407
--- Comment #2 from Dan (dan...@consultd.de) ---
Thx a million...
appreciate your support very much
as a newbie, sorry for the question: How can I know what the next kernel
version with this amended will be?
4.16.2 still has this problem
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #85 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
(In reply to Ricardo Ribalda from comment #84)
> Hi Andrey
>
> I have removed the GALLIUM_DDEBUG=flush hack and performed around 10 boots.
> I have not been able to
Den 16.04.2018 10.46, skrev Daniel Vetter:
On Sat, Apr 14, 2018 at 01:53:14PM +0200, Noralf Trønnes wrote:
These helpers keep track of fbdev users and drm_driver.last_close will
only restore fbdev when actually in use. Additionally the display is
turned off when the last user is closing. fbcon
> Subject: Re: [kbuild-all] [PATCH] drm: fix drm-get-put.cocci warnings
>
> On Thu, Apr 12, 2018 at 07:54:10AM +0200, Julia Lawall wrote:
> > From: Fengguang Wu
> >
> > Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and
> > drm_*_unreference()
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #11 from taij...@posteo.de ---
(In reply to Joshua Lee from comment #3)
> How do I find an prior boot's dmesg?
Try "journalctl -b -1" (for the boot attempt directly prior to this one, -2 for
the one before that, etc...).
--
You
Ok, confusion around backend is I think cleared up. The other
confusion seems to be around dma-buf:
dma-buf is the cross subsystem zerocopy abstraction. PRIME is the
drm-specific support for it, 100% based on top of the generic struct
dma_buf.
You need a dma_buf exporter to convert a xen grant
On Mon, Apr 16, 2018 at 2:15 PM, Thomas Hellstrom wrote:
> On 04/16/2018 11:19 AM, Daniel Vetter wrote:
>>
>> On Mon, Apr 16, 2018 at 10:23 AM, Thomas Hellstrom
>> wrote:
>>>
>>> On 04/14/2018 10:33 AM, Daniel Vetter wrote:
Hi Thomas,
On 09/04/18 11:41, Daniel Vetter wrote:
> On Fri, Apr 06, 2018 at 09:10:43AM +0300, Tomi Valkeinen wrote:
>> On 05/04/18 19:50, Daniel Vetter wrote:
>>> On Thu, Apr 05, 2018 at 06:13:58PM +0300, Ville Syrjala wrote:
From: Ville Syrjälä
https://bugs.freedesktop.org/show_bug.cgi?id=105760
taij...@posteo.de changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #9 from taij...@posteo.de ---
This is possibly the same bug described in bug #105760.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=105883
taij...@posteo.de changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
Hello, all!
After discussing xen-zcopy and hyper-dmabuf [1] approaches
it seems that xen-zcopy can be made not depend on DRM core any more
and be dma-buf centric (which it in fact is).
The DRM code was mostly there for dma-buf's FD import/export
with DRM PRIME UAPI and with DRM use-cases in
On Wed, 2018-04-11 at 17:31 +0200, Lucas Stach wrote:
> The LVDS signal integrity is only guaranteed when the correct enable
> sequence (first IPU DI, then LDB) is used. If the LDB display output was
> active before the imx-drm driver is loaded (like when a bootsplash was
> active) the DI will be
On Mon, 16 Apr 2018, Daniel Vetter wrote:
> On Thu, Apr 12, 2018 at 07:54:10AM +0200, Julia Lawall wrote:
> > From: Fengguang Wu
> >
> > Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and
> > drm_*_unreference() helpers.
> >
> > Generated by:
On Sat, Apr 14, 2018 at 8:54 AM, Peter Rosin wrote:
> On 2018-04-13 19:46, Rob Herring wrote:
>> On Mon, Apr 09, 2018 at 12:59:15PM +0200, Peter Rosin wrote:
>>> Useful for beating cases where an output mode selection heuristic
>>> fails.
>>>
>>> Signed-off-by: Peter Rosin
On Mon, Apr 16, 2018 at 12:30:13PM +0200, Robert Foss wrote:
Hi Rob,
Thanks for the review.
> Hey Alexandru,
>
> Feel free to add:
> Signed-off-by: Robert Foss
>
Should I re-send this 3 patches or could you just pushed them to
master and adding your SoB in the
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #10 from taij...@posteo.de ---
And yes, Arch has had CONFIG_DRM_AMD_DC_DCN1_0=y since 4.15.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
https://bugs.freedesktop.org/show_bug.cgi?id=105680
Marta Löfstedt changed:
What|Removed |Added
Status|RESOLVED|REOPENED
vers/base/platform.c#L553
but was apparently removed in 4.5:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/base/platform.c?h=next-20180416=2d30bb0b3889adf09b342722b2ce596c0763bc93
So we might not need this patch anymore.
Best regards,
Tomasz
Den 16.04.2018 10.21, skrev Daniel Vetter:
On Sat, Apr 14, 2018 at 01:52:53PM +0200, Noralf Trønnes wrote:
This patchset explores the possibility of having generic fbdev emulation
in DRM for drivers that supports dumb buffers which they can export. An
API is added to support in-kernel clients
Rockchip doesn't support per-pixel alpha blending for the lowest
window in the stack. While the hw supports restacking the windows, we
don't expose that in KMS, so just filter out alpha formats for the
primary plane.
Change-Id: I7828d5bf0f0b5c6dd23f9e52aa01a5a683131d2f
Signed-off-by: Kristian H.
On Wed, Apr 11, 2018 at 04:22:13PM +0100, Alexandru Gheorghe wrote:
> vsyncworker::Routine assumes that when -EINTR is returned by
> WaitForSignalOrExitLocked the lock as been released, which is not
> true, so it hangs if a vsyncworker is never enabled and Exit is
> called.
>
> There are two code
On Wed, Apr 11, 2018 at 04:22:18PM +0100, Alexandru Gheorghe wrote:
> In the current implementation TryEncoderForDisplay just looks
> at the crtc linked to the display, if that's not assigned to
> a display it means the encoder could be used, otherwise iterate
> to the list of possible_crtcs and
On Mon, Apr 16, 2018 at 12:25 PM, Eric Anholt wrote:
> The GPU subsystem node was a workaround to have a central device to
> bind V3D and display to. Following the lead of 246774d17fc0
> ("drm/etnaviv: remove the need for a gpu-subsystem DT node"), remove
> the subsystem node
On Mon, Apr 16, 2018 at 10:44:57AM -0700, abhin...@codeaurora.org wrote:
> Hi Sean
>
> Thanks for reviewing.
>
> Reply inline.
>
> On 2018-04-16 10:07, Sean Paul wrote:
> > On Fri, Apr 13, 2018 at 03:04:48PM -0700, abhin...@codeaurora.org wrote:
> > > On 2018-04-13 14:10,
On Thu, Apr 12, 2018 at 04:37:15PM +0200, Lukasz Majewski wrote:
> This commit adds support for KOE's 5.7" display.
>
> Signed-off-by: Lukasz Majewski
> ---
> .../bindings/display/panel/koe,tx14d24vm1bpa.txt | 42
> ++
> drivers/gpu/drm/panel/panel-simple.c
On Fri, Apr 13, 2018 at 10:53:01AM +0530, Sandeep Panda wrote:
> Document the bindings used for the sn65dsi86 DSI to eDP bridge.
>
> Signed-off-by: Sandeep Panda
> ---
> .../bindings/display/bridge/ti,sn65dsi86.txt | 75
> ++
> 1 file changed,
On Wed, Apr 11, 2018 at 04:22:16PM +0100, Alexandru Gheorghe wrote:
> Use the newly added ResourceManager for creating and detecting all the
> drm devices instead of assuming that there is only one device.
>
> Signed-off-by: Alexandru Gheorghe
> ---
>
On Wed, Apr 11, 2018 at 09:39:24AM +0200, Maxime Ripard wrote:
> Hi,
>
> This serie aims at enhancing the support for plane-wide alpha in the
> drivers that are implementing it at the moment, by turning it into a
> generic property and converting the drivers (rcar-du and atmel-hclcdc). It
> also
Stefan Schake writes:
> The hardware has a single block for applying a CTM prior to gamma lut.
> It can be fed with pixels from one of our CRTC at a time and uses a
> matrix with S0.9 scalars. Use private atomic state to reject attempts
> from userland to apply CTM for more
On Wed, Apr 11, 2018 at 04:22:19PM +0100, Alexandru Gheorghe wrote:
> drmModeEncoder has a field called possible_clones. It's a bit mask
> which tells if the encoder could be simultaneously connected, to the
> same CRTC, with the encoders specified in the possible_clones mask.
>
> Signed-off-by:
Yeah, I definitely agree on the idea of expanding the use case to the
general domain where dmabuf sharing is used. However, what you are
targetting with proposed changes is identical to the core design of
hyper_dmabuf.
On top of this basic functionalities, hyper_dmabuf has driver level
On Wed, Apr 11, 2018 at 04:22:17PM +0100, Alexandru Gheorghe wrote:
> Writeback connector is a special case of connector, which can be
> linked to a CRTC in order to get the result of the composition back to
> a memory buffer. This had not been merged to the mainline kernel yet,
> latest version
On Mon, Apr 16, 2018 at 12:01:03PM -0700, Kristian H. Kristensen wrote:
> Rockchip doesn't support per-pixel alpha blending for the lowest
> window in the stack. While the hw supports restacking the windows, we
> don't expose that in KMS, so just filter out alpha formats for the
> primary plane.
>
Hi John,
Am Montag, 16. April 2018, 18:46:56 CEST schrieb John Keeping:
> Hi Sandy,
>
> On Tue, 10 Apr 2018 20:40:06 +0800, Sandy Huang wrote:
>
> > Reviewed-by: Sandy huang
>
> Thanks for the review, but I don't see this in drm-misc yet. Are you
> planning to pick this
The GPU subsystem node was a workaround to have a central device to
bind V3D and display to. Following the lead of 246774d17fc0
("drm/etnaviv: remove the need for a gpu-subsystem DT node"), remove
the subsystem node usage and just create a platform device for the DRM
device to attach to if any of
https://bugs.freedesktop.org/show_bug.cgi?id=106053
--- Comment #3 from Roland Scheidegger ---
(In reply to Marek Olšák from comment #2)
> r300g on RC410 uses software emulation for vertex shaders and clipping (the
> same code as llvmpipe), because the hardware doesn't have
"Kristian H. Kristensen" writes:
> Rockchip doesn't support per-pixel alpha blending for the lowest
> window in the stack. While the hw supports restacking the windows, we
> don't expose that in KMS, so just filter out alpha formats for the
> primary plane.
In discussing
https://bugs.freedesktop.org/show_bug.cgi?id=106053
--- Comment #4 from Marek Olšák ---
I think the hw doesn't have a clipper, though it shouldn't be hard to verify if
it's true. Yeah, draw could use some optimizations for the clipper, e.g. the
guardband, but simply doing
On Mon, Apr 16, 2018 at 2:59 PM Eric Anholt wrote:
> "Kristian H. Kristensen" writes:
> > Rockchip doesn't support per-pixel alpha blending for the lowest
> > window in the stack. While the hw supports restacking the windows, we
> > don't expose that in
Blending win0 with the background color doesn't seem to work
correctly. We only get the background color, no matter the contents of
the win0 framebuffer. However, blending pre-multiplied color with the
default opaque black default background color is a no-op, so we can
just disable blending to
Hi Bjorn
Thanks for the review.
Reply inline.
On 2018-04-16 09:41, Bjorn Andersson wrote:
On Sat 14 Apr 00:25 PDT 2018, Abhinav Kumar wrote:
Register truly panel as a backlight led device and
provide methods to control its backlight operation.
Changes in v2:
- Removed redundant NULL checks
>-Original Message-
>From: Jani Nikula [mailto:jani.nik...@linux.intel.com]
>Sent: Wednesday, April 11, 2018 5:27 AM
>To: Ian W MORRISON
>Cc: Vivi, Rodrigo ; Srivatsa, Anusha
>; Wajdeczko, Michal
On 04/13/2018 06:37 PM, Daniel Vetter wrote:
On Wed, Apr 11, 2018 at 08:59:32AM +0300, Oleksandr Andrushchenko wrote:
On 04/10/2018 08:26 PM, Dongwon Kim wrote:
On Tue, Apr 10, 2018 at 09:37:53AM +0300, Oleksandr Andrushchenko wrote:
On 04/06/2018 09:57 PM, Dongwon Kim wrote:
On Fri, Apr 06,
On Thu, Apr 12, 2018 at 06:34:46PM +0200, Noralf Trønnes wrote:
> I hit a 'Sending rate exceeded' error with this patchset, so it didn't go
> out as it should.
> I will resend the patchset when I find out how to avoid this problem.
That's generally an issue with your ISP. gmail works ime for mail
On Thu, Apr 12, 2018 at 07:54:10AM +0200, Julia Lawall wrote:
> From: Fengguang Wu
>
> Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and
> drm_*_unreference() helpers.
>
> Generated by: scripts/coccinelle/api/drm-get-put.cocci
>
> Fixes:
On 04/14/2018 10:33 AM, Daniel Vetter wrote:
Hi Thomas,
On Fri, Apr 13, 2018 at 10:23 PM, Thomas Hellstrom
wrote:
On 04/13/2018 07:13 PM, Daniel Vetter wrote:
On Wed, Apr 11, 2018 at 10:27:06AM +0200, Thomas Hellstrom wrote:
2) Should we add a *real* wound-wait choice
On Sat, Apr 14, 2018 at 01:53:12PM +0200, Noralf Trønnes wrote:
> The modesetting code is already present, this adds the rest of the API.
Mentioning the TODO in the commit message would be good. Helps readers
like me who have an attention span measured in seconds :-)
Just commenting on the
+CC: linux-input list and maintainer
On 05.04.2018 11:49, Enric Balletbo i Serra wrote:
> From: "Kristian H. Kristensen"
>
> To improve PSR exit latency, we speculatively start exiting when we
> receive input events. Occasionally, this may lead to false positives,
> but
On 2018-04-14 00:59, Sean Paul wrote:
On Fri, Apr 13, 2018 at 10:53:00AM +0530, 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
From: Randy Dunlap
When CONFIG_MMU_NOTIFIER is not enabled, struct mmu_notifier has an
incomplete type definition, which causes build errors.
../drivers/gpu/drm/amd/amdkfd/kfd_priv.h:607:22: error: field 'mmu_notifier'
has incomplete type
On 2018-04-13 19:46, Rob Herring wrote:
> On Mon, Apr 09, 2018 at 12:59:15PM +0200, Peter Rosin wrote:
>> Useful for beating cases where an output mode selection heuristic
>> fails.
>>
>> Signed-off-by: Peter Rosin
>> ---
>>
Use new return type vm_fault_t for fault handler
in struct vm_operations_struct.
Signed-off-by: Souptick Joarder
Reviewed-by: Matthew Wilcox
---
drivers/gpu/drm/gma500/framebuffer.c | 14 +-
drivers/gpu/drm/gma500/gem.c | 27
On Fri, Apr 13, 2018 at 5:39 PM, Maxime Ripard
wrote:
> On Fri, Apr 13, 2018 at 05:30:04PM +0530, Jagan Teki wrote:
>> On Wed, Apr 11, 2018 at 6:13 PM, Maxime Ripard
>> wrote:
>> > On Wed, Apr 04, 2018 at 11:57:08AM +0200, Maxime Ripard
Use new return type vm_fault_t for fault handler
in struct vm_operations_struct.
Signed-off-by: Souptick Joarder
Reviewed-by: Matthew Wilcox
---
drivers/gpu/drm/exynos/exynos_drm_gem.c | 21 -
Three^W Two of the TTM drivers intercept the pagefault handler in a rather
un-Linuxy and racy way. If they really must intercept the fault call
(and it's not clear to me that they need to), I'd rather see them do it
like this.
The QXL driver seems least likely to need it; as the virtio driver
On Wed, Apr 11, 2018 at 6:13 PM, Maxime Ripard
wrote:
> On Wed, Apr 04, 2018 at 11:57:08AM +0200, Maxime Ripard wrote:
>> Hi,
>>
>> Here is an preliminary version of the MIPI-DSI support for the Allwinner
>> SoCs.
>>
>> This controller can be found on a number of recent
On Mon, Apr 16, 2018 at 10:16:31AM +0300, Oleksandr Andrushchenko wrote:
> On 04/13/2018 06:37 PM, Daniel Vetter wrote:
> > On Wed, Apr 11, 2018 at 08:59:32AM +0300, Oleksandr Andrushchenko wrote:
> > > On 04/10/2018 08:26 PM, Dongwon Kim wrote:
> > > > On Tue, Apr 10, 2018 at 09:37:53AM +0300,
On 04/16/2018 10:43 AM, Daniel Vetter wrote:
On Mon, Apr 16, 2018 at 10:16:31AM +0300, Oleksandr Andrushchenko wrote:
On 04/13/2018 06:37 PM, Daniel Vetter wrote:
On Wed, Apr 11, 2018 at 08:59:32AM +0300, Oleksandr Andrushchenko wrote:
On 04/10/2018 08:26 PM, Dongwon Kim wrote:
On Tue, Apr
On Sat, Apr 14, 2018 at 01:53:04PM +0200, Noralf Trønnes wrote:
> Add functions to deal with the registred connectors as an array:
> - drm_connector_get_all()
> - drm_connector_put_all()
>
> And to get the enabled status of those connectors:
> drm_connector_get_enabled_status()
>
> This is prep
On Sat, Apr 14, 2018 at 01:52:53PM +0200, Noralf Trønnes wrote:
> This patchset explores the possibility of having generic fbdev emulation
> in DRM for drivers that supports dumb buffers which they can export. An
> API is added to support in-kernel clients in general.
>
> In this version I was
On Sat, Apr 14, 2018 at 01:52:59PM +0200, Noralf Trønnes wrote:
> Prepare for moving drm_fb_helper modesetting code to drm_client.
> drm_client will be linked to drm.ko, so move
> __drm_atomic_helper_disable_plane() and __drm_atomic_helper_set_config()
> out of drm_kms_helper.ko.
>
>
This patch series adds support to DSI connector
virtualization for Dual-DSI configuration.
These changes have been tested using dual-dsi truly panel on sdm845 platform.
Additional changes that will be needed to have end-to-end functionality:
--> DSI6G-v2 changes:
https://bugs.freedesktop.org/show_bug.cgi?id=106053
--- Comment #5 from Roland Scheidegger ---
(In reply to Marek Olšák from comment #4)
> I think the hw doesn't have a clipper, though it shouldn't be hard to verify
> if it's true. Yeah, draw could use some optimizations for
Applied to drm-misc-next. Thanks!
在 2018/4/17 5:43, Heiko Stuebner 写道:
Hi John,
Am Montag, 16. April 2018, 18:46:56 CEST schrieb John Keeping:
Hi Sandy,
On Tue, 10 Apr 2018 20:40:06 +0800, Sandy Huang wrote:
Reviewed-by: Sandy huang
Thanks for the review, but I
1 - 100 of 144 matches
Mail list logo