[PATCH 3/3] drm/panel: simple: Add support for the Frida FRD350H54004 panel

2019-11-20 Thread Paul Cercueil
The FRD350H54004 is a simple 3.5" 320x240 24-bit TFT panel, found for instance inside the Anbernic RG-350 handheld gaming console. Signed-off-by: Paul Cercueil --- drivers/gpu/drm/panel/panel-simple.c | 29 1 file changed, 29 insertions(+) diff --git a/drivers/gpu/d

[PATCH v1 4/5] fbtft: Make use of device property API

2019-11-20 Thread Andy Shevchenko
Make use of device property API in this driver so that both OF based system and ACPI based system can use this driver. Signed-off-by: Andy Shevchenko --- drivers/staging/fbtft/fbtft-core.c | 105 - 1 file changed, 58 insertions(+), 47 deletions(-) diff --git a/driver

[PATCH 2/3] dt-bindings: panel: Document Frida FRD350H54004 LCD panel

2019-11-20 Thread Paul Cercueil
Add bindings documentation for the Frida 3.5" (320x240 pixels) 24-bit TFT LCD panel. Signed-off-by: Paul Cercueil --- .../bindings/display/panel/frida,frd350h54004.txt| 12 1 file changed, 12 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/panel/frid

Re: [Intel-gfx] linux-next: Tree for Nov 19 (i915)

2019-11-20 Thread Randy Dunlap
On 11/20/19 8:56 AM, Chris Wilson wrote: > Quoting Jani Nikula (2019-11-20 16:15:08) >> On Tue, 19 Nov 2019, Randy Dunlap wrote: >>> On 11/19/19 12:46 AM, Stephen Rothwell wrote: Hi all, Changes since 20191118: >>> >>> >>> on x86_64: >>> >>> ERROR: "pm_suspend_target_state" [drivers

[PATCH v1 2/5] fbtft: Describe function parameters in kernel-doc

2019-11-20 Thread Andy Shevchenko
Kernel documentation script complains that some of the function parameters are not described: drivers/staging/fbtft/fbtft-core.c:543: warning: Function parameter or member 'pdata' not described in 'fbtft_framebuffer_alloc' Describe function parameters where it's appropriate. Signed-off-by: Andy

Re: [PATCH] drm/mgag200: Fix Kconfig indentation

2019-11-20 Thread Thomas Zimmermann
Am 20.11.19 um 14:36 schrieb Krzysztof Kozlowski: > Adjust indentation from spaces to tab (+optional two spaces) as in > coding style with command like: > $ sed -e 's/^/\t/' -i */Kconfig > > Signed-off-by: Krzysztof Kozlowski Acked-by: Thomas Zimmermann > --- > drivers/gpu/drm

Re: [PATCH v3 4/4] dt-bindings: display: add IMX MIPI DSI host controller doc

2019-11-20 Thread Adrian Ratiu
On Wed, 20 Nov 2019, Neil Armstrong wrote: Hi, On 18/11/2019 16:25, Adrian Ratiu wrote: A small commit log would be welcome here. Signed-off-by: Sjoerd Simons Signed-off-by: Martyn Welch Signed-off-by: Adrian Ratiu --- .../bindings/display/imx/mipi-dsi.txt | 56

Re: 2989f64510 ("dma-buf: Add selftests for dma-fence"): WARNING: CPU: 0 PID: 1 at lib/debugobjects.c:524 __debug_object_init

2019-11-20 Thread Chris Wilson
Quoting kernel test robot (2019-11-21 07:19:43) > Greetings, > > 0day kernel testing robot got the below dmesg and the first bad commit is > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > > commit 2989f6451084aed3f8cc9992477f7a9bf57a3716 > Author: Chris Wilson

[PATCH v7 18/24] media/v4l2-core: pin_user_pages (FOLL_PIN) and put_user_page() conversion

2019-11-20 Thread John Hubbard
1. Change v4l2 from get_user_pages() to pin_user_pages(). 2. Because all FOLL_PIN-acquired pages must be released via put_user_page(), also convert the put_page() call over to put_user_pages_dirty_lock(). Acked-by: Hans Verkuil Cc: Ira Weiny Signed-off-by: John Hubbard --- drivers/media/v4l2-

[PATCH v7 10/24] mm/gup: introduce pin_user_pages*() and FOLL_PIN

2019-11-20 Thread John Hubbard
Introduce pin_user_pages*() variations of get_user_pages*() calls, and also pin_longterm_pages*() variations. For now, these are placeholder calls, until the various call sites are converted to use the correct get_user_pages*() or pin_user_pages*() API. These variants will eventually all set FOLL

[PATCH v7 21/24] mm/gup_benchmark: use proper FOLL_WRITE flags instead of hard-coding "1"

2019-11-20 Thread John Hubbard
Fix the gup benchmark flags to use the symbolic FOLL_WRITE, instead of a hard-coded "1" value. Also, clean up the filtering of gup flags a little, by just doing it once before issuing any of the get_user_pages*() calls. This makes it harder to overlook, instead of having little "gup_flags & 1" phr

[PATCH v7 19/24] vfio, mm: pin_user_pages (FOLL_PIN) and put_user_page() conversion

2019-11-20 Thread John Hubbard
1. Change vfio from get_user_pages_remote(), to pin_user_pages_remote(). 2. Because all FOLL_PIN-acquired pages must be released via put_user_page(), also convert the put_page() call over to put_user_pages_dirty_lock(). Note that this effectively changes the code's behavior in vfio_iommu_type1.c:

[PATCH v7 07/24] IB/umem: use get_user_pages_fast() to pin DMA pages

2019-11-20 Thread John Hubbard
And get rid of the mmap_sem calls, as part of that. Note that get_user_pages_fast() will, if necessary, fall back to __gup_longterm_unlocked(), which takes the mmap_sem as needed. Reviewed-by: Jan Kara Reviewed-by: Jason Gunthorpe Reviewed-by: Ira Weiny Signed-off-by: John Hubbard --- drivers

[PATCH v7 24/24] mm, tree-wide: rename put_user_page*() to unpin_user_page*()

2019-11-20 Thread John Hubbard
In order to provide a clearer, more symmetric API for pinning and unpinning DMA pages. This way, pin_user_pages*() calls match up with unpin_user_pages*() calls, and the API is a lot closer to being self-explanatory. Reviewed-by: Jan Kara Signed-off-by: John Hubbard --- Documentation/core-api/p

[PATCH v7 20/24] powerpc: book3s64: convert to pin_user_pages() and put_user_page()

2019-11-20 Thread John Hubbard
1. Convert from get_user_pages() to pin_user_pages(). 2. As required by pin_user_pages(), release these pages via put_user_page(). In this case, do so via put_user_pages_dirty_lock(). That has the side effect of calling set_page_dirty_lock(), instead of set_page_dirty(). This is probably more acc

[PATCH v7 03/24] mm/gup: move try_get_compound_head() to top, fix minor issues

2019-11-20 Thread John Hubbard
An upcoming patch uses try_get_compound_head() more widely, so move it to the top of gup.c. Also fix a tiny spelling error and a checkpatch.pl warning. Reviewed-by: Jan Kara Reviewed-by: Ira Weiny Signed-off-by: John Hubbard --- mm/gup.c | 29 +++-- 1 file changed, 15

[PATCH v7 15/24] fs/io_uring: set FOLL_PIN via pin_user_pages()

2019-11-20 Thread John Hubbard
Convert fs/io_uring to use the new pin_user_pages() call, which sets FOLL_PIN. Setting FOLL_PIN is now required for code that requires tracking of pinned pages, and therefore for any code that calls put_user_page(). In partial anticipation of this work, the io_uring code was already calling put_us

[PATCH v7 06/24] goldish_pipe: rename local pin_user_pages() routine

2019-11-20 Thread John Hubbard
1. Avoid naming conflicts: rename local static function from "pin_user_pages()" to "pin_goldfish_pages()". An upcoming patch will introduce a global pin_user_pages() function. Reviewed-by: Jan Kara Reviewed-by: Jérôme Glisse Reviewed-by: Ira Weiny Signed-off-by: John Hubbard --- drivers/plat

[PATCH v7 00/24] mm/gup: track dma-pinned pages: FOLL_PIN

2019-11-20 Thread John Hubbard
Hi, OK, here is v7, maybe this is the last one. The corresponding git repo and branch is: g...@github.com:johnhubbard/linux.git pin_user_pages_tracking_v7 Ira, you reviewed the gup_benchmark patches a bit earlier, but I removed one or two of those review-by tags, due to invasive changes I ma

[PATCH v7 09/24] vfio, mm: fix get_user_pages_remote() and FOLL_LONGTERM

2019-11-20 Thread John Hubbard
As it says in the updated comment in gup.c: current FOLL_LONGTERM behavior is incompatible with FAULT_FLAG_ALLOW_RETRY because of the FS DAX check requirement on vmas. However, the corresponding restriction in get_user_pages_remote() was slightly stricter than is actually required: it forbade all

[PATCH v7 22/24] mm/gup_benchmark: support pin_user_pages() and related calls

2019-11-20 Thread John Hubbard
Up until now, gup_benchmark supported testing of the following kernel functions: * get_user_pages(): via the '-U' command line option * get_user_pages_longterm(): via the '-L' command line option * get_user_pages_fast(): as the default (no options required) Add test coverage for the new correspon

[PATCH v7 23/24] selftests/vm: run_vmtests: invoke gup_benchmark with basic FOLL_PIN coverage

2019-11-20 Thread John Hubbard
It's good to have basic unit test coverage of the new FOLL_PIN behavior. Fortunately, the gup_benchmark unit test is extremely fast (a few milliseconds), so adding it the the run_vmtests suite is going to cause no noticeable change in running time. So, add two new invocations to run_vmtests: 1) R

[PATCH v7 16/24] net/xdp: set FOLL_PIN via pin_user_pages()

2019-11-20 Thread John Hubbard
Convert net/xdp to use the new pin_longterm_pages() call, which sets FOLL_PIN. Setting FOLL_PIN is now required for code that requires tracking of pinned pages. In partial anticipation of this work, the net/xdp code was already calling put_user_page() instead of put_page(). Therefore, in order to

[PATCH v7 11/24] goldish_pipe: convert to pin_user_pages() and put_user_page()

2019-11-20 Thread John Hubbard
1. Call the new global pin_user_pages_fast(), from pin_goldfish_pages(). 2. As required by pin_user_pages(), release these pages via put_user_page(). In this case, do so via put_user_pages_dirty_lock(). That has the side effect of calling set_page_dirty_lock(), instead of set_page_dirty(). This i

[PATCH v7 17/24] mm/gup: track FOLL_PIN pages

2019-11-20 Thread John Hubbard
Add tracking of pages that were pinned via FOLL_PIN. As mentioned in the FOLL_PIN documentation, callers who effectively set FOLL_PIN are required to ultimately free such pages via put_user_page(). The effect is similar to FOLL_GET, and may be thought of as "FOLL_GET for DIO and/or RDMA use". Pag

[PATCH v7 02/24] mm/gup: factor out duplicate code from four routines

2019-11-20 Thread John Hubbard
There are four locations in gup.c that have a fair amount of code duplication. This means that changing one requires making the same changes in four places, not to mention reading the same code four times, and wondering if there are subtle differences. Factor out the common code into static functi

[PATCH v7 13/24] mm/process_vm_access: set FOLL_PIN via pin_user_pages_remote()

2019-11-20 Thread John Hubbard
Convert process_vm_access to use the new pin_user_pages_remote() call, which sets FOLL_PIN. Setting FOLL_PIN is now required for code that requires tracking of pinned pages. Also, release the pages via put_user_page*(). Also, rename "pages" to "pinned_pages", as this makes for easier reading of p

[PATCH v7 05/24] mm: devmap: refactor 1-based refcounting for ZONE_DEVICE pages

2019-11-20 Thread John Hubbard
An upcoming patch changes and complicates the refcounting and especially the "put page" aspects of it. In order to keep everything clean, refactor the devmap page release routines: * Rename put_devmap_managed_page() to page_is_devmap_managed(), and limit the functionality to "read only": return

[PATCH v7 04/24] mm: Cleanup __put_devmap_managed_page() vs ->page_free()

2019-11-20 Thread John Hubbard
From: Dan Williams After the removal of the device-public infrastructure there are only 2 ->page_free() call backs in the kernel. One of those is a device-private callback in the nouveau driver, the other is a generic wakeup needed in the DAX case. In the hopes that all ->page_free() callbacks ca

[PATCH v7 01/24] mm/gup: pass flags arg to __gup_device_* functions

2019-11-20 Thread John Hubbard
A subsequent patch requires access to gup flags, so pass the flags argument through to the __gup_device_* functions. Also placate checkpatch.pl by shortening a nearby line. Reviewed-by: Jan Kara Reviewed-by: Jérôme Glisse Reviewed-by: Ira Weiny Cc: Kirill A. Shutemov Signed-off-by: John Hubba

[PATCH v7 14/24] drm/via: set FOLL_PIN via pin_user_pages_fast()

2019-11-20 Thread John Hubbard
Convert drm/via to use the new pin_user_pages_fast() call, which sets FOLL_PIN. Setting FOLL_PIN is now required for code that requires tracking of pinned pages, and therefore for any code that calls put_user_page(). In partial anticipation of this work, the drm/via driver was already calling put_

[PATCH v7 12/24] IB/{core, hw, umem}: set FOLL_PIN via pin_user_pages*(), fix up ODP

2019-11-20 Thread John Hubbard
Convert infiniband to use the new pin_user_pages*() calls. Also, revert earlier changes to Infiniband ODP that had it using put_user_page(). ODP is "Case 3" in Documentation/core-api/pin_user_pages.rst, which is to say, normal get_user_pages() and put_page() is the API to use there. The new pin_u

[PATCH v4 6/6] drm/komeda: Expose side_by_side by sysfs/config_id

2019-11-20 Thread james qian wang (Arm Technology China)
There are some restrictions if HW works on side_by_side, expose it via config_id to user. Signed-off-by: James Qian Wang (Arm Technology China) --- drivers/gpu/drm/arm/display/include/malidp_product.h | 3 ++- drivers/gpu/drm/arm/display/komeda/komeda_dev.c | 1 + 2 files changed, 3 inserti

[PATCH v4 5/6] drm/komeda: Update writeback signal for side_by_side

2019-11-20 Thread james qian wang (Arm Technology China)
In side by side mode, a writeback job is completed by two pipelines: left by master and right by slave, we need to wait both pipeline finished (EOW), then can signal the writeback job completion. Signed-off-by: James Qian Wang (Arm Technology China) --- .../gpu/drm/arm/display/komeda/komeda_crtc

[PATCH v7 08/24] media/v4l2-core: set pages dirty upon releasing DMA buffers

2019-11-20 Thread John Hubbard
After DMA is complete, and the device and CPU caches are synchronized, it's still required to mark the CPU pages as dirty, if the data was coming from the device. However, this driver was just issuing a bare put_page() call, without any set_page_dirty*() call. Fix the problem, by calling set_page_

[PATCH v4 4/6] drm/komeda: Add side by side support for writeback

2019-11-20 Thread james qian wang (Arm Technology China)
In side by side mode, the master pipeline writeback the left frame and the slave writeback the right part, the data flow as below: slave.compiz -> slave.wb_layer -> fb (right-part) master.compiz -> master.wb_layer -> fb (left-part) Signed-off-by: James Qian Wang (Arm Technology China) --- .

[PATCH v4 3/6] drm/komeda: Build side by side display output pipeline

2019-11-20 Thread james qian wang (Arm Technology China)
For side by side, the slave pipeline merges to master via image processor slave-layers -> slave-compiz-> slave-improc- \ master-layers -> master-compiz -> master-improc -> v3: Rebase. Signed-off-by: James Qian Wang (Arm Technology China)

[PATCH v4 1/6] drm/komeda: Add side by side assembling

2019-11-20 Thread james qian wang (Arm Technology China)
Komeda HW can support side by side, which splits the internal display processing to two single halves (LEFT/RIGHT) and handle them by two pipelines separately. komeda "side by side" is enabled by DT property: "side_by_side_master", once DT configured side by side, komeda need to verify it with HW's

[PATCH v4 2/6] drm/komeda: Add side by side plane_state split

2019-11-20 Thread james qian wang (Arm Technology China)
On side by side mode, The full display frame will be split into two parts (Left/Right), and each part will be handled by a single pipeline separately master pipeline for left part, slave for right. To simplify the usage and implementation, komeda use the following scheme to do the side by side spl

[PATCH v4 0/6] arm/komeda: Add side_by_side support

2019-11-20 Thread james qian wang (Arm Technology China)
Hi: All Komeda HW (two pipelines) can work on side by side mode, which splits the internal display processing to two halves (LEFT/RIGHT) and handle them by two pipelines separately and simultaneously. And since one single pipeline only handles the half display frame, so the main engine clock requi

Re: drm/komeda: Remove unnecessary komeda_wb_connector_detect

2019-11-20 Thread james qian wang (Arm Technology China)
On Wed, Nov 20, 2019 at 12:03:55PM +, Mihail Atanassov wrote: > The func is optional and the connector will report as always connected, > i.e. no change in behaviour. > > Signed-off-by: Mihail Atanassov > --- > drivers/gpu/drm/arm/display/komeda/komeda_wb_connector.c | 7 --- > 1 file ch

[PATCH v3] video: Fix Kconfig indentation

2019-11-20 Thread Krzysztof Kozlowski
Adjust indentation from spaces to tab (+optional two spaces) as in coding style with command like: $ sed -e 's/^/\t/' -i */Kconfig Signed-off-by: Krzysztof Kozlowski Acked-by: Bartlomiej Zolnierkiewicz --- Changes since v2: 1. Add Bartlomiej's ack. Changes since v1: 1. Fix als

linux-next: build failure after merge of the tip tree

2019-11-20 Thread Stephen Rothwell
Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/trace/define_trace.h:102, from drivers/gpu/drm/amd/amdgpu/amdgpu_trace.h:502, from drivers/gpu/drm/amd/amdgpu/amdgpu_trace_points.c:

[PATCH v2] video: Fix Kconfig indentation

2019-11-20 Thread Krzysztof Kozlowski
Adjust indentation from spaces to tab (+optional two spaces) as in coding style with command like: $ sed -e 's/^/\t/' -i */Kconfig Signed-off-by: Krzysztof Kozlowski --- Changes since v1: 1. Fix also 7-space and tab+1 space indentation issues. --- drivers/video/Kconfig

Re: [PATCH V13 4/6] mdev: introduce mediated virtio bus

2019-11-20 Thread Jason Wang
On 2019/11/20 下午9:49, Jason Gunthorpe wrote: On Wed, Nov 20, 2019 at 10:14:26AM +0800, Jason Wang wrote: I don't quite get the question here. In the driver model the bus_type and foo_device are closely linked. I don't get the definition of "closely linked" here. Do you think the bus and devi

Re: [PATCH] drm/msm: Don't init ww_mutec acquire ctx before needed

2019-11-20 Thread Rob Clark
On Wed, Nov 20, 2019 at 2:56 AM Daniel Vetter wrote: > > For locking semantics it really doesn't matter when we grab the > ticket. But for lockdep validation it does: the acquire ctx is a fake > lockdep. Since other drivers might want to do a full multi-lock dance > in their fault-handler, not jus

[pull] amdgpu drm-fixes-5.4

2019-11-20 Thread Alex Deucher
Hi Dave, Daniel, A few fixes for 5.4. Stability and regression fixes. Most CCed to stable. The following changes since commit af42d3466bdc8f39806b26f593604fdc54140bcb: Linux 5.4-rc8 (2019-11-17 14:47:30 -0800) are available in the Git repository at: git://people.freedesktop.org/~agd5f/lin

Re: [PATCH v4] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-11-20 Thread Rafael J. Wysocki
On Wed, Nov 20, 2019 at 10:40 PM Karol Herbst wrote: > > On Wed, Nov 20, 2019 at 10:37 PM Rafael J. Wysocki wrote: > > > > On Wed, Nov 20, 2019 at 4:53 PM Mika Westerberg > > wrote: > > > > > > On Wed, Nov 20, 2019 at 04:37:14PM +0100, Karol Herbst wrote: > > > > On Wed, Nov 20, 2019 at 4:15 PM

[PATCH 0/1] drm/panel: simple: Add support for BOE NV140FHM-N49 panel to panel-simple

2019-11-20 Thread Tobias Schramm
This patch adds support for the 14 inch BOE NV140FHM-N49 eDP panel to the panel-simple driver. This panel is used by the Pinebook Pro. Tobias Schramm (1): drm/panel: simple: Add support for BOE NV140FHM-N49 panel to panel-simple drivers/gpu/drm/panel/panel-simple.c | 35 +++

[PATCH 1/1] drm/panel: simple: Add support for BOE NV140FHM-N49 panel to panel-simple

2019-11-20 Thread Tobias Schramm
This patch adds support for the BOE NV140FHM-N49 panel to the panel-simple driver. The panel is used by the pine64 Pinebook Pro. Signed-off-by: Tobias Schramm --- drivers/gpu/drm/panel/panel-simple.c | 35 1 file changed, 35 insertions(+) diff --git a/drivers/gpu/dr

Re: [PATCH v4] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-11-20 Thread Karol Herbst
On Wed, Nov 20, 2019 at 10:37 PM Rafael J. Wysocki wrote: > > On Wed, Nov 20, 2019 at 4:53 PM Mika Westerberg > wrote: > > > > On Wed, Nov 20, 2019 at 04:37:14PM +0100, Karol Herbst wrote: > > > On Wed, Nov 20, 2019 at 4:15 PM Mika Westerberg > > > wrote: > > > > > > > > On Wed, Nov 20, 2019 at

Re: [PATCH v4] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-11-20 Thread Rafael J. Wysocki
On Wed, Nov 20, 2019 at 4:53 PM Mika Westerberg wrote: > > On Wed, Nov 20, 2019 at 04:37:14PM +0100, Karol Herbst wrote: > > On Wed, Nov 20, 2019 at 4:15 PM Mika Westerberg > > wrote: > > > > > > On Wed, Nov 20, 2019 at 01:11:52PM +0100, Karol Herbst wrote: > > > > On Wed, Nov 20, 2019 at 1:09 PM

Re: [PATCH v4] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-11-20 Thread Karol Herbst
with the branch and patch applied: https://gist.githubusercontent.com/karolherbst/03c4c8141b0fa292d781badfa186479e/raw/5c62640afbc57d6e69ea924c338bd2836e770d02/gistfile1.txt On Wed, Nov 20, 2019 at 5:23 PM Mika Westerberg wrote: > > On Wed, Nov 20, 2019 at 05:53:07PM +0200, Mika Westerberg wrote:

[PULL] drm-misc-next-fixes

2019-11-20 Thread Sean Paul
Hi Dave & Daniel, Just one patch this week which fixes the bo refcounts when mmap'ing ttm buffers using the new ->mmap() hook. drm-misc-next-fixes-2019-11-20: - Fix ttm bo refcnt when using the new gem obj mmap hook (Thomas) Cc: Gerd Hoffmann Cheers, Sean The following changes since commit

[PULL] drm-intel-next-fixes

2019-11-20 Thread Joonas Lahtinen
Hi Dave & Daniel, NOTE: CI shard results are delayed, bu I'm sending this already because I'll travel tomorrow. I'll let you know if the results look OK or not. Or you can look up CI_DINF_162 results check at: https://intel-gfx-ci.01.org/tree/drm-intel-next-fixes/combined-alt.html This was rebas

[Bug 205589] Green screen crash with 3400G

2019-11-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205589 --- Comment #3 from p...@spth.de --- The bug ist still there with AGESA 1.0.0.4 B BIOS. dmesg: http://www.colecovision.eu/stuff/dmesg-log2 Xorg: http://www.colecovision.eu/stuff/Xorg.0.log http://www.colecovision.eu/stuff/Xorg.0.log.old http:/

Re: [PATCH] drm/mcde: dsi: Fix invalid pointer dereference if panel cannot be found

2019-11-20 Thread Linus Walleij
On Mon, Nov 18, 2019 at 2:04 PM Stephan Gerhold wrote: > The "panel" pointer is not reset to NULL if of_drm_find_panel() > returns an error. Therefore we later assume that a panel was found, > and try to dereference the error pointer, resulting in: > > mcde-dsi a0351000.dsi: failed to find pa

Re: [PATCH] drm/mcde: Support using DSI in LP mode

2019-11-20 Thread Linus Walleij
On Tue, Nov 19, 2019 at 10:42 PM Linus Walleij wrote: > It is possible to set a flag in the struct mipi_dsi_device > so the panel is handled in low power (LP) mode. Some displays > only support this mode and it is also good for testing. > > Cc: Stephan Gerhold > Signed-off-by: Linus Walleij In

[Bug 205585] [Regression] [amdgpu] AMD Vega 64 GPU invalid access and EEH under load

2019-11-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205585 --- Comment #2 from Timothy Pearson (tpear...@raptorengineering.com) --- I am travelling now but can bisect when back at the lab next week. -- You are receiving this mail because: You are watching the assignee of the bug. ___

linux-next - DEBUG_MUTEX=y causes message flood

2019-11-20 Thread Valdis Klētnieks
I haven't narrowed down when this started, other than "sometime between 10/23 and 11/13". Looks to me like something in the i915/DRM arena doesn't play nice with mutex debugging. The system still acts fine, but my /var partition filled up due to gigabytes of the following two warning calls repeat

Re: [PATCH][next] drm/dp_mst: fix multiple frees of tx->bytes

2019-11-20 Thread Lyude Paul
On Wed, 2019-11-20 at 19:11 +, Colin Ian King wrote: > On 20/11/2019 18:59, Lyude Paul wrote: > > Heh, surprised I missed this one! > > > > Reviewed-by: Lyude Paul > > > > Do you need me to push this to drm-misc, or do you have commit rights > > already > > I have no commit rights. Gotcha:

Re: [PATCH][next] drm/dp_mst: fix multiple frees of tx->bytes

2019-11-20 Thread Colin Ian King
On 20/11/2019 18:59, Lyude Paul wrote: > Heh, surprised I missed this one! > > Reviewed-by: Lyude Paul > > Do you need me to push this to drm-misc, or do you have commit rights already I have no commit rights. > > On Wed, 2019-11-20 at 17:35 +, Colin King wrote: >> From: Colin Ian King

Re: [PATCH][next] drm/dp_mst: fix multiple frees of tx->bytes

2019-11-20 Thread Lyude Paul
Heh, surprised I missed this one! Reviewed-by: Lyude Paul Do you need me to push this to drm-misc, or do you have commit rights already? On Wed, 2019-11-20 at 17:35 +, Colin King wrote: > From: Colin Ian King > > Currently tx->bytes is being freed r->num_transactions number of > times bec

[PATCH][next] drm/dp_mst: fix multiple frees of tx->bytes

2019-11-20 Thread Colin King
From: Colin Ian King Currently tx->bytes is being freed r->num_transactions number of times because tx is not being set correctly. Fix this by setting tx to &r->transactions[i] so that the correct objects are being freed on each loop iteration. Addresses-Coverity: ("Double free") Fixes: 2f015ec6

[Bug 205589] Green screen crash with 3400G

2019-11-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205589 --- Comment #2 from p...@spth.de --- Out of the three Manjaro reports, only one is about the 3400G, the other two are about the 2400G, but the symptoms seem to be the same. My dmesg output is at: http://www.colecovision.eu/stuff/dmesg-log In 5.

[PATCH][next] drm/amd/display: fix double assignment to msg_id field

2019-11-20 Thread Colin King
From: Colin Ian King The msg_id field is being assigned twice. Fix this by replacing the second assignment with an assignment to msg_size. Addresses-Coverity: ("Unused value") Fixes: 11a00965d261 ("drm/amd/display: Add PSP block to verify HDCP2.2 steps") Signed-off-by: Colin Ian King --- drive

Re: [Intel-gfx] [PATCH 2/2] drm/rect: Keep the clipped dst rectangle in place

2019-11-20 Thread Ville Syrjälä
On Wed, Nov 20, 2019 at 05:43:40PM +0100, Daniel Vetter wrote: > On Wed, Nov 20, 2019 at 06:25:12PM +0200, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > Now that we've constrained the clipped source rectangle such > > that it can't have negative dimensions doing the same for the > > dst re

Re: [Intel-gfx] linux-next: Tree for Nov 19 (i915)

2019-11-20 Thread Chris Wilson
Quoting Jani Nikula (2019-11-20 16:15:08) > On Tue, 19 Nov 2019, Randy Dunlap wrote: > > On 11/19/19 12:46 AM, Stephen Rothwell wrote: > >> Hi all, > >> > >> Changes since 20191118: > > > > > > on x86_64: > > > > ERROR: "pm_suspend_target_state" [drivers/gpu/drm/i915/i915.ko] undefined! > > > > #

Re: [PATCH] staging: fbtft: Fix Kconfig indentation

2019-11-20 Thread Greg Kroah-Hartman
On Wed, Nov 20, 2019 at 05:41:55PM +0100, Daniel Vetter wrote: > On Wed, Nov 20, 2019 at 09:39:11PM +0800, Krzysztof Kozlowski wrote: > > Adjust indentation from spaces to tab (+optional two spaces) as in > > coding style with command like: > > $ sed -e 's/^/\t/' -i */Kconfig > > > > S

Re: [PATCH 1/2] dt-bindings: display: Add xylon logicvc bindings documentation

2019-11-20 Thread Paul Kocialkowski
Hi, On Wed 20 Nov 19, 10:02, Rob Herring wrote: > On Wed, Nov 20, 2019 at 8:50 AM Paul Kocialkowski > wrote: > > > > Hi, > > > > Circling back to this thread now, sorry for the delay. > > > > On Tue 24 Sep 19, 09:58, Rob Herring wrote: > > > On Mon, Sep 23, 2019 at 10:33 AM Paul Kocialkowski > >

Re: [Intel-gfx] [PATCH 2/2] drm/rect: Keep the clipped dst rectangle in place

2019-11-20 Thread Daniel Vetter
On Wed, Nov 20, 2019 at 06:25:12PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Now that we've constrained the clipped source rectangle such > that it can't have negative dimensions doing the same for the > dst rectangle seems appropriate. Should at least result in > the clipped src and

Re: [PATCH] staging: fbtft: Fix Kconfig indentation

2019-11-20 Thread Daniel Vetter
On Wed, Nov 20, 2019 at 09:39:11PM +0800, Krzysztof Kozlowski wrote: > Adjust indentation from spaces to tab (+optional two spaces) as in > coding style with command like: > $ sed -e 's/^/\t/' -i */Kconfig > > Signed-off-by: Krzysztof Kozlowski Acked-by: Daniel Vetter I expect Gr

Re: [PATCH] drm/bridge: Fix Kconfig indentation

2019-11-20 Thread Daniel Vetter
On Wed, Nov 20, 2019 at 09:36:34PM +0800, Krzysztof Kozlowski wrote: > Adjust indentation from spaces to tab (+optional two spaces) as in > coding style with command like: > $ sed -e 's/^/\t/' -i */Kconfig > > Signed-off-by: Krzysztof Kozlowski lima, mga200g and bridge patches also

Re: [PATCH] drm/nouveau: Fix Kconfig indentation

2019-11-20 Thread Daniel Vetter
On Wed, Nov 20, 2019 at 09:36:19PM +0800, Krzysztof Kozlowski wrote: > Adjust indentation from spaces to tab (+optional two spaces) as in > coding style with command like: > $ sed -e 's/^/\t/' -i */Kconfig > > Signed-off-by: Krzysztof Kozlowski Queued for 5.6 in drm-misc, thanks fo

Re: [PATCH] drm/omap: Fix Kconfig indentation

2019-11-20 Thread Daniel Vetter
On Wed, Nov 20, 2019 at 09:36:14PM +0800, Krzysztof Kozlowski wrote: > Adjust indentation from spaces to tab (+optional two spaces) as in > coding style with command like: > $ sed -e 's/^/\t/' -i */Kconfig > > Signed-off-by: Krzysztof Kozlowski Queued for 5.6 in drm-misc, thanks fo

Re: [PATCH] drm/rockchip: Fix Kconfig indentation

2019-11-20 Thread Daniel Vetter
On Wed, Nov 20, 2019 at 09:33:48PM +0800, Krzysztof Kozlowski wrote: > Adjust indentation from spaces to tab (+optional two spaces) as in > coding style with command like: > $ sed -e 's/^/\t/' -i */Kconfig > > Signed-off-by: Krzysztof Kozlowski Queued for 5.6 in drm-misc, thanks fo

Re: [PATCH] drm/udl: Fix Kconfig indentation

2019-11-20 Thread Daniel Vetter
On Wed, Nov 20, 2019 at 09:33:41PM +0800, Krzysztof Kozlowski wrote: > Adjust indentation from spaces to tab (+optional two spaces) as in > coding style with command like: > $ sed -e 's/^/\t/' -i */Kconfig > > Signed-off-by: Krzysztof Kozlowski Queued for 5.6 in drm-misc, thanks fo

Re: [PATCH] vga: Fix Kconfig indentation

2019-11-20 Thread Daniel Vetter
On Wed, Nov 20, 2019 at 09:33:27PM +0800, Krzysztof Kozlowski wrote: > Adjust indentation from spaces to tab (+optional two spaces) as in > coding style with command like: > $ sed -e 's/^/\t/' -i */Kconfig > > Signed-off-by: Krzysztof Kozlowski Queued for 5.6 in drm-misc, thanks fo

[PATCH 1/2] drm/rect: Keep the scaled clip bounded

2019-11-20 Thread Ville Syrjala
From: Ville Syrjälä Limit the scaled clip to only clip at most dst_w/h pixels. This avoids the problem with clip_scaled() not being able to return negative values. Since new_src_w/h is now properly bounded we can remove the clamp()s. Cc: Benjamin Gaignard Cc: Maarten Lankhorst Signed-off-by: V

Re: [PATCH] drm/rect: remove useless call to clamp_t

2019-11-20 Thread Ville Syrjälä
On Wed, Nov 20, 2019 at 05:22:34PM +0200, Ville Syrjälä wrote: > On Tue, Nov 19, 2019 at 02:34:35PM +0100, Benjamin Gaignard wrote: > > Clamping a value between INT_MIN and INT_MAX always return the value itself > > and generate warnings when compiling with W=1. > > > > Signed-off-by: Benjamin Gai

[PATCH 2/2] drm/rect: Keep the clipped dst rectangle in place

2019-11-20 Thread Ville Syrjala
From: Ville Syrjälä Now that we've constrained the clipped source rectangle such that it can't have negative dimensions doing the same for the dst rectangle seems appropriate. Should at least result in the clipped src and dst rectangles being a bit more consistent with each other. Cc: Benjamin G

Re: [PATCH v4] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-11-20 Thread Mika Westerberg
On Wed, Nov 20, 2019 at 05:53:07PM +0200, Mika Westerberg wrote: > On Wed, Nov 20, 2019 at 04:37:14PM +0100, Karol Herbst wrote: > > On Wed, Nov 20, 2019 at 4:15 PM Mika Westerberg > > wrote: > > > > > > On Wed, Nov 20, 2019 at 01:11:52PM +0100, Karol Herbst wrote: > > > > On Wed, Nov 20, 2019 at

Re: [Intel-gfx] linux-next: Tree for Nov 19 (i915)

2019-11-20 Thread Jani Nikula
On Tue, 19 Nov 2019, Randy Dunlap wrote: > On 11/19/19 12:46 AM, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20191118: > > > on x86_64: > > ERROR: "pm_suspend_target_state" [drivers/gpu/drm/i915/i915.ko] undefined! > > # CONFIG_SUSPEND is not set a70a9e998e8e ("drm/i915: Defer rc6 shu

Re: [PATCH 1/2] dt-bindings: display: Add xylon logicvc bindings documentation

2019-11-20 Thread Rob Herring
On Wed, Nov 20, 2019 at 8:50 AM Paul Kocialkowski wrote: > > Hi, > > Circling back to this thread now, sorry for the delay. > > On Tue 24 Sep 19, 09:58, Rob Herring wrote: > > On Mon, Sep 23, 2019 at 10:33 AM Paul Kocialkowski > > wrote: > > > > > > Hi, > > > > > > On Fri 13 Sep 19, 20:16, Rob He

Re: [PATCH v4] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-11-20 Thread Mika Westerberg
On Wed, Nov 20, 2019 at 04:37:14PM +0100, Karol Herbst wrote: > On Wed, Nov 20, 2019 at 4:15 PM Mika Westerberg > wrote: > > > > On Wed, Nov 20, 2019 at 01:11:52PM +0100, Karol Herbst wrote: > > > On Wed, Nov 20, 2019 at 1:09 PM Mika Westerberg > > > wrote: > > > > > > > > On Wed, Nov 20, 2019 at

[Bug 205589] Green screen crash with 3400G

2019-11-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205589 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.c

Re: [PATCH v4] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-11-20 Thread Karol Herbst
On Wed, Nov 20, 2019 at 4:15 PM Mika Westerberg wrote: > > On Wed, Nov 20, 2019 at 01:11:52PM +0100, Karol Herbst wrote: > > On Wed, Nov 20, 2019 at 1:09 PM Mika Westerberg > > wrote: > > > > > > On Wed, Nov 20, 2019 at 12:58:00PM +0100, Karol Herbst wrote: > > > > overall, what I really want to

Re: [PATCH] drm/rect: remove useless call to clamp_t

2019-11-20 Thread Ville Syrjälä
On Tue, Nov 19, 2019 at 02:34:35PM +0100, Benjamin Gaignard wrote: > Clamping a value between INT_MIN and INT_MAX always return the value itself > and generate warnings when compiling with W=1. > > Signed-off-by: Benjamin Gaignard > --- > drivers/gpu/drm/drm_rect.c | 8 > 1 file changed

[Bug 205585] [Regression] [amdgpu] AMD Vega 64 GPU invalid access and EEH under load

2019-11-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205585 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.c

Re: [PATCH v4] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

2019-11-20 Thread Mika Westerberg
On Wed, Nov 20, 2019 at 01:11:52PM +0100, Karol Herbst wrote: > On Wed, Nov 20, 2019 at 1:09 PM Mika Westerberg > wrote: > > > > On Wed, Nov 20, 2019 at 12:58:00PM +0100, Karol Herbst wrote: > > > overall, what I really want to know is, _why_ does it work on windows? > > > > So do I ;-) > > > > >

Re: [PATCH v2 3/3] drm/i915: Add support for integrated privacy screens

2019-11-20 Thread Jani Nikula
On Tue, 12 Nov 2019, Rajat Jain wrote: > On Mon, Nov 4, 2019 at 11:41 AM Rajat Jain wrote: >> >> Certain laptops now come with panels that have integrated privacy >> screens on them. This patch adds support for such panels by adding >> a privacy-screen property to the intel_connector for the pane

Re: [PATCH v2 3/3] drm/i915: Add support for integrated privacy screens

2019-11-20 Thread Jani Nikula
On Mon, 04 Nov 2019, Rajat Jain wrote: > Certain laptops now come with panels that have integrated privacy > screens on them. This patch adds support for such panels by adding > a privacy-screen property to the intel_connector for the panel, that > the userspace can then use to control and check t

Re: [PATCH v1 3/5] fbtft: Drop useless #ifdef CONFIG_OF and dead code

2019-11-20 Thread Noralf Trønnes
Den 20.11.2019 15.43, skrev Noralf Trønnes: > > > Den 20.11.2019 10.57, skrev Andy Shevchenko: >> First of all there is no need to guard GPIO request by CONFIG_OF. >> It works for everybody independently on resource provider. While here, >> rename the function to reflect the above. >> >> Moreov

Re: [PATCH v3 1/2] dt-bindings: display: Document the Xylon LogiCVC display controller

2019-11-20 Thread Paul Kocialkowski
Hi, On Fri 27 Sep 19, 17:20, Rob Herring wrote: > On Fri, Sep 27, 2019 at 12:07:37PM +0200, Paul Kocialkowski wrote: > > The Xylon LogiCVC is a display controller implemented as programmable > > logic in Xilinx FPGAs. > > > > Signed-off-by: Paul Kocialkowski > > --- > > .../display/xylon,logicv

Re: [PATCH v2 2/3] drm/i915: Lookup and attach ACPI device node for connectors

2019-11-20 Thread Jani Nikula
On Mon, 04 Nov 2019, Rajat Jain wrote: > Lookup and attach ACPI nodes for intel connectors. The lookup is done > in compliance with ACPI Spec 6.3 > https://uefi.org/sites/default/files/resources/ACPI_6_3_final_Jan30.pdf > (Ref: Pages 1119 - 1123). > > This can be useful for any connector specific

Re: [PATCH 1/2] dt-bindings: display: Add xylon logicvc bindings documentation

2019-11-20 Thread Paul Kocialkowski
Hi, Circling back to this thread now, sorry for the delay. On Tue 24 Sep 19, 09:58, Rob Herring wrote: > On Mon, Sep 23, 2019 at 10:33 AM Paul Kocialkowski > wrote: > > > > Hi, > > > > On Fri 13 Sep 19, 20:16, Rob Herring wrote: > > > On Fri, Sep 13, 2019 at 4:58 PM Paul Kocialkowski > > > wrot

Re: [PATCH v1 3/5] fbtft: Drop useless #ifdef CONFIG_OF and dead code

2019-11-20 Thread Noralf Trønnes
Den 20.11.2019 10.57, skrev Andy Shevchenko: > First of all there is no need to guard GPIO request by CONFIG_OF. > It works for everybody independently on resource provider. While here, > rename the function to reflect the above. > > Moreover, since we have a global dependency to OF, the rest of

Re: [PATCH v2 1/3] drm/i915: Move the code to populate ACPI device ID into intel_acpi

2019-11-20 Thread Jani Nikula
On Mon, 04 Nov 2019, Rajat Jain wrote: > Move the code that populates the ACPI device ID for devices, into > more appripriate intel_acpi.c. This is done in preparation for more > users of this code (in next patch). I don't think your use of the code makes sense (I'll explain in reply to the other

Re: [PATCH] drm/rect: remove useless call to clamp_t

2019-11-20 Thread Jani Nikula
On Tue, 19 Nov 2019, Benjamin Gaignard wrote: > Clamping a value between INT_MIN and INT_MAX always return the value itself > and generate warnings when compiling with W=1. Does that hold for 32-bit too? BR, Jani. > > Signed-off-by: Benjamin Gaignard > --- > drivers/gpu/drm/drm_rect.c | 8 +++

Re: [PATCH] drm: Fix Kconfig indentation

2019-11-20 Thread Jani Nikula
On Wed, 20 Nov 2019, Krzysztof Kozlowski wrote: > Adjust indentation from spaces to tab (+optional two spaces) as in > coding style with command like: > $ sed -e 's/^/\t/' -i */Kconfig > > Signed-off-by: Krzysztof Kozlowski > --- > drivers/gpu/drm/Kconfig | 30 +++--

  1   2   >