https://bugs.freedesktop.org/show_bug.cgi?id=99841
--- Comment #20 from Jari Tahvanainen ---
Michel and others - landed to drm-tip. Ready for resolved+fixed ? Or even
verified...
commit 12ffed96d4369f086261ba2ee734fa8c932d7f55
Author: Michel Dänzer
AuthorDate: Thu Mar 23 17:53:26 2017 +0900
Op 28-03-17 om 09:01 schreef Daniel Vetter:
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c
> b/drivers/gpu/drm/i915/intel_display.c
> index 68cded453882..43dbad62786e 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -12463,6 +12463,11 @@
+ Patrice for sti DT
2017-03-29 16:15 GMT+02:00 Hans Verkuil :
> From: Benjamin Gaignard
>
> To use CEC notifier sti CEC driver needs to get phandle
> of the hdmi device.
>
> Signed-off-by: Benjamin Gaignard
> Signed-off-by: Hans Verkuil
> CC: devicet...@vger.kernel.org
> ---
> arch/arm/boot/d
On Wed, Mar 29, 2017 at 02:05:26PM -0700, Sinclair Yeh wrote:
> Hi Daniel,
>
> On Tue, Mar 28, 2017 at 09:49:38AM +0200, Daniel Vetter wrote:
> > On Mon, Mar 27, 2017 at 03:01:03PM -0700, Sinclair Yeh wrote:
> > > Switch over to using internal atomic API for mode set.
> > >
> > > This removes the
On Thu, Mar 30, 2017 at 08:44:25AM +0200, David Herrmann wrote:
> Hey
>
> On Wed, Mar 29, 2017 at 11:42 PM, Laurent Pinchart
> wrote:
> > Hi David,
> >
> > On Wednesday 29 Mar 2017 14:51:48 David Herrmann wrote:
> >> On Wed, Mar 29, 2017 at 2:20 PM, Laurent Pinchart wrote:
> >> > On Wednesday 29
On Wed, Mar 29, 2017 at 09:59:34PM +0200, Hans Verkuil wrote:
> Hi Daniel,
>
> On 29/03/17 19:47, Daniel Vetter wrote:
> > On Wed, Mar 29, 2017 at 04:15:32PM +0200, Hans Verkuil wrote:
> >> From: Hans Verkuil
> >>
> >> This patch series adds the CEC physical address notifier code, based on
> >> R
On Wed, Mar 29, 2017 at 10:47:34PM +0200, Julia Lawall wrote:
> The kfree on line 926 would only be a problem for the references to e on
> lines 933 and 937 if the return value of drm_event_reserve_init can be
> -EDEADLK.
It cannot, but would indeed be prudent to reset to NULL, like we do at the
t
On Thu, Mar 30, 2017 at 07:48:45AM +, Pandiyan, Dhinakaran wrote:
> On Thu, 2017-03-30 at 09:36 +0200, Maarten Lankhorst wrote:
> > Op 28-03-17 om 09:01 schreef Daniel Vetter:
> > >
> > > diff --git a/drivers/gpu/drm/i915/intel_display.c
> > > b/drivers/gpu/drm/i915/intel_display.c
> > > inde
https://bugs.freedesktop.org/show_bug.cgi?id=99841
--- Comment #21 from Michel Dänzer ---
If people are okay with that before it lands in 4.10.y, sure.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
On Wed, Mar 29, 2017 at 02:45:23PM +0100, Javi Merino wrote:
> The size of .word is the size of a word in the given platform, which
> for intel systems is 16-bits but other architectures use different
> sizes. However, .hword emits 16-bit numbers regardless of the
> platform (and despite the name)
Am 30.03.2017 um 03:41 schrieb Michel Dänzer:
On 30/03/17 12:18 AM, Christian König wrote:
Am 29.03.2017 um 16:54 schrieb Michel Dänzer:
On 29/03/17 10:22 PM, Christian König wrote:
Am 29.03.2017 um 11:18 schrieb Jan Burgmeier:
Signed-off-by: Jan Burgmeier
---
drivers/gpu/drm/amd/amdgpu/
Am 30.03.2017 um 08:38 schrieb Michel Dänzer:
On 29/03/17 09:55 PM, Christian König wrote:
From: Christian König
No need to implement the same logic twice. Also check if the busy placements
are identical to the already scanned placements before checking them.
Signed-off-by: Christian König
On Wed, Mar 29, 2017 at 03:11:26PM -0700, Ben Widawsky wrote:
> On 17-03-29 23:17:13, Ville Syrjälä wrote:
> >On Fri, Mar 24, 2017 at 02:29:50PM -0700, Ben Widawsky wrote:
> >> This was based on a patch originally by Kristian. It has been modified
> >> pretty heavily to use the new callbacks from t
From: Laurent Pinchart
In preparation for adding PHY operations to handle RX SENSE and HPD,
group all the PHY interrupt setup code in a single location and extract
it to a separate function.
Signed-off-by: Laurent Pinchart
Reviewed-by: Jose Abreu
[narmstrong: renamed dw_hdmi_fb_registered to d
This patch adds a new DRM documentation entry and links to the input
format table added in the dw_hdmi header.
Signed-off-by: Neil Armstrong
---
Documentation/gpu/bridge/dw-hdmi.rst | 15 +++
Documentation/gpu/index.rst | 1 +
2 files changed, 16 insertions(+)
create mode
Some display pipelines can only provide non-RBG input pixels to the HDMI TX
Controller, this patch takes the pixel format from the plat_data if provided.
Reviewed-by: Jose Abreu
Signed-off-by: Neil Armstrong
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 326 +-
inc
The Amlogic GX SoCs implements a Synopsys DesignWare HDMI TX Controller
in combination with a very custom PHY.
Thanks to Laurent Pinchart's changes, the HW report the following :
Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
The following differs from common PHY integration as
The HDMI TX controller support HPD and RXSENSE signaling from the PHY
via it's STAT0 PHY interface, but some vendor PHYs can manage these
signals independently from the controller, thus these STAT0 handling
should be moved to PHY specific operations and become optional.
The existing STAT0 HPD and
Add documentation for added Bus Formats to describe RGB and YUV formats used
as input to the Synopsys DesignWare HDMI TX Controller.
Signed-off-by: Neil Armstrong
---
Documentation/media/uapi/v4l/subdev-formats.rst | 871 +++-
1 file changed, 857 insertions(+), 14 deletions(-
In order to describe the RGB and YUV bus formats used to feed the
Synopsys DesignWare HDMI TX Controller, add missing formats to the
list of Bus Formats.
Documentation for these formats is added in a separate patch.
Reviewed-by: Archit Taneja
Reviewed-by: Jose Abreu
Signed-off-by: Neil Armstron
https://bugs.freedesktop.org/show_bug.cgi?id=99841
Elimar Riesebieter changed:
What|Removed |Added
CC||riese...@lxtec.de
--- Comment #22 f
On 03/30/2017 11:30 AM, Patrice CHOTARD wrote:
> Hi Benjamin
>
> On 03/30/2017 09:41 AM, Benjamin Gaignard wrote:
>> + Patrice for sti DT
>
> In order to be coherent with all previous STi DT patches,
>
> can you update the commit message with "ARM: dts: STiH410: update
> sti-cec for CEC notifie
From: Colin Ian King
trivial fix to spelling mistake in DRM_ERROR error message
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/amd/amdgpu/mxgpu_vi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/mxgpu_vi.c
b/drivers/gpu/drm/amd/amdgpu/mxgpu_
Handlers are currently the only blocker to compile the kernel with gcc 7
and KASAN+use-after-scope enabled:
drivers/gpu/drm/i915/gvt/handlers.c:2200:1: error: the frame size of 43760
bytes is larger than 2048 bytes [-Werror=frame-larger-than=]
drivers/gpu/drm/i915/gvt/handlers.c:2402:1: error: the
On 03/28/2017 07:02 PM, Jyri Sarha wrote:
On 03/27/17 08:58, Archit Taneja wrote:
Hi,
On 03/07/2017 03:21 AM, Christopher Spinrath wrote:
Hi Fabio,
On 03/06/2017 10:46 PM, Fabio Estevam wrote:
Hi Christopher,
On Mon, Mar 6, 2017 at 6:40 PM,
wrote:
From: Christopher Spinrath
On some bo
On ke, 2017-03-29 at 10:10 +0100, Chris Wilson wrote:
> Scatter a few cond_resched() in between phases of the drm_mm selftests
> to try and prevent us incurring the wrath of the NMI watchdog.
>
> Signed-off-by: Chris Wilson
> Cc: Joonas Lahtinen
Reviewed-by: Joonas Lahtinen
Regards, Joonas
--
Hi Thierry,
On 29.03.2017 16:43, Thierry Reding wrote:
> From: Thierry Reding
>
> This set of patches adds support for deferring FB helper setup, which is
> useful to obtain a sane configuration even when no outputs are available
> during probe.
>
> One example is HDMI, where fbdev will currently
The 'req->mip_levels' parameter in vmw_gb_surface_define_ioctl() is
a user-controlled 'uint32_t' value which is used as a loop count limit.
This can lead to a kernel lockup and DoS. Add check for 'req->mip_levels'.
References:
https://bugzilla.redhat.com/show_bug.cgi?id=1437431
Signed-off-by: Vlad
On 29/03/17 13:30, Laurent Pinchart wrote:
> Hi Tomi,
>
> Thank you for the patch.
>
> On Tuesday 28 Mar 2017 16:08:09 Tomi Valkeinen wrote:
>> If omap_plane_atomic_update() is called when the crtc is disabled, and
>> the timings are zero, we'll see the following warning:
>>
>> omapdss DISPC erro
Op 30-03-17 om 10:42 schreef Dhinakaran Pandiyan:
> From: "Pandiyan, Dhinakaran"
>
> Having an ->atomic_release callback is useful to release shared resources
> that get allocated in compute_config(). This function is expected to be
> called in the atomic_check() phase before new resources are acq
On 29/03/17 13:08, Laurent Pinchart wrote:
> Hi Tomi,
>
> Thank you for the patch.
>
> On Tuesday 28 Mar 2017 16:08:10 Tomi Valkeinen wrote:
>> From: Peter Ujfalusi
>>
>> Keep the panel_list ordered according to aliases. The DRM connectors will
>> be created following the panel_list. By keeping
https://bugs.freedesktop.org/show_bug.cgi?id=100465
Bug ID: 100465
Summary: Hard lockup with radeonsi driver on FirePro W600,
W9000 and W9100
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #1 from Julien Isorce ---
Created attachment 130564
--> https://bugs.freedesktop.org/attachment.cgi?id=130564&action=edit
xorg.log
--
You are receiving this mail because:
You are the assignee for the bug._
Thx for the suggestions.
No, it does not respond to ping.
radeon.dpm=0 does not help. But it only tells to use the old power
management right ?
So I tried: low, mid and high for /sys/class/drm/card0/device/prower_profile
(and setting profile for power_mode)
With radeon.dpm=1 I tried all values f
This is the fouth revision of this series. Note that this series depends on
"drm/atomic: Introduce drm_atomic_helper_shutdown" which has not yet been
merged to drm-next.
The main changes in v4:
- fix missing breaks in "improve DPI clock selection on DRA7xx"
- dropped "fix plane update warning whe
We are working towards enabling omapdss6, which will consists of a new
dss, dispc and dpi drivers. omapdss6 will be a new module. The panel,
encoder and omapdrm will need to use either the current omapdss driver
or the new omapdss6 driver, depending on the platform.
This will be implemented with a
mode_config's min_width and min_height are both set to 32, which is
overly restrictive.
The real limits depend on whether we're configuring a crtc or a plane,
but a limit of 8x2 is safe for both cases.
Signed-off-by: Tomi Valkeinen
Reviewed-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/omap
The current driver doesn't expose any of the CRTC HW properties like
background color or transparency key, and sets them at CRTC enable time.
Refactor this into a separate function and call that function from
omap_crtc_atomic_flush(). This is the behavior we want when the
properties can be configu
DRA7 errata i886 (FPDLink PLL Unlocks With Certain SoC PLL M/N Values)
says that FPDLink is sensitive to jitter on the vout clock, and that low
PLL M and N values result in more jitter than high M and N values.
This patch implements a workaround for the problem by changing the PLL
setup to search
The clock source selection for the LCD outputs is too hardcoded at the
moment. For example, LCD3 is set to use PLL2_1, and PLL2 doesn't exist
on DRA72x SoCs.
There are quite many ways to configure the clocks, even using HDMI PLL
for LCD outputs, but enabling full configuration of the clocks is rat
While implementing writeback support, odd behavior of WBDELAYCOUNT was
observed with the combination of WB capture and HDMI. The result of the
debugging was that the HDMI sync polarities are not set correctly.
The current code sets the sync polarities going from HDMI WP to DISPC
according to the v
We want to change the dispc API from plain functions to a struct with
functions pointers, so that omapdrm can call either omapdss or omapdss6
depending on the platform.
This patch adds 'struct dispc_ops' and adds functions to omapdss-base
to set and get the ops.
Signed-off-by: Tomi Valkeinen
---
omapdss_is_initialized() is used to find out if omapdss has been probed
successfully. This patch moves the related code to the common
omapdss-base module, so that the same support will be there for both
omapdss and omapdss6.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/base.c
The driver only uses even dividers for hsdiv when pclk >= 100MHz, as odd
dividers can create uneven duty cycle. However, while this holds true
for some dividers like DISPC's LCK and PCK dividers, it is not actually
true for hsdiv.
hsdiv always produces even duty cycle, so the constraint can be rem
This patch changes the current omapdss driver to fill a dispc_ops struct
and set it to omapdss-base.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/dispc.c | 40 +
1 file changed, 40 insertions(+)
diff --git a/drivers/gpu/drm/omapdrm/dss/dispc.
omapdrm now uses dispc_ops instead of direct function calls so we can
remove all EXPORT_SYMBOLs from dispc. Most of the functions can also be
made static, but a few are used outside dispc.c.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/dispc.c | 84 +---
This patch moves the common parts of omapdss to omapdss-base so that
both the current omapdss driver and the new omapdss6 driver can use
them.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/Makefile | 6 +++---
drivers/gpu/drm/omapdrm/dss/display.c | 2 --
drivers/gpu/drm/omapdrm
omapdrm still uses a few non-dispc functions: dss_feat_get_num_mgrs(),
dss_feat_get_num_ovls() and dss_feat_get_supported_color_modes(). We
want to provide omapdrm a single dispc_ops function pointer struct so
that omapdrm will use either the current omapdss or the new omapdss6
driver depending on
At the moment VSYNC/HSYNC/DE high/low flags set by the panel/encoder
drivers get lost when the videotimings are translated to DRM's
videomode, as DRM's mode does not have corresponding flags.
DRM has bus-flags for this purpose, and while it lacks a few flags at
the moment, it should be used here.
From: Peter Ujfalusi
The functions can be used to check a component (by it's of_node) if it is
part of the omapdss display or output list. If the component is found, it
means that the driver is loaded.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss
We don't have omapdss's custom error printing functions in the common
omapdss-base module, to which we want to move output.c.
This patch changes output.c to use dev_err instead of DSSERR so that it
doesn't depend on DSSERR.
Signed-off-by: Tomi Valkeinen
Acked-by: Laurent Pinchart
---
drivers/g
Use drm_atomic_helper_shutdown() to ensure that all crtcs are disabled
when unloading the driver.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/omap_drv.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/omapdrm/omap_drv.c
b/drivers/gpu/drm/omapdrm/omap_drv.c
in
From: Hemant Hariyani
Add support for render nodes in omap driver and allow required
ioctls to be accessible via render nodes.
This enables unprivileged clients to allocate resources like GEM buffers
for rendering their content into. Mode setting (KMS ioctls) is not
allowed using render nodes. T
When unloading omapdrm we get a NULL pointer deref in
omap_drm_irq_uninstall(). This is caused by:
967dd48417874dd25491a4e933648f394a64f70f ("drm: remove
drm_vblank_no_hw_counter assignment from driver code")
We shut down all the crtcs at unload time before calling
omap_drm_irq_uninstall, so the
From: Peter Ujfalusi
When the connector associated detect callback is not provided, we can not
detect if the display is connected or disconnected. These displays do not
support hot plug, they are always connected. Let DRM know that connectors
w/o detect callback should not be polled.
Signed-off-
From: Peter Ujfalusi
Instead of 'guessing' based on aliases of the status of the DSS drivers,
use the new interface to check that all needed drivers are loaded.
In this way we can be sure that all needed drivers are loaded so it is
safe to continue the probing of omapdrm.
This method will allow t
From: Peter Ujfalusi
Keep the panel_list ordered according to aliases. The DRM connectors will
be created following the panel_list. By keeping the list ordered the DRM
connectors will be created in the same order regardless of the driver
probe order.
Signed-off-by: Peter Ujfalusi
Signed-off-by:
Change omapdrm to get dispc_ops and use that to call the dispc functions
instead or direct function calls.
The change is very straightforward.
The only problem was in omap_crtc_init() which calls pipe2vbl(crtc), and
at that point of time the crtc->dev link, which is used to get the
dispc_ops, has
DSS uses "replication logic" to convert color components from smaller
bit widths to bigger bit widths. Without replication logic, the color
component would be shifted and the least significant bits would be left
at 0, whereas with replication logic, the least significat bits will be
filled with the
Remove two unused WB functions.
Signed-off-by: Tomi Valkeinen
Reviewed-by: Laurent Pinchart
---
drivers/gpu/drm/omapdrm/dss/dispc.c | 10 --
drivers/gpu/drm/omapdrm/dss/dss.h | 2 --
2 files changed, 12 deletions(-)
diff --git a/drivers/gpu/drm/omapdrm/dss/dispc.c
b/drivers/gpu/drm
From: Peter Ujfalusi
When omapdss is loaded (all core components are in place) create a list of
devices used in the display graph. This list later can be used by omapdrm
via the omapdss_stack_is_ready() function to check that these components
are loaded. Based on this information, omapdrm can def
display.c uses dsi_get_pixel_size() which is implemented in the DSI
driver, and we won't have that in the omapdss-base module, to which we
want to move display.c
This patch changes display.c not to use dsi_get_pixel_size(). The call
can be replaced with a simple check for OMAP_DSS_DSI_FMT_RGB565.
Instead of printing 0/1 for display flags like vsync high/low, use a
tri-state print (-1/0/1) to indicate the "undefined" state.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/dispc.c | 20 +++-
1 file changed, 15 insertions(+), 5 deletions(-)
diff --git a/drivers
From: Peter Ujfalusi
The associated backlight device can be configured via DT by providing the
phandle to the device.
If the backlight device is configured, the driver can manage the backligt
along with the panel's power state, iow it can turn on the backlight when
the panel is enabled and turn
On Wed, Mar 22, 2017 at 09:56:12PM +0100, Daniel Vetter wrote:
> If we restrict this helper to only kms drivers (which is the case) we
> can look up the correct mode easily ourselves. But it's a bit tricky:
>
> - All legacy drivers look at crtc->hwmode. But that is update already
> at the beginn
Hi,
I am trying to add support of new component framework API in ARC PGU driver.
The point is that for now we have ARC PGU driver which works with adv7511
encoder. Both of them don't support component framework API. I had to add
support of component framework based dw_hdmi encoder to ARC PGU dri
https://bugs.freedesktop.org/show_bug.cgi?id=100465
--- Comment #2 from Julien Isorce ---
Created attachment 130569
--> https://bugs.freedesktop.org/attachment.cgi?id=130569&action=edit
Same result with amdgpu using a 4.10 kernel
--
You are receiving this mail because:
You are the assignee fo
On Thu, Mar 30, 2017 at 2:39 AM, Michel Dänzer wrote:
> On 29/03/17 09:55 PM, Christian König wrote:
>> From: Christian König
>>
>> We will probably never see this combination.
>>
>> Signed-off-by: Christian König
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 25 -
Am 30.03.2017 um 15:09 schrieb Alex Deucher:
On Thu, Mar 30, 2017 at 2:39 AM, Michel Dänzer wrote:
On 29/03/17 09:55 PM, Christian König wrote:
From: Christian König
We will probably never see this combination.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c |
On Thu, Mar 30, 2017 at 2:03 PM, Ville Syrjälä
wrote:
> On Wed, Mar 22, 2017 at 09:56:12PM +0100, Daniel Vetter wrote:
>> If we restrict this helper to only kms drivers (which is the case) we
>> can look up the correct mode easily ourselves. But it's a bit tricky:
>>
>> - All legacy drivers look a
I'm getting real lazy, let's start scripting this. Very rough draft,
but adds a Link: (patchwork tracks pull requests too, maybe we'll
start CI-ing them too), and sob line. In the future we might add more
checks here ...
Signed-off-by: Daniel Vetter
---
dim | 34 +
With the explicit retry loop static analyzers get confused by the
control flow and believe that e could be accessed after kfree. That's
not possible, but it's non-obvious, so let's clear it to NULL.
We already cleared e = NULL at the top of the function, so this is all
in line.
Cc: Julia Lawall
On Thu, Mar 30, 2017 at 03:27:57PM +0200, Daniel Vetter wrote:
> On Thu, Mar 30, 2017 at 2:03 PM, Ville Syrjälä
> wrote:
> > On Wed, Mar 22, 2017 at 09:56:12PM +0100, Daniel Vetter wrote:
> >> If we restrict this helper to only kms drivers (which is the case) we
> >> can look up the correct mode e
ARM v6 (at least) only allows cmpxchg on 32bit variables which doesn't
always include the bool type.
drivers/built-in.o: In function `vblank_disable_and_save':
imx-ocotp.c:(.text+0xb45e8): undefined reference to `__bad_cmpxchg'
Makefile:986: recipe for target 'vmlinux' failed
Reported-by: kbuild
On Thu, Mar 30, 2017 at 03:08:32PM +0100, Chris Wilson wrote:
> ARM v6 (at least) only allows cmpxchg on 32bit variables which doesn't
> always include the bool type.
>
> drivers/built-in.o: In function `vblank_disable_and_save':
> imx-ocotp.c:(.text+0xb45e8): undefined reference to `__bad_cmpxchg
https://bugs.freedesktop.org/show_bug.cgi?id=100395
--- Comment #6 from Harry Wentland ---
Thanks, Andy, for the report and taking the time to bisect.
Jordan from my team spotted the bug as well and is working on a solution.
If you're curious about the cause of this... The gist of it is that we
On Thu, Mar 30, 2017 at 02:00:08PM +0800, Jason Wang wrote:
>
>
> On 2017年03月30日 04:48, Michael S. Tsirkin wrote:
> > We are going to add more parameters to find_vqs, let's wrap the call so
> > we don't need to tweak all drivers every time.
> >
> > Signed-off-by: Michael S. Tsirkin
> > ---
>
>
Reviewed-by: Harry Wentland
On 2017-03-30 09:32 AM, Daniel Vetter wrote:
With the explicit retry loop static analyzers get confused by the
control flow and believe that e could be accessed after kfree. That's
not possible, but it's non-obvious, so let's clear it to NULL.
We already cleared e =
Accidentally removed with earlier commit. Although rather than simply
adding the check for all platforms, use the same heuristics as we do in
mesa.
Namely: pthread-stubs is a thing only for BSD platforms. Everyone else
should have lightweight pthread API in their C runtime library.
Fixes: 4ecd1ef
On Thu, Mar 30, 2017 at 10:26:24AM -0400, Harry Wentland wrote:
> Reviewed-by: Harry Wentland
Thanks for the quick review, pushed to drm-misc.
-Daniel
>
> On 2017-03-30 09:32 AM, Daniel Vetter wrote:
> > With the explicit retry loop static analyzers get confused by the
> > control flow and beli
On Thu, Mar 30, 2017 at 04:41:57PM +0300, Ville Syrjälä wrote:
> On Thu, Mar 30, 2017 at 03:27:57PM +0200, Daniel Vetter wrote:
> > On Thu, Mar 30, 2017 at 2:03 PM, Ville Syrjälä
> > wrote:
> > > On Wed, Mar 22, 2017 at 09:56:12PM +0100, Daniel Vetter wrote:
> > >> If we restrict this helper to on
On Wed, Mar 29, 2017 at 4:09 PM, Mario Kleiner
wrote:
> At dot clocks > approx. 250 Mhz, some of these calcs will overflow and
> cause miscalculation of latency watermarks, and for some overflows also
> divide-by-zero driver crash ("divide error: [#1] PREEMPT SMP" in
> "dce_v10_0_latency_wate
We'd like to reuse these register definitions for the DRM CLCD driver,
but there's a bunch of fbdev-specific code in the current header.
Signed-off-by: Eric Anholt
---
include/linux/amba/clcd-regs.h | 76 ++
include/linux/amba/clcd.h | 68 +---
From: Tom Cooksey
This is a modesetting driver for the pl111 CLCD display controller
found on various ARM platforms such as the Versatile Express. The
driver has only been tested on the bcm911360_entphn platform so far,
with PRIME-based buffer sharing between vc4 and clcd.
It reuses the existing
We want to lock the primary plane, not the cursor (which might be
optional). Real bad case of copy-paste fail, unfortunately our CI
didn't catch that because i915 does have a cursor plane.
Cc: Eric Anholt
Reported-by: Eric Anholt
Fixes: 29dc0d1de182 ("drm: Roll out acquire context for the page_f
Reviewed-by: Harry Wentland
Harry
On 2017-03-30 04:48 PM, Daniel Vetter wrote:
We want to lock the primary plane, not the cursor (which might be
optional). Real bad case of copy-paste fail, unfortunately our CI
didn't catch that because i915 does have a cursor plane.
Cc: Eric Anholt
Reporte
Eric Anholt writes:
> From: Tom Cooksey
>
> This is a modesetting driver for the pl111 CLCD display controller
> found on various ARM platforms such as the Versatile Express. The
> driver has only been tested on the bcm911360_entphn platform so far,
> with PRIME-based buffer sharing between vc4
Hi Jyri,
Thank you for the patch.
On Friday 24 Mar 2017 16:47:51 Jyri Sarha wrote:
> Allocate one CRTC for each connected output and get rid of
> DRM_OMAP_NUM_CRTCS config option. We still can not create more CRTCs
> than we have DSS display managers. We also reserve one overlay per
> CRTC for pr
Hi Dave,
New stuff for 4.12:
- Preliminary vega10 support
- Support for multi-level page tables
- GPU sensor stuff for mesa
- job tracing improvements
- PRT support for sparse buffers
- Additional SR-IOV improvements
- ttm improvements
- misc bug fixes and code cleanups
The following changes sinc
Hi Jyri,
On Friday 24 Mar 2017 16:47:52 Jyri Sarha wrote:
> The enum omap_plane conflicted with the same struct name for omapdrm
> plane private data. This rename should solve the conflict.
>
> The rename was implement with this very simple coccinelle patch:
>
> @@
> @@
>
Hi Jyri,
Thank you for the patch.
On Friday 24 Mar 2017 16:47:53 Jyri Sarha wrote:
> Fix one ugly indentation style break left by the previous coccilnelle
> patch.
>
> Signed-off-by: Jyri Sarha
Acked-by: Laurent Pinchart
> ---
> drivers/gpu/drm/omapdrm/dss/dispc.c | 5 ++---
> 1 file change
Hi Jyri,
Thank you for the patch.
On Friday 24 Mar 2017 16:47:54 Jyri Sarha wrote:
> Remove the obsolete "#define omap_plane _omap_plane" hack and other
> related hacks to get around the enum omap_plane colliding with struct
> omap_plane.
>
> Signed-off-by: Jyri Sarha
Reviewed-by: Laurent Pinc
Hi Jyri,
Thank you for the patch.
On Friday 24 Mar 2017 16:47:56 Jyri Sarha wrote:
> Implement CTM color management property for OMAP CRTC using DSS
> overlay manager's Color Phase Rotation matrix. The CPR matrix does not
> exactly match the CTM property documentation. On DSS the CPR matrix is
>
On Thursday, 2017-03-30 18:01:12 +0100, Emil Velikov wrote:
> Accidentally removed with earlier commit. Although rather than simply
> adding the check for all platforms, use the same heuristics as we do in
> mesa.
>
> Namely: pthread-stubs is a thing only for BSD platforms. Everyone else
> should
From: Tom Cooksey
This is a modesetting driver for the pl111 CLCD display controller
found on various ARM platforms such as the Versatile Express. The
driver has only been tested on the bcm911360_entphn platform so far,
with PRIME-based buffer sharing between vc4 and clcd.
It reuses the existing
We'd like to reuse these register definitions for the DRM CLCD driver,
but there's a bunch of fbdev-specific code in the current header.
Signed-off-by: Eric Anholt
---
include/linux/amba/clcd-regs.h | 76 ++
include/linux/amba/clcd.h | 68 +---
Martin Peres writes:
> On 26/01/17 14:37, Martin Peres wrote:
>> Despite all the careful planing of the kernel, a link may become
>> insufficient to handle the currently-set mode. At this point, the
>> kernel should mark this particular configuration as being broken
>> and potentially prune the m
Daniel Vetter writes:
> On Tue, Mar 28, 2017 at 01:13:43PM -0700, Eric Anholt wrote:
>> Without this, the first modeset would dereference past the allocation
>> when trying to free the mm node.
>>
>> Signed-off-by: Eric Anholt
>> Tested-by: Stefan Wahren
> Fixes: d8dbf44f13b9 ("drm/vc4: Make t
On Thu, Mar 30, 2017 at 05:37:55PM -0700, Eric Anholt wrote:
> Martin Peres writes:
>
> > On 26/01/17 14:37, Martin Peres wrote:
> >> Despite all the careful planing of the kernel, a link may become
> >> insufficient to handle the currently-set mode. At this point, the
> >> kernel should mark thi
On 30/03/17 10:09 PM, Alex Deucher wrote:
> On Thu, Mar 30, 2017 at 2:39 AM, Michel Dänzer wrote:
>> On 29/03/17 09:55 PM, Christian König wrote:
>>> From: Christian König
>>>
>>> We will probably never see this combination.
>>>
>>> Signed-off-by: Christian König
>>> ---
>>> drivers/gpu/drm/amd
1 - 100 of 143 matches
Mail list logo
