[PATCH v2 2/2] drm/vmwgfx: drop reminaing users of drmP.h

2019-06-23 Thread Sam Ravnborg
Drop use of the deprecated drmP.h file from the remaining files. In several cases the drmP.h include could be removed without furter fixes. Other files required a few header files to be added. In all files divided includes files in blocks and sort them. v2: - fix warning in i386 build wiht HIGHME

[PATCH v2 0/2] drm/vmwgfx: drop use of drmP.h

2019-06-23 Thread Sam Ravnborg
In two steps drop the use of drmP.h First patch remove drmP.h from header files and fixes fallout. Second patch remove drmP.h from the remaining files. While touching the list of include files divide them in blocks and sort include files within the blocks. Patches made on top of drm-misc-next, an

[PATCH v2 1/2] drm/vmwgfx: drop use of drmP.h in header files

2019-06-23 Thread Sam Ravnborg
To facilitate removal of drmP.h in the .c files remove the use from header files first. Fix fallout in the other files. Sorted include files in blocks and sorted files within each block in alphabetical order. This revealed a dependency from an uapi header to a header located below drivers/gpu/drm

[PATCH v2 1/4] drm/mga: drop dependency on drm_os_linux.h

2019-06-23 Thread Sam Ravnborg
Opencode all macros used from the deprecated drm_os_linux.h header file. The DRM_WAIT_ON used 3 * HZ as timeout. This was translated to 3000 msec. The return value of mga_driver_fence_wait() was not used, so make it return void to simplify code a bit. v2: - fixed timeout to 3000 msec (original va

[PATCH v2 0/4] drm/{mga,mgag200}: drop use of drmP.h

2019-06-23 Thread Sam Ravnborg
Drop use of the deprecated drmP.h header file. Also drop use of drm_os_linux.h as it is deprecated too, and was pulled in via drmP.h Build tested with allmodconfig, allyesconfig on various architectures. v2: - Fix timeout in wait_event*. 3 * HZ equals to 3000 msecs (this is at least my best und

[PATCH v2 2/4] drm/mga: make header file self contained

2019-06-23 Thread Sam Ravnborg
This makes migration away from drmP.h simple as we do not need to duplicate dependencies required by mga_drv.h Signed-off-by: Sam Ravnborg Acked-by: Thomas Zimmermann Cc: Daniel Vetter Cc: David Airlie --- drivers/gpu/drm/mga/mga_drv.h | 13 + 1 file changed, 13 insertions(+) dif

[PATCH v2 4/4] drm/mgag200: drop use of drmP.h

2019-06-23 Thread Sam Ravnborg
Drop use of the deprecated drmP.h header file. Replace with necessary include files to fix build. Signed-off-by: Sam Ravnborg Acked-by: Thomas Zimmermann Cc: Daniel Vetter Cc: David Airlie --- drivers/gpu/drm/mgag200/mgag200_cursor.c | 3 ++- drivers/gpu/drm/mgag200/mgag200_drv.c| 10 +++

[PATCH v2 3/4] drm/mga: drop use of drmP.h

2019-06-23 Thread Sam Ravnborg
Drop the use of the deprecated drmP.h header file. Clean up list of include files and sort them. Signed-off-by: Sam Ravnborg Acked-by: Thomas Zimmermann Cc: Daniel Vetter Cc: David Airlie --- drivers/gpu/drm/mga/mga_dma.c | 2 -- drivers/gpu/drm/mga/mga_drv.c | 7 +++ drivers/gpu/drm/

Re: [Intel-gfx] [PATCH v3 3/4] drm/connector: Split out orientation quirk detection

2019-06-23 Thread Hans de Goede
Hi, On 22-06-19 05:41, Derek Basehore wrote: Not every platform needs quirk detection for panel orientation, so split the drm_connector_init_panel_orientation_property into two functions. One for platforms without the need for quirks, and the other for platforms that need quirks. Signed-off-by:

[Bug 110972] bug bug

2019-06-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110972 Vaishnavi changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[PATCH v1 2/3] drm/tegra: Fix 2d and 3d clients detaching from IOMMU domain

2019-06-23 Thread Dmitry Osipenko
This should should fire up on the DRM's driver module re-loader because there won't be enough available domains on older Tegra SoCs. Cc: stable Fixes: 0c407de5ed1a ("drm/tegra: Refactor IOMMU attach/detach") Signed-off-by: Dmitry Osipenko --- drivers/gpu/drm/tegra/dc.c | 4 ++-- drivers/gpu/d

[PATCH v1 1/3] gpu: host1x: Remove implicit IOMMU backing on client's registration

2019-06-23 Thread Dmitry Osipenko
On ARM32 we don't want any of the clients device to be backed by the implicit domain, simply because we can't afford such a waste on older Tegra SoCs that have very few domains available in total. The recent IOMMU support addition for the Video Decoder hardware uncovered the problem that an unfortu

[PATCH v1 3/3] drm/tegra: vic: Use common helpers to attach/detach from IOMMU domain

2019-06-23 Thread Dmitry Osipenko
We now have helpers for the domain's attachment, let's use them. Signed-off-by: Dmitry Osipenko --- drivers/gpu/drm/tegra/vic.c | 27 --- 1 file changed, 8 insertions(+), 19 deletions(-) diff --git a/drivers/gpu/drm/tegra/vic.c b/drivers/gpu/drm/tegra/vic.c index 982ce37

Re: [PATCH v5 2/2] DRM: Add KMS driver for the Ingenic JZ47xx SoCs

2019-06-23 Thread Paul Cercueil
Le ven. 21 juin 2019 à 11:13, Daniel Vetter a écrit : On Fri, Jun 21, 2019 at 11:07:30AM +0200, Paul Cercueil wrote: Le ven. 21 juin 2019 à 11:04, Daniel Vetter a écrit : > On Thu, Jun 20, 2019 at 04:15:59PM +0200, Paul Cercueil wrote: > > > > > > Le mer. 19 juin 2019 à 14:26, Sam

[Bug 203963] New: Unable to overclock memory while core is overclocking fine. RX560X

2019-06-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203963 Bug ID: 203963 Summary: Unable to overclock memory while core is overclocking fine. RX560X Product: Drivers Version: 2.5 Kernel Version: 5.2-rc6 Hardware: All

[Bug 203817] Raven Ridge VEGA8 stuck on 400Mhz on battery

2019-06-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203817 Haxk20 (haxk...@gmail.com) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 110972] bug bug

2019-06-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110972 Andre Klapper changed: What|Removed |Added Status|ASSIGNED|RESOLVED Component|General

Re: [PATCH 0/4] drm/bridge: dw-hdmi: Add support for HDR metadata

2019-06-23 Thread Laurent Pinchart
On Fri, Jun 21, 2019 at 11:01:25AM +0200, Daniel Vetter wrote: > On Thu, Jun 20, 2019 at 04:40:12PM +0200, Neil Armstrong wrote: > > Hi Andrzej, > > > > Gentle ping, could you review the dw-hdmi changes here ? > > btw not sure you absolutely need review from Andrzej, we're currently a > bit under

[Bug 201539] AMDGPU R9 390 automatic fan speed control in Linux 4.19/4.20/5.0

2019-06-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201539 --- Comment #19 from Sean Birkholz (supas...@hotmail.com) --- I've done a bit of digging and I've managed to get a proper hysteresis value to appear in a 5.1.14 kernel built from source. I now have this output from sensors: amdgpu-pci-0100 Adapt

linux-next: manual merge of the drm tree with the jc_docs tree

2019-06-23 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the drm tree got a conflict in: Documentation/fb/modedb.rst between commit: ab42b818954c ("docs: fb: convert docs to ReST and rename to *.rst") from the jc_docs tree and commit: 1bf4e09227c3 ("drm/modes: Allow to specify rotation and reflection on the

Re: linux-next: manual merge of the drm-intel tree with the pci tree

2019-06-23 Thread Stephen Rothwell
Hi all, On Mon, 17 Jun 2019 13:20:27 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the drm-intel tree got a conflict in: > > drivers/gpu/drm/i915/i915_drv.h > > between commit: > > 151f4e2bdc7a ("docs: power: convert docs to ReST and rename to *.rst") > > from the pci tre

Re: linux-next: build failure after merge of the fbdev tree

2019-06-23 Thread Stephen Rothwell
Hi all, On Mon, 24 Jun 2019 11:45:38 +1000 Stephen Rothwell wrote: > > On Thu, 20 Jun 2019 11:41:26 +1000 Stephen Rothwell > wrote: > > > > After merging the fbdev tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > x86_64-linux-gnu-ld: drivers/gpu/vga/vga_switc

Re: [PATCH] android: libdrm_platform: add liblog shared dependency

2019-06-23 Thread Chih-Wei Huang
Sorry for the late reply since I didn't notice it. (I rarely read the ML) The patch of Jiyong Park is the one he submitted to the ML before. https://patchwork.kernel.org/patch/9864539/ https://patchwork.kernel.org/patch/10109599/ I'm not sure why it's not merged. Maybe just forgotten. The 2nd an

[v2 0/2] Add BOE tv101wum-nl6 panel driver

2019-06-23 Thread Jitao Shi
Changes since v1: - update typo nl6 -> n16. - update new panel config and makefile are added in alphabetically order. - add the panel mode and panel info in driver data. Jitao Shi (2): dt-bindngs: display: panel: Add BOE tv101wum-n16 panel bindings drm/panel: support for BOE tv101wum-nl6 w

[v2 2/2] drm/panel: support for BOE tv101wum-nl6 wuxga dsi video mode panel

2019-06-23 Thread Jitao Shi
Add driver for BOE tv101wum-nl6 panel is a 10.1" 1200x1920 panel. Signed-off-by: Jitao Shi --- drivers/gpu/drm/panel/Kconfig | 10 + drivers/gpu/drm/panel/Makefile| 1 + .../gpu/drm/panel/panel-boe-tv101wum-nl6.c| 715 ++ 3 files changed, 72

[v2 1/2] dt-bindngs: display: panel: Add BOE tv101wum-n16 panel bindings

2019-06-23 Thread Jitao Shi
Add documentation for boe tv101wum-n16 panel. Signed-off-by: Jitao Shi --- .../display/panel/boe,tv101wum-nl6.txt| 34 +++ 1 file changed, 34 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/panel/boe,tv101wum-nl6.txt diff --git a/Documentati

Re: [PATCH v2 00/28] drivers: Consolidate device lookup helpers

2019-06-23 Thread Greg KH
On Fri, Jun 14, 2019 at 06:53:55PM +0100, Suzuki K Poulose wrote: > We have device iterators to find a particular device matching a criteria > for a given bus/class/driver. i.e, {bus,class,driver}_find_device() APIs. > The matching criteria is a function pointer for the APIs. Often the lookup > is

Re: [PATCH v2 00/18] drm/ttm: make ttm bo a gem bo subclass

2019-06-23 Thread Gerd Hoffmann
Hi, > Yeah, my point was not really suggesting that we do this, but rather that > people would rightfully get upset because the struct contains unused stuff. Well, struct drm_gem_object isn't that big, lets have a look: 320 bytes in total, of which are: 184 bytes the embedded vma_mode 64

drm/msm/dpu: Correct dpu encoder spinlock initialization

2019-06-23 Thread Shubhashree Dhar
dpu encoder spinlock should be initialized during dpu encoder init instead of dpu encoder setup which is part of commit. There are chances that vblank control uses the uninitialized spinlock if not initialized during encoder init. Change-Id: I5a18b95fa47397c834a266b22abf33a517b03a4e Signed-off-by: