Re: [PATCH 1/3] drm/sun4i: tcon: Reduce the scope of the LVDS error a bit

Hi, On Tue, Mar 06, 2018 at 03:38:25PM +0800, Chen-Yu Tsai wrote: > > - /* > > -* This can only be made optional since we've had DT nodes > > -* without the LVDS reset properties. > > -* > > -* If the property is missing, just disable LVDS, and print a > > -

[Bug 105145] vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically

https://bugs.freedesktop.org/show_bug.cgi?id=105145 --- Comment #9 from k.phil...@gmail.com --- (In reply to Christian König from comment #8) > (In reply to k.philipp from comment #7) > > I did think about that, but it has the problem of breaking deinterlacing on > > all clients that do *not* set

Re: [RFC][PATCH 4/4 v2] drm_hwcomposer: Try to fallback if GLCompisition fails

On Tue, Feb 13, 2018 at 2:03 PM, John Stultz wrote: > On Tue, Feb 13, 2018 at 2:45 AM, Alexandru-Cosmin Gheorghe > wrote: >> On Mon, Feb 12, 2018 at 08:43:10PM -0800, John Stultz wrote: >>> On Wed, Jan 31, 2018 at 11:03 AM, John Stultz

Re: Aspirant for GSOC 2018 for Nouveau Vulkan driver

Hi, I am not been able to contact with mentor of this project. Can someone else from the community help me with this ? Regards, Anusha Srivastava On 3 March 2018 at 11:16, Anusha Srivastava wrote: > Hi Martin, > > Any update on this ? > Regards, > Anusha Srivastava >

RE: [PATCH] drm/atomic: Add new reverse iterator over all plane state

Hi Alex, Have resent the V2 with R-B of Daniel. Regards, Shirish S -Original Message- From: Alex Deucher [mailto:alexdeuc...@gmail.com] Sent: Tuesday, March 6, 2018 11:01 PM To: Vishwakarma, Pratik Cc: Daniel Vetter ; Deucher, Alexander

[PATCH] drm/atomic: Add new reverse iterator over all plane state (V2)

Add reverse iterator for_each_oldnew_plane_in_state_reverse to compliment the for_each_oldnew_plane_in_state way or reading plane states. The plane states are required to be read in reverse order for amd drivers, cause the z order convention followed in linux is opposite to how the planes are

[radeon-alex:amd-staging-drm-next 3/5] drivers/gpu/drm/ttm/ttm_tt.c:240:6: sparse: symbol 'ttm_tt_init_fields' was not declared. Should it be static?

tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next head: 085145ebf0e9c401e18cd9f7b2dd835a20c188c9 commit: 69665e4b79150133c3b28807f212972a1d3a392a [3/5] drm/ttm: add ttm_sg_tt_init reproduce: # apt-get install sparse git checkout

[RFC PATCH radeon-alex] drm/ttm: ttm_tt_init_fields() can be static

Fixes: 69665e4b7915 ("drm/ttm: add ttm_sg_tt_init") Signed-off-by: Fengguang Wu --- ttm_tt.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/ttm/ttm_tt.c b/drivers/gpu/drm/ttm/ttm_tt.c index 9711331..45c8ae1 100644 ---

Re: [PATCH v3 1/8] drm/blend: Add a generic alpha property

Hey, On Wed, Feb 21, 2018 at 2:04 PM, Maxime Ripard wrote: > > What is the behaviour of the tegra engine when it has both a > pixel-alpha and a plane-alpha? > > Atmel at least will drop one (but I'm not sure which one anymore). Sorry, I have no more on the Tegra

Re: [Intel-gfx] [PATCH] drm/dp: Correctly mask DP_TRAINING_AUX_RD_INTERVAL values for DP 1.4

On Tue, 2018-03-06 at 17:36 -0800, Manasi Navare wrote: > On Wed, Mar 07, 2018 at 12:24:46AM +, Pandiyan, Dhinakaran wrote: > > > > > > > > On Tue, 2018-03-06 at 15:24 -0800, Rodrigo Vivi wrote: > > > On Tue, Mar 06, 2018 at 10:37:48AM -0800, matthew.s.atw...@intel.com > > > wrote: > >

Re: [Intel-gfx] [PATCH] drm/dp: Correctly mask DP_TRAINING_AUX_RD_INTERVAL values for DP 1.4

On Wed, Mar 07, 2018 at 12:24:46AM +, Pandiyan, Dhinakaran wrote: > > > > On Tue, 2018-03-06 at 15:24 -0800, Rodrigo Vivi wrote: > > On Tue, Mar 06, 2018 at 10:37:48AM -0800, matthew.s.atw...@intel.com wrote: > > > From: Matt Atwood > > > > > >

Re: [PATCH v6 5/9] drm: Handle aspect-ratio info in getblob

Hi Ankit, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on drm/drm-next] [also build test WARNING on v4.16-rc4 next-20180306] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [Intel-gfx] [PATCH] drm/dp: Correctly mask DP_TRAINING_AUX_RD_INTERVAL values for DP 1.4

On Tue, 2018-03-06 at 16:48 -0800, Dhinakaran Pandiyan wrote: > > > On Tue, 2018-03-06 at 15:24 -0800, Rodrigo Vivi wrote: > > On Tue, Mar 06, 2018 at 10:37:48AM -0800, matthew.s.atw...@intel.com wrote: > > > From: Matt Atwood > > > > > >

[PATCH/RFC 43/60] drm/omap: dss: Acquire next dssdev at probe time

Look up the next dssdev at probe time based on device tree links for all DSS outputs and encoders. This will be used to reverse the order of the dssdev connect and disconnect call chains. Signed-off-by: Laurent Pinchart ---

[PATCH/RFC 51/60] drm/omap: Reverse direction of DSS device (dis)connect operations

The omapdrm and omapdss drivers are architectured based on display pipelines made of multiple components handled from sink (display) to source (DSS output). This is incompatible with the DRM bridge and panel APIs that handle components from source to sink. To reconcile the omapdrm and omapdss

[PATCH/RFC 53/60] drm/omap: dss: Move display type validation to initialization time

The display type is validated when the display is connected to the DSS output. We already have all the information we need for validation when initializing the outputs. Move validation to output initialization to simplify pipeline connection handling. Signed-off-by: Laurent Pinchart

[PATCH/RFC 36/60] drm/omap: dss: Extend omapdss_of_find_source_for_first_ep() to sinks

The omapdss_of_find_source_for_first_ep() function locates the source corresponding to the first endpoint of the first port of a device node. We can easily extend it to locate sinks as well by passing the port number as a parameter. This will be useful to find sinks in encoders drivers. Extend

[PATCH/RFC 58/60] drm/omap: Remove supported output check in CRTC connect handler

The CRTC connect handler checks whether the DSS output supports the DISPC channel assigned to it. As the channel is assigned to the output by the output driver a failure there could only result from a driver bug. All the output drivers have been verified and they are always assigned a DISPC

[PATCH/RFC 55/60] drm/omap: Pass pipe pointer to omap_crtc_init()

Replace the dss display device pointer by a pipe pointer that will allow the omap_crtc_init() function to access both the display and the DSS output. As a result we can remove the omapdss_device_get_dispc_channel() function that is now unneeded. Signed-off-by: Laurent Pinchart

[PATCH/RFC 47/60] drm/omap: dss: Get regulators at probe time

Regulators for the DPI, DSI, HDMI, SDI and VENC outputs are all looked up when connecting the output omap_dss_device. There's no need to delay regulator handling to that time, get the regulators at probe time. Signed-off-by: Laurent Pinchart ---

[PATCH/RFC 59/60] drm/omap: Set dispc_channel_connect from DSS output connect handlers

The omap_dss_device.dispc_channel_connect field is used by DSS outputs to fail the .enable() operation if they're not connected. Set the field directly from the (dis)connect handlers of the DSS outputs instead of going through the CRTC dss_mgr operations. Signed-off-by: Laurent Pinchart

[PATCH/RFC 56/60] drm/omap: Store CRTC lookup by channel table in omap_drm_private

The omap_crtcs global array is used to store pointers to omap_crtc indexed by DISPC channel number, in order to look them up in the dss_mgr operations. Store the information in the omap_drm_private structure in the form of an array of omap_drm_pipeline pointers. Signed-off-by: Laurent Pinchart

[PATCH/RFC 44/60] drm/omap: dss: Add for_each_dss_output() macro

Similarly to for_each_dss_display(), the for_each_dss_output() macro iterates over all the DSS connected outputs. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/base.c| 20 ++-- drivers/gpu/drm/omapdrm/dss/omapdss.h | 9

[PATCH/RFC 50/60] drm/omap: Group CRTC, encoder, connector and dssdev in a structure

Create an omap_drm_pipeline structure to model display pipelines, made of a CRTC, an encoder, a connector and a DSS display device. This allows grouping related parameters together instead of storing them in independent arrays and thus improves code readability. Signed-off-by: Laurent Pinchart

[PATCH/RFC 40/60] drm/omap: dss: hdmi4: Move initialization code from bind to probe

There's no reason to delay initialization of most of the driver (such as mapping memory I/O or enabling runtime PM) to the component bind handler. Perform as much of the initialization as possible at probe time, initializing at bind time only the parts that depends on the DSS. The cleanup code is

[PATCH/RFC 35/60] drm/omap: dss: Replace omap_dss_device port number with bitmask

The omap_dss_device port_num field stores the DT port number associated with the device. The field is used in different ways depending on the device type: - For DPI outputs, the port number is used as an identifier of the DPI instance - For sources, the port number is used to look up the

[PATCH/RFC 54/60] drm/omap: dss: Merge two disconnection helpers

To simplify the pipeline disconnection handling merge the omapdss_device_disconnect() and omapdss_output_unset_device() functions. The device state check is now called for every device in the pipeline, extending this sanity check coverage. There is no need to return an error from

[PATCH/RFC 57/60] drm/omap: Remove omap_crtc_output global array

The omap_crtc_output global array is used to look up the DSS output device by channel. We can replace that by accessing the output device from the pipeline if we store the pipeline pointer in the omap_crtc structure. The global array is also used to protect against double connection of an output.

[PATCH/RFC 38/60] drm/omap: dss: Cleanup error paths in output init functions

Rename the jump labels according to the cleanup they perform, not the location they're accessed from, and move functions from error checks to cleanup paths, and move reference handling to simplify cleanup. Signed-off-by: Laurent Pinchart ---

Re: [Intel-gfx] [PATCH] drm/dp: Correctly mask DP_TRAINING_AUX_RD_INTERVAL values for DP 1.4

On Tue, 2018-03-06 at 15:24 -0800, Rodrigo Vivi wrote: > On Tue, Mar 06, 2018 at 10:37:48AM -0800, matthew.s.atw...@intel.com wrote: > > From: Matt Atwood > > > > DP_TRAINING_AUX_RD_INTERVAL with DP 1.3 spec changed bit scheme from 8 > > bits to 7 bits in DPCD

[PATCH/RFC 60/60] drm/omap: dss: Remove the dss_mgr_(dis)connect() operations

The dss_mgr .connect() and .disconnect() are implemented as no-op in omapdrm. The operations are unneeded, remove them. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dpi.c | 10 +- drivers/gpu/drm/omapdrm/dss/dsi.c | 10

[PATCH/RFC 41/60] drm/omap: dss: hdmi5: Move initialization code from bind to probe

There's no reason to delay initialization of most of the driver (such as mapping memory I/O or enabling runtime PM) to the component bind handler. Perform as much of the initialization as possible at probe time, initializing at bind time only the parts that depends on the DSS. The cleanup code is

[PATCH/RFC 48/60] drm/omap: Remove unneeded variable assignments in omap_modeset_init

The crtc_idx and plane_idw variables in the main loop are always equal to the loop counter i, use it instead. Don't unnecessarily initialize dssdev to NULL. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_drv.c | 18 +- 1 file

[PATCH/RFC 45/60] drm/omap: dss: Add function to retrieve display for an output

Add a new omapdss_display_get() function to retrieve the omap_dss_device for a given DSS output. This will be used when reversing the direction of the DSS pipeline handling logic. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/display.c | 9

[PATCH/RFC 34/60] drm/omap: dss: Modify omapdss_find_output_from_display() to return channel

The omapdss_find_output_from_display() function is only used to retrieve the dispc channel corresponding to the display. Return the dispc channel directly, and rename the function to omapdss_device_get_dispc_channel() to match its new purpose. The dssdev->id check is removed as the dssdev is

[PATCH/RFC 52/60] drm/omap: dss: Move connection checks to omapdss_device_(dis)connect

When a DSS output is (dis)connected the omapdss_output_(un)set_device() function performs a sanity check to ensure that the output isn't already (dis)connected. The check is unnecessary as those situations should never happen, but can nonetheless be useful to catch driver bugs. To prepare for

[PATCH/RFC 42/60] drm/omap: dss: venc: Move initialization code from bind to probe

There's no reason to delay initialization of most of the driver (such as mapping memory I/O or enabling runtime PM) to the component bind handler. Perform as much of the initialization as possible at probe time, initializing at bind time only the parts that depends on the DSS. The cleanup code is

[PATCH/RFC 46/60] drm/omap: dss: Remove duplicated parameter to dss_mgr_(dis)connect()

The dss_mgr_connect() and dss_mgr_disconnect() functions take two omap_dss_device pointers as parameters, which are always set to the same value by all callers. Remove the duplicated pointer. Signed-off-by: Laurent Pinchart ---

[PATCH/RFC 49/60] drm/omap: Create all planes before CRTCs

Creating all the planes in a single location instead of creating them per-CRTC with remaining planes then created in a second step simplifies the logic. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_drv.c | 45

[PATCH/RFC 33/60] drm/omap: dss: Move DSS mgr ops and private data to dss_device

The DSS manager ops and private data pointer are specific to a DSS instance. Store them in the dss_device structure instead of global variable. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dss.h | 2 ++

[PATCH/RFC 22/60] drm/omap: dss: Move src and dst check and set to connection handlers

The encoders duplicate the same omap_dss_device src and dst fields set and checks in their connect and disconnect handlers. Move the code to the connect and disconnect wrappers. Signed-off-by: Laurent Pinchart ---

[PATCH/RFC 37/60] drm/omap: displays: Don't cast dssdev to panel data unnecessarily

The connect handle of the analog TV and HDMI connectors casts the dssdev to panel data only to then access fields of the panel data that are also present in the dssdev. Remove the cast and use dssdev directly. Signed-off-by: Laurent Pinchart ---

[PATCH/RFC 32/60] drm/omap: dss: Store dss_device pointer in omap_dss_device

Storing the dss_device pointer in the omap_dss_device structure will allow accessing the dss_device from the dss_mgr API functions. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/displays/connector-analog-tv.c | 2 +-

[PATCH/RFC 30/60] drm/omap: dss: Remove panel devices list

The panel devices list isn't used anymore, all panel devices are accessed through the global devices list. Remove it. Signed-off-by: Laurent Pinchart --- .../gpu/drm/omapdrm/displays/connector-analog-tv.c | 9 ++--

[PATCH/RFC 39/60] drm/omap: dss: dsi: Move initialization code from bind to probe

There's no reason to delay initialization of most of the driver (such as mapping memory I/O or enabling runtime PM) to the component bind handler. Perform as much of the initialization as possible at probe time, initializing at bind time only the parts that depends on the DSS. The cleanup code is

[PATCH/RFC 19/60] drm/omap: dss: Move common device operations to common structure

The various types of omapdss_*_ops structures define multiple operations that are not specific to a bus type. To simplify the code and remove dependencies on specific bus types move those operations to a common structure. Operations that are specific to a bus type are kept in the specialized ops

[PATCH/RFC 28/60] drm/omap: dss: Make omap_dss_get_next_device() more generic

Despite its name, the omap_dss_get_next_device() function operates on display devices only. Make it more generic by allowing operation on all devices, with a parameter to specify the device type. While at it rename the function to omapdss_device_get_next() to match the naming of the other

[PATCH/RFC 14/60] drm/omap: dss: Rename omap_dss_device list field to output_list

For coherency with the panel_list field, rename list to output_list. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/omapdss.h | 2 +- drivers/gpu/drm/omapdrm/dss/output.c | 10 +- 2 files changed, 6 insertions(+), 6 deletions(-)

[PATCH/RFC 21/60] drm/omap: dss: Move debug message and checks to connection handlers

The connectors, encoders and display duplicate the same debug messages and connection checks in their omap_dss_device connect and disconnect handlers. Move the code to the connect and disconnect wrappers. To simplify the code the connect function returns -EBUSY unconditionally if the device is

[PATCH/RFC 27/60] drm/omap: dss: Rename for_each_dss_dev macro to for_each_dss_display

The macro iterates over displays only, rename it accordingly. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dss.c | 2 +- drivers/gpu/drm/omapdrm/dss/omapdss.h | 2 +- drivers/gpu/drm/omapdrm/omap_drv.c| 4 ++-- 3 files changed, 4

[PATCH/RFC 24/60] drm/omap: dsi: Simplify debugfs implementation

The DSI debugfs regs and irqs show handlers received a pointer to the DSI private data. There's no need to look it up from the list of DSS outputs. Use the pointer directly, this allows simplifying the implementation of the handlers. Signed-off-by: Laurent Pinchart

[PATCH/RFC 29/60] drm/omap: dss: Split omapdss_register_display()

Split the function into omapdss_display_init() to perform display-specific initialization of the omap_dss_device, and omapdss_register_display() to register the device. The latter will then be replaced by more generic registration. Signed-off-by: Laurent Pinchart

[PATCH/RFC 18/60] drm/omap: dss: Allow looking up any device by port

The omap_dss_find_output_by_port() function looks up an omap_dss_device by port from the list of devices registered as outputs. In preparation for looking up sinks in addition to sources, allow the function to look up any registered device. Rename it to omap_dss_find_device_by_port() to match its

[PATCH/RFC 26/60] drm/omap: dss: Remove output devices list

The output devices list isn't used anymore, all output devices are accessed through the global devices list. Remove it. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/displays/encoder-opa362.c | 9 ++-

[PATCH/RFC 12/60] drm/omap: displays: Remove videomode from omap_dss_device structure

The omap_dss_device structure stores a videomode. All the connector and panel drivers that use omap_dss_device also store the videomode in their own panel_drv_data structures. There's no need to duplicate, remove the videomode field from omap_dss_device. Signed-off-by: Laurent Pinchart

[PATCH/RFC 25/60] drm/omap: Move DSI debugfs clocks dump to dsi%u_clks files

The DSI clocks are dumped in the DSS-level debugfs clocks file. This complicates the implementation as the DSI private data has to be looked up through the outputs list. Simplify it by creating two debugfs files, dsi1_clks and dsi2_clks, to dump the DSI clocks. Signed-off-by: Laurent Pinchart

[PATCH/RFC 16/60] drm/omap: dss: Create and use omapdss_device_is_registered()

The omapdss_component_is_loaded() function test whether a component is loaded by checking whether it is present in the displays list or the outputs list. Simplify the implementation by checking for the component in the global omap_dss_device list. Signed-off-by: Laurent Pinchart

[PATCH/RFC 20/60] drm/omap: dss: Add functions to connect and disconnect devices

The omap_dss_device objects model display components and are connected at runtime to create display pipelines. The connect and disconnect operations implemented by each component contain lots of duplicate code. As a first step towards fixing this, create new functions to wrap the direct calls to

[PATCH/RFC 31/60] drm/omap: dss: Move and rename omap_dss_(get|put)_device()

The functions operate on any omap_dss_device, move them from display.c to base.c. While at it rename them to match the naming of the other functions operating on struct omap_dss_device. Signed-off-by: Laurent Pinchart ---

[PATCH/RFC 11/60] drm/omap: dss: Constify omap_dss_driver operations structure

The structure contains function pointers that don't need to be modified. Make all its instances const to improve security. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/displays/connector-analog-tv.c | 2 +-

[PATCH/RFC 10/60] drm/omap: dss: Remove unused omapdss_default_get_timings()

All omap_dss_driver instances provide the get_timings operation. Remove the default function. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/display.c | 10 -- 1 file changed, 10 deletions(-) diff --git

[PATCH/RFC 15/60] drm/omap: dss: Create global list of all omap_dss_device instances

The omap_dss_device instances are stored in two separate lists, depending on whether they are panels or outputs. Create a third list that stores all omap_dss_device instances to allow generic code to operate on all instances. Signed-off-by: Laurent Pinchart ---

[PATCH/RFC 23/60] drm/omap: displays: Remove input omap_dss_device from panel data

All connectors, encoders and panels store a pointer to their input omap_dss_device in the panel driver data structure. This duplicates the src field in the omap_dss_device structure. Remove the private copy and use the src field. Signed-off-by: Laurent Pinchart

[PATCH/RFC 17/60] drm/omap: dss: Rework output lookup by port node

The omap_dss_find_output_by_port_node() function defined in output.c looks up an output from its port node. To do so it needs to call helper functions from dss-of.c to lookup the port parent and the port number. As omap_dss_find_output_by_port_node() is only called by

[PATCH/RFC 08/60] drm/omap: dss: Remove omapdss_atv_ops get_wss and set_wss operations

The operations are never used, remove them. If the need to set wide screen signaling data arises later, it should be implemented by extending the DRM bridge API. Signed-off-by: Laurent Pinchart --- .../gpu/drm/omapdrm/displays/connector-analog-tv.c | 19

[PATCH/RFC 13/60] drm/omap: dss: Remove omap_dss_device panel fields

The omap_dss_device panel.dsi_pix_fmt and panel.dsi_mode fields are unused. Remove them. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/displays/panel-dsi-cm.c | 1 - drivers/gpu/drm/omapdrm/dss/omapdss.h | 5 - 2 files changed, 6

[PATCH/RFC 07/60] drm/omap: dss: Remove omapdss_hdmi_ops set_infoframe operation

The operation is never used, remove it. If the need to set HDMI infoframe arises later, it should be implemented by extending the DRM bridge API. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/displays/connector-hdmi.c| 10 --

[PATCH/RFC 09/60] drm/omap: dss: Remove DSS encoders get_timings operation

The get_timings operation from DSS encoders (not to be confused with the identically named operation in omap_dss_driver) is never called. Remove it. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/displays/encoder-opa362.c| 11 ---

[PATCH/RFC 06/60] drm/omap: dss: Move platform_device_register from core.c to dss.c probe

From: Jyri Sarha Register the omapdrm device when we know that dss device probe going to succeed. This avoids DSS6 and DSS2 omapdrm device registration from colliding with each other. Signed-off-by: Jyri Sarha Signed-off-by: Laurent Pinchart

[PATCH/RFC 03/60] drm/omap: Do dss_device (display) ordering in omap_drv.c

From: Peter Ujfalusi Sort the dssdev array based on DT aliases. With this change we can remove the panel ordering from dss/display.c and have all sorting related to dssdevs in one place. Signed-off-by: Peter Ujfalusi Signed-off-by: Tomi Valkeinen

[PATCH/RFC 05/60] drm/omap: dss: Gather OMAP DSS components at probe time

The omapdss_gather_components() function walks the OF graph to create a list of all components part of the display device. There's no need to delay this operation until DSS bind time as we have all the information we need at probe time. Signed-off-by: Laurent Pinchart

[PATCH/RFC 00/60] omapdrm: Reverse direction of DSS device (dis)connect operations

Hello, This patch series is a first step towards moving the omapdrm driver away from the custom bridge and panel drivers to drm_bridge and drm_panel. The main blocker to transition to drm_bridge and drm_panel is the direction of the bridge operations. While the omapdrm driver manages its

[PATCH/RFC 01/60] drm/omap: Allocate drm_device earlier and unref it as last step

From: Peter Ujfalusi If we allocate the drm_device earlier we can just return the error code without the need to use goto. Do the unref of the drm_device as a last step when cleaning up. This will make the drm_device available longer for us and makes sure that we only free

[PATCH/RFC 04/60] drm/omap: dss: Remove display ordering from dss/display.c

From: Peter Ujfalusi As ordering of the dss_devices based on DT aliases is now implemented in omap_drm.c, there is no need to do the ordering in dss/display.c anymore. At the same time remove the alias member of the omap_dss_device struct since it is no longer needed. The

[PATCH/RFC 02/60] drm/omap: Manage the usable omap_dss_device list within omap_drm_private

From: Peter Ujfalusi Instead of reaching back to DSS to iterate through the dss_devices every time, use an internal array where we store the available and usable dss_devices. At the same time remove the omapdss_device_is_connected() check from omap_modeset_init() as it

Re: [PATCH 2/3] drm/vc4: Check if plane requires background fill

Ville Syrjälä writes: > On Tue, Mar 06, 2018 at 02:48:38AM +0100, Stefan Schake wrote: >> Considering a single plane only, we have to enable background color >> when the plane has an alpha format and could be blending from the >> background or when it doesn't cover

[PATCH v3 5/6] drm/i915: Introduce 'priority offset' for GPU contexts (v2)

There are cases where a system integrator may wish to raise/lower the priority of GPU workloads being submitted by specific OS process(es), independently of how the software self-classifies its own priority. Exposing "priority offset" as an i915-specific cgroup parameter will enable such

[PATCH v3 6/6] drm/i915: Add context priority & priority offset to debugfs (v2)

Update i915_context_status to include priority information. v2: - Clarify that the offset is based on cgroup (Chris) Signed-off-by: Matt Roper --- drivers/gpu/drm/i915/i915_debugfs.c | 3 +++ 1 file changed, 3 insertions(+) diff --git

[PATCH v3 1/6] cgroup: Allow registration and lookup of cgroup private data

There are cases where other parts of the kernel may wish to store data associated with individual cgroups without building a full cgroup controller. Let's add interfaces to allow them to register and lookup this private data for individual cgroups. A kernel system (e.g., a driver) that wishes to

[PATCH v3 3/6] cgroup: Introduce cgroup_permission()

Non-controller kernel subsystems may base access restrictions for cgroup-related syscalls/ioctls on a process' access to the cgroup. Let's make it easy for other parts of the kernel to check these cgroup permissions. Cc: Tejun Heo Cc: cgro...@vger.kernel.org Signed-off-by: Matt

[PATCH v3 4/6] drm/i915: cgroup integration (v2)

Introduce a new DRM_IOCTL_I915_CGROUP_SETPARAM ioctl that will allow userspace to set i915-specific parameters for individual cgroups. i915 cgroup data will be registered and later looked up via the new cgroup_priv infrastructure. v2: - Large rebase/rewrite for new cgroup_priv interface

[PATCH v3 2/6] cgroup: Introduce task_get_dfl_cgroup()

Wraps task_dfl_cgroup() to also take a reference to the cgroup. Cc: Tejun Heo Cc: cgro...@vger.kernel.org Signed-off-by: Matt Roper --- include/linux/cgroup.h | 23 +++ 1 file changed, 23 insertions(+) diff --git

[PATCH v3 0/6] DRM/i915 cgroup integration

This is the third iteration of the work previously posted here: (v1) https://lists.freedesktop.org/archives/intel-gfx/2018-January/153156.html (v2) https://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg208170.html The high level goal of this work is to allow non-cgroup-controller

Re: New KFD ioctls: taking the skeletons out of the closet

On Tue, Mar 06, 2018 at 05:44:41PM -0500, Felix Kuehling wrote: > Hi all, > > Christian raised two potential issues in a recent KFD upstreaming code > review that are related to the KFD ioctl APIs: > > 1. behaviour of -ERESTARTSYS > 2. transactional nature of KFD ioctl definitions, or lack

[Bug 103234] KWin crashed when Alt+Tab-ing through open windows

https://bugs.freedesktop.org/show_bug.cgi?id=103234 --- Comment #15 from Marek Olšák --- Can you get a backtrace with GALLIUM_THREAD=0 ? I'd like to know where indexbuf == NULL is coming from. -- You are receiving this mail because: You are the assignee for the

Re: [Intel-gfx] [PATCH] drm/dp: Correctly mask DP_TRAINING_AUX_RD_INTERVAL values for DP 1.4

On Tue, Mar 06, 2018 at 10:37:48AM -0800, matthew.s.atw...@intel.com wrote: > From: Matt Atwood > > DP_TRAINING_AUX_RD_INTERVAL with DP 1.3 spec changed bit scheme from 8 > bits to 7 bits in DPCD 0x000e. The 8th bit describes a new feature, for > panels that use this

Re: [PATCH v6 5/9] drm: Handle aspect-ratio info in getblob

Hi Ankit, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on drm/drm-next] [also build test WARNING on v4.16-rc4 next-20180306] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

[RFC][PATCH 2/2 v4] drm_hwcomposer: Add platformhisi buffer importer for hikey and hikey960

This allows for importing buffers allocated from the hikey and hikey960 gralloc implelementations. Cc: Marissa Wall Cc: Sean Paul Cc: Dmitry Shmidt Cc: Robert Foss Cc: Matt Szczesiak

[RFC][PATCH 1/2] drm_hwcomposer: Error out on YUV layer as it would fail for single planes

As suggested by Alexandru-Cosmin Gheorghe: ConvertHALFormatToDrm logic would work only for 1 plane formats, and probably gets rejected by drmModeAddFb2, but to save debugging time maybe it worth removing DRM_FORMAT_YVU420 from ConvertHALFormatToDrm and checking it's return code. So this patch

Re: New KFD ioctls: taking the skeletons out of the closet

On 7 March 2018 at 08:44, Felix Kuehling wrote: > Hi all, > > Christian raised two potential issues in a recent KFD upstreaming code > review that are related to the KFD ioctl APIs: > > 1. behaviour of -ERESTARTSYS > 2. transactional nature of KFD ioctl definitions, or

Re: [PATCHv2 5/7] cec-pin: add error injection support

On 05/03/18 14:51, Hans Verkuil wrote: > From: Hans Verkuil > > Implement all the error injection commands. > > The state machine gets new states for the various error situations, > helper functions are added to detect whether an error injection is > active and the

New KFD ioctls: taking the skeletons out of the closet

Hi all, Christian raised two potential issues in a recent KFD upstreaming code review that are related to the KFD ioctl APIs: 1. behaviour of -ERESTARTSYS 2. transactional nature of KFD ioctl definitions, or lack thereof I appreciate constructive feedback, but I also want to encourage an

Re: Overlay sugar syntax (was: Re: [PATCH v6 3/4] drm: rcar-du: Fix legacy DT to create LVDS encoder nodes)

On Tue, Mar 6, 2018 at 8:07 AM, David Gibson wrote: > On Tue, Mar 06, 2018 at 01:30:05PM +0100, Geert Uytterhoeven wrote: >> Hi David, >> >> On Tue, Mar 6, 2018 at 4:54 AM, David Gibson >> wrote: >> > On Fri, Feb 23, 2018 at 09:05:24AM

Re: [PATCH 6/6] drm/amdgpu: explicit give BO type to amdgpu_bo_create

NAK. For KFD we need the ability to create a BO from an SG list that doesn't come from another BO. We use this for mapping pages from the doorbell aperture into GPUVM for GPU self-dispatch. If you remove this now, I'll need to add it back in some form in a month or two when I get to that part of

[RFC][PATCH] libdrm: gralloc_handle.h: Fix build issue with Android

In trying to integrate the new gralloc_handle.h with the drm_hwcomposer, I started seeing the following compilation errors: In file included from external/drm_hwcomposer/platformdrmgeneric.cpp:28: external/libdrm/android/gralloc_handle.h:108:9: error: cannot initialize return object of type

[Bug 105089] radeonsi GPU lockup / crash with wine [The Witcher 3]

https://bugs.freedesktop.org/show_bug.cgi?id=105089 mirh changed: What|Removed |Added CC||m...@protonmail.ch ---

Re: [PATCH 1/3] drm/vc4: Set premultiplied for alpha formats

On Tue, Mar 6, 2018 at 8:35 PM, Eric Anholt wrote: > Stefan Schake writes: > >> Alpha formats in DRM are assumed to be premultiplied, so we should be >> setting the PREMULT bit in the plane configuration for HVS. >> >> Signed-off-by: Stefan Schake

Re: [PATCH 2/3] drm/vc4: Check if plane requires background fill

On Tue, Mar 06, 2018 at 02:48:38AM +0100, Stefan Schake wrote: > Considering a single plane only, we have to enable background color > when the plane has an alpha format and could be blending from the > background or when it doesn't cover the entire screen. > > Signed-off-by: Stefan Schake

Re: [PATCH 1/3] drm/vc4: Set premultiplied for alpha formats

Stefan Schake writes: > Alpha formats in DRM are assumed to be premultiplied, so we should be > setting the PREMULT bit in the plane configuration for HVS. > > Signed-off-by: Stefan Schake > --- > drivers/gpu/drm/vc4/vc4_plane.c | 3 ++- >

Re: [PULL] drm-misc-next

On Tue, Mar 06, 2018 at 09:07:52PM +0200, Ville Syrjälä wrote: > On Tue, Mar 06, 2018 at 02:01:21PM -0500, Sean Paul wrote: > > On Tue, Mar 06, 2018 at 07:42:53AM +0100, Daniel Vetter wrote: > > > On Tue, Mar 6, 2018 at 12:20 AM, Sean Paul wrote: > > > > On Mon, Mar 5, 2018

  1   2   3   4   >