[Bug 96866] System frozen after resume, on Ubuntu 16.04 kernel 4.4.0-22

this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160708/74728d5d/attachment.html>

[Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7 merge window

On Fri, Jul 08, 2016 at 07:48:29AM -0700, James Bottomley wrote: > On Fri, 2016-07-08 at 13:19 +0300, Ville Syrjälä wrote: > > On Thu, Jul 07, 2016 at 12:19:36PM -0700, James Bottomley wrote: > > > On Thu, 2016-07-07 at 09:55 -0700, James Bottomley wrote: > > > > On Thu, 2016-07-07 at 19:14

[PATCH 11/16] gpu: ipu-v3: Fix CSI data format for 16-bit media bus formats

Am Donnerstag, den 07.07.2016, 16:03 -0700 schrieb Steve Longerbeam: > The CSI data format was being programmed incorrectly for the > 1x16 media bus formats. The CSI data format for 16-bit must > be bayer/generic (CSI_SENS_CONF_DATA_FMT_BAYER). I think this is not the case for BT.1120, but right

[PATCH 05/16] gpu: ipu-v3: Add IDMA channel linking support

Am Donnerstag, den 07.07.2016, 16:03 -0700 schrieb Steve Longerbeam: > Adds functions to link and unlink IDMAC source channels to sink > channels. > > So far the following links are supported: > > IPUV3_CHANNEL_IC_PRP_ENC_MEM -> IPUV3_CHANNEL_MEM_ROT_ENC > PUV3_CHANNEL_IC_PRP_VF_MEM ->

[PATCH 02/16] gpu: ipu-cpmem: Add ipu_cpmem_set_uv_offset()

Am Donnerstag, den 07.07.2016, 16:03 -0700 schrieb Steve Longerbeam: > Adds ipu_cpmem_set_uv_offset(), to set planar U/V offsets. > > Signed-off-by: Steve Longerbeam > --- > drivers/gpu/ipu-v3/ipu-cpmem.c | 7 +++ > include/video/imx-ipu-v3.h | 1 + > 2 files changed, 8 insertions(+) >

[PATCH 12/16] gpu: ipu-v3: Fix CSI0 blur in NTSC format

Am Donnerstag, den 07.07.2016, 16:03 -0700 schrieb Steve Longerbeam: > From: Suresh Dhandapani > > This patch will change the register IPU_CSI0_CCIR_CODE_2 value from > 0x40596 to 0x405A6. The change is related to the Start of field 1 > first blanking line command bit[5-3] for NTSC format only.

[PATCH 00/16] IPUv3 prep for i.MX5/6 v4l2 staging drivers

Hi Steve, Am Donnerstag, den 07.07.2016, 16:03 -0700 schrieb Steve Longerbeam: > These updates to IPUv3 are needed for media staging drivers > for i.MX5/6 video capture and mem2mem. Thank you for the update, I'll have a proper look at this next week. regards Philipp

[Nouveau] [PATCH v2 0/4] nouveau RPM fixes for Optimus

Hi, On 08-07-16 01:38, Peter Wu wrote: > Hi, > > Here are two patches to fix an issue reported on kernel bugzilla (infinite > loop > due to unchecked function) and a more important fix to fix hanging Optimus > machines when runtime PM is enabled (with pm/pci patches). > > See the first

[PATCH 0/3] imx drm atomic mode setting fixups

Hi Liu, Am Freitag, den 08.07.2016, 17:38 +0800 schrieb Liu Ying: [...] > I'll respin to fix the LVDS bus format translation issue. > To keep my patch set as small as possible, I'll leave your 3 patches > for you to handle. Please consider to rebase. Thanks, that works. I have rebased my

[PATCH v2 3/3] drm/imx: turn remaining container_of macros into inline functions

This allows the compiler to do type checking. Signed-off-by: Philipp Zabel --- drivers/gpu/drm/imx/imx-ldb.c | 7 +-- drivers/gpu/drm/imx/imx-tve.c | 7 +-- drivers/gpu/drm/imx/ipuv3-crtc.c | 5 - drivers/gpu/drm/imx/ipuv3-plane.c | 5 -

[PATCH v2 2/3] drm/imx: store internal bus configuration in crtc state

The internal bus configuration is imx-drm specific crtc state. Store it in imx_crtc_state and let the encoder atomic_check callbacks determine bus_flags, bus_format and the sync pins, possibly taking into account the mode and the connector display info. The LDB driver additionally stores

[PATCH v2 1/3] drm/imx: remove empty mode_set encoder callbacks

With atomic modeset support, these callbacks are optional. Signed-off-by: Philipp Zabel --- drivers/gpu/drm/imx/dw_hdmi-imx.c | 7 --- drivers/gpu/drm/imx/parallel-display.c | 7 --- 2 files changed, 14 deletions(-) diff --git a/drivers/gpu/drm/imx/dw_hdmi-imx.c

[Bug 121481] No video output after loading nouveau module

https://bugzilla.kernel.org/show_bug.cgi?id=121481 Dmitrii Tcvetkov changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #10 from Dmitrii

[Bug 117861] DRM dead lock code path

https://bugzilla.kernel.org/show_bug.cgi?id=117861 --- Comment #3 from Alex Deucher --- fixed in: https://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-next=bd6e2732f0e2894ce792f344c41fc32591436fe3 drm/prime: fix error path deadlock fail There were a couple messed up things about this fail

[PATCH v4 10/10] drm/imx: atomic phase 3 step 3: Advertise DRIVER_ATOMIC

With all the beforehand phases and steps done, we can adverstise DRIVER_ATOMIC. Signed-off-by: Liu Ying --- v3->v4: * None. v2->v3: * None. v1->v2: * None. drivers/gpu/drm/imx/imx-drm-core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH v4 09/10] drm/imx: atomic phase 3 step 2: Legacy callback fixups

Now that we can use atomic configurations, all the legacy callbacks of CRTCs, encoders and connectors can be switched to the atomic version. For the imx-ldb driver, there is a clock parent setting mismatch bewteen ->enable and ->disable after the switch, so a fixup is added. For the imx-tve

[PATCH v4 08/10] drm/bridge: dw-hdmi: Remove the legacy drm_connector_funcs structure

There is no one using the legacy drm_connector_funcs structure since the imx-drm has been converted to atomic, so we may remove it. Signed-off-by: Liu Ying --- v3->v4: * None. v2->v3: * Newly introduced to remove the legacy drm_connector_funcs structure step-by-step.

[PATCH v4 07/10] drm/imx: atomic phase 3 step 1: Use atomic configuration

Replacing drm_crtc_helper_set_config() by drm_atomic_helper_set_config() and converting the suspend/resume operations to atomic make us be able to use atomic configurations. All of these allow us to remove the crtc_funcs->mode_set callback as it is no longer used. Also, change the

[PATCH v4 06/10] drm/imx: Remove encoders' ->prepare callbacks

The main task of imx encoders' ->prepare callbacks is to set bus_format, bus_flags, di_vsync_pin and di_hsync_pin. We may create a structure named imx_encoder to cache them. The atomic encoder callback ->disable may replace ->prepare later, so let's remove ->prepare. Signed-off-by: Liu Ying

[PATCH v4 05/10] drm/imx: atomic phase 2 step 2: Track plane_state->fb correctly in ->page_flip

Use drm_atomic_set_fb_for_plane() in the legacy ->page_flip path to track the pointer plane_state->fb correctly. Signed-off-by: Liu Ying --- v3->v4: * None. v2->v3: * None. v1->v2: * None. drivers/gpu/drm/imx/ipuv3-crtc.c | 4 1 file changed, 4 insertions(+) diff --git

[PATCH v4 04/10] drm/imx: atomic phase 2 step 1: Wire up state ->reset, ->duplicate and ->destroy

Wire up CRTCs', planes' and connectors' ->reset, ->duplicate and ->destroy state hooks to use the default implementations from the atomic helper library. The helpers track each DRM object state. Signed-off-by: Liu Ying --- v3->v4: * None. v2->v3: * For dw-hdmi bridge driver, simply add the

[PATCH v4 03/10] drm/imx: atomic phase 1: Use transitional atomic CRTC and plane helpers

Use the drm_plane_helper_update/disable() and drm_helper_crtc_mode_set() transitional atomic helpers. The crtc->mode_set_nofb callback is added so that the primary plane is no longer tied to the CRTC. Check/update logics are separated to make sure crtc->mode_set_nofb and plane->atomic_update are

[PATCH v4 02/10] gpu: ipu-v3: ipu-dmfc: Use static DMFC FIFO allocation mechanism

For all video modes we support currently, we always get 2 slots for a plane by using the current existing dynamic DMFC FIFO allocation mechanism. So, let's change to use the static one to simplify the code. This also makes it easier to implement the atomic mode setting as we don't need to handle

[PATCH v4 01/10] drm/imx: ipuv3 plane: Check different types of plane separately

The IPUv3 primary plane doesn't support partial off screen. So, this patch separates plane check logics for primary plane and overlay plane and adds more limitations on the primary plane. Signed-off-by: Liu Ying --- v3->v4: * None. v2->v3: * None. v1->v2: * Remove an unnecessary copy to

[PATCH v4 00/10] imx drm atomic mode setting conversion

Hi, This is the v4 patch set to convert imx drm into atomic mode setting. It takes 3 phases to achieve the goal. v3->v4: * Rebase onto Daniel Vetter's open git branch for-linux-next. * Fix wrong LVDS bus format translation issue in imx_ldb_connector_get_modes() so that bus format could be

[PATCH 0/3] imx drm atomic mode setting fixups

Hi Philipp, 2016-07-07 16:29 GMT+08:00 Philipp Zabel : > Hi Liu, > > Am Donnerstag, den 07.07.2016, 15:44 +0800 schrieb Ying Liu: >> Hi Philipp, >> >> On Wed, Jul 6, 2016 at 11:52 PM, Philipp Zabel >> wrote: >> > Hi, >> > >> > I have tested Liu Ying's imx drm atomic mode setting conversion

[PATCH v2 1/5] drm/exynos: iommu: move dma_params configuration code to separate functions

Hi Marek, 2016년 06월 17일 16:54에 Marek Szyprowski 이(가) 쓴 글: > Move code for managing DMA max segment size parameter to separate > functions. This patch also replaces devm_kzalloc() with kzalloc() and > adds proper kfree call. devm_kzalloc() cannot be used for dma_params > structure,

[PATCH 7/7] drm/rockchip: dw-mipi: fix insufficient bandwidth of some panel

Set the lanes bps to 1 / 0.9 times of pclk, the margin is not enough for some panel, it will cause the screen display is not normal, so increases the badnwidth to 1 / 0.8. Signed-off-by: Chris Zhong --- drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH 6/7] drm/rockchip: dw-mipi: fix phy clk lane stop state timeout

Before phy init, the detection of phy state should be controlled manually. After that, we can switch the detection to hardward, it is automatic. Hence move PHY_TXREQUESTCLKHS setting to the end of phy init. Signed-off-by: Chris Zhong --- drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 3 ++- 1 file

[PATCH 5/7] drm/rockchip: dw-mipi: support HPD poll

At the first time of bind, there is no any panel attach in mipi. Add a DRM_CONNECTOR_POLL_HPD porperty to detect the panel status, when panel probe, the dw_mipi_dsi_host_attach would be called, then mipi-dsi will trigger a event to notify the drm framework. Signed-off-by: Chris Zhong ---

[PATCH 4/7] drm/rockchip: dw-mipi: add dw-mipi power domain support

Reference the power domain incase dw-mipi power down when in use. Signed-off-by: Chris Zhong --- drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 17 + 1 file changed, 17 insertions(+) diff --git a/drivers/gpu/drm/rockchip/dw-mipi-dsi.c b/drivers/gpu/drm/rockchip/dw-mipi-dsi.c index

[PATCH 3/7] dt-bindings: add power domain node for dw-mipi-rockchip

Signed-off-by: Chris Zhong --- .../devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt| 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt

[PATCH 2/7] DRM: mipi: support rk3399 mipi dsi

The vopb/vopl switch register of rk3399 mipi is different from rk3288, the default setting for mipi dsi mode is different too, so add a of_device_id structure to distinguish them, and make sure set the correct mode before mipi phy init. Signed-off-by: Chris Zhong Signed-off-by: Mark Yao ---

[PATCH 1/7] dt-bindings: add rk3399 support for dw-mipi-rockchip

The dw-mipi-dsi of rk3399 is almost the same as rk3288, the rk3399 has additional phy config clock. Signed-off-by: Chris Zhong --- .../devicetree/bindings/display/rockchip/dw_mipi_dsi_rockchip.txt| 5 + 1 file changed, 5 insertions(+) diff --git

[PATCH 0/7] Rockchip dw-mipi-dsi driver

Hi all This is a bunch of dw-mipi-dsi driver for RK3399 and RK3288, they have been tested on rk3399 and rk3288 evb board. This series is based on Mark Yao's branch: https://github.com/markyzq/kernel-drm-rockchip/tree/drm-rockchip-next-2016-05-23 Chris Zhong (7): dt-bindings: add rk3399

next build: 7 warnings 3 failures (next/next-20160708)

ux/kernel/git/next/linux-next.git (master >> branch) >> >> Topmost commit: >> >> a379b037 Add linux-next specific files for 20160708 >> >> Build logs (stderr only) can be found at the following link (experimental): >> >> http://arm-so

[Bug 92248] [KBL/SKL/BYT/BXT] igt/kms_plane_scaling fail

-- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160708/7f58a3b2/attachment.html>

[PATCH v3 6/7] drm/nouveau/fifo/gk104: make use of new strcpytoupper() function

Call strcpytoupper() rather than copying the string explicitly and then walking it to convert it to uppercase. Signed-off-by: Markus Mayer --- drivers/gpu/drm/nouveau/nvkm/engine/fifo/gk104.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git

[PATCH v3 2/7] drm/nouveau/core: make use of new strlcpytolower() function

Call strlcpytolower() rather than copying the string explicitly and then walking it to convert it to lowercase. Signed-off-by: Markus Mayer --- The semantics of the new function has changed, so this patch has been updated since v2 to match the new strlcpy() semantics (no explicit NULL

[PATCH v3 1/7] lib: string: add functions to case-convert strings

Add a collection of generic functions to convert strings to lowercase or uppercase. Changing the case of a string (with or without copying it first) seems to be a recurring requirement in the kernel that is currently being solved by several duplicated implementations doing the same thing. This

[PATCH v3 0/7] lib: string: add functions to case-convert strings

This series introduces a family of generic string case conversion functions. This kind of functionality is needed in several places in the kernel. Right now, everybody seems to be implementing their own copy of this functionality. Based on the discussion of the previous version of this series[1]

[Bug 96860] Aliasing when using vdpau with mpv

. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160708/309f0308/attachment.html>

[PATCH] drm/radeon: Remove deprecated create_singlethread_workqueue

just 1ms (or even significantly less) may cause the flip to be delayed by one refresh cycle. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer -- next part -- A non-text attachment was

[PATCH 5/7] drm/rockchip: dw-mipi: support HPD poll

On Fri, 8 Jul 2016 17:04:59 +0800, Chris Zhong wrote: > At the first time of bind, there is no any panel attach in mipi. Add a > DRM_CONNECTOR_POLL_HPD porperty to detect the panel status, when panel > probe, the dw_mipi_dsi_host_attach would be called, then mipi-dsi will > trigger a event to

[Bug 96860] Aliasing when using vdpau with mpv

-- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160708/89887f0b/attachment.html>

[Bug 54381] [drm:radeon_atom_pick_pll] *ERROR* unable to allocate a PPLL

Was Sent from my iPhone

[git pull] vmwgfx-fixes

Hi Sinclair, When sending fixes pulls please include some text about what is in here, after about -rc3/4 you generally need more justification and text for non-trivial changes. These seem somewhat large changes, and it would be nice to have a summary of them. It also appears that the ttm patch

[Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7 merge window

On Thu, Jul 07, 2016 at 12:19:36PM -0700, James Bottomley wrote: > On Thu, 2016-07-07 at 09:55 -0700, James Bottomley wrote: > > On Thu, 2016-07-07 at 19:14 +0300, Ville Syrjälä wrote: > > > On Tue, Jun 21, 2016 at 06:44:34PM +0300, Ville Syrjälä wrote: > > > > On Tue, Jun 21, 2016 at

[PATCH] dma-buf/sync_file: only enable fence signalling during wait

From: Gustavo Padovan Signalling doesn't need to be enabled at sync_file creation, it is only required if userspace waiting the fence to signal through poll(). Thus we delay fence_add_callback() until poll is called. It only adds the callback the first time

next build: 7 warnings 3 failures (next/next-20160708)

st commit: > > a379b037 Add linux-next specific files for 20160708 > > Build logs (stderr only) can be found at the following link (experimental): > > http://arm-soc.lixom.net/buildlogs/next/next-20160708/ > > > Runtime:114m 2s &g

[PATCH 2/2] drm/vc4: Squash commit for Mario's precise vblank timestamping.

Read out the DISPBASE registers to decide on the FIFO size. Signed-off-by: Eric Anholt --- Mario: How about this for a squash into your commit? Here are the values I dumped for cob_size: [2.148314] [drm] Scaler 0 size 5232 [2.162239] [drm] Scaler 2 size 2048 [2.172957] [drm]

[PATCH 1/2] drm/vc4: Bind the HVS before we bind the individual CRTCs.

We need to be able to look at the CRTC's registers in the HVS as part of initialization, while the HVS doesn't need to look at the PV registers. Signed-off-by: Eric Anholt --- This commit would be slipped in before Mario's commit. drivers/gpu/drm/vc4/vc4_drv.c | 2 +- 1 file changed, 1

[PATCH] drm/amdgpu: Disable RPM helpers while reprobing connectors on resume

Just about all of amdgpu's connector probing functions try to acquire runtime PM refs. If we try to do this in the context of amdgpu_resume_kms by calling drm_helper_hpd_irq_event(), we end up deadlocking the system. Since we're guaranteed to be holding the spinlock for RPM in amdgpu_resume_kms,

[PATCH v2 4/4] drm/nouveau/acpi: fix lockup with PCIe runtime PM

On Fri, Jul 08, 2016 at 01:38:27AM +0200, Peter Wu wrote: > Since "PCI: Add runtime PM support for PCIe ports", the parent PCIe port > can be runtime-suspended which disables power resources via ACPI. This > is incompatible with DSM, resulting in a GPU device which is still in D3 > and locks up

[PATCH 4/4] arm: dts: qcom: apq8064-ifc6410: Add HDMI support

Add HDMI support on IFC6410. Populate the regulators required by HDMI-TX and PHY. Establish the link between the MDP4 DTV encoder and HDMI. Create a generic micro HDMI connector DT node. The msm drm driver doesn't parse for HDMI connectors in DT, but it will do so later. Cc: Rob Herring Cc:

[PATCH 3/4] arm: dts: qcom: apq8064: Add display DT nodes

APQ8064 contains a MDP4 based display controller. It contains a HDMI, LVDS and 2 DSI outputs. Add display DT nodes for MDP4, HDMI TX and HDMI PHY. MDP4 based display blocks have a flat device hierarchy. Nodes for other outputs will be added later. Cc: Rob Herring Cc: devicetree at

[PATCH 2/4] drm/msm/hdmi: Use more DT friendly GPIO names

Update the gpio name parsing code to try to search for without the "qcom,hdmi-tx-" prefix. The older downstream bindings that expect "qcom,hdmi-tx-xyz" or "qcom,hdmi-tx-xyz-gpio" would work as the property name would work as before. Update the binding doc. Add an entry for the missing hpd and lpm

[PATCH 1/4] drm/msm/mdp4: Fix issue with LCDC/LVDS port parsing

The LVDS port is the first in the list of the output ports in MDP4. The driver assumed that if the port and its corresponding endpoint is defined, then there should be a panel node too. This isn't necessary since boards may not really use a LVDS panel. Don't fail if there isn't a panel node

[PATCH 0/4] drm/msm: HDMI support on IFC6410

This set adds the display DT parts for the APQ8064 based IFC6410 board. There were a couple of small fixes/cleanups required in the driver to use the correct bindings. Those are a part of this patchset too. Archit Taneja (4): drm/msm/mdp4: Fix issue with LCDC/LVDS port parsing drm/msm/hdmi:

[PATCH v2 1/7] lib: string: add functions to case-convert strings

On 7 July 2016 at 17:19, Rasmus Villemoes wrote: > On Tue, Jul 05 2016, Markus Mayer wrote: > >> +/** >> + * strncpytoupper - Copy a length-limited string and convert to uppercase. >> + * @dst: The buffer to store the result. >> + * @src: The string to convert to uppercase. >> + * @len: Maximum

[PATCH v3 3/4] drm/bridge: analogix_dp: add the PSR function support

On 07/08/2016 10:26 AM, Yakir Yang wrote: > Sean, > > Thanks for your review. > > On 07/02/2016 03:46 AM, Sean Paul wrote: >> On Fri, Jul 1, 2016 at 5:19 AM, Yakir Yang wrote: >>> The full name of PSR is Panel Self Refresh, panel device could refresh >>> itself with the hardware framebuffer in

[PATCH v3 4/4] drm/rockchip: analogix_dp: implement PSR function

Sean, On 07/02/2016 04:05 AM, Sean Paul wrote: > On Fri, Jul 1, 2016 at 5:19 AM, Yakir Yang wrote: >> Alway enable the PSR function for Rockchip analogix_dp driver. If panel >> don't support PSR, then the core analogix_dp would ignore this setting. >> >> Signed-off-by: Yakir Yang >> --- >>

[PATCH v3 1/4] drm/rockchip: vop: export line flag function

Sean, On 07/01/2016 11:32 PM, Sean Paul wrote: > On Fri, Jul 1, 2016 at 11:30 AM, Sean Paul wrote: >> On Fri, Jul 1, 2016 at 5:19 AM, Yakir Yang wrote: >>> VOP have integrated a hardware counter which indicate the exact display >>> line that vop is scanning. And if we're interested in a

[PATCH v3 3/4] drm/bridge: analogix_dp: add the PSR function support

Sean, Thanks for your review. On 07/02/2016 03:46 AM, Sean Paul wrote: > On Fri, Jul 1, 2016 at 5:19 AM, Yakir Yang wrote: >> The full name of PSR is Panel Self Refresh, panel device could refresh >> itself with the hardware framebuffer in panel, this would make lots of >> sense to save the

[PATCH v3 2/4] drm/rockchip: add an common abstracted PSR driver

Sean, On 07/02/2016 02:00 AM, Sean Paul wrote: > On Fri, Jul 1, 2016 at 5:19 AM, Yakir Yang wrote: >> The PSR driver have exported four symbols for specific device driver: >> - rockchip_drm_psr_register() >> - rockchip_drm_psr_unregister() >> - rockchip_drm_psr_enable() >> -

[PATCH v3 4/6] drm/panel: simple: Add support for Samsung LSN122DL01-C01 2560x1600 panel

Doug, On 06/14/2016 01:00 AM, Doug Anderson wrote: > Yakir, > > On Sat, Jun 11, 2016 at 7:56 PM, Yakir Yang wrote: >> The Samsung LSN122DL01-C01 is an 12.2" 2560x1600 (WQXGA) TFT-LCD panel >> connected using eDP interfaces. >> >> Signed-off-by: Yakir Yang >> --- >> Changes in v3: >> - Correct

[PATCH v5 4/4] drm: rcar: use generic code for managing zpos plane property

Hi Laurent, May I suggest to merge only zpos core files (i.e the first patch of this series) and sti patches ? Like that we can progress and we can resend your patch for rcar when media_tree vsp1 branch will be merged into drm-next? Dave, Daniel: is it possible to do like this ? Regards,

[Bug 96835] "gallium: Force blend color to 16-byte alignment" crash with "-march=native -O3" causes some 32bit games to crash

e assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160708/788368ad/attachment.html>

[PATCH v5 0/4] Generic zpos property

htmldocs get information directly from the comments in .h and .c files 2016-07-07 18:09 GMT+02:00 Tobias Jakobi : > Benjamin Gaignard wrote: >> zpos new fields are correctly documented in drm-kms.html after running >> make htmldocs. > I'm not sure I understand. Where does htmldocs get the

iommu/rockchip: Fix bugs and enable on ARM64

On 2016年06月27日 20:57, Joerg Roedel wrote: > On Fri, Jun 24, 2016 at 10:13:25AM +0800, Shunqian Zheng wrote: >> drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 100 +++-- >> drivers/gpu/drm/rockchip/rockchip_drm_drv.h | 3 + >> drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 221 >>

[git pull] vmwgfx-fixes

Hi Dave, This contains one small patch to make sure we release a mutex when hitting a framebuffer pinning and mapping failure. It is not very often that we'll run into this case, and given that it's late in the current release, I'm okay with batching this up with the next one if this cannot go

[PATCH v5 6/8] drm/rockchip: Do not use DMA mapping API if attached to IOMMU domain

On 2016年06月24日 10:13, Shunqian Zheng wrote: > From: Tomasz Figa > > The API is not suitable for subsystems consisting of multiple devices > and requires severe hacks to use it. To mitigate this, this patch > implements allocation and address space management locally by using > helpers

[PATCH v5 7/8] drm/rockchip: Use common IOMMU API to attach devices

On 2016年06月24日 10:13, Shunqian Zheng wrote: > Rockchip DRM used the arm special API, arm_iommu_*(), to attach > iommu for ARM32 SoCs. This patch convert to common iommu API > so it would support ARM64 like RK3399. > > Since previous patch added support for direct IOMMU address space >

[PATCH] apple-gmux: Sphinxify docs

On Wed, Jul 06, 2016 at 01:40:25PM -0700, Darren Hart wrote: > On Mon, Jul 04, 2016 at 12:40:35PM +0200, Lukas Wunner wrote: > > Convert asciidoc-formatted docs to rst in accordance with Jonathan's and > > Jani's effort to use sphinx for kernel-doc rendering in 4.8. > > Somebody help me out here.

[Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7 merge window

On Fri, 2016-07-08 at 13:19 +0300, Ville Syrjälä wrote: > On Thu, Jul 07, 2016 at 12:19:36PM -0700, James Bottomley wrote: > > On Thu, 2016-07-07 at 09:55 -0700, James Bottomley wrote: > > > On Thu, 2016-07-07 at 19:14 +0300, Ville Syrjälä wrote: > > > > On Tue, Jun 21, 2016 at 06:44:34PM

[git pull] drm fixes

Hi Linus, One nouveau fix, and a few AMD Polaris fixes and some Allwinner fixes. I've got some vmware fixes that I might send separate over the weekend, they fix some black screens, but I'm still debating them. Dave. The following changes since commit

[Bug 96835] "gallium: Force blend color to 16-byte alignment" crash with "-march=native -O3" causes some 32bit games to crash

: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160708/984dba99/attachment.html>

[PATCH v2 1/7] lib: string: add functions to case-convert strings

On Tue, Jul 05 2016, Markus Mayer wrote: > Add a collection of generic functions to convert strings to lowercase > or uppercase. > > Changing the case of a string (with or without copying it first) seems > to be a recurring requirement in the kernel that is currently being > solved by several

[PATCH v2 4/4] drm/nouveau/acpi: fix lockup with PCIe runtime PM

Since "PCI: Add runtime PM support for PCIe ports", the parent PCIe port can be runtime-suspended which disables power resources via ACPI. This is incompatible with DSM, resulting in a GPU device which is still in D3 and locks up the kernel on resume (on a Clevo P651RA, GTX965M). Mirror the

[PATCH v2 3/4] drm/nouveau/acpi: check for function 0x1B before using it

Do not unconditionally invoke function 0x1B without checking for its availability, it leads to an infinite loop on some firmware. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=104791 Fixes: 5addcf0a5f0fad ("nouveau: add runtime PM support (v0.9)") Signed-off-by: Peter Wu ---

[PATCH v2 2/4] drm/nouveau/acpi: return supported DSM functions

Return the set of supported functions to the caller. No functional changes. Signed-off-by: Peter Wu --- drivers/gpu/drm/nouveau/nouveau_acpi.c | 16 +--- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_acpi.c

[PATCH v2 1/4] drm/nouveau/acpi: ensure matching ACPI handle and supported functions

Ensure that the returned set of supported DSM functions (MUX, Optimus) match the ACPI handle that is set in nouveau_dsm_pci_probe. As there are no machines with a MUX function on just one PCI device and an Optimus on another, there should not be a functional impact. This change however makes this

[PATCH v2 0/4] nouveau RPM fixes for Optimus

Hi, Here are two patches to fix an issue reported on kernel bugzilla (infinite loop due to unchecked function) and a more important fix to fix hanging Optimus machines when runtime PM is enabled (with pm/pci patches). See the first version[1] for a background on the fixed problems. This is the

[PATCH v1 5/5] ARM: dts: rockchip: add the panel power supply for rk3288-evb board with rk808 pmu

Am Dienstag, 28. Juni 2016, 12:51:24 schrieb Yakir Yang: > Panel regulator is controller by a normal GPIO, so we need to > write a regulator-fixed node for it. > > Signed-off-by: Yakir Yang applied after rewording the commit message a bit. On the rk808-evb vcc_lcd comes from the rk808 directly

[PATCH v1 4/5] ARM: dts: rockchip: add the panel power supply for rk3288-evb board with act8846 pmu

Am Dienstag, 28. Juni 2016, 12:51:21 schrieb Yakir Yang: > Panel regulator is controller by a normal GPIO, so we need to > write a regulator-fixed node for it. > > Signed-off-by: Yakir Yang applied, thanks. Heiko

[PATCH v1 3/5] ARM: dts: rockchip: add eDP/panel display device nodes for rk3288-evb

Am Dienstag, 28. Juni 2016, 12:51:18 schrieb Yakir Yang: > The default eDP panel on RK3288 EVB board is LG LP079QX1-SP0V TFT LCD, > we haven't declared the panel regulator in the 'panel-simple' device > node here, so the specific board like ACT8846 / RK8080 need to support > the panel power

[PATCH v3 1/6] dt-bindings: add LG LP097QX1-SPA1 panel binding

On Thu, Jul 07, 2016 at 11:55:23PM +0200, Thierry Reding wrote: > On Sun, Jun 12, 2016 at 10:53:30AM +0800, Yakir Yang wrote: > > The LG LP097QX1-SPA1 is an 9.7", 2048x1536 (QXGA) TFT-LCD panel > > connected using eDP interfaces. > > > > Signed-off-by: Yakir Yang > > Acked-by: Rob Herring > >

[PATCH v3 1/6] dt-bindings: add LG LP097QX1-SPA1 panel binding

On Sun, Jun 12, 2016 at 10:53:30AM +0800, Yakir Yang wrote: > The LG LP097QX1-SPA1 is an 9.7", 2048x1536 (QXGA) TFT-LCD panel > connected using eDP interfaces. > > Signed-off-by: Yakir Yang > Acked-by: Rob Herring > --- > Changes in v3: None > Changes in v2: > - Add Rob's acked for dt-bindings

[PATCH v1 2/5] drm/panel: simple: Add support for LG LP079QX1-SP0V 1536x2048 panel

On Tue, Jun 28, 2016 at 12:51:15PM +0800, Yakir Yang wrote: > The LG LP079QX1-SP0V is an 7.9" QXGA TFT with LED Backlight unit and > 32 pins eDP interface. This module supports 1536x2048 mode. > > Signed-off-by: Yakir Yang > --- > drivers/gpu/drm/panel/panel-simple.c | 26

[PATCH v1 1/5] dt-bindings: Add support for LG LP079QX1-SP0V 1536x2048 panel

On Tue, Jun 28, 2016 at 12:51:12PM +0800, Yakir Yang wrote: > The LG LP079QX1-SP0V is an 7.9" QXGA TFT with LED Backlight unit and > 32 pins eDP interface. This module supports 1536x2048 mode. > > Signed-off-by: Yakir Yang > --- > .../devicetree/bindings/display/panel/lg,lp079qx1-sp0v.txt