[PATCH 06/11] drm: i915: i915_oa_hsw: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_hsw.c | 12 ++--

[PATCH 09/11] drm: i915: i915_oa_sklgt3: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_sklgt3.c | 36

Re: [Intel-gfx] [PATCH 00/11] constify i915 attribute_group structures.

Hi Lionel, On Friday 04 August 2017 02:33 PM, Lionel Landwerlin wrote: Hi Arwind, These files were generated by a script maintained in this repository : https://github.com/rib/gputop/blob/master/scripts/i915-perf-kernelgen.py It would best to update this script first to make sure future

[PATCH] staging: vboxvideo: remove dead gamma lut code

The redundant fb helpers .load_lut, .gamma_set and .gamma_get are no longer used. Remove the dead code that was not doing anything sensible anyway. Signed-off-by: Peter Rosin --- drivers/staging/vboxvideo/vbox_fb.c | 15 --- drivers/staging/vboxvideo/vbox_mode.c |

[RESEND PATCH] staging: vboxvideo: remove dead gamma lut code

The redundant fb helpers .load_lut, .gamma_set and .gamma_get are no longer used. Remove the dead code that was not doing anything sensible anyway. Signed-off-by: Peter Rosin --- drivers/staging/vboxvideo/vbox_fb.c | 15 --- drivers/staging/vboxvideo/vbox_mode.c |

[PATCH 03/11] drm: i915: i915_oa_bxt: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_bxt.c | 30

[PATCH RESEND 2/2] dt/bindings: display: move rotation into a common place

Commit b60c1be74741 (dt-bindings: display/panel: Add common rotation property) added the rotation property description in a new file. We have a place for common display panel properties already. Move there the rotation property. Acked-by: Noralf Trønnes Acked-by: Rob Herring

Re: [Intel-gfx] [PATCH 00/11] constify i915 attribute_group structures.

On Friday 04 August 2017 04:04 PM, Lionel Landwerlin wrote: On 04/08/17 11:22, Arvind Yadav wrote: Hi Lionel, On Friday 04 August 2017 02:33 PM, Lionel Landwerlin wrote: Hi Arwind, These files were generated by a script maintained in this repository :

Re: [PATCH 2/2] ARM: dts: exynos: Add HDMI and Sil9234 to Trats2 board

On Fri, Aug 4, 2017 at 8:32 AM, Marek Szyprowski wrote: > > Hi Krzysztof, > > > On 2017-08-03 21:20, Krzysztof Kozlowski wrote: >> >> On Thu, Aug 03, 2017 at 09:45:23AM +0200, Maciej Purski wrote: >>> >>> This patch adds HDMI and Sil9234 MHL converter to Trats2 board. >>

[PATCH 11/11] drm: i915: i915_sysfs: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_sysfs.c | 6 +++--- 1 file

[PATCH 05/11] drm: i915: i915_oa_glk: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_glk.c | 30

[PATCH 02/11] drm: i915: i915_oa_bdw: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_bdw.c | 44

[PATCH 00/11] constify i915 attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Arvind Yadav (11): [PATCH 01/11] drm: i915: i915_oa_kblgt2: constify attribute_group structures. [PATCH

[PATCH v1 2/2] drm: Update framework with new video formats

The following new fourcc codes introduced in patch 514b144b2dd7 (uapi: drm: New fourcc codes needed by Xilinx Video IP) to DRM framework: * AVUY * VUY888 * XVUY * XVUY2101010 * Y8 * Y10 * XV15 Signed-off-by: Jeffrey Mouroux --- drivers/gpu/drm/drm_fourcc.c | 7 +++

[PATCH v1 1/2] uapi: drm: Add fourcc codes needed by Xilinx Video IP

The Xilinx Video Mixer andn Xilinx Video Framebuffer DMA IP support video memory formats that are not represented in the current DRM fourcc library. This patch adds those missing fourcc codes. Signed-off-by: Jeffrey Mouroux --- include/uapi/drm/drm_fourcc.h | 9 +

[PATCH 08/11] drm: i915: i915_oa_sklgt2: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_sklgt2.c | 36

[PATCH v1 0/2] New DRM fourcc codes needed by Video DMA Driver

This patch set is introduced to support a driver we are developing for our new Video Framebuffer DMA IP, a DMA device that is "video format aware". Clients need only specify memory layout information for a single plane (i.e. luma) and then provide a video format code (e.g. YUV420) which will

[drm/vmwgfx] invalid read access at vmw_du_primary_plane_atomic_check()

Code added by commit 060e2ad57041b42c ("drm/vmwgfx: Add and connect plane helper functions") is hitting KASAN error shown below. I guess that either *vcs is invalid or vcs->is_implicit is off-by-one. -- [ 19.654429] Linux agpgart interface v0.103 [ 19.657444] agpgart-intel

[PATCH 07/11] drm: i915: i915_oa_kblgt3: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_kblgt3.c | 36

Re: [linux-sunxi] [PATCH 10/13] [NOT FOR REVIEW NOW] clk: sunxi: Add CLK_SET_RATE_PARENT flag for H3 HDMI clock

于 2017年8月4日 GMT+08:00 下午12:15:27, Chen-Yu Tsai 写到: >Hi, > >On Tue, Aug 1, 2017 at 9:13 PM, Icenowy Zheng wrote: >> From: Jernej Skrabec >> >> When setting the HDMI clock of H3, the PLL_VIDEO clock needs to be >set. >> >> Add

[PATCH 04/11] drm: i915: i915_oa_chv: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_chv.c | 28

[PATCH 01/11] drm: i915: i915_oa_kblgt2: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_kblgt2.c | 36

[PATCH RESEND 1/2] dt/bindings: display: fix display-timing reference

Fixes: 14da3ed8dd08 ("devicetree/bindings: display: Document common panel properties") Cc: Laurent Pinchart Acked-by: Rob Herring Signed-off-by: Baruch Siach ---

[PATCH 10/11] drm: i915: i915_oa_sklgt4: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_sklgt4.c | 36

[PATCH v4] drm: kirin: Add mode_valid logic to avoid mode clocks we can't generate

Currently the hikey dsi logic cannot generate accurate byte clocks values for all pixel clock values. Thus if a mode clock is selected that cannot match the calculated byte clock, the device will boot with a blank screen. This patch uses the new mode_valid callback (many thanks to Jose Abreu for

Re: [PATCH] drm/syncobj: add sync obj wait interface. (v7)

I'm working on a VK_KHR_external_fence implementation based on this and have found some issues. :-) On Mon, Jul 17, 2017 at 11:44 PM, Dave Airlie wrote: > From: Dave Airlie > > This interface will allow sync object to be used to back > Vulkan fences. This

Re: [PATCH v3 00/35] omapdrm: Deconstruct DSS features

On Saturday 05 Aug 2017 01:43:44 Laurent Pinchart wrote: > Hello, > > This patch series is a third version of the code previously posted as > "[PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform > code". > > The omapdss/omapdrm initialization code is quite a mess. The physical

[PATCH v3 35/35] drm: omapdrm: Remove dss_features.h

The header file only contains four macros, two of which are never used. Move the other two to dss.h and remove dss_features.h. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/core.c | 1 - drivers/gpu/drm/omapdrm/dss/dispc.c|

[PATCH v3 34/35] drm: omapdrm: Move supported outputs feature to dss driver

The supported outputs feature is specific to the DSS, move it from the omap_dss_features structure to the dss driver. The omap_dss_features structure is now empty and can be removed. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/Makefile

[PATCH v3 28/35] drm: omapdrm: Move FEAT_DPI_USES_VDDS_DSI feature to dpi code

The FEAT_DPI_USES_VDDS_DSI feature is specific to the DPI, move it from the omap_dss_features structure to the dpi code. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dpi.c | 13 -

[PATCH v3 27/35] drm: omapdrm: Move FEAT_HDMI_* features to hdmi4 driver

The FEAT_HDMI_* features are specific to the HDMI4, move them from the omap_dss_features structure to the hdmi4 driver. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dss_features.c | 5 drivers/gpu/drm/omapdrm/dss/dss_features.h | 2 --

[PATCH v3 32/35] drm: omapdrm: Move PCD, LINEWIDTH and DOWNSCALE features to dispc driver

The FEAT_PARAM_DSS_PCD, FEAT_PARAM_LINEWIDTH and FEAT_PARAM_DOWNSCALE features are specific to the DISPC, move them from the omap_dss_features structure to the dispc driver. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dispc.c| 53

[PATCH v3 33/35] drm: omapdrm: Move DSS_FCK feature to dss driver

The FEAT_PARAM_DSS_FCK feature is specific to the DSS, move it from the omap_dss_features structure to the dss driver. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dispc.c| 2 +- drivers/gpu/drm/omapdrm/dss/dpi.c | 2 +-

[PATCH v3 29/35] drm: omapdrm: Move FEAT_LCD_CLK_SRC feature to dss_features structure

The FEAT_LCD_CLK_SRC feature is specific to the DSS, move it from the omap_dss_features structure to the dss_features structure. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dss.c | 15 +++

[PATCH v3 30/35] drm: omapdrm: Move FEAT_* features to dispc driver

All the remaining FEAT_* features are specific to the DISPC, move them from the omap_dss_features structure to the dispc driver. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dispc.c| 257 +

[PATCH v3 31/35] drm: omapdrm: Move FEAT_PARAM_DSI* features to dsi driver

The FEAT_PARAM_DSI* features are specific to the DSI, move them from the omap_dss_features structure to the dsi driver. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dsi.c | 25 +++--

[PATCH v3 25/35] drm: omapdrm: Move FEAT_VENC_REQUIRES_TV_DAC_CLK to venc driver

The FEAT_VENC_REQUIRES_TV_DAC_CLK is specific to the VENC, move it from the omap_dss_features structure to the venc driver. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dss_features.c | 2 -- drivers/gpu/drm/omapdrm/dss/dss_features.h | 1

[PATCH v3 24/35] drm: omapdrm: Move reg_fields to dispc_features structure

The reg_fields feature describes DISPC registers only. Move it from the omap_dss_features structure to the dispc_features structure. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dispc.c| 87 +

[PATCH v3 21/35] drm: omapdrm: Move overlay caps features to dispc_features structure

The overlay_caps is a dispc feature. Move it from the omap_dss_features structure to the dispc_features structure. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dispc.c| 106 +++--

[PATCH v3 26/35] drm: omapdrm: Move FEAT_DSI_* features to dsi driver

The FEAT_DSI_* features are specific to the DSI, move them from the omap_dss_features structure to the dsi driver. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dsi.c | 137 ++---

[PATCH v3 20/35] drm: omapdrm: Move color modes feature to dispc_features structure

The supported_color_modes is a dispc feature. Move it from the omap_dss_features structure to the dispc_features structure. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dispc.c| 127 +++-

[PATCH v3 23/35] drm: omapdrm: Move DISPC_CLK_SWITCH reg feature to struct dss_features

The register belongs to the DSS, move the feature to the dss_features structure. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dss.c | 15 +++ drivers/gpu/drm/omapdrm/dss/dss.h | 5 +

[PATCH v3 18/35] drm: omapdrm: Move shutdown() handler from core to dss

In preparation for removal of the core module, move the shutdown() handler from core to dss. Signed-off-by: Laurent Pinchart Reviewed-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/core.c | 20

[PATCH v3 16/35] drm: omapdrm: dss: Initialize DSS internal features at probe time

The DSS internal features are derived from the platform device compatible string which is available at probe time. Don't delay initialization until bind time. This prepares for the merge of the two DSS features structures that will be needed before the DSS is bound. Signed-off-by: Laurent

[PATCH v3 15/35] drm: omapdrm: dss: Use supported outputs instead of display types

The dss driver uses the supported display types to check whether the DSS has SDI, VENC or HDMI outputs. We can instead use the supported outputs the provide the same information. This removes the last use of the supported display types, that we can then remove as well. Signed-off-by: Laurent

[PATCH v3 19/35] drm: omapdrm: Move size unit features to dispc_features structure

The buffer_size_unit and burst_size_unit are dispc features. Move them from the omap_dss_features structure to the dispc_features structure. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dispc.c| 25 +---

[PATCH v3 22/35] drm: omapdrm: Move num_ovls and num_mgrs to dispc_features structure

The num_ovls and num_mgrs are dispc features. Move them from the omap_dss_features structure to the dispc_features structure. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dispc.c| 91 ++

[PATCH v3 14/35] drm: omapdrm: dss: Select features based on compatible string

Use the compatible string instead of the OMAP SoC revision to determine device features. The various OMAP3-based SoCs can't be told apart using the compatible string, use soc_device_match() to tell them apart. Signed-off-by: Laurent Pinchart Reviewed-by: Tomi

[PATCH v3 17/35] drm: omapdrm: Move all debugfs code from core to dss

debugfs code is spread between the core and dss drivers. In preparation for removal of the core driver, move it all to the dss driver. Signed-off-by: Laurent Pinchart --- Changes since v2: - Call dss_uninitialize_debugfs() in probe error path - Remove empty

[PATCH v3 13/35] drm: omapdrm: dsi: Store DSI model and PLL hardware data in OF data

The DSI PLL hardware data and DSS channels are selected based on the OMAP SoC model. There's no need for fine-grained model information, as the driver only needs to differentiate between OMAP3, OMAP4 and OMAP5. As this can be done through the DSI compatible string, store the corresponding

[PATCH v3 10/35] drm: omapdrm: Don't forward set_min_bus_tput() to no-op platform code

The OMAP implementation of the set_min_bus_tput() API is a no-op. There's no point in forwarding the driver calls to the platform code. Remove the use of the related platform data callback, but keep the internal function as a reminder that the feature will need to be implemented when the OMAP

[PATCH v3 11/35] drm: omapdrm: dispc: Select features based on compatible string

Use the compatible string instead of the OMAP SoC revision to determine device features. On OMAP34xx the features depend on the ES revision that can not be determined from the compatible string. Use soc_device_match() in that case. Signed-off-by: Laurent Pinchart

[PATCH v3 12/35] drm: omapdrm: dpi: Replace OMAP SoC model checks with DSS model

The DPI code only needs to differentiate between major OMAP revisions, which can be obtained from the DSS compatible string. Replace the OMAP SoC model checks to prepare for removal of the OMAP SoC version platform data. Signed-off-by: Laurent Pinchart ---

[PATCH v3 09/35] drm: omapdrm: dsi: Handle pin muxing internally

Don't rely on callback functions provided by the platform, but access the syscon internally to mux the DSI pins. Signed-off-by: Laurent Pinchart Reviewed-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/core.c | 20 --

[PATCH v3 05/35] drm: omapdrm: dpi: Remove unneeded regulator check

The dpi_display_enable() function ensures that a VDDS_DSI regulator is available if the DSI uses the VDDS_DSI supply. This is not needed, as a failure to get the VDDS_DSI supply will result in a probe failure, dpi_display_enable() will thus never be called in that case. Remove the check, and

[PATCH v3 08/35] drm: omapdrm: dss: Split operations out of dss_features structure

Move the two function pointers to a new dss_ops structure. This will allow merging the dss_features and omap_dss_features structures without having to expose the DPI source selection and LCD clock muxing functions in header files. Signed-off-by: Laurent Pinchart

[PATCH v3 06/35] drm: omapdrm: venc: Don't export omap_dss_pal_vm and omap_dss_ntsc_vm

The two variables are never used outside of their compilation unit, make them static. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/omapdss.h | 7 --- drivers/gpu/drm/omapdrm/dss/venc.c| 6 ++ 2 files changed, 2 insertions(+), 11

[PATCH v3 04/35] drm: omapdrm: panel-dpi: Remove unneeded check for OF node

As non-DT booting is no longer supported, the only way to instantiate the device is through an OF node, which is guaranteed to be present. Remove the unneeded check. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/displays/panel-dpi.c | 3 +++ 1

[PATCH v3 07/35] drm: omapdrm: hdmi: Store PHY features in PHY data structure

PHY features are stored in a global variable, while they should be properties of the PHY object. As existing OMAP platforms have a single HDMI PHY this doesn't cause any issue, but doesn't follow the driver model. Move the PHY features to the HDMI PHY data structure to follow the driver model and

[PATCH v3 03/35] drm: omapdrm: connector-analog-tv: Remove unneeded check for OF node

As non-DT booting is no longer supported, the only way to instantiate the device is through an OF node, which is guaranteed to be present. Remove the unneeded check. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/displays/connector-analog-tv.c | 3

[PATCH v3 02/35] drm: omapdrm: acx565akm: Remove unneeded check for OF node

As non-DT booting is no longer supported, the only way to instantiate the device is through an OF node, which is guaranteed to be present. Remove the unneeded check. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/displays/panel-sony-acx565akm.c |

[PATCH v3 00/35] omapdrm: Deconstruct DSS features

Hello, This patch series is a third version of the code previously posted as "[PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code". The omapdss/omapdrm initialization code is quite a mess. The physical devices are instantiated from DT, but two virtual devices named omapdrm

[PATCH v3 01/35] ARM: OMAP2+: Register SoC device attributes from machine .init()

SoC device attributes are registered with a call to soc_device_register() from the machine .init_late() operation, which is called from the late initcall, after all drivers built-in drivers have been probed. This results in the impossibility for drivers to use SoC device matching in their probe

Re: [PATCH v5 2/6] drm/bridge: Add a devm_ allocator for panel bridge.

On Fri, Aug 4, 2017 at 4:43 PM, Eric Anholt wrote: > Laurent Pinchart writes: > >> Hi Eric, >> >> (CC'ing Daniel) >> >> Thank you for the patch. >> >> On Tuesday 18 Jul 2017 14:05:06 Eric Anholt wrote: >>> This will let drivers reduce the error

Re: [PATCH v5] drm/fb-helper: pass physical dimensions to fbdev

Hi David, Thank you for the patch. On Friday 04 Aug 2017 11:25:24 David Lechner wrote: > The fbdev subsystem has a place for physical dimensions (width and height > in mm) that is readable by userspace. Since DRM also knows these > dimensions, pass this information to the fbdev device. I'm

Re: [PATCH v5 2/6] drm/bridge: Add a devm_ allocator for panel bridge.

Hi Eric, On Friday 04 Aug 2017 13:43:25 Eric Anholt wrote: > Laurent Pinchart writes: > > On Tuesday 18 Jul 2017 14:05:06 Eric Anholt wrote: > >> This will let drivers reduce the error cleanup they need, in > >> particular the "is_panel_bridge" flag. > >> > >>

Re: [PATCH v5 1/6] drm/vc4: Avoid using vrefresh==0 mode in DSI htotal math.

Boris Brezillon writes: > On Tue, 18 Jul 2017 14:05:05 -0700 > Eric Anholt wrote: > >> The incoming mode might have a missing vrefresh field if it came from >> drmModeSetCrtc(), which the kernel is supposed to calculate using >>

Re: [PATCH] drm/vc4: Advertise supported modifiers for planes

Daniel Stone writes: > The IN_FORMATS blob allows the kernel to advertise to userspace which > format/modifier combinations are supported, per plane. Use this to > advertise that we support both T_TILED and linear. > > Signed-off-by: Daniel Stone >

Re: [PATCH v5 2/6] drm/bridge: Add a devm_ allocator for panel bridge.

Laurent Pinchart writes: > Hi Eric, > > (CC'ing Daniel) > > Thank you for the patch. > > On Tuesday 18 Jul 2017 14:05:06 Eric Anholt wrote: >> This will let drivers reduce the error cleanup they need, in >> particular the "is_panel_bridge" flag. >> >> v2:

[Bug 101377] Gigabyte R9 380 card fails to load, kernel reports bug

https://bugs.freedesktop.org/show_bug.cgi?id=101377 --- Comment #11 from j...@dev1ce.com --- initrd was rebuilt. Im purchasing another R9 380 card for further testing (different manufacturer.) Its possible the build quality of the card is just mediocre as ive seen numerous reports of problems

Re: [PATCH v3 3/6] dt-bindings: add binding for Sitronix ST7586 display panels

Hi David, On Friday 04 Aug 2017 10:51:37 David Lechner wrote: > On 08/04/2017 09:54 AM, Laurent Pinchart wrote: > > On Thursday 03 Aug 2017 17:33:47 David Lechner wrote: > >> This adds a new binding for Sitronix ST7586 display panels. > >> > >> Using lego as the vendor prefix in the compatible

Re: [PATCH v3 3/6] dt-bindings: add binding for Sitronix ST7586 display panels

Den 04.08.2017 18.51, skrev David Lechner: On 08/04/2017 04:48 AM, Noralf Trønnes wrote: Den 04.08.2017 00.33, skrev David Lechner: This adds a new binding for Sitronix ST7586 display panels. Using lego as the vendor prefix in the compatible string because the display panel I am working

Re: [PATCH v3 3/6] dt-bindings: add binding for Sitronix ST7586 display panels

Hi Laurent, Den 04.08.2017 16.54, skrev Laurent Pinchart: Hi David, Thank you for the patch. On Thursday 03 Aug 2017 17:33:47 David Lechner wrote: This adds a new binding for Sitronix ST7586 display panels. Using lego as the vendor prefix in the compatible string because the display panel

Re: [PATCH v3 3/6] dt-bindings: add binding for Sitronix ST7586 display panels

On 08/04/2017 04:48 AM, Noralf Trønnes wrote: Den 04.08.2017 00.33, skrev David Lechner: This adds a new binding for Sitronix ST7586 display panels. Using lego as the vendor prefix in the compatible string because the display panel I am working with is an integral part of the LEGO

Re: [PATCH v4] drm/fb-helper: pass physical dimensions to fbdev

On 08/04/2017 11:22 AM, David Lechner wrote: The fbdev subsystem has a place for physical dimensions (width and height in mm) that is readable by userspace. Since DRM also knows these dimensions, pass this information to the fbdev device. This has to be done in drm_setup_crtcs_fb() instead of

[PATCH v5] drm/fb-helper: pass physical dimensions to fbdev

The fbdev subsystem has a place for physical dimensions (width and height in mm) that is readable by userspace. Since DRM also knows these dimensions, pass this information to the fbdev device. This has to be done in drm_setup_crtcs_fb() instead of drm_setup_crtcs() because fb_helper->fbdev may

[PATCH v4] drm/fb-helper: pass physical dimensions to fbdev

The fbdev subsystem has a place for physical dimensions (width and height in mm) that is readable by userspace. Since DRM also knows these dimensions, pass this information to the fbdev device. This has to be done in drm_setup_crtcs_fb() instead of drm_setup_crtcs() because fb_helper->fbdev may

Re: [Intel-gfx] [PATCH 00/11] constify i915 attribute_group structures.

On 04/08/17 11:39, Arvind Yadav wrote: On Friday 04 August 2017 04:04 PM, Lionel Landwerlin wrote: On 04/08/17 11:22, Arvind Yadav wrote: Hi Lionel, On Friday 04 August 2017 02:33 PM, Lionel Landwerlin wrote: Hi Arwind, These files were generated by a script maintained in this

Re: [PATCH v3 3/6] dt-bindings: add binding for Sitronix ST7586 display panels

On 08/04/2017 09:54 AM, Laurent Pinchart wrote: Hi David, Thank you for the patch. On Thursday 03 Aug 2017 17:33:47 David Lechner wrote: This adds a new binding for Sitronix ST7586 display panels. Using lego as the vendor prefix in the compatible string because the display panel I am working

[PATCH libdrm 2/2] etnaviv: add etna_bo_from_handle

Although etnaviv_drmif.h declared etna_bo_from_handle from the start, there was no implementation. Signed-off-by: Philipp Zabel --- etnaviv/etnaviv_bo.c | 19 +++ 1 file changed, 19 insertions(+) diff --git a/etnaviv/etnaviv_bo.c b/etnaviv/etnaviv_bo.c

[PATCH libdrm 1/2] etnaviv: fix etna_bo_from_name

Look up BOs from the name table using the name parameter instead of req.handle (which at this point is always zero). Signed-off-by: Philipp Zabel Reviewed-by: Eric Engestrom --- Sorry for the resend, this time to the correct list. ---

Re: [PATCH v5 2/6] drm/bridge: Add a devm_ allocator for panel bridge.

Now CC'ing Daniel with his correct address :-/ I'll blame auto-completion in my e-mail client. Sorry for the noise. On Friday 04 Aug 2017 16:46:24 Laurent Pinchart wrote: > Hi Eric, > > (CC'ing Daniel) > > Thank you for the patch. > > On Tuesday 18 Jul 2017 14:05:06 Eric Anholt wrote: > >

Re: [PATCH v3 3/6] dt-bindings: add binding for Sitronix ST7586 display panels

Hi David, Thank you for the patch. On Thursday 03 Aug 2017 17:33:47 David Lechner wrote: > This adds a new binding for Sitronix ST7586 display panels. > > Using lego as the vendor prefix in the compatible string because the display > panel I am working with is an integral part of the LEGO

Re: [PATCH v2 23/28] drm: omapdrm: Merge the dss_features and omap_dss_features structures

Hi Tomi, On Monday 15 May 2017 09:32:01 Tomi Valkeinen wrote: > On 13/05/17 14:12, Laurent Pinchart wrote: > >> Is it? You already use the dss compat string and soc_device_match to > >> figure out some versions. Isn't that a proper way to find out about the > >> SoC? But I agree that a more fine

[Bug 196337] [amdgpu][carrizo] Re-enable GFX PG breaks Carrizo

https://bugzilla.kernel.org/show_bug.cgi?id=196337 --- Comment #3 from Johannes Hirte (johannes.hi...@datenkhaos.de) --- Created attachment 257811 --> https://bugzilla.kernel.org/attachment.cgi?id=257811=edit Xorg.0.log -- You are receiving this mail because: You are watching the assignee of

[Bug 196337] [amdgpu][carrizo] Re-enable GFX PG breaks Carrizo

https://bugzilla.kernel.org/show_bug.cgi?id=196337 --- Comment #2 from Johannes Hirte (johannes.hi...@datenkhaos.de) --- Created attachment 257809 --> https://bugzilla.kernel.org/attachment.cgi?id=257809=edit dmesg -- You are receiving this mail because: You are watching the assignee of the

[Bug 196337] [amdgpu][carrizo] Re-enable GFX PG breaks Carrizo

https://bugzilla.kernel.org/show_bug.cgi?id=196337 --- Comment #1 from Johannes Hirte (johannes.hi...@datenkhaos.de) --- Still an issue with linux-4.13-rc3. I can login via ssh, so I can provide the logs. Showing blocked tasks gives me this: [ 620.046142] sysrq: SysRq : Show Blocked State [

[Bug 102008] DRI_PRIME causes X Error of failed request: BadAlloc (insufficient resources for operation)

https://bugs.freedesktop.org/show_bug.cgi?id=102008 bartos.p...@gmail.com changed: What|Removed |Added Component|Drivers/Gallium/radeonsi|Drivers/DRI/i965 QA

Re: [PATCH v5 2/6] drm/bridge: Add a devm_ allocator for panel bridge.

Hi Eric, (CC'ing Daniel) Thank you for the patch. On Tuesday 18 Jul 2017 14:05:06 Eric Anholt wrote: > This will let drivers reduce the error cleanup they need, in > particular the "is_panel_bridge" flag. > > v2: Slight cleanup of remove function by Andrzej I just want to point out that, in

Re: [PATCH v2 2/4] drm/bridge: dw-hdmi: add better clock disable control

On 07/31/2017 08:56 PM, Hans Verkuil wrote: On 07/31/2017 04:29 PM, Russell King wrote: The video setup path aways sets the clock disable register to a specific value, which has the effect of disabling the CEC engine. When we add the CEC driver, this becomes a problem. Fix this by only

Re: [PATCH v2 1/4] drm/bridge: dw-hdmi: add cec notifier support

On 07/31/2017 08:55 PM, Hans Verkuil wrote: On 07/31/2017 04:29 PM, Russell King wrote: Add CEC notifier support to the HDMI bridge driver, so that the CEC part of the IP can receive its physical address. Signed-off-by: Russell King Acked-by: Hans Verkuil

Re: [PATCH v3 2/6] drm/tinydrm: generalize tinydrm_xrgb8888_to_gray8()

Den 04.08.2017 09.27, skrev Noralf Trønnes: Den 04.08.2017 00.33, skrev David Lechner: This adds parameters for vaddr and clip to tinydrm_xrgb_to_gray8() to make it more generic. dma_buf_{begin,end}_cpu_access() are moved out to the repaper driver. Signed-off-by: David Lechner

Re: [PATCH v3 1/6] drm/tinydrm: remove call to mipi_dbi_init() from mipi_dbi_spi_init()

Den 04.08.2017 00.33, skrev David Lechner: This removes the call to mipi_dbi_init() from mipi_dbi_spi_init() so that drivers can have a driver-specific implementation if needed. Suggested-by: Noralf Trønnes Signed-off-by: David Lechner Reviewed-by:

Re: [PATCH 07/41] drm/fsl-dcu: Use .dumb_map_offset and .dumb_destroy defaults

Den 29.07.2017 19.24, skrev Stefan Agner: On 2017-07-23 12:16, Noralf Trønnes wrote: This driver can use the drm_driver.dumb_destroy and drm_driver.dumb_map_offset defaults, so no need to set them. Cc: Stefan Agner Cc: Alison Wang Signed-off-by:

Re: [PATCH] drm/etnaviv: Fix off-by-one error in reloc checking

2017-07-25 14:33 GMT+02:00 Wladimir J. van der Laan : > A relocation pointing to the last four bytes of a buffer can > legitimately happen in the case of small vertex buffers. > > Signed-off-by: Wladimir J. van der Laan Reviewed-by: Christian Gmeiner

[Bug 101672] radeonsi: 3D engines causing frequent GPU lockups

https://bugs.freedesktop.org/show_bug.cgi?id=101672 --- Comment #21 from MirceaKitsune --- Created attachment 133244 --> https://bugs.freedesktop.org/attachment.cgi?id=133244=edit Memtest86 screenshot To rule out the possibility of a hardware issue, I ran

[Bug 100306] System randomly freezes or crashes to the login screen, glitches until rebooted

https://bugs.freedesktop.org/show_bug.cgi?id=100306 --- Comment #35 from MirceaKitsune --- Created attachment 133243 --> https://bugs.freedesktop.org/attachment.cgi?id=133243=edit Memtest86 screenshot To rule out the possibility of a hardware issue, I ran

Re: [PATCH 2/3] drm/msm/mdp5: mark runtime_pm functions as __maybe_unused

On 08/03/2017 05:20 PM, Arnd Bergmann wrote: When CONFIG_PM is disabled, we get harmless warnings about unused functions: drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c:1025:12: error: 'mdp5_runtime_resume' defined but not used [-Werror=unused-function] static int mdp5_runtime_resume(struct

[drm:drm-syncobj-wait-null 31/31] htmldocs: include/drm/drm_syncobj.h:56: warning: No description found for parameter 'null_fence_attached'

tree: git://people.freedesktop.org/~airlied/linux.git drm-syncobj-wait-null head: 77645c44e3fc32028b3bef3b75889c1524b8df3a commit: 77645c44e3fc32028b3bef3b75889c1524b8df3a [31/31] drm/syncobj: allow wait on unsignalled semantics reproduce: make htmldocs All warnings (new ones prefixed by

Re: [Intel-gfx] [PATCH 00/11] constify i915 attribute_group structures.

On 04/08/17 11:22, Arvind Yadav wrote: Hi Lionel, On Friday 04 August 2017 02:33 PM, Lionel Landwerlin wrote: Hi Arwind, These files were generated by a script maintained in this repository : https://github.com/rib/gputop/blob/master/scripts/i915-perf-kernelgen.py It would best to update

  1   2   >