On Sun, Jan 20, 2019 at 06:12:17PM +0100, Sam Ravnborg wrote:
> Reversed logic when writing the original comment, now fixed.
>
> Fixes: e9eafcb58921 ("drm: move drm_can_sleep() to drm_util.h")
> Reported-by: Laurent Pinchart
> Signed-off-by: Sam Ravnborg
> Cc: Laurent Pinchart
> Cc: Maarten
On Fri, Jan 18, 2019 at 05:22:58PM +0100, Geert Uytterhoeven wrote:
> Since its incarnation in v3.7 almost 7 years ago, no users of the SH
> Mobile DRM driver have appeared.
>
> Hence remove the driver. It can be resurrected from git history,
> if/when needed.
>
> Signed-off-by: Geert
We have a wrapper for a reason.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/drm_dp_helper.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/drm_dp_helper.c b/drivers/gpu/drm/drm_dp_helper.c
index 26835d174939..4def0bface85 100644
---
https://bugs.freedesktop.org/show_bug.cgi?id=109384
Michel Dänzer changed:
What|Removed |Added
CC||harry.wentl...@amd.com,
Hi Noralf.
On Sun, Jan 20, 2019 at 12:43:07PM +0100, Noralf Trønnes wrote:
> This patchset is part of the effort to remove tinydrm.ko. It removes
> struct tinydrm_device and tinydrm.h.
>
> While doing this refactoring I have ensured that device unplug is
> working.
Very nice series, it looks
Heavily based on the Armada 510 (Dove) support. Like with 510 support, this
also just supports a single source clock -- the "Display 1" clock as
generated by the APMU. This one was chosen because the OLPC XO 1.75 laptop
uses it for its internal panel.
If anyone uses this to drive a MIPI or HDMI
It's going to document more than just marvell,dove-lcd: more components
of the display subsystems with more compatible strings.
It seems to make sense to organize this the way it is done in
Documentation/devicetree/bindings/display/imx/fsl-imx-drm.txt
Signed-off-by: Lubomir Rintel
---
There are also 1280x800 versions of the Ideapad D330. I don't know the
dmi strings for the lower versions, but they could be equal between
versions of the same model.
Could be possible to add orientation_data matrix elements with the
same dmi strings and different driver data to complain both
The Marvell Armada DRM master device is a virtual device needed to list all
nodes that comprise the graphics subsystem.
Signed-off-by: Lubomir Rintel
---
.../display/armada/marvell-armada-drm.txt | 24 +++
1 file changed, 24 insertions(+)
diff --git
This makes it possible to choose a different pixel format for the
endpoint. Modelled after what other LCD controllers use, including
marvell,pxa2xx-lcdc and atmel,hlcdc-display-controller and perhaps more.
Signed-off-by: Lubomir Rintel
---
.../bindings/display/armada/marvell-armada-drm.txt
Hi,
this patch set extends the bindings documentation of Armada LCDC to
cover the rest of the display subsystem.
It is based on what was implemented by Russel's patch set that
implements the dt bindings for armada-drm [1].
[1]
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/gpu/drm/stm/ltdc.c: In function 'ltdc_plane_atomic_check':
drivers/gpu/drm/stm/ltdc.c:694:13: warning:
variable 'src_y' set but not used [-Wunused-but-set-variable]
u32 src_x, src_y, src_w, src_h;
^
^
On Fri, Jan 18, 2019 at 10:51:10PM +0100, Jernej Škrabec wrote:
> Dne četrtek, 17. januar 2019 ob 08:24:02 CET je Priit Laes napisal(a):
> > On Wed, Jan 16, 2019 at 06:00:32PM +0100, Jernej Škrabec wrote:
> > > Dne sreda, 16. januar 2019 ob 13:09:58 CET je Priit Laes napisal(a):
> > > > On Thu,
On Fri, Jan 18, 2019 at 11:11:38PM +, Peter Rosin wrote:
> The gpio API explicitly allows skipping the NULL check, precisely to
> allow for neat support for optional gpios. Which is exactly what is at
> play here.
>
> Reported-by: Andrzej Hajda
> Signed-off-by: Peter Rosin
lgtm,
On Sun, Jan 20, 2019 at 12:43:16PM +0100, Noralf Trønnes wrote:
> No more users left so it can go alongside its helpers.
> Update the tinydrm docs description and remove todo entry.
>
> Signed-off-by: Noralf Trønnes
> ---
> Documentation/gpu/tinydrm.rst | 26 +--
>
Hi,
On 15-01-19 15:55, Ville Syrjälä wrote:
On Sat, Dec 01, 2018 at 12:31:46PM +0100, Hans de Goede wrote:
The display engine has 2 dithering enable bits which both need to be set
for dithering to happen, 1 in the PIPECONF register which is taken care of
by i9xx_set_pipeconf() and a second bit
Le lun. 21 janv. 2019 à 09:21, YueHaibing a écrit :
>
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/gpu/drm/stm/ltdc.c: In function 'ltdc_plane_atomic_check':
> drivers/gpu/drm/stm/ltdc.c:694:13: warning:
> variable 'src_y' set but not used [-Wunused-but-set-variable]
> u32
On Sun, Jan 20, 2019 at 12:43:08PM +0100, Noralf Trønnes wrote:
> This adds resource managed (devres) versions of drm_dev_init() and
> drm_dev_register().
>
> Also added is devm_drm_dev_register_with_fbdev() which sets up generic
> fbdev emulation as well.
>
> devm_drm_dev_register() isn't
On Fri, 18 Jan 2019, "Kristian H. Kristensen" wrote:
> Otherwise we get hard to track down "Purging: 123123 bytes" messages in
> the log.
>
> Signed-off-by: Kristian H. Kristensen
> ---
> drivers/gpu/drm/msm/msm_gem_shrinker.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff
On Mon, Jan 21, 2019 at 11:03:44AM +0100, Geert Uytterhoeven wrote:
> Hi Daniel,
>
> On Mon, Jan 21, 2019 at 10:35 AM Daniel Vetter wrote:
> > On Fri, Jan 18, 2019 at 05:22:58PM +0100, Geert Uytterhoeven wrote:
> > > Since its incarnation in v3.7 almost 7 years ago, no users of the SH
> > >
The driver will work on a MMP2 as well.
Signed-off-by: Lubomir Rintel
---
.../bindings/display/armada/marvell-armada-drm.txt | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git
a/Documentation/devicetree/bindings/display/armada/marvell-armada-drm.txt
This is the binding for memory that is set aside for allocation of Marvell
Armada framebuffer objects.
Signed-off-by: Lubomir Rintel
---
.../display/armada/marvell-armada-drm.txt | 25 +++
1 file changed, 25 insertions(+)
diff --git
If there's a simple-framebuffer carried over from boot firmware, it's going
to stop working once we setup the LCDC for use via DRM. Kick it off from
the hardware.
Signed-off-by: Lubomir Rintel
---
drivers/gpu/drm/armada/armada_drv.c | 11 +++
1 file changed, 11 insertions(+)
diff --git
The port is a child, not a property. And it deserves an example.
Also, make the title a bit more visually distinguishable -- this will
look better when the documentation of other Adrmada DRM nodes will be
present.
Signed-off-by: Lubomir Rintel
---
.../display/armada/marvell-armada-drm.txt
Hi,
On 15-01-19 15:51, Ville Syrjälä wrote:
On Sat, Dec 01, 2018 at 12:31:45PM +0100, Hans de Goede wrote:
There are 3 problems with the dsi code's pipe_bpp handling for 6 bpc
pixel-formats which this commit addresses:
1) It assumes that the pipe_bpp is the same as the bpp going over the dsi
Hi Daniel,
On Mon, Jan 21, 2019 at 10:35 AM Daniel Vetter wrote:
> On Fri, Jan 18, 2019 at 05:22:58PM +0100, Geert Uytterhoeven wrote:
> > Since its incarnation in v3.7 almost 7 years ago, no users of the SH
> > Mobile DRM driver have appeared.
> >
> > Hence remove the driver. It can be
https://bugs.freedesktop.org/show_bug.cgi?id=109403
Bug ID: 109403
Summary: amdgpu randomly hangs while streaming or when CPU is
busy on X399 with TR 1950X
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
Hi,
Sorry for being a bit sporadic on this. I was out travelling last week
with little time for email.
On Fri, Jan 18, 2019 at 11:16:31AM -0600, Andrew F. Davis wrote:
> On 1/17/19 7:11 PM, Liam Mark wrote:
> > On Thu, 17 Jan 2019, Andrew F. Davis wrote:
> >
> >> On 1/16/19 4:54 PM, Liam Mark
Hi Daniel,
On Thu, Jan 17, 2019 at 12:52:16PM +0100, Daniel Vetter wrote:
> On Thu, Jan 17, 2019 at 12:38 PM Liviu Dudau wrote:
> >
> > On Wed, Jan 16, 2019 at 05:39:03PM +0100, Daniel Vetter wrote:
> > > Compared to the RFC[1] no changes to the patch itself, but igt moved
> > > forward a lot:
>
On Sun, Jan 20, 2019 at 12:43:18PM +0100, Noralf Trønnes wrote:
> It's now safe to let fbcon unbind automatically on fbdev unregister.
> The crash problem was fixed in commit 2122b40580dd
> ("fbdev: fbcon: Fix unregister crash when more than one framebuffer")
>
> Signed-off-by: Noralf Trønnes
>
On 01/18, Thomas Gleixner wrote:
> Rodrigo,
>
> On Wed, 16 May 2018, Rodrigo Siqueira wrote:
>
> All files added by this commit have inconsistent license information:
>
> > --- /dev/null
> > +++ b/drivers/gpu/drm/vkms/vkms_crtc.c
> > @@ -0,0 +1,35 @@
> > +// SPDX-License-Identifier: GPL-2.0
> >
On Sun, Jan 20, 2019 at 12:43:10PM +0100, Noralf Trønnes wrote:
> This adds a function that creates a simple connector that has only one
> static mode. Additionally add a helper to set _mode_config width
> and height from the static mode.
>
> Signed-off-by: Noralf Trønnes
> ---
>
https://bugzilla.kernel.org/show_bug.cgi?id=201497
Ivan Molodetskikh (yalt...@gmail.com) changed:
What|Removed |Added
CC||yalt...@gmail.com
On Mon, Jan 21, 2019 at 10:10:14AM +0100, Daniel Vetter wrote:
> On Sun, Jan 20, 2019 at 12:43:08PM +0100, Noralf Trønnes wrote:
> > This adds resource managed (devres) versions of drm_dev_init() and
> > drm_dev_register().
> >
> > Also added is devm_drm_dev_register_with_fbdev() which sets up
Hi Gustavo:
Thank you for helping fix this problem
On Fri, Jan 18, 2019 at 03:40:18PM -0600, Gustavo A. R. Silva wrote:
> Remove unused variable *pdev* in komeda_parse_dt():
>
> drivers/gpu/drm/arm/display/komeda//komeda_dev.c: In function
> ‘komeda_parse_dt’:
>
https://bugs.freedesktop.org/show_bug.cgi?id=109403
Ivan Avdeev <1...@provod.gl> changed:
What|Removed |Added
CC||1...@provod.gl
---
On Sun, Jan 20, 2019 at 12:43:11PM +0100, Noralf Trønnes wrote:
> Further strip down tinydrm.ko and switch to drm_simple_connector_create().
>
> Signed-off-by: Noralf Trønnes
> ---
> Documentation/gpu/tinydrm.rst | 3 -
> drivers/gpu/drm/tinydrm/core/Makefile | 2 +-
>
Am 21.01.19 um 11:06 schrieb Ard Biesheuvel:
> Currently, the DRM code assumes that PCI devices are always cache
> coherent for DMA, and that this can be selectively overridden for
> some buffers using non-cached mappings on the CPU side and PCIe
> NoSnoop transactions on the bus side.
>
> Whether
Den 21.01.2019 10.55, skrev Daniel Vetter:
> On Mon, Jan 21, 2019 at 10:10:14AM +0100, Daniel Vetter wrote:
>> On Sun, Jan 20, 2019 at 12:43:08PM +0100, Noralf Trønnes wrote:
>>> This adds resource managed (devres) versions of drm_dev_init() and
>>> drm_dev_register().
>>>
>>> Also added is
Den 21.01.2019 10.29, skrev Daniel Vetter:
> On Sun, Jan 20, 2019 at 12:43:16PM +0100, Noralf Trønnes wrote:
>> No more users left so it can go alongside its helpers.
>> Update the tinydrm docs description and remove todo entry.
>>
>> Signed-off-by: Noralf Trønnes
>> ---
>>
On 1/18/19 1:53 PM, Laura Abbott wrote:
> On 1/16/19 9:12 AM, Andrew F. Davis wrote:
>> On 1/16/19 9:28 AM, Brian Starkey wrote:
>>> Hi Andrew,
>>>
>>> On Fri, Jan 11, 2019 at 12:05:20PM -0600, Andrew F. Davis wrote:
The heap name can be used for debugging but otherwise does not seem
to
Den 20.01.2019 23.25, skrev Sam Ravnborg:
> On Sun, Jan 20, 2019 at 11:22:36PM +0100, Sam Ravnborg wrote:
>> Hi Noralf.
>>
>> On Sun, Jan 20, 2019 at 12:43:14PM +0100, Noralf Trønnes wrote:
>>> Use devm_drm_dev_init(), devm_drm_dev_register_with_fbdev() and drop
>>> using tinydrm_device.
>>>
>>>
On 1/18/19 3:43 PM, Liam Mark wrote:
> On Fri, 18 Jan 2019, Andrew F. Davis wrote:
>
>> On 1/17/19 7:04 PM, Liam Mark wrote:
>>> On Thu, 17 Jan 2019, Andrew F. Davis wrote:
>>>
On 1/16/19 4:48 PM, Liam Mark wrote:
> On Wed, 16 Jan 2019, Andrew F. Davis wrote:
>
>> On 1/15/19 1:05
On Fri, Jan 18, 2019 at 02:51:26PM +, Priit Laes wrote:
> On Fri, Jan 18, 2019 at 03:04:18PM +0100, Maxime Ripard wrote:
> > On Fri, Jan 18, 2019 at 10:10:53AM +, Priit Laes wrote:
> > > > > > > > It doesn't look related to the clock rate itself, since it
> > > > > > > > doesn't
> > > > >
https://bugzilla.kernel.org/show_bug.cgi?id=201815
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=109375
Alex Deucher changed:
What|Removed |Added
CC||christian.frank.uwb@googlem
https://bugs.freedesktop.org/show_bug.cgi?id=109388
Alex Deucher changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Fri, 18 Jan 2019 at 13:08, Guenter Roeck wrote:
>
> On 1/18/19 3:05 AM, Rafael J. Wysocki wrote:
> > On Fri, Jan 18, 2019 at 11:53 AM Vincent Guittot
> > wrote:
> >>
> >> On Fri, 18 Jan 2019 at 11:42, Vincent Guittot
> >> wrote:
> >>>
> >>> Hi Guenter,
> >>>
> >>> Le Thursday 17 Jan 2019 à
Hi,
On 21-01-19 15:26, Hans de Goede wrote:
Hi,
On 15-01-19 16:00, Ville Syrjälä wrote:
On Sat, Dec 01, 2018 at 12:31:47PM +0100, Hans de Goede wrote:
On devices with a burst_mode_ratio which is not 100 (1:1), the pclk
will have a different value then drm_display_mode.clock .
On a Prowise
The lanes parameter is not solely about the number of lanes, but it also
carries the fact that those are the first lanes in use during the
transmission.
It was implicit so far, so make sure it's explicit now.
Suggested-by: Sakari Ailus
Acked-by: Sakari Ailus
Signed-off-by: Maxime Ripard
---
Den 21.01.2019 07.11, skrev Sam Ravnborg:
> Hi Noralf.
>
> On Sun, Jan 20, 2019 at 12:43:08PM +0100, Noralf Trønnes wrote:
>> This adds resource managed (devres) versions of drm_dev_init() and
>> drm_dev_register().
>>
>> Also added is devm_drm_dev_register_with_fbdev() which sets up generic
>>
Den 21.01.2019 09.34, skrev Sam Ravnborg:
> Hi Noralf.
>
> On Sun, Jan 20, 2019 at 12:43:07PM +0100, Noralf Trønnes wrote:
>> This patchset is part of the effort to remove tinydrm.ko. It removes
>> struct tinydrm_device and tinydrm.h.
>>
>> While doing this refactoring I have ensured that
tree: git://anongit.freedesktop.org/drm-intel drm-intel-next-queued
head: 9f58892ea9962002399132fd3f40c6a273f8d9e1
commit: 9f58892ea9962002399132fd3f40c6a273f8d9e1 [2/2] drm/i915: Pull all the
reset functionality together into i915_reset.c
config: i386-randconfig-x007-201903 (attached as
On Thu, Jan 17, 2019 at 08:33:38AM -0500, Sean Paul wrote:
> > @@ -768,49 +769,90 @@ static int cdns_dsi_mode2cfg(struct cdns_dsi *dsi,
> >
> > dsi_cfg->hsa = dpi_to_dsi_timing(tmp, bpp,
> > DSI_HSA_FRAME_OVERHEAD);
> > -
Hi Liam,
On Fri, Jan 18, 2019 at 10:37:47AM -0800, Liam Mark wrote:
> Add support for configuring dma mapping attributes when mapping
> and unmapping memory through dma_buf_map_attachment and
> dma_buf_unmap_attachment.
>
> For example this will allow ION clients to skip cache maintenance, by
>
Hi Sean,
On Thu, Jan 17, 2019 at 08:53:22AM -0500, Sean Paul wrote:
> On Wed, Jan 09, 2019 at 10:33:25AM +0100, Maxime Ripard wrote:
> > + opts->wakeup = cdns_dphy_get_wakeup_time_ns(dphy) * 1000;
>
> This should be "/ 1000" since the units of wakeup is us now (thanks to patch
> 2).
> You've
On 1/18/19 2:19 PM, Laura Abbott wrote:
> On 1/16/19 8:05 AM, Andrew F. Davis wrote:
>> On 1/15/19 12:58 PM, Laura Abbott wrote:
>>> On 1/15/19 9:47 AM, Andrew F. Davis wrote:
On 1/14/19 8:39 PM, Laura Abbott wrote:
> On 1/11/19 10:05 AM, Andrew F. Davis wrote:
>> Hello all,
>>
On Mon, Jan 21, 2019 at 01:27:58PM +0200, Jani Nikula wrote:
> We have a wrapper for a reason.
>
> Signed-off-by: Jani Nikula
Reviewed-by: Ville Syrjälä
> ---
> drivers/gpu/drm/drm_dp_helper.c | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git
The mdev->irq value comes from platform_get_irq() so it can't be more
than INT_MAX and if it's unsigned then it breaks the error handling in
komeda_parse_dt().
Fixes: 29e56aec911d ("drm/komeda: Add DT parsing")
Signed-off-by: Dan Carpenter
---
drivers/gpu/drm/arm/display/komeda/komeda_dev.h | 2
Hi,
On 15-01-19 16:00, Ville Syrjälä wrote:
On Sat, Dec 01, 2018 at 12:31:47PM +0100, Hans de Goede wrote:
On devices with a burst_mode_ratio which is not 100 (1:1), the pclk
will have a different value then drm_display_mode.clock .
On a Prowise PT301 tablet where vbt.lfp_lvds_vbt_mode.clock
Cadence has designed a D-PHY that can be used by the, currently in tree,
DSI bridge (DRM), CSI Transceiver and CSI Receiver (v4l2) drivers.
Only the DSI driver has an ad-hoc driver for that phy at the moment, while
the v4l2 drivers are completely missing any phy support. In order to make
that phy
Now that our MIPI D-PHY driver has been converted to the phy framework,
let's move it into the drivers/phy directory.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/sun4i/Kconfig | 10 +-
drivers/gpu/drm/sun4i/Makefile | 1 +-
The Init and wakeup D-PHY parameters are in the micro/milliseconds range,
putting the values real close to the types limits if they were in
picoseconds.
Move them to microseconds which should be better fit.
Suggested-by: Sakari Ailus
Acked-by: Sakari Ailus
Signed-off-by: Maxime Ripard
---
The videomode.h header inclusion is an artifact from the patches
development, remove it.
Suggested-by: Sakari Ailus
Acked-by: Sakari Ailus
Signed-off-by: Maxime Ripard
---
include/linux/phy/phy-mipi-dphy.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/phy/phy-mipi-dphy.h
Now that we have everything we need in the phy framework to allow to tune
the phy parameters, let's convert the Cadence DSI bridge to that API
instead of creating a ad-hoc driver for its phy.
Acked-by: Sean Paul
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/bridge/Kconfig| 1 +-
The current configuration of the DSI bridge and its associated D-PHY is
intertwined. In order to ease the future conversion to the phy framework
for the D-PHY part, let's split the configuration in two.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/bridge/cdns-dsi.c | 101
Hi,
Here is a set of patches to allow the phy framework consumers to test and
apply runtime configurations.
This is needed to support more phy classes that require tuning based on
parameters depending on the current use case of the device, in addition to
the power state management already
The Cadence D-PHY bindings was defined as part of the DSI block so far.
However, since it's now going to be a separate driver, we need to move the
binding to a file of its own.
Acked-by: Sakari Ailus
Signed-off-by: Maxime Ripard
---
Documentation/devicetree/bindings/display/bridge/cdns,dsi.txt
Now that we have everything in place in the PHY framework to deal in a
generic way with MIPI D-PHY phys, let's convert our PHY driver and its
associated DSI driver to that new API.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/sun4i/Kconfig | 11 +-
drivers/gpu/drm/sun4i/Makefile
On Sun, Jan 20, 2019 at 11:26 AM Lubomir Rintel wrote:
>
> The Marvell Armada DRM master device is a virtual device needed to list all
> nodes that comprise the graphics subsystem.
>
> Signed-off-by: Lubomir Rintel
> ---
> .../display/armada/marvell-armada-drm.txt | 24 +++
>
On Mon, Jan 21, 2019 at 9:46 AM Lubomir Rintel wrote:
>
> On Mon, 2019-01-21 at 09:35 -0600, Rob Herring wrote:
> > On Sun, Jan 20, 2019 at 11:26 AM Lubomir Rintel wrote:
> > > The Marvell Armada DRM master device is a virtual device needed to list
> > > all
> > > nodes that comprise the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #65 from bmil...@gmail.com ---
Please look at this devs, still no solution in mind?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
On Wed, Jan 16, 2019 at 04:27:58PM +0100, Lucas Stach wrote:
> The Vivante GPU cores are found in many different SoCs and the driver
> does not depend on anything architecture specific, so just drop the
> architecture restriction.
With my Debian kernel team member hat on I don't like changes like
On Mon, Jan 21, 2019 at 10:07:11AM -0600, Rob Herring wrote:
> On Mon, Jan 21, 2019 at 9:46 AM Lubomir Rintel wrote:
> >
> > On Mon, 2019-01-21 at 09:35 -0600, Rob Herring wrote:
> > > On Sun, Jan 20, 2019 at 11:26 AM Lubomir Rintel wrote:
> > > > The Marvell Armada DRM master device is a
On 1/21/19 1:44 PM, Liam Mark wrote:
> On Mon, 21 Jan 2019, Christoph Hellwig wrote:
>
>> On Sat, Jan 19, 2019 at 08:50:41AM -0800, Laura Abbott wrote:
And who is going to decide which ones to pass? And who documents
which ones are safe?
I'd much rather have explicit, well
-ci/linux/commits/Kristian-H-Kristensen/drm-Add-DRM_DEV_INFO_RATELIMITED/20190121-162608
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
net/mac80211/sta_info.h:590: warning: Function parameter or member
'status_stats.ack_signal_filled' not described in 'sta_info'
On 2019-01-21 6:59 p.m., Ard Biesheuvel wrote:
> On Mon, 21 Jan 2019 at 18:55, Michel Dänzer wrote:
>>
>> On 2019-01-21 5:30 p.m., Ard Biesheuvel wrote:
>>> On Mon, 21 Jan 2019 at 17:22, Christoph Hellwig wrote:
>>>
Until that happens we should just change the driver ifdefs to default
On Mon, Jan 21, 2019 at 12:54 PM Brian Starkey wrote:
>
> Hi Daniel,
>
> On Thu, Jan 17, 2019 at 12:52:16PM +0100, Daniel Vetter wrote:
> > On Thu, Jan 17, 2019 at 12:38 PM Liviu Dudau wrote:
> > >
> > > On Wed, Jan 16, 2019 at 05:39:03PM +0100, Daniel Vetter wrote:
> > > > Compared to the
On 2019-01-21 7:20 p.m., Ard Biesheuvel wrote:
> On Mon, 21 Jan 2019 at 19:04, Michel Dänzer wrote:
>>
>> On 2019-01-21 6:59 p.m., Ard Biesheuvel wrote:
>>> On Mon, 21 Jan 2019 at 18:55, Michel Dänzer wrote:
On 2019-01-21 5:30 p.m., Ard Biesheuvel wrote:
> On Mon, 21 Jan 2019 at
On Tue, Jan 22, 2019 at 1:18 AM Jernej Škrabec wrote:
>
> Dne ponedeljek, 21. januar 2019 ob 16:07:28 CET je Priit Laes napisal(a):
> > On Mon, Jan 21, 2019 at 02:25:17PM +0100, Maxime Ripard wrote:
> > > On Fri, Jan 18, 2019 at 02:51:26PM +, Priit Laes wrote:
> > > > On Fri, Jan 18, 2019 at
https://bugzilla.kernel.org/show_bug.cgi?id=201815
siyia (eutychio...@gmail.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
On 2019-01-21 7:28 p.m., Ard Biesheuvel wrote:
> On Mon, 21 Jan 2019 at 19:24, Michel Dänzer wrote:
>> On 2019-01-21 7:20 p.m., Ard Biesheuvel wrote:
>>> On Mon, 21 Jan 2019 at 19:04, Michel Dänzer wrote:
On 2019-01-21 6:59 p.m., Ard Biesheuvel wrote:
> On Mon, 21 Jan 2019 at 18:55,
On 2019-01-21 5:30 p.m., Ard Biesheuvel wrote:
> On Mon, 21 Jan 2019 at 17:22, Christoph Hellwig wrote:
>
>> Until that happens we should just change the driver ifdefs to default
>> the hacks to off and only enable them on setups where we 100%
>> positively know that they actually work. And
On 1/21/19 2:20 PM, Liam Mark wrote:
> On Mon, 21 Jan 2019, Andrew F. Davis wrote:
>
>> On 1/21/19 1:44 PM, Liam Mark wrote:
>>> On Mon, 21 Jan 2019, Christoph Hellwig wrote:
>>>
On Sat, Jan 19, 2019 at 08:50:41AM -0800, Laura Abbott wrote:
>> And who is going to decide which ones to
From: Ville Syrjälä
Logs can get confusing when some operations are done multiple times
due to the ww mutex backoff. Add a debug print into
drm_modeset_backoff() so that at least the reason for the odd
looking logs will be obvious.
Signed-off-by: Ville Syrjälä
---
From: Ville Syrjälä
Only some of the drm mode object lookups have a corresponding debug
print for the lookup failure. That makes logs a bit hard to parse
when you can't see where the bad object ID is being used. Add a bunch
more debug prints, and unify their appearance.
Signed-off-by: Ville
From: Ville Syrjälä
Use ENOENT consistently for the case where the requested property
isn't found, and EINVAL for the case where the object has no
properties whatsoever. Currenrly these are handled differently
in the atomic and legacy codepaths.
Signed-off-by: Ville Syrjälä
---
On Mon, Jan 21, 2019 at 09:45:22PM +0100, Lubomir Rintel wrote:
> On Mon, 2019-01-21 at 17:53 +, Russell King - ARM Linux admin
> wrote:
> > On Mon, Jan 21, 2019 at 10:07:11AM -0600, Rob Herring wrote:
> > > On Mon, Jan 21, 2019 at 9:46 AM Lubomir Rintel wrote:
> > > > On Mon, 2019-01-21 at
https://bugs.freedesktop.org/show_bug.cgi?id=109370
--- Comment #2 from MIka R ---
Created attachment 143181
--> https://bugs.freedesktop.org/attachment.cgi?id=143181=edit
Apitrace
AMD RX 480
--
You are receiving this mail because:
You are the assignee for the
Rather than every backend and GPU driver reinventing the same wheel for
user level debugging of HW execution, the common dma-fence framework
should include the tracing infrastructure required for most client API
level flow visualisation.
With these common dma-fence level tracepoints, the
On Mon, Jan 21, 2019 at 11:53 AM Russell King - ARM Linux admin
wrote:
>
> On Mon, Jan 21, 2019 at 10:07:11AM -0600, Rob Herring wrote:
> > On Mon, Jan 21, 2019 at 9:46 AM Lubomir Rintel wrote:
> > >
> > > On Mon, 2019-01-21 at 09:35 -0600, Rob Herring wrote:
> > > > On Sun, Jan 20, 2019 at
Fixes license inconsistent related to the VKMS driver and remove the
redundant boilerplate comment.
Fixes: 854502fa0a38 ("drm/vkms: Add basic CRTC initialization")
Signed-off-by: Rodrigo Siqueira
---
drivers/gpu/drm/vkms/vkms_crc.c| 3 ++-
drivers/gpu/drm/vkms/vkms_crtc.c | 8 +---
On 1/21/19 5:22 AM, Brian Starkey wrote:
> Hi,
>
> Sorry for being a bit sporadic on this. I was out travelling last week
> with little time for email.
>
> On Fri, Jan 18, 2019 at 11:16:31AM -0600, Andrew F. Davis wrote:
>> On 1/17/19 7:11 PM, Liam Mark wrote:
>>> On Thu, 17 Jan 2019, Andrew F.
Hi Daniel et al.
> >
> > Yeah the drm_crtc_helper.h header is a bit the miniature drmP.h for legacy
> > kms drivers. Just removing it from all the atomic drivers caused lots of
> > fallout, I expect even more if you entirely remove the includes it has.
> > Maybe a todo, care to pls create that
On Mon, Jan 21, 2019 at 4:17 PM Vincent Guittot
wrote:
>
> On Fri, 18 Jan 2019 at 13:08, Guenter Roeck wrote:
> >
> > On 1/18/19 3:05 AM, Rafael J. Wysocki wrote:
> > > On Fri, Jan 18, 2019 at 11:53 AM Vincent Guittot
> > > wrote:
> > >>
> > >> On Fri, 18 Jan 2019 at 11:42, Vincent Guittot
> >
Hi Douglas,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v5.0-rc2]
[also build test ERROR on next-20190116]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://bugs.freedesktop.org/show_bug.cgi?id=109217
fin4...@hotmail.com changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
Hi CK,
Ok, I'll send it again in an independent patch.
Best Regards
Jitao
On Wed, 2019-01-16 at 14:52 +0800, CK Hu (胡俊光) wrote:
> Hi, Chunhui:
>
> > -Original Message-
> > From: chunhui dai [mailto:chunhui@mediatek.com]
> > Sent: Friday, January 04, 2019 3:04 PM
> > To:
On Mon, Jan 21, 2019 at 06:58:57PM -0200, Rodrigo Siqueira wrote:
> Fixes license inconsistent related to the VKMS driver and remove the
> redundant boilerplate comment.
>
> Fixes: 854502fa0a38 ("drm/vkms: Add basic CRTC initialization")
>
> Signed-off-by: Rodrigo Siqueira
> ---
>
On 18 December 2018 7:07:01 pm NZDT, Christopher James Halse Rogers
wrote:
>On 18 December 2018 4:35:37 am AEDT, Emil Velikov
> wrote:
>>Hi Christopher,
>>
>>On Tue, 20 Nov 2018 at 03:37, Christopher James Halse Rogers
>> wrote:
>>>
>>> We can't use drmSetMaster to query whether or not a drm fd
1 - 100 of 106 matches
Mail list logo
