Re: [Intel-gfx] [PATCH] drm/atomic: Fix memleak on ERESTARTSYS during non-blocking commits

On Wed, Jan 17, 2018 at 12:51:08PM +0100, Maarten Lankhorst wrote: > From: "Leo (Sunpeng) Li" > > During a non-blocking commit, it is possible to return before the > commit_tail work is queued (-ERESTARTSYS, for example). > > Since a reference on the crtc commit object is

Re: [PATCH] [v2] drm/exynos: g2d: use monotonic timestamps

Hey Arnd, looks good to me! Reviewed-by: Tobias Jakobi - Tobias Arnd Bergmann wrote: > The exynos DRM driver uses real-time 'struct timeval' values > for exporting its timestamps to user space. This has multiple > problems: > > 1. signed seconds overflow in

[Bug 102800] DRI_PRIME regression- radeon: Failed to allocate virtual address for buffer

https://bugs.freedesktop.org/show_bug.cgi?id=102800 --- Comment #19 from higu...@gmx.net --- Created attachment 136810 --> https://bugs.freedesktop.org/attachment.cgi?id=136810=edit Dmesg with patch Here is the dmesg with the patch applied -- You are receiving this mail because: You are the

Re: [PATCH 01/19] drm/fourcc: Add a function to tell if the format embeds alpha

On Tue, Jan 16, 2018 at 09:17:24PM +0100, Maxime Ripard wrote: > Hi Ayan, > > On Mon, Jan 15, 2018 at 03:47:44PM +, Ayan Halder wrote: > > On Tue, Jan 09, 2018 at 02:28:33PM +0100, Maxime Ripard wrote: > > > On Tue, Jan 09, 2018 at 02:29:58PM +0200, Laurent Pinchart wrote: > > > > On Tuesday,

[Bug 104001] GPU driver hung when start steam client while playback video on Youtube (it occurs on latest staging kernel)

https://bugs.freedesktop.org/show_bug.cgi?id=104001 --- Comment #16 from mikhail.v.gavri...@gmail.com --- Created attachment 136809 --> https://bugs.freedesktop.org/attachment.cgi?id=136809=edit dmesg with 4.15.0-rc4 amd-staging-drm-next with SysRq : Show State -- You are receiving this mail

Re: [PATCH] drm: Remove bridge support from legacy helpers

On Wed, Jan 17, 2018 at 07:27:03PM +0200, Laurent Pinchart wrote: > DRM bridges are only used by atomic drivers, and none of them use the > legacy helpers. Drop bridge support from those helpers to prepare for > making the bridge operations atomic-aware. > > Signed-off-by: Laurent Pinchart

Re: [PATCH] drm/panel: panasonic-vvx10f034n00: Fix wuxga_nt_panel_disable() return value

On Wed, Jan 17, 2018 at 05:01:07PM +, Philippe CORNU wrote: > Hi Sean, > > On 01/16/2018 11:22 PM, Sean Paul wrote: > > Return value for mipi_dsi_shutdown_peripheral() is unchecked. > > Check it and return any errors if they come up. Even if > > mipi_dsi_shutdown_peripheral() fails, continue

[PATCH] drm: Remove bridge support from legacy helpers

DRM bridges are only used by atomic drivers, and none of them use the legacy helpers. Drop bridge support from those helpers to prepare for making the bridge operations atomic-aware. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/drm_crtc_helper.c

Re: [PATCH 2/6] backlight/generic-bl: remove DRIVER1 state

On Wed, Jan 17, 2018 at 04:44:00PM +, Daniel Thompson wrote: > On 17/01/18 14:01, Daniel Vetter wrote: > > Nothing in the entire tree ever sets this, which means this is dead > > code. Remove it. > > > > Cc: Lee Jones > > Cc: Daniel Thompson

Re: [PATCH v16 05/10] video: backlight: Add devres versions of of_find_backlight

On 16/01/18 10:34, Meghana Madhyastha wrote: Add devm_of_find_backlight and the corresponding release function because some drivers use devres versions of functions for acquiring device resources. Signed-off-by: Meghana Madhyastha ---

Re: [PATCH 6/6] MAINTAINERS: add dri-devel for backlight subsystem patches

On Wednesday, January 17, 2018 11:53 AM, Daniel Thompson wrote: > On 17/01/18 14:01, Daniel Vetter wrote: > > For the same reasons we've added dri-devel for all fbdev patches: Most > > of the actively developed drivers using this infrastructure are in > > drivers/gpu/. It just makes sense to

[PATCH] [v2] drm/exynos: g2d: use monotonic timestamps

The exynos DRM driver uses real-time 'struct timeval' values for exporting its timestamps to user space. This has multiple problems: 1. signed seconds overflow in y2038 2. the 'struct timeval' definition is deprecated in the kernel 3. time may jump or go backwards after a 'settimeofday()' syscall

Re: [PATCH v16 03/10] video: backlight: Add of_find_backlight helper in backlight.c

On 16/01/18 10:33, Meghana Madhyastha wrote: Add of_find_backlight, a helper function which is a generic version of tinydrm_of_find_backlight that can be used by other drivers to avoid repetition of code and simplify things. Signed-off-by: Meghana Madhyastha

Re: [PATCH] drm/panel: panasonic-vvx10f034n00: Fix wuxga_nt_panel_disable() return value

Hi Sean, On 01/16/2018 11:22 PM, Sean Paul wrote: > Return value for mipi_dsi_shutdown_peripheral() is unchecked. > Check it and return any errors if they come up. Even if > mipi_dsi_shutdown_peripheral() fails, continue attempting to > disable. > > Cc: Philippe Cornu >

Re: [PATCH v16 01/10] video: backlight: Add helpers to enable and disable backlight

On 16/01/18 10:31, Meghana Madhyastha wrote: Add helper functions backlight_enable and backlight_disable to enable/disable a backlight device. These helper functions can then be used by different drm and tinydrm drivers to avoid repetition of code and also to enforce a uniform and consistent

Re: [PATCH] exynos: drm: use monotonic timestamps

On Fri, Nov 3, 2017 at 3:04 PM, Tobias Jakobi wrote: > Hello Arnd, > > I guess you could coordinate the IPP changes with Marek, who is rewriting the > IPP subsystem anyway (added Marek to Cc). > > Here is the most recent IPPv2 series: >

Re: [PATCH 6/6] MAINTAINERS: add dri-devel for backlight subsystem patches

On 17/01/18 14:01, Daniel Vetter wrote: For the same reasons we've added dri-devel for all fbdev patches: Most of the actively developed drivers using this infrastructure are in drivers/gpu/. It just makes sense to cross-post patches and keep aligned. And total activity in the backlight

Re: [PATCH 5/6] backlight: Also nuke BL_CORE_DRIVER1

On 17/01/18 14:01, Daniel Vetter wrote: Now that the 3 drivers using this are cleaned up we can also remove this final bit of confusion of leaking driver internals into the backlight power interface. The backlight power interface itself is still a massive mess. Cc: Lee Jones

Re: [PATCH 4/6] staging/fbtft: Stop using BL_CORE_DRIVER1

On 17/01/18 14:01, Daniel Vetter wrote: Leaking driver internal tracking into the already massively confusing backlight power tracking is really confusing. Luckily we have already a drvdata structure, so fixing this is really easy. Cc: Lee Jones Cc: Daniel Thompson

Re: [PATCH -next] drm/etnaviv: make local symbols static

Am Donnerstag, den 11.01.2018, 11:34 + schrieb Wei Yongjun: > Fixes the following sparse warnings: > > drivers/gpu/drm/etnaviv/etnaviv_iommu.c:161:39: warning: >  symbol 'etnaviv_iommuv1_ops' was not declared. Should it be static? > drivers/gpu/drm/etnaviv/etnaviv_iommu_v2.c:239:39: warning:

[PATCH 1/1] drm: add kernel doc for exported gem dmabuf_ops

Signed-off-by: Samuel Li --- drivers/gpu/drm/drm_prime.c | 81 + 1 file changed, 81 insertions(+) diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c index ca09ce7..3ead5a6 100644 --- a/drivers/gpu/drm/drm_prime.c

Re: [PATCH 3/6] backlight/pandora: Stop using BL_CORE_DRIVER1

On 17/01/18 14:01, Daniel Vetter wrote: Leaking driver internal tracking into the already massively confusing backlight power tracking is really confusing. Stop that by allocating a tiny driver private data structure instead. Cc: Lee Jones Cc: Daniel Thompson

Re: [PATCH 2/6] backlight/generic-bl: remove DRIVER1 state

On 17/01/18 14:01, Daniel Vetter wrote: Nothing in the entire tree ever sets this, which means this is dead code. Remove it. Cc: Lee Jones Cc: Daniel Thompson Cc: Jingoo Han Signed-off-by: Daniel Vetter

Re: [PATCH 2/6] backlight/generic-bl: remove DRIVER1 state

On 17/01/18 14:36, Emil Velikov wrote: On 17 January 2018 at 14:01, Daniel Vetter wrote: Nothing in the entire tree ever sets this, which means this is dead code. Remove it. Cc: Lee Jones Cc: Daniel Thompson Cc:

[git pull] vmwgfx-fixes-4.15 for -rc9 / final

Dave, Last minute fixes for vmwgfx. One fix for a drm helper warning introduced in 4.15 One important fix for a longer standing memory corruption issue on older hardware versions. The following changes since commit 0d9cac0ca0429830c40fe1a4e50e60f6221fd7b6: drm/vmwgfx: Potential off by one in

Re: [PATCH] drm: arc: Don't set connector DPMS handler

On Wed, Jan 17, 2018 at 04:32:18PM +0200, Laurent Pinchart wrote: > The connector .dpms operation is only used by the legacy helpers. The > arc driver being fully atomic, the operation isn't needed anymore. > Remove it. > > Signed-off-by: Laurent Pinchart

[PATCH] [RESEND] drm: i915: remove timeval users

struct timeval is deprecated because it cannot represent times past 2038. In this driver, the only use of this structure is to capture debug information. This is easily changed to ktime_t, which we then format as needed when printing it later. Reviewed-by: Chris Wilson

[Bug 104611] [fiji, polaris10] BUG: unable to handle kernel NULL pointer dereference when waking up displays with amdgpu.dc=1

https://bugs.freedesktop.org/show_bug.cgi?id=104611 Vedran Miletić changed: What|Removed |Added Summary|[fiji] BUG: unable to |[fiji, polaris10]

[Bug 104611] [fiji] BUG: unable to handle kernel NULL pointer dereference when waking up displays with amdgpu.dc=1

https://bugs.freedesktop.org/show_bug.cgi?id=104611 --- Comment #4 from Vedran Miletić --- Created attachment 136808 --> https://bugs.freedesktop.org/attachment.cgi?id=136808=edit dmesg with rx580 amdgpu.dc_log=1 -- You are receiving this mail because: You are the

Re: [git pull] vmwgfx-fixes-4.15 for -rc9 / final

Dave, On 01/17/2018 09:40 AM, Thomas Hellstrom wrote: Dave, A last minute minimal fix to kill a warning introduced in a helper in 4.15. The following changes since commit 0d9cac0ca0429830c40fe1a4e50e60f6221fd7b6: drm/vmwgfx: Potential off by one in vmw_view_add() (2018-01-10 15:21:39

Re: [PATCH] drm/vmwgfx: fix memory corruption with legacy/sou connectors

On 01/17/2018 04:16 PM, Rob Clark wrote: From: Rob Clark It looks like in all cases 'struct vmw_connector_state' is used. But only in stdu connectors, was atomic_{duplicate,destroy}_state() properly subclassed. Leading to writes beyond the end of the allocated connector

Re: [PATCH v3 3/8] drm/edid: Fix cea mode aspect ratio handling

On Wed, Jan 17, 2018 at 02:35:40PM +0530, Sharma, Shashank wrote: > Regards > > Shashank > > > On 1/12/2018 11:51 AM, Nautiyal, Ankit K wrote: > > From: Ville Syrjälä > > > > commit 6dffd431e229 ("drm: Add aspect ratio parsing in DRM layer") > > cause us to not

[Bug 104611] [fiji] BUG: unable to handle kernel NULL pointer dereference when waking up displays with amdgpu.dc=1

https://bugs.freedesktop.org/show_bug.cgi?id=104611 --- Comment #3 from Vedran Miletić --- (In reply to Harry Wentland from comment #1) > Does this reproduce consistently or intermittently? No, but I just got it on RX 580: [ 3582.972912] BUG: unable to handle kernel NULL

Re: [PATCH v3 1/8] drm/modes: Introduce drm_mode_match()

On Wed, Jan 17, 2018 at 02:11:55PM +0530, Sharma, Shashank wrote: > > > On 1/12/2018 11:51 AM, Nautiyal, Ankit K wrote: > > From: Ville Syrjälä > > > > Make mode matching less confusing by allowing the caller to specify > > which parts of the modes should match

[PATCH] drm/vmwgfx: fix memory corruption with legacy/sou connectors

From: Rob Clark It looks like in all cases 'struct vmw_connector_state' is used. But only in stdu connectors, was atomic_{duplicate,destroy}_state() properly subclassed. Leading to writes beyond the end of the allocated connector state block and all sorts of fun memory

Re: [PATCH 1/6] backlight: Nuke unused backlight.props.state states

On 17/01/18 14:01, Daniel Vetter wrote: The backlight power state handling is supremely confusing. We have: - props.power, using FB_BLANK_* defines - props.fb_blank, using the same, but deprecated int favour of props.state - props.state, using the BL_CORE_* defines - and finally a bunch of

Re: [PATCH] [RESEND] drm/gma500: initialize gma_clock_t structures

On Wed, Jan 17, 2018 at 3:36 PM, Arnd Bergmann wrote: > On Wed, Jan 17, 2018 at 9:27 AM, Daniel Vetter wrote: >> On Tue, Jan 16, 2018 at 03:57:10PM +0100, Arnd Bergmann wrote: >>> The two functions pass a partially initialized structure back to the >>> caller

Re: [PATCH] [RESEND] drm/gma500: initialize gma_clock_t structures

On Wed, Jan 17, 2018 at 9:27 AM, Daniel Vetter wrote: > On Tue, Jan 16, 2018 at 03:57:10PM +0100, Arnd Bergmann wrote: >> The two functions pass a partially initialized structure back to the >> caller after a memset() on the destination. >> >> This is not entirely well-defined,

Re: [PATCH 2/6] backlight/generic-bl: remove DRIVER1 state

On 17 January 2018 at 14:01, Daniel Vetter wrote: > Nothing in the entire tree ever sets this, which means this is dead > code. Remove it. > > Cc: Lee Jones > Cc: Daniel Thompson > Cc: Jingoo Han >

[PATCH] drm: arc: Don't set connector DPMS handler

The connector .dpms operation is only used by the legacy helpers. The arc driver being fully atomic, the operation isn't needed anymore. Remove it. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/arc/arcpgu_sim.c | 1 - 1 file changed, 1

[PATCH] drm/arcpgu: remove drm_encoder_slave

drm_encoder_slave is the old way to write bridge drivers, for i2c bridges only. It's deprecated, and definitely should not be used in new drivers. This has absolutely nothing to do with the new bridge driver infrastructure implemented by drm_bridge. What's even strange is that arcpgu doesn't even

Re: [PATCH] drm: Don't include drm/drm_encoder_slave.h when not needed

On Wed, Jan 17, 2018 at 03:57:52PM +0200, Laurent Pinchart wrote: > The dw-hdmi, kirin and imx drivers include the drm/drm_encoder_slave.h > header but don't use the encoder slave API. Remove it or replace it with > drm/drm_encoder.h as needed. > > Signed-off-by: Laurent Pinchart

Re: [PATCH] drm/arcpgu: remove drm_encoder_slave

On Wed, Jan 17, 2018 at 01:55:55PM +, Alexey Brodkin wrote: > Hi Daniel, > > On Wed, 2018-01-17 at 14:43 +0100, Daniel Vetter wrote: > > drm_encoder_slave is the old way to write bridge drivers, for i2c > > bridges only. It's deprecated, and definitely should not be used in > > new drivers. >

[PATCH 5/6] backlight: Also nuke BL_CORE_DRIVER1

Now that the 3 drivers using this are cleaned up we can also remove this final bit of confusion of leaking driver internals into the backlight power interface. The backlight power interface itself is still a massive mess. Cc: Lee Jones Cc: Daniel Thompson

[PATCH 4/6] staging/fbtft: Stop using BL_CORE_DRIVER1

Leaking driver internal tracking into the already massively confusing backlight power tracking is really confusing. Luckily we have already a drvdata structure, so fixing this is really easy. Cc: Lee Jones Cc: Daniel Thompson Cc: Jingoo Han

[PATCH 1/6] backlight: Nuke unused backlight.props.state states

The backlight power state handling is supremely confusing. We have: - props.power, using FB_BLANK_* defines - props.fb_blank, using the same, but deprecated int favour of props.state - props.state, using the BL_CORE_* defines - and finally a bunch of backlight drivers treat brightness == 0 as

[PATCH 3/6] backlight/pandora: Stop using BL_CORE_DRIVER1

Leaking driver internal tracking into the already massively confusing backlight power tracking is really confusing. Stop that by allocating a tiny driver private data structure instead. Cc: Lee Jones Cc: Daniel Thompson Cc: Jingoo Han

[PATCH 6/6] MAINTAINERS: add dri-devel for backlight subsystem patches

For the same reasons we've added dri-devel for all fbdev patches: Most of the actively developed drivers using this infrastructure are in drivers/gpu/. It just makes sense to cross-post patches and keep aligned. And total activity in the backlight subsystem is miniscule compared to drm overall.

[PATCH 2/6] backlight/generic-bl: remove DRIVER1 state

Nothing in the entire tree ever sets this, which means this is dead code. Remove it. Cc: Lee Jones Cc: Daniel Thompson Cc: Jingoo Han Signed-off-by: Daniel Vetter ---

Re: [PATCH] drm/arcpgu: remove drm_encoder_slave

Hi Daniel, Thank you for the patch. On Wednesday, 17 January 2018 15:53:07 EET Daniel Vetter wrote: > drm_encoder_slave is the old way to write bridge drivers, for i2c > bridges only. It's deprecated, and definitely should not be used in > new drivers. > > What's even strange is that arcpgu

[PATCH] drm: Don't include drm/drm_encoder_slave.h when not needed

The dw-hdmi, kirin and imx drivers include the drm/drm_encoder_slave.h header but don't use the encoder slave API. Remove it or replace it with drm/drm_encoder.h as needed. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c

[PATCH] drm/arcpgu: remove drm_encoder_slave

drm_encoder_slave is the old way to write bridge drivers, for i2c bridges only. It's deprecated, and definitely should not be used in new drivers. What's even strange is that arcpgu doesn't even use any of this, it really only wants a plain normal drm_encoder. Nuke all the surplus real estate.

[Bug 198123] Console is the wrong color at boot with radeon 6670

https://bugzilla.kernel.org/show_bug.cgi?id=198123 --- Comment #19 from Daniel Vetter (dan...@ffwll.ch) --- Yeah test result on latest -rc8 is needed, since maybe there's some other bug somewhere ... -- You are receiving this mail because: You are watching the assignee of the bug.

Re: [PATCH v3 09/13] drm/sun4i: backend: Wire in the frontend

On Tue, Jan 9, 2018 at 6:09 PM, Maxime Ripard wrote: > Now that we have a driver, we can make use of it. This is done by > adding a flag to our custom plane state that will trigger whether we should > use the frontend on that particular plane or not. > > The rest

Re: [PATCH v3 08/13] drm/sun4i: Add a driver for the display frontend

On Tue, Jan 9, 2018 at 6:09 PM, Maxime Ripard wrote: > The display frontend is an hardware block that can be used to implement > some more advanced features like hardware scaling or colorspace > conversions. It can also be used to implement the output format of

[PATCH] drm/arcpgu: remove drm_encoder_slave

drm_encoder_slave is the old way to write bridge drivers, for i2c bridges only. It's deprecated, and definitely should not be used in new drivers. What's even strange is that arcpgu doesn't even use any of this, it really only wants a plain normal drm_encoder. Nuke all the surplus real estate.

Re: [PATCH] drm/arm/malidp: Disable pixel alpha blending for colors that do not have alpha

Hi Ayan, On Fri, Jan 12, 2018 at 04:33:07PM +, Ayan Halder wrote: > Mali dp needs to disable pixel alpha blending (use layer alpha blending) to > display color formats that do not contain alpha bits per pixel In the future, please mention any dependencies on other patches that are not part

[PATCH] drm/atomic: Fix memleak on ERESTARTSYS during non-blocking commits

From: "Leo (Sunpeng) Li" During a non-blocking commit, it is possible to return before the commit_tail work is queued (-ERESTARTSYS, for example). Since a reference on the crtc commit object is obtained for the pending vblank event when preparing the commit, the above

[Bug 104655] AMD R9 Fury + BenQ XL2546: Setting 240 Hz results in screen distortion

https://bugs.freedesktop.org/show_bug.cgi?id=104655 --- Comment #4 from omin...@autistici.org --- Created attachment 136806 --> https://bugs.freedesktop.org/attachment.cgi?id=136806=edit dmesg -- You are receiving this mail because: You are the assignee for the

[Bug 104655] AMD R9 Fury + BenQ XL2546: Setting 240 Hz results in screen distortion

https://bugs.freedesktop.org/show_bug.cgi?id=104655 Nicolai Hähnle changed: What|Removed |Added QA Contact|mesa-dev@lists.freedesktop. |

Re: [Intel-gfx] IGT news - New mailing list, switching to meson

Cc'ing dri-devel. -Daniel On Mon, Jan 15, 2018 at 04:06:01PM +0200, Petri Latvala wrote: > > New mailing list > > > > IGT now has its own mailing list. For a transition period, patches on > both the new mailing list and intel-gfx (with the appropriate patch > subjectprefix)

[PATCH 7/7] dt-bindings: display: msm/dsi: Add updates for SDM845

SDM845 uses a newer revision (v2.0+) of the 6G DSI controller. This revision has another clock input at the block boundary called the byte interface clock. Specify this new clock in the binding. A 10nm DSI PHY is used along with the controller. Add a compatible string for it and specify its base

[PATCH 3/7] drm/msm/dsi: Add byte_intf_clk

DSI6G v2.0+ blocks have a new clock input to them called byte_intf_clk. It's rate is to be set as byte_clk / 2. Within the clock controller (CC) subsystem, this clock is a child/descendant of the byte_clk. Set it up as an optional clock in the DSI host driver. Make sure that we enable/set its

[PATCH 4/7] dt-bindings: display: msm/dsi: Remove unused properties

"qcom,dsi-host-index" and "qcom,dsi-phy-index" DT props aren't acceptable and have never been used in any DT files. Remove them. Cc: Rob Herring Cc: devicet...@vger.kernel.org Signed-off-by: Archit Taneja ---

[PATCH 6/7] dt-bindings: display: msm/dsi: Add compatible for 14nm DSI PHY

Add the compatible string for 14nm DSI PHY (used in MSM8996/APQ8096). From 14nm PHY onwards, the "dsi_phy_regulator" reg-name is not required, but "dsi_phy_lane" reg-name is. Update the doc to specify the reg-names each PHY revision needs. Cc: Rob Herring Cc:

[PATCH 5/7] dt-bindings: display: msm/dsi: Fix the PHY regulator supply props

The PHY regulator supply names vary across different PHY versions. Mention explicitly which PHYs require which supplies. Cc: Rob Herring Cc: devicet...@vger.kernel.org Signed-off-by: Archit Taneja ---

[PATCH 1/7] drm/msm/dsi: Use msm_clk_get in dsi_get_config

We try to get the interface clock in dsi_get_config early during DSI's component bind. Try getting both the "iface" and "iface_clk" clock name variants so that we are compatible with both new and legacy DT. Signed-off-by: Archit Taneja ---

[PATCH 0/7] drm/msm/dsi: SDM845 DSI host controller and DT updates

This series adds some of the host controller changes needed for SDM845.\ The DT patches in the series do some minor clean ups and add missing bindings for 14nm DSI PHY (8x96) and new bindings for 10nm PHY. Archit Taneja (7): drm/msm/dsi: Use msm_clk_get in dsi_get_config drm/msm/dsi: Add

[PATCH 2/7] drm/msm/dsi: Add SDM845 in dsi_cfg

SDM845 contains 2 DSI6G v2.2.1 host controllers. Add them in dsi_cfg. Cc: Jordan Crouse Signed-off-by: Archit Taneja --- drivers/gpu/drm/msm/dsi/dsi_cfg.c | 19 +++ drivers/gpu/drm/msm/dsi/dsi_cfg.h | 1 + 2 files changed, 20

Re: [PATCH] drm/ttm: add VADDR_FLAG_UPDATED_COUNT to correctly update dma_page global count

Am 17.01.2018 um 09:59 schrieb Roger He: add this for correctly updating global mem count in ttm_mem_zone. before that when ttm_mem_global_alloc_page fails, we would update all dma_page's global mem count in ttm_dma->pages_list. but actually here we should not update for the last dma_page. v2:

Re: [PATCH libdrm] drm: fix return value

On Wed, Jan 17, 2018 at 05:26:41PM +0800, Chunming Zhou wrote: > > > On 2018年01月17日 17:24, Christian König wrote: > > Am 17.01.2018 um 09:53 schrieb Chunming Zhou: > > > > > > > > > On 2018年01月17日 16:21, Daniel Vetter wrote: > > > > On Tue, Jan 16, 2018 at 02:01:40PM +, Zhou,

Re: [PATCH 06/19] drm/blend: Add a generic alpha property

On Wed, Jan 17, 2018 at 10:20:24AM +0100, Maxime Ripard wrote: > On Thu, Jan 11, 2018 at 08:34:58PM +0200, Laurent Pinchart wrote: > > Hi Daniel, > > > > On Thursday, 11 January 2018 18:36:10 EET Daniel Vetter wrote: > > > On Thu, Jan 11, 2018 at 4:58 PM, Maxime Ripard wrote: > > > > On Tue, Jan

Re: [Nouveau] [PATCH] drm/nouveau/bar/gk20a: Avoid bar teardown during init

On 10/01/18 12:20, Thierry Reding wrote: On Thu, Jan 04, 2018 at 11:29:09AM +, Jon Hunter wrote: Commit bbb163e18960 ("drm/nouveau/bar: implement bar1 teardown") introduced add a teardown helper function for BAR1. During initialisation of the Nouveau, initially all the teardown helpers are

[PULL] drm-misc-fixes

Hi Dave, drm-misc-fixes-2018-01-17: Final 4.15 drm-misc pull: Just 3 sun4i patches to fix clock computation/checks. Cheers, Daniel The following changes since commit b0bb222440a5c8273f67dd37946707e6ba6ad832: Merge branch 'linux-4.15' of git://github.com/skeggsb/linux into drm-fixes

Re: [PATCH libdrm] drm: fix return value

On 2018年01月17日 17:24, Christian König wrote: Am 17.01.2018 um 09:53 schrieb Chunming Zhou: On 2018年01月17日 16:21, Daniel Vetter wrote: On Tue, Jan 16, 2018 at 02:01:40PM +, Zhou, David(ChunMing) wrote: Can your guys help me push it and last vamgr patches to upstream? My new count

Re: [PATCH libdrm] drm: fix return value

Am 17.01.2018 um 09:53 schrieb Chunming Zhou: On 2018年01月17日 16:21, Daniel Vetter wrote: On Tue, Jan 16, 2018 at 02:01:40PM +, Zhou, David(ChunMing) wrote: Can your guys help me push it and last vamgr patches to upstream? My new count request for libdrm still is under pending. Or hand

Re: [PATCH 06/19] drm/blend: Add a generic alpha property

On Thu, Jan 11, 2018 at 08:34:58PM +0200, Laurent Pinchart wrote: > Hi Daniel, > > On Thursday, 11 January 2018 18:36:10 EET Daniel Vetter wrote: > > On Thu, Jan 11, 2018 at 4:58 PM, Maxime Ripard wrote: > > > On Tue, Jan 09, 2018 at 03:28:34PM +0100, Daniel Vetter wrote: > > >> On Tue, Jan 09,

Re: [Intel-gfx] [PATCH] drm: Fix PANEL_ORIENTATION_QUIRKS breaking the Kconfig DRM menuconfig

Hi, On 17-01-18 09:48, Daniel Vetter wrote: On Wed, Jan 17, 2018 at 9:42 AM, Hans de Goede wrote: Hi, On 17-01-18 09:40, Daniel Vetter wrote: On Wed, Jan 17, 2018 at 09:10:32AM +0100, Hans de Goede wrote: All Kconfig menu menu entries should have a depends on

Re: [PATCH v3 4/8] drm: Add DRM client cap for aspect-ratio

Regards Shashank On 1/12/2018 11:51 AM, Nautiyal, Ankit K wrote: From: Ankit Nautiyal A new drm client cap is required to enable user-space to advertise if it supports modes with aspect-ratio. Based on this cap value, the kernel will take a call on exposing the

Re: [PATCH v3 3/8] drm/edid: Fix cea mode aspect ratio handling

Regards Shashank On 1/12/2018 11:51 AM, Nautiyal, Ankit K wrote: From: Ville Syrjälä commit 6dffd431e229 ("drm: Add aspect ratio parsing in DRM layer") cause us to not send out any VICs in the AVI infoframes. That commit was since reverted, but if and when we

[PATCH] drm/ttm: add VADDR_FLAG_UPDATED_COUNT to correctly update dma_page global count

add this for correctly updating global mem count in ttm_mem_zone. before that when ttm_mem_global_alloc_page fails, we would update all dma_page's global mem count in ttm_dma->pages_list. but actually here we should not update for the last dma_page. v2: only the update of last dma_page is not

Re: [PATCH v3 2/8] drm/edid: Use drm_mode_match_no_clocks_no_stereo() for consistentcy

Regards Shashank On 1/12/2018 11:51 AM, Nautiyal, Ankit K wrote: From: Ville Syrjälä Use drm_mode_equal_no_clocks_no_stereo() in drm_match_hdmi_mode_clock_tolerance() for consistency as we also use it in drm_match_hdmi_mode() and the cea mode matching functions.

Re: [PATCH libdrm] drm: fix return value

On 2018年01月17日 16:21, Daniel Vetter wrote: On Tue, Jan 16, 2018 at 02:01:40PM +, Zhou, David(ChunMing) wrote: Can your guys help me push it and last vamgr patches to upstream? My new count request for libdrm still is under pending. Or hand out commmit rights? That's easier long-term imo

Re: [Intel-gfx] [PATCH] drm: Fix PANEL_ORIENTATION_QUIRKS breaking the Kconfig DRM menuconfig

Hi, On 17-01-18 09:40, Daniel Vetter wrote: On Wed, Jan 17, 2018 at 09:10:32AM +0100, Hans de Goede wrote: All Kconfig menu menu entries should have a depends on MENU_OPTION, the menu stops after the first Kconfig entry without this depends on. Since the PANEL_ORIENTATION_QUIRKS option is

Re: [PATCH] [RESEND] vmwgfx: use monotonic event timestamps

Thomas Hellstrom wrote: Hi, Arnd, Sinclair's on paternal leave and I thought this patch was already in drm-next. My bad. Dave, is it too late to pull this in for the next merge window? /Thomas On 01/16/2018 06:18 PM, Arnd Bergmann wrote: DRM_VMW_EVENT_FENCE_SIGNALED (struct

[PATCH] drm: Fix PANEL_ORIENTATION_QUIRKS breaking the Kconfig DRM menuconfig

All Kconfig menu menu entries should have a depends on MENU_OPTION, the menu stops after the first Kconfig entry without this depends on. Since the PANEL_ORIENTATION_QUIRKS option is also used outside of DRM, it deliberately does not have a depends on DRM, but this causes all items after it to

Re: [PATCH] drm/vmwgfx: Fix a boot time warning

On 01/17/2018 09:47 AM, Daniel Vetter wrote: On Wed, Jan 17, 2018 at 09:21:25AM +0100, Thomas Hellstrom wrote: From: Woody Suwalski The 4.15 vmwgfx driver shows a warning during boot. It is caused by a mismatch between the result of vmw_enable_vblank() and what the

Re: [Intel-gfx] [PATCH] drm: Fix PANEL_ORIENTATION_QUIRKS breaking the Kconfig DRM menuconfig

On Wed, Jan 17, 2018 at 9:42 AM, Hans de Goede wrote: > Hi, > > On 17-01-18 09:40, Daniel Vetter wrote: >> >> On Wed, Jan 17, 2018 at 09:10:32AM +0100, Hans de Goede wrote: >>> >>> All Kconfig menu menu entries should have a depends on MENU_OPTION, the >>> menu stops

Re: [PATCH] drm/vmwgfx: Fix a boot time warning

On Wed, Jan 17, 2018 at 09:21:25AM +0100, Thomas Hellstrom wrote: > From: Woody Suwalski > > The 4.15 vmwgfx driver shows a warning during boot. > It is caused by a mismatch between the result of vmw_enable_vblank() > and what the drm_atomic_helper expects. > >

Re: [PATCH v3 1/8] drm/modes: Introduce drm_mode_match()

On 1/12/2018 11:51 AM, Nautiyal, Ankit K wrote: From: Ville Syrjälä Make mode matching less confusing by allowing the caller to specify which parts of the modes should match via some flags. Signed-off-by: Ville Syrjälä ---

[git pull] vmwgfx-fixes-4.15 for -rc9 / final

Dave, A last minute minimal fix to kill a warning introduced in a helper in 4.15. The following changes since commit 0d9cac0ca0429830c40fe1a4e50e60f6221fd7b6: drm/vmwgfx: Potential off by one in vmw_view_add() (2018-01-10 15:21:39 +0100) are available in the git repository at:

Re: [Intel-gfx] [PATCH] drm: Fix PANEL_ORIENTATION_QUIRKS breaking the Kconfig DRM menuconfig

On Wed, Jan 17, 2018 at 09:10:32AM +0100, Hans de Goede wrote: > All Kconfig menu menu entries should have a depends on MENU_OPTION, the > menu stops after the first Kconfig entry without this depends on. > > Since the PANEL_ORIENTATION_QUIRKS option is also used outside of DRM, > it deliberately

Re: [PATCH 4/4] drm/vgem: flush page during page fault

On Tue, Jan 16, 2018 at 04:35:59PM -0800, Gurchetan Singh wrote: > This is required to use buffers allocated by vgem on AMD and ARM devices. > We're experiencing a case where eviction of the cache races with userspace > writes. To fix this, flush the cache after retrieving a page. > >

Re: [PATCH 3/4] drm: add ARM flush implementations

On Tue, Jan 16, 2018 at 04:35:58PM -0800, Gurchetan Singh wrote: > The DMA API can be used to flush scatter gather tables and physical > pages on ARM devices. > > Signed-off-by: Gurchetan Singh > --- > drivers/gpu/drm/drm_cache.c | 17

Re: drm: fix vmwgfx boot warning WAS Re: [PATCH] [RESEND] vmwgfx: use monotonic event timestamps

On 01/17/2018 07:33 AM, Thomas Hellstrom wrote: Hi, Woody, On 01/16/2018 10:39 PM, Woody Suwalski wrote: Thomas, the same way my DRM patch has disappeared: Date Tue, 19 Dec 2017 11:50:57 -0800 From Sinclair Yeh <> Subject Re: [PATCH v.2] 4.15 vmgfx boot warning This looks okay

Re: [PATCH] [RESEND] drm/gma500: initialize gma_clock_t structures

On Tue, Jan 16, 2018 at 03:57:10PM +0100, Arnd Bergmann wrote: > The two functions pass a partially initialized structure back to the > caller after a memset() on the destination. > > This is not entirely well-defined, most compilers are sensible enough > to either keep the zero-initialization

Re: [PATCH 6/7] drm/vmwgfx: Send the correct nonblock option for atomic_commit

On Tue, Jan 16, 2018 at 02:34:33PM +0100, Thomas Hellstrom wrote: > From: Deepak Rawat > > Page flip can be slow for vmwgfx in some cases, like need to do surface > copy to different surface or waiting for IN_FENCE_FD. Enabling > nonblocking commits for vmwgfx in case

Re: [PATCH] [RESEND] drm/gma500: initialize gma_clock_t structures

On Tue, Jan 16, 2018 at 3:57 PM, Arnd Bergmann wrote: > The two functions pass a partially initialized structure back to the > caller after a memset() on the destination. > > This is not entirely well-defined, most compilers are sensible enough > to either keep the

[PATCH] drm/vmwgfx: Fix a boot time warning

From: Woody Suwalski The 4.15 vmwgfx driver shows a warning during boot. It is caused by a mismatch between the result of vmw_enable_vblank() and what the drm_atomic_helper expects. Signed-off by: Woody Suwalski Signed-off-by: Thomas Hellstrom

Re: [PATCH libdrm] drm: fix return value

On Tue, Jan 16, 2018 at 02:01:40PM +, Zhou, David(ChunMing) wrote: > Can your guys help me push it and last vamgr patches to upstream? > My new count request for libdrm still is under pending. Or hand out commmit rights? That's easier long-term imo ... -Daniel > > Thanks, > David Zhou > >

  1   2   >