On Wed, Mar 22, 2017 at 11:03:41PM +, Russell King - ARM Linux wrote:
> On Wed, Mar 22, 2017 at 10:50:41PM +0100, Daniel Vetter wrote:
> > diff --git a/drivers/gpu/drm/armada/armada_overlay.c
> > b/drivers/gpu/drm/armada/armada_overlay.c
> > index 34cb73d0db77..b54fd8cbd3a6 100644
> > --- a/dr
On 23/03/17 19:04, Tony Lindgren wrote:
> Looks like in Linux next we can now get an oops when unloading omapdrm:
>
> Unable to handle kernel NULL pointer dereference at virtual address
>
> ...
> LR is at omap_drm_irq_uninstall+0xb0/0xe0 [omapdrm]
> ...
> [] (omap_drm_irq_uninstall [omapd
On Fri, Mar 24, 2017 at 12:31 AM, Russell King - ARM Linux
wrote:
> On Thu, Mar 23, 2017 at 10:54:53PM +0100, Linus Walleij wrote:
>> Hm, I certainly want it... but it would be unreasonable of me to expect
>> Eric to cold-code a big upfront design for systems he can't even test
>> this on.
>>
>> W
On Wed, Mar 22, 2017 at 09:54:01PM +0100, Daniel Vetter wrote:
> I've decided to not document drm_debugfs_remove_files, it's on the way
> out.
>
> The biggest part is a huge todo.rst entry with what all should be
> improved.
>
> v2: Nits from Gabriel.
>
> Cc: Gabriel Krisman Bertazi
> Reviewed-
On 23/03/17 06:26 PM, Julien Isorce wrote:
> Hi Michel,
>
> When it happens, the main thread of our gl based app is stuck on a
> ioctl(RADEON_CS). I set RADEON_THREAD=false to ease the debugging but
> same thing happens if true. Other threads are only si_shader:0,1,2,3 and
> are doing nothing, jus
From: Peter Ujfalusi
Do not try to init the fbdev if either num_crtcs or num_connectors is 0.
In this case we do not have display so the fbdev init would fail anyways.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/omap_fbdev.c | 3 +++
1 file changed,
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
---
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
---
drivers/gpu/drm/omapdrm/dss/output.c
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
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.
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
---
drivers/gpu/drm/omapdrm/omap_drv.c | 4 ++--
1 file changed
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
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
Remove two unused WB functions.
Signed-off-by: Tomi Valkeinen
---
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/omapdrm/dss/dispc.c
index 7104
Hi,
This is an update of the "drm/omap: miscallaneous improvements" series I sent
last Nov. I have dropped some patches, and added one fix, but otherwise the
contents are the same. The main changes in v2:
- Interrupt based HPD removed, as there's a race issue which needs to be fixed
- Added patc
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
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
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
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 +---
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
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
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
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
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
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
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:
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.
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
From: Peter Ujfalusi
Add fbdev emulation only for the first DRM connector.
When the fbdev emulation was created for all connectors with different
resolution, the lower res display would only be able to show part of the
framebuffer.
By creating the fbdev emulation only for the first connector we c
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 error: cannot calculate scaling settings: pclk is zero
omapdrm omapdrm.0: Failed to setup plane vid2
It shouldn't cause any issues, as the crtc is disabled s
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
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
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")
As OMAP DSS does not have a HW vblank counter, vblank[i].last is anyway
always 0, so we
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 does not
support hot plug, they are always connected. Let DRM know that connectors
w/o detect callback should not be polled.
Signed-of
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.
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
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
On 22/03/17 23:50, Daniel Vetter wrote:
> Again this is an internal helper, not the official way to lock a crtc.
>
> Cc: Jyri Sarha
> Cc: Tomi Valkeinen
> Signed-off-by: Daniel Vetter
> ---
> drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions
Hi Michel,
(Just for other readers my reply has been delayed on the mailing lists and
should have been on second position)
We have actually spotted this /0/i/ but somehow I convinced myself it was
intentional. The reason I found was that you wanted to set the fpfn only if
there is 2 placements, w
On 24/03/17 06:50 PM, Julien Isorce wrote:
> Hi Michel,
>
> (Just for other readers my reply has been delayed on the mailing lists
> and should have been on second position)
It is on https://patchwork.freedesktop.org/patch/145731/ , did you mean
something else?
The delay was because you weren't
On 24/03/17 12:31 AM, Zachary Michaels wrote:
>
> I should also note that we are experiencing another issue where the
> kernel locks up in similar circumstances. As Julien noted, we get no
> output, and the watchdogs don't seem to work. It may be the case that
> Xorg and our process are calling tt
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #26 from intermedi...@hotmail.com ---
Need to notice the issue now is present on 8x slot too on kernel 4.11 rc3
--
You are receiving this mail because:
You are the assignee for the bug.___
On Tue, Mar 21, 2017 at 06:18:44PM +0100, Philipp Zabel wrote:
> Hi Martyn,
>
> On Tue, 2017-03-21 at 09:50 +, Martyn Welch wrote:
> > I have an i.MX6 platform with 2 display port interfaces, one driven by the
> > HDMI interface, the other by LVDS, both via bridges. We are currently
> > experi
https://bugs.freedesktop.org/show_bug.cgi?id=100375
Bug ID: 100375
Summary: forced EDID's can cause a amdgpu to null ptr deref
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity
https://bugzilla.kernel.org/show_bug.cgi?id=86351
--- Comment #27 from Gerion (gerion-ker...@flump.de) ---
I've experienced a little more with CPU load and it seems, that not the CPU
load is the essential part, but the memory access.
To be concrete:
stress -m 1
is enough to let the sound play nor
On Fri, 2017-03-24 at 10:24 +, Martyn Welch wrote:
[...]
> > Could you move to v4.9 or v4.10 and check if the four patches in
> > https://git.pengutronix.de/cgit/pza/linux/tag/?id=v4.9-ipu-dp-plane-fix
> > or
> > https://git.pengutronix.de/cgit/pza/linux/tag/?id=v4.10-ipu-dp-plane-fix-2
> > hel
https://bugzilla.kernel.org/show_bug.cgi?id=86351
--- Comment #28 from Andy Furniss (adf.li...@gmail.com) ---
Yea, I fount that you need io load, I use mprime - but not the test that just
stresses cpu...
Of course using pulse, as most people do, avoids the bug as it uses sound
different from alsa
On 03/22/17 23:50, Daniel Vetter wrote:
> Again this is an internal helper, not the official way to lock a crtc.
>
> Cc: Jyri Sarha
> Cc: Tomi Valkeinen
> Signed-off-by: Daniel Vetter
Acked-by: Jyri Sarha
> ---
> drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 12 ++--
> 1 file changed, 6 in
Hi Jose,
On 24 March 2017 at 14:03, Jose Fonseca wrote:
> On 22/03/17 20:57, Dylan Baker wrote:
>> Cross compiling for mingw is supported, and it provides a way to
>> differentiate
>> the build, host, and target machines [1], I've cross compiled for
>> aarch64-linux-gnu, and it was trivial (I've
Mali DP needs to have all the planes that are becoming inactive in the
new state disabled before re-enabling the active CRTC, otherwise we
start streaming out data from old pointers in memory.
Signed-off-by: Liviu Dudau
Reviewed-by: Brian Starkey
---
drivers/gpu/drm/arm/malidp_drv.c | 12 ++
Enable runtime and system Power Management. Clocks are now managed
from malidp_crtc_{enable,disable} functions. Suspend-to-RAM tested
as working on Juno.
Signed-off-by: Liviu Dudau
Reviewed-by: Brian Starkey
---
drivers/gpu/drm/arm/malidp_crtc.c | 14 -
drivers/gpu/drm/arm/malidp_drv.c |
The first patch removes CONFIG_DRM_OMAP_NUM_CRTCS config option. The
patches number 2-4 gets rid of annoying name collision between dss
backend and omapdrm. The second last patch cleans up the unnecessary
complexity from omap_modeset_init(). And finally the last implements
CRTC's CTM matrix propety
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 primary plane so we can not have more CRTCs than we have
overlays either.
Signed-off-by: Jyri
Cleanup overly complex omap_modeset_init(). The function is trying to
support many unusual configuration, that have never been tested and
are not supported by other parts of the dirver.
After cleanup the init function creates exactly one connector,
encoder, crtc, and primary plane per each connect
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:
@@
@@
enum
-omap_plane
+omap_plane_id
The patch was app
Fix one ugly indentation style break left by the previous coccilnelle
patch.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/omapdrm/dss/dispc.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/omapdrm/dss/dispc.c
b/drivers/gpu/drm/omapdrm/dss/dispc.c
index
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
---
drivers/gpu/drm/omapdrm/omap_plane.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/driv
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
applied before gamma table look up. However, it seems stupid to add a
custom property just fo
On 24/03/17 16:29, Tony Lindgren wrote:
> * Sebastian Reichel [170304 16:45]:
>> Add basic panel support for the Nokia N950. It must be tweaked a
>> little bit later, since the panel was built into the device
>> upside-down. Also the first 5 and the last 5 pixels are covered
>> by plastic.
>
> Th
On 24/03/17 17:12, Tony Lindgren wrote:
> * Tomi Valkeinen [170324 08:01]:
>> On 24/03/17 16:29, Tony Lindgren wrote:
>>> * Sebastian Reichel [170304 16:45]:
Add basic panel support for the Nokia N950. It must be tweaked a
little bit later, since the panel was built into the device
In vmw_surface_define_ioctl(), a num_sizes parameter is assigned a
user-controlled value which is not checked for zero. It is used in
a call to kmalloc() which returns ZERO_SIZE_PTR. Later ZERO_SIZE_PTR
is dereferenced which leads to a GPF and possibly to a kernel panic.
Add the check for zero to a
On Mon, Mar 20, 2017 at 02:32:22PM +0100, Richard Genoud wrote:
> This adds support for the Winstar Display Co. WF35LTIACD 3.5" QVGA TFT
> LCD panel, which can be supported by the simple panel driver.
>
> Signed-off-by: Richard Genoud
> ---
>
> Changes since v1:
> Add power-supply property and a
https://bugs.freedesktop.org/show_bug.cgi?id=100067
--- Comment #7 from Mig ---
Backtrace:
(gdb) run
Starting program:
/home/miguel/Dokumente/OpenCLExamples/myGEMM-master/extra/minimal
>>> Initializing OpenCL...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr
https://bugs.freedesktop.org/show_bug.cgi?id=100067
--- Comment #8 from Mig ---
BTW:
I applied the patch from bug 99856 to clc but apparently the bug described
above is not related to that.
--
You are receiving this mail because:
You are the assignee for the bug.___
> Another tool I heard good about but have not direct experience is
> https://bazel.build . Any thoughts about it?
Having looked a bit into it, it also is just a build system (albeit
higher level than ninja or make). It doesn't do configure or install
and working with system dependencies is annoy
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #27 from Alex Deucher ---
(In reply to intermedi...@hotmail.com from comment #26)
> Need to notice the issue now is present on 8x slot too on kernel 4.11 rc3
Can you bisect? That might give us a clue as to the overall root cause
(wh
Quoting Colin Cross (2017-03-23 17:03:58)
> On Thu, Mar 23, 2017 at 4:56 PM, Dylan Baker wrote:
> >
> > I'm hoping you can clarify a couple of questions I have about blueprint:
> > 1) android is moving to blueprint from android.mk files?
>
> Yes, in a phased transition. We support both for now.
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #28 from intermedi...@hotmail.com ---
I can but i dont know how to ... im a newbee in this geek things.
but for sure of 411.rc1 was not present . i suggest wait the 4.11.rc4 because
on ml i sow there are many patch for rc 4.11rc3 in c
On Mon, 20 Mar 2017, Matt Turner wrote:
- dropping the Autotools will lead to OpenBSD and NetBSD having to
write one from scratch, IIRC Solaris/FreeBSD and others are in similar
boat.
Solaris is a closed source operating system whose developers do not
contribute to the project. We do not
Quoting Jose Fonseca (2017-03-24 06:42:18)
>
> I tend to disagree. While we can't avoid a transitory period, when we
> embark on another build system (Meson or something else) I think we
> should aim at 1) ensure such tool can indeed _completely_ replace at
> least _one_ existing build system,
On Fri, Mar 24, 2017 at 04:16:28AM +0100, Mario Kleiner wrote:
> Looks good to me. As a further optimization, i think we could move
> the vblank_disable_fn() call outside/below the
> spin_unlock_irqrestore for event_lock, as vblank_disable_fn()
> doesn't need any locks held at call time, so slightl
We want to provide the vblank irq shadow for pageflip events as well as
vblank queries. Such events are completed within the vblank interrupt
handler, and so the current check for disabling the irq will disable it
from with the same interrupt as the last pageflip event. If we move the
decision on w
Dylan Baker writes:
> [ Unknown signature status ]
> Quoting Jose Fonseca (2017-03-24 06:42:18)
>>
>> I tend to disagree. While we can't avoid a transitory period, when we
>> embark on another build system (Meson or something else) I think we
>> should aim at 1) ensure such tool can indeed _c
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #29 from Alex Deucher ---
(In reply to intermedi...@hotmail.com from comment #28)
> I can but i dont know how to ... im a newbee in this geek things.
> but for sure of 411.rc1 was not present . i suggest wait the 4.11.rc4
> because on
https://bugs.freedesktop.org/show_bug.cgi?id=100364
--- Comment #2 from Alex Deucher ---
Do you physically turn the monitor on/off with the button on the monitor or
just let dpms do it's thing?
--
You are receiving this mail because:
You are the assignee for the bug.
On Wed, Mar 22, 2017 at 09:54:49AM +0800, Chris Zhong wrote:
> For RK3399, the grf clock should be controlled by dw-mipi-dsi driver,
> add the description for this clock.
>
> Signed-off-by: Chris Zhong
> Reviewed-by: Sean Paul
> ---
>
> Changes in v4:
> - remove "additional"
>
> Changes in v3:
Hi,
On 24 March 2017 at 17:51, Eric Anholt wrote:
> Dylan Baker writes:
>> I also think it's worth talking to Eric (who said he's porting X to meson),
>> Daniel Stone (who has patches to port weston to meson), and Peter Hutterer
>> (who
>> has patches to port libinput to meson). If they're seri
https://bugzilla.kernel.org/show_bug.cgi?id=193981
--- Comment #12 from winches (dry...@gmx.fr) ---
I start to bisect.
My problem is, between the linux-git-4.8.r15051.g133d970e0dad and the
linux-git-4.9rc5.r369.g697ed8d03909 my system doesn't found my harddrive with
his UUID and refuse to boot. It
https://bugs.freedesktop.org/show_bug.cgi?id=100289
--- Comment #7 from omegap...@startmail.com ---
Just turned the monitors on in sequence left to right after dinner (new monitor
is last), and the problem occurred:
$ x
Hi Michel,
I double checked and you are right, the change 0 -> i works.
Cheers
Julien
On 24 March 2017 at 09:59, Michel Dänzer wrote:
> On 24/03/17 06:50 PM, Julien Isorce wrote:
> > Hi Michel,
> >
> > (Just for other readers my reply has been delayed on the mailing lists
> > and should have b
Hi Michel,
No this change does not help on the other issue (hard lockup).
I have no tried it in combination with the 0 -> i change.
Thx anyway.
Julien
On 24 March 2017 at 10:03, Michel Dänzer wrote:
> On 24/03/17 12:31 AM, Zachary Michaels wrote:
> >
> > I should also note that we are experie
On Mon, Mar 13, 2017 at 12:24 PM, Shashank Sharma
wrote:
> +/**
> + * struct drm_hdmi_info - runtime information about the connected HDMI sink
> + *
> + * Describes if a given display supports advanced HDMI 2.0 features.
> + * This information is available in CEA-861-F extension blocks (like
> HF
On Fri, Mar 24, 2017 at 6:42 AM, Jose Fonseca wrote:
> On 23/03/17 01:38, Rob Clark wrote:
>>
>> On Wed, Mar 22, 2017 at 9:18 PM, Jonathan Gray wrote:
>>>
>>> On Wed, Mar 22, 2017 at 01:10:14PM -0700, Dylan Baker wrote:
On Wed, Mar 22, 2017 at 12:40 PM, Alex Deucher
wrote:
>
>
On Wed, Mar 22, 2017 at 11:21:20AM +0800, Jeffy Chen wrote:
> Currently we are adding all components from the dts, if one of their
> drivers been disabled, we would not be able to bring up others.
>
> Refactor component match logic, follow exynos drm.
Applied to drm-misc
Thanks,
Sean
>
> Sign
On Wed, Mar 22, 2017 at 09:54:47AM +0800, Chris Zhong wrote:
> Hi all
>
> This series set the phy_cfg_clk to be a required clock for RK3399, and
> add a grf clock control in dw-mipi-dsi driver. And then correct a
> register name.
>
Applied to drm-misc
Thanks,
Sean
>
> Changes in v4:
> - rem
https://bugs.freedesktop.org/show_bug.cgi?id=100364
--- Comment #3 from John Brooks ---
(In reply to Alex Deucher from comment #2)
> Do you physically turn the monitor on/off with the button on the monitor or
> just let dpms do it's thing?
I'm turning it on and off with the button. I seem to rec
https://bugs.freedesktop.org/show_bug.cgi?id=100364
--- Comment #4 from John Brooks ---
It's possible that I just didn't leave it alone for long enough after it turned
off (or after I turned it off with xset dpms force off). Maybe after a period
of time with no signal, the monitor itself goes int
https://bugs.freedesktop.org/show_bug.cgi?id=100364
--- Comment #6 from John Brooks ---
Created attachment 130441
--> https://bugs.freedesktop.org/attachment.cgi?id=130441&action=edit
Xorg.log
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=100364
--- Comment #5 from John Brooks ---
Created attachment 130440
--> https://bugs.freedesktop.org/attachment.cgi?id=130440&action=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the bug.__
On Fri, Mar 24, 2017 at 12:44 PM, Jose Fonseca wrote:
> On 24/03/17 19:10, Kristian Høgsberg wrote:
>>
>> On Fri, Mar 24, 2017 at 6:42 AM, Jose Fonseca wrote:
>>>
>>> On 23/03/17 01:38, Rob Clark wrote:
On Wed, Mar 22, 2017 at 9:18 PM, Jonathan Gray wrote:
>
>
> On Wed
On Tue 21 Mar 2017, Matt Turner wrote:
> On Mon, Mar 20, 2017 at 12:39 PM, Emil Velikov
> wrote:
> > On 20 March 2017 at 18:30, Matt Turner wrote:
> >> On Mon, Mar 20, 2017 at 6:55 AM, Emil Velikov
> >> wrote:
> >>> These projects have been getting closer to upstream and "forcing" the
> >>> e
On Tue 21 Mar 2017, Matt Turner wrote:
> On Tue, Mar 21, 2017 at 10:16 AM, Emil Velikov
> wrote:
> > On 21 March 2017 at 15:57, Matt Turner wrote:
> >> On Mon, Mar 20, 2017 at 12:39 PM, Emil Velikov
> >> wrote:
> >>> On 20 March 2017 at 18:30, Matt Turner wrote:
> On Mon, Mar 20, 2017 at
On Fri, Mar 24, 2017 at 3:10 PM, Kristian Høgsberg wrote:
> On Fri, Mar 24, 2017 at 6:42 AM, Jose Fonseca wrote:
>> On 23/03/17 01:38, Rob Clark wrote:
>>>
>>> On Wed, Mar 22, 2017 at 9:18 PM, Jonathan Gray wrote:
On Wed, Mar 22, 2017 at 01:10:14PM -0700, Dylan Baker wrote:
>
>
drivers/gpu/drm/nouveau/nouveau_display.c:154:8-9: WARNING: return of 0/1 in
function 'nouveau_display_scanoutpos' with return type bool
Return statements in functions returning bool should use
true/false instead of 1/0.
Generated by: scripts/coccinelle/misc/boolreturn.cocci
CC: Daniel Vetter
Hi Daniel,
[auto build test WARNING on drm/drm-next]
[cannot apply to v4.11-rc3 next-20170324]
[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/linux/commits/Daniel-Vetter/more-drmP-h-cleanup/20170325-030940
Originally based off of a patch by Kristian.
This new ioctl extends DRM_IOCTL_MODE_GETPLANE, by returning information
about the modifiers that will work with each format.
It's modified from Kristian's patch in that the modifiers and formats
are setup by the driver, and then a callback is used to
This was based on a patch originally by Kristian. It has been modified
pretty heavily to use the new callbacks from the previous patch.
v2:
- Add LINEAR and Yf modifiers to list (Ville)
- Combine i8xx and i965 into one list of formats (Ville)
- Allow 1010102 formats for Y/Yf tiled (Ville)
v
They're the same, so use the one which makes more sense.
Signed-off-by: Ben Widawsky
---
drivers/gpu/drm/i915/intel_display.c | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_display.c
b/drivers/gpu/drm/i915/intel_disp
On Fri, Mar 24, 2017 at 5:16 PM, Jose Fonseca wrote:
> On 24/03/17 20:08, Kristian Høgsberg wrote:
>>
>> On Fri, Mar 24, 2017 at 12:44 PM, Jose Fonseca
>> wrote:
>>>
>>> On 24/03/17 19:10, Kristian Høgsberg wrote:
On Fri, Mar 24, 2017 at 6:42 AM, Jose Fonseca
wrote:
>
>>>
Hi Daniel,
[auto build test WARNING on drm/drm-next]
[cannot apply to v4.11-rc3 next-20170324]
[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/linux/commits/Daniel-Vetter/more-drmP-h-cleanup/20170325-030940
1 - 100 of 119 matches
Mail list logo
