Dne četrtek, 26. julij 2018 ob 19:12:57 CEST je Icenowy Zheng napisal(a):
> From: Jagan Teki
>
> Enable all necessary device tree nodes and add connector node to device
> trees for all supported A64 boards with HDMI.
>
> Signed-off-by: Jagan Teki
> [Icenowy: squash all board patches altogether
From: Jernej Skrabec
Some boards have HDMI VCC pin connected to voltage regulator which may
not be turned on by default.
Add support for such boards by adding voltage regulator handling code to
HDMI driver.
Signed-off-by: Jernej Skrabec
Signed-off-by: Icenowy Zheng
---
Changes in v3.1:
- New
Dne četrtek, 26. julij 2018 ob 19:12:48 CEST je Icenowy Zheng napisal(a):
> From: Jagan Teki
>
> According to documentation and experience with other similar SoCs, video
> PLLs don't work stable if their output frequency is set below 192 MHz.
>
> Because of that, set minimal rate to both A64 vid
From: Jagan Teki
Display Engine(DE2) in Allwinner A64 has two mixers and tcons.
The routing for mixer0 is through tcon0 and connected to
LVDS/RGB/MIPI-DSI controller.
The routing for mixer1 is through tcon1 and connected to HDMI.
Signed-off-by: Jagan Teki
Signed-off-by: Icenowy Zheng
---
Cha
This allows device drivers to convey the drivers core that implicit IOMMU
backing for devices DMA shouldn't happen. It is needed for drivers that
manage IOMMU by themselves, like for example it is needed by the NVIDIA
Tegra GPU driver.
Signed-off-by: Dmitry Osipenko
---
include/linux/device.h |
Host1x driver manages IOMMU by itself, backing DMA with IOMMU by the
drivers core breaks the Host1x driver.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/host1x/dev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/host1x/dev.c b/drivers/gpu/host1x/dev.c
index afabd33a48d9..0966
Use new return type vm_fault_t for fault handler.
Signed-off-by: Souptick Joarder
---
v2: Updated patch title
drivers/gpu/drm/vkms/vkms_drv.h | 2 +-
drivers/gpu/drm/vkms/vkms_gem.c | 5 ++---
2 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/vkms/vkms_drv.h b/drive
From: Jagan Teki
Allwinner A64 has two clock parents PLL_VIDEO0 and PLL_VIDEO1.
Include these macros on dt-bindings so-that the same can be
used while defining CCU clock phadles.
Signed-off-by: Jagan Teki
Reviewed-by: Rob Herring
Signed-off-by: Icenowy Zheng
---
Changes for v3.1:
- none
Chan
Dne četrtek, 26. julij 2018 ob 19:12:53 CEST je Icenowy Zheng napisal(a):
> From: Jagan Teki
>
> Allwinner A64 has two clock parents PLL_VIDEO0 and PLL_VIDEO1.
>
> Include these macros on dt-bindings so-that the same can be
> used while defining CCU clock phadles.
>
> Signed-off-by: Jagan Teki
convert drm_atomic_helper_suspend/resume() to use
drm_mode_config_helper_suspend/resume().
exynos_drm_fbdev_suspend/resume can be removed
as drm_mode_config_helper_suspend/resume has
implement the same in generic way.
Signed-off-by: Souptick Joarder
Signed-off-by: Ajit Negi
---
v2: Address Inki
From: Jagan Teki
Mixers in Allwinner have similar capabilities as others SoCs with DE2.
Add support for them.
Signed-off-by: Jagan Teki
[Icenowy: Add mixer0]
Signed-off-by: Icenowy Zheng
---
Changes for v3.1:
- Add mixer0
Changes for v3:
- none
Changes for v2:
- New patch
drivers/gpu/drm/s
On Thu, Jul 19, 2018 at 9:34 PM, Souptick Joarder wrote:
> convert drm_atomic_helper_suspend/resume() to use
> drm_mode_config_helper_suspend/resume().
>
> Fixed one sparse warning by making hibmc_drm_interrupt
> static.
>
> Signed-off-by: Souptick Joarder
> Signed-off-by: Ajit Negi
> ---
Any c
Respect device driver requirement for device DMA not to be implicitly
backed with IOMMU by skipping the backing setup for drivers that do not
want that.
Signed-off-by: Dmitry Osipenko
---
drivers/of/device.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/of/device.c b/drivers
于 2018年7月27日 GMT+08:00 上午2:03:00, "Jernej Škrabec" 写到:
>Dne četrtek, 26. julij 2018 ob 19:12:57 CEST je Icenowy Zheng
>napisal(a):
>> From: Jagan Teki
>>
>> Enable all necessary device tree nodes and add connector node to
>device
>> trees for all supported A64 boards with HDMI.
>>
>> Signed-o
From: Jagan Teki
The HDMI controller on Allwinner A64 is similar on the one on
H3/H5/A83T (although the PHY is different with A83T).
Add A64 compatible and append A83T compatible as fallback.
Signed-off-by: Jagan Teki
Reviewed-by: Rob Herring
[Icenowy: refactor commit log]
Signed-off-by: Icen
Tegra DRM manages IOMMU by itself, backing DMA with IOMMU by the drivers
core breaks the Tegra driver.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/tegra/dc.c | 1 +
drivers/gpu/drm/tegra/gr2d.c | 1 +
drivers/gpu/drm/tegra/gr3d.c | 1 +
drivers/gpu/drm/tegra/vic.c | 1 +
4 files change
Hello,
There is a trouble on ARM with DMA allocations made by device drivers,
the trouble is that DMA allocations are getting implicitly backed with
IOMMU mapping by the driver core if IOMMU presents in a system and IOMMU
could handle device. This is an undesired behaviour for drivers that
manage
From: Jagan Teki
According to documentation and experience with other similar SoCs, video
PLLs don't work stable if their output frequency is set below 192 MHz.
Because of that, set minimal rate to both A64 video PLLs to 192 MHz.
Signed-off-by: Jagan Teki
Signed-off-by: Icenowy Zheng
---
Chan
Implicit backing DMA with IOMMU breaks Nouveau on Tegra, the current
approach with detaching device from IOMMU that was added in commit
b59fb482b522 ("drm/nouveau: tegra: Detach from ARM DMA/IOMMU mapping")
works only for arm32 which has the CONFIG_ARM_DMA_USE_IOMMU, but not for
arm64 which doesn't
Dne četrtek, 26. julij 2018 ob 19:12:50 CEST je Icenowy Zheng napisal(a):
> From: Jagan Teki
>
> Mixers in Allwinner have similar capabilities as others SoCs with DE2.
>
> Add support for them.
>
> Signed-off-by: Jagan Teki
> [Icenowy: Add mixer0]
> Signed-off-by: Icenowy Zheng
Reviewed-by:
In Linux-4.16, drivers/video/fbdev/broadsheetfb.c,
158. static void broadsheet_mmio_send_cmdargs(...) {
..
163. par->board->mmio_write(...);
..
166. par->board->mmio_write(...);
167. }
For x86 kernel configuration, I find that there is no assignment of the
From: Jagan Teki
Allwinner A64 has a DE2 display pipeline. The TCONs are similar to the
ones in A83T, but the mixers are new (similar to the later R40 SoC).
This patch adds dt-binding documentation for A64 DE2 display pipeline.
Signed-off-by: Jagan Teki
Reviewed-by: Rob Herring
[Icenowy: Refa
On 2018/7/26 22:34, Bartlomiej Zolnierkiewicz wrote:
On Thursday, July 26, 2018 10:17:44 PM bai wrote:
In Linux-4.16, drivers/video/fbdev/broadsheetfb.c,
158. static void broadsheet_mmio_send_cmdargs(...) {
..
163. par->board->mmio_write(...);
..
166.
The "atomic" API allows us to configure PWM period and duty_cycle and
enable it in one call.
The patch also moves the pwm_init_state just before any use of the
pwm_state struct, this fixes a potential bug where pwm_get_state
can be called before pwm_init_state.
Signed-off-by: Enric Balletbo i Ser
From: Randy Dunlap
Fix build warning when built as a loadable module.
amifb_setup() and amifb_setup_mcap() are only needed when the driver
is builtin.
This matches how the functions are called (using #ifndef MODULE).
../drivers/video/fbdev/amifb.c:2344:19: warning: 'amifb_setup' defined but not
Improper DMA backing with IOMMU has been resolved now using the new
drivers core option that allows to avoid the implicit backing, hence
detaching isn't necessary anymore.
This reverts commit b59fb482b52269977ee5de205308e5b236a03917.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/nouveau/nv
Allwinner A64 has display engine pipeline like other Allwinner SOC's A83T/H3/H5.
A64 behaviour similar to Allwinner A83T where
Mixer0 => TCON0 => LVDS/RGB/MIPI-DSI
Mixer1 => TCON1 => HDMI
as per Display System Block Diagram from the A64 user manual.
This is third patch-set followed with previous
From: Jagan Teki
Allwinner A64 have a display pipeline with 2 mixers/TCONs, the first
TCON is connected to LCD and the second is to HDMI.
The HDMI controller/PHY pair is similar to the one on H3/H5, but have
two video PLLs selectable.
Add all required device tree nodes of the display pipeline,
Dne četrtek, 26. julij 2018 ob 19:12:54 CEST je Icenowy Zheng napisal(a):
> From: Jagan Teki
>
> Allwinner A64 have a display pipeline with 2 mixers/TCONs, the first
> TCON is connected to LCD and the second is to HDMI.
>
> The HDMI controller/PHY pair is similar to the one on H3/H5, but have
>
From: Jagan Teki
Enable all necessary device tree nodes and add connector node to device
trees for all supported A64 boards with HDMI.
Signed-off-by: Jagan Teki
[Icenowy: squash all board patches altogether and change supply name]
Signed-off-by: Icenowy Zheng
---
Changes in v3,1:
- Squash all
Allwiner SoCs with DesignWare HDMI controller all come with a "HVCC"
pin, which is the VCC of HDMI part.
Add a supply property to specify HVCC's regulator in the device tree.
Signed-off-by: Icenowy Zheng
---
Changes in v3.1:
- New patch.
Documentation/devicetree/bindings/display/sunxi/sun4i-dr
Hi Randy,
On Fri, Jul 27, 2018 at 2:00 AM Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix build warning when built as a loadable module.
> amifb_setup() and amifb_setup_mcap() are only needed when the driver
> is builtin.
> This matches how the functions are called (using #ifndef MODULE).
>
> .
On 26.07.2018 09:36, Archit Taneja wrote:
>
> On Wednesday 25 July 2018 09:16 PM, Andrzej Hajda wrote:
>> Add a drm_bridge driver for the Toshiba TC358764 DSI to LVDS bridge.
>>
>> Changes in v4:
>> - removed license blob,
>> - ordered includes,
>> - added error handling,
>> - fixed reset GPIO hand
https://bugs.freedesktop.org/show_bug.cgi?id=107384
--- Comment #1 from Christoph Haag ---
Some websites trigger it more often and more reliably than others. Simpler (?)
websites seem to never crash it, reddit sometimes crashes it, gitter channels
always crash it after ~2-3 seconds.
--
You are
On 25.07.2018 07:25, Masahiro Yamada wrote:
> Please do not comment out unneeded code. Remove.
>
> Signed-off-by: Masahiro Yamada
Queued to drm-misc-next.
Regards
Andrzej
> ---
>
> drivers/gpu/drm/bridge/synopsys/Makefile | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/gpu/d
https://bugs.freedesktop.org/show_bug.cgi?id=107393
Bug ID: 107393
Summary: 4.18.0-rc6 amdgpu framebuffer problems with
DisplayPort
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
https://bugs.freedesktop.org/show_bug.cgi?id=107367
--- Comment #4 from Christian König ---
(In reply to Gregor Münch from comment #3)
> This is the crash with kernel from today:
Well that is not very helpful, please add the full dmesg as attachment.
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=107367
--- Comment #5 from Christian König ---
Created attachment 140849
--> https://bugs.freedesktop.org/attachment.cgi?id=140849&action=edit
Possible fix
A shoot into the dark, but maybe the attached patch helps.
--
You are receiving this mail b
On Fri, 2018-07-27 at 14:36 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the drm tree got a conflict in:
>
> drivers/gpu/ipu-v3/ipu-cpmem.c
>
> between commit:
>
> 343b23a7c6b6 ("media: gpu: ipu-v3: Allow negative offsets for interlaced
> scanning")
>
> from th
On Friday, July 27, 2018 09:49:41 AM Jia-Ju Bai wrote:
>
> On 2018/7/26 22:34, Bartlomiej Zolnierkiewicz wrote:
> > On Thursday, July 26, 2018 10:17:44 PM bai wrote:
> >> In Linux-4.16, drivers/video/fbdev/broadsheetfb.c,
> >>
> >> 158. static void broadsheet_mmio_send_cmdargs(...) {
> >>
drm-misc-fixes-2018-07-27:
drm-misc-fixes pull request for v4.18-rc7:
- Small fixes to drm_atomic_helper_async_check(). (bbrezillon)
- Fix error handling in drm_legacy_addctx(). (Nicholas)
- Handle register reset on hotplug in adv7511. (seanpaul)
The following changes since commit 3156b53c2e2fadaf
https://bugzilla.kernel.org/show_bug.cgi?id=200661
--- Comment #2 from beta990 (francois5...@gmail.com) ---
Created attachment 277567
--> https://bugzilla.kernel.org/attachment.cgi?id=277567&action=edit
dmesg
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=200661
--- Comment #3 from beta990 (francois5...@gmail.com) ---
@Alex Deucher just had this issue again and on linux 4.17.9:
https://photos.app.goo.gl/hzELmg88ofD1Q3qg7
https://photos.app.goo.gl/WZH6vSbo1yRtNnvq7
Don't hope this is a hardware issue, but
On Fri, Jul 27, 2018 at 02:16:18AM +0300, Dmitry Osipenko wrote:
> The proposed solution adds a new option to the base device driver
> structure that allows device drivers to explicitly convey to the drivers
> core that the implicit IOMMU backing for devices must not happen.
Why is IOMMU mapping a
https://bugzilla.kernel.org/show_bug.cgi?id=200661
--- Comment #4 from Michel Dänzer (mic...@daenzer.net) ---
Does amdgpu.dc=0 on the kernel command line avoid the issue?
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=200661
beta990 (francois5...@gmail.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Resol
https://bugzilla.kernel.org/show_bug.cgi?id=200661
--- Comment #5 from beta990 (francois5...@gmail.com) ---
@Michel Dänzer @Alex Deucher Without this flag, the issue remains.
Unfortunately it seems the GPU also starts crashing in Windows, probably the
onboard memory died. :/
Thanks for looking at
Recently drm_mode_connector_attach_encoder changed it's name. The change
was not noticed by bridge author, as a result gcc reports compile error
on next branch.
Fixes: f38b7cca6d0e ("drm/bridge: tc358764: Add DSI to LVDS bridge driver")
Reported-by: kbuild test robot
Signed-off-by: Andrzej Hajda
Op 27-07-18 om 10:38 schreef Satendra Singh Thakur:
> 1.In the func drm_atomic_plane_check, the fb geometry checking code
> can be replaced by func drm_framebuffer_check_src_coords, this will
> remove several redundant lines of code.
> 2. Currently, in the func drm_atomic_plane_check;
> there are 3
Hi Andrzej,
On Friday, 27 July 2018 10:17:50 EEST Andrzej Hajda wrote:
> On 26.07.2018 09:36, Archit Taneja wrote:
> > On Wednesday 25 July 2018 09:16 PM, Andrzej Hajda wrote:
> >> Add a drm_bridge driver for the Toshiba TC358764 DSI to LVDS bridge.
> >>
> >> Changes in v4:
> >> - removed license
Em Fri, 27 Jul 2018 14:36:40 +1000
Stephen Rothwell escreveu:
> Hi all,
>
> Today's linux-next merge of the drm tree got a conflict in:
>
> drivers/gpu/ipu-v3/ipu-cpmem.c
>
> between commit:
>
> 343b23a7c6b6 ("media: gpu: ipu-v3: Allow negative offsets for interlaced
> scanning")
>
> fr
On 27.07.2018 12:30, Laurent Pinchart wrote:
> Hi Andrzej,
>
> On Friday, 27 July 2018 10:17:50 EEST Andrzej Hajda wrote:
>> On 26.07.2018 09:36, Archit Taneja wrote:
>>> On Wednesday 25 July 2018 09:16 PM, Andrzej Hajda wrote:
Add a drm_bridge driver for the Toshiba TC358764 DSI to LVDS bridg
On 26/07/18 10:15, Enric Balletbo i Serra wrote:
The "atomic" API allows us to configure PWM period and duty_cycle and
enable it in one call.
The patch also moves the pwm_init_state just before any use of the
pwm_state struct, this fixes a potential bug where pwm_get_state
can be called before p
https://bugzilla.kernel.org/show_bug.cgi?id=200667
--- Comment #1 from Christian Widmer (cwid...@umbrox.de) ---
Created attachment 277571
--> https://bugzilla.kernel.org/attachment.cgi?id=277571&action=edit
Kernel configuration
--
You are receiving this mail because:
You are watching the assig
https://bugzilla.kernel.org/show_bug.cgi?id=200667
Bug ID: 200667
Summary: [AMDGPU] stacktrace in dmesg, starting at
drm_dp_i2c_do_msg
Product: Drivers
Version: 2.5
Kernel Version: 4.17.10
Hardware: All
https://bugzilla.kernel.org/show_bug.cgi?id=200667
--- Comment #2 from Christian Widmer (cwid...@umbrox.de) ---
Created attachment 277573
--> https://bugzilla.kernel.org/attachment.cgi?id=277573&action=edit
lspci
I am using an RX 580.
--
You are receiving this mail because:
You are watching t
https://bugzilla.kernel.org/show_bug.cgi?id=200667
--- Comment #3 from Christian Widmer (cwid...@umbrox.de) ---
I might add simply booting the kernel is all that is needed to trigger the
issue. The stacktraces automatically appear during the boot process.
--
You are receiving this mail because:
Hey,
Op 27-07-18 om 12:12 schreef Satendra Singh Thakur:
> Following changes are done to this func:
> 1. Currently there are many redundant error checks for
> count_connectors, mode, fb and mode_valid.
> if (crtc_req->mode_valid)
> if (crtc_req->count_connectors == 0 && mode)
> if (crtc_req->count
https://bugs.freedesktop.org/show_bug.cgi?id=107390
--- Comment #6 from Justinas Narusevicius ---
Hey Alex,
Yes ac916c914c3156e53505e9ea3a9d1495518bf873 was found by bisecting mainline
kernel between tags of v4.16 (0adb32858b0bddf4ada5f364a84ed60b196dbcda good)
and v4.17-rc1 (60cc43fc888428bb2f1
https://bugs.freedesktop.org/show_bug.cgi?id=107390
--- Comment #7 from Justinas Narusevicius ---
Created attachment 140853
--> https://bugs.freedesktop.org/attachment.cgi?id=140853&action=edit
Patch to revert the problematic commit
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=107402
Martin Peres changed:
What|Removed |Added
Component|DRM/Intel |DRM/AMDgpu
Summary|[CI][BAT]
https://bugs.freedesktop.org/show_bug.cgi?id=107403
Bug ID: 107403
Summary: Quadratic behavior due to leaking fence contexts in
reservation objects
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=107402
--- Comment #4 from Michel Dänzer ---
(In reply to Chris Wilson from comment #2)
> Use after free by amdgpu.ko
How do you know it's a use-after-free? Can you provide more information about
that, e.g. from KASAN?
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=107402
--- Comment #5 from Chris Wilson ---
RBX: 6b6b6b6b6b6b6b6b == POISON_FREE
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedeskt
https://bugs.freedesktop.org/show_bug.cgi?id=107402
--- Comment #6 from Martin Peres ---
Our KASAN runs do not currently run AMDGPU tests. This should be fixed by the
next run (triggered manually).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=107403
--- Comment #1 from Christian König ---
Well that should be already fixed by the following commits:
commit ca25fe5efe4ab43cc5b4f3117a205c281805a5ca
Author: Christian König
Date: Tue Nov 14 15:24:36 2017 +0100
dma-buf: try to replace a s
https://bugs.freedesktop.org/show_bug.cgi?id=107403
Bas Nieuwenhuizen changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
On Thu, Jul 26, 2018 at 05:17:54PM +0100, Alexandru Gheorghe wrote:
> A new helper function(__drm_atomic_helper_plane_reset) has been added
> for linking a plane with its state and resetting the core
> properties(alpha, rotation, etc.) to their default values.
> Use that instead of duplicating the
On Fri, Jul 27, 2018 at 01:12:57AM +0800, Icenowy Zheng wrote:
> diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts
> b/arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts
> index 1b9b92e541d2..1b972bade9f6 100644
> --- a/arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts
> +++ b/ar
On Fri, Jul 27, 2018 at 01:12:47AM +0800, Icenowy Zheng wrote:
> Allwinner A64 has display engine pipeline like other Allwinner SOC's
> A83T/H3/H5.
>
> A64 behaviour similar to Allwinner A83T where
> Mixer0 => TCON0 => LVDS/RGB/MIPI-DSI
> Mixer1 => TCON1 => HDMI
> as per Display System Block Diag
https://bugs.freedesktop.org/show_bug.cgi?id=107001
cla...@mathr.co.uk changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
broadsheetfb is a platform driver and it should not be used on x86.
It should be used only by single ARM PXA board, so adding the
dependency in Kconfig.
Signed-off-by: Jia-Ju Bai
---
drivers/video/fbdev/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/fb
On Fri, Jul 27, 2018 at 10:25:13AM +0200, Joerg Roedel wrote:
> On Fri, Jul 27, 2018 at 02:16:18AM +0300, Dmitry Osipenko wrote:
> > The proposed solution adds a new option to the base device driver
> > structure that allows device drivers to explicitly convey to the drivers
> > core that the impli
于 2018年7月27日 GMT+08:00 下午8:56:15, Maxime Ripard 写到:
>On Fri, Jul 27, 2018 at 01:12:57AM +0800, Icenowy Zheng wrote:
>> diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts
>b/arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts
>> index 1b9b92e541d2..1b972bade9f6 100644
>> --- a/arch/
Currently, in the func drm_atomic_plane_check;
there are 3 if statements in the beginning with total 5 conditions.
these conditions are
crtc is NULL but fb is non-NULL
if (state->crtc && !state->fb)
crtc is non-NULL but fb is NULL
if (state->fb && !state->crtc)
crtc is NULL (and fb is also NULL)
if
1.In the func drm_atomic_plane_check, the fb geometry checking code
can be replaced by func drm_framebuffer_check_src_coords, this will
remove several redundant lines of code.
2. Currently, in the func drm_atomic_plane_check;
there are 3 if statements in the beginning with total 5 conditions.
these
In the func drm_atomic_plane_check, the fb geometry checking code
can be replaced by func drm_framebuffer_check_src_coords, this will
remove several redundant lines of code.
Signed-off-by: Satendra Singh Thakur
---
v1: Hi Mr Maarten, Thanks for the comments.
I have splitted them into two pa
Following changes are done to this func:
1. Currently there are many redundant error checks for
count_connectors, mode, fb and mode_valid.
if (crtc_req->mode_valid)
if (crtc_req->count_connectors == 0 && mode)
if (crtc_req->count_connectors > 0 && (!mode || !fb))
if (crtc_req->count_connectors > 0)
If qxl_device_init fails on creating resources and does not report it,
then qxl module will catch null pointer exception on remove, or on
probe's error path.
The patch adds error path with resources release into qxl_device_init.
Found by Linux Driver Verification project (linuxtesting.org).
Sign
On Fri, Jul 27, 2018 at 09:26:11PM +0800, Icenowy Zheng wrote:
>
>
> 于 2018年7月27日 GMT+08:00 下午8:56:15, Maxime Ripard
> 写到:
> >On Fri, Jul 27, 2018 at 01:12:57AM +0800, Icenowy Zheng wrote:
> >> diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts
> >b/arch/arm64/boot/dts/allwinner/s
On Fri, Jul 27, 2018 at 05:10:22PM +0300, Dmitry Osipenko wrote:
> I'm not sure what you guys are meaning by the "firmware", could you elaborate
> please? Do you mean the Open Firmware and hence the devicetree or what?
Yes, I think the best way to request this is using a device-tree
property. Let
https://bugzilla.kernel.org/show_bug.cgi?id=200605
--- Comment #3 from ric...@gmx.at ---
I didn't forget, it just didn't happen since then...
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing list
d
https://bugs.freedesktop.org/show_bug.cgi?id=106175
gr...@sub.red changed:
What|Removed |Added
CC||gr...@sub.red
--- Comment #22 from gr...
https://bugs.freedesktop.org/show_bug.cgi?id=107390
Alex Deucher changed:
What|Removed |Added
CC||harry.wentl...@amd.com,
https://bugs.freedesktop.org/show_bug.cgi?id=107021
--- Comment #2 from f...@hardijzer.nl ---
Same issue on 4.18.0-rc3, also on a Vega 64. My machine also locks up whenever
I manually turn off my monitor with its physical button.
--
You are receiving this mail because:
You are the assignee for t
https://bugzilla.kernel.org/show_bug.cgi?id=200667
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
On 27/07/18 15:10, Dmitry Osipenko wrote:
On Friday, 27 July 2018 12:03:28 MSK Will Deacon wrote:
On Fri, Jul 27, 2018 at 10:25:13AM +0200, Joerg Roedel wrote:
On Fri, Jul 27, 2018 at 02:16:18AM +0300, Dmitry Osipenko wrote:
The proposed solution adds a new option to the base device driver
str
https://bugs.freedesktop.org/show_bug.cgi?id=103907
--- Comment #3 from thomas.rin...@arcor.de ---
Bisecting would be very hard since the crashes appear randomly.
However the error seems to be gone.
Either by 18.1.4 or with the new game version that was released this week.
--
You are receiving
On Fri, Jul 27, 2018 at 05:02:37PM +0100, Robin Murphy wrote:
> On 27/07/18 15:10, Dmitry Osipenko wrote:
> >On Friday, 27 July 2018 12:03:28 MSK Will Deacon wrote:
> >>On Fri, Jul 27, 2018 at 10:25:13AM +0200, Joerg Roedel wrote:
> >>>On Fri, Jul 27, 2018 at 02:16:18AM +0300, Dmitry Osipenko wrote
On Fri, Jul 27, 2018 at 8:20 AM Joerg Roedel wrote:
>
> On Fri, Jul 27, 2018 at 05:10:22PM +0300, Dmitry Osipenko wrote:
> > I'm not sure what you guys are meaning by the "firmware", could you
> > elaborate
> > please? Do you mean the Open Firmware and hence the devicetree or what?
>
> Yes, I thi
The VSP uses a lock to protect the BRU and BRS assignment when
configuring pipelines. The lock is taken in vsp1_du_atomic_begin() and
released in vsp1_du_atomic_flush(), as well as taken and released in
vsp1_du_setup_lif(). This guards against multiple pipelines trying to
assign the same BRU and BR
https://bugs.freedesktop.org/show_bug.cgi?id=104300
--- Comment #6 from Mariusz Mazur ---
I found it! Before I knew 4.14 worked fine and 4.15+ introduced this bug.
Now I know precisely which patches:
- 4.14.35 works correctly
- 4.14.36 exhibits this behavior
There are only a few amdgpu patches
https://bugzilla.kernel.org/show_bug.cgi?id=200667
--- Comment #5 from Christian Widmer (cwid...@umbrox.de) ---
The bisect identified commit 9168c089a2122606e2c01f6fbeda85ff950ac189 (Revert
"drm/amd/display: Don't return ddc result and read_bytes in same return value",
upstream commit 5292221d6ddf
https://bugzilla.kernel.org/show_bug.cgi?id=200667
--- Comment #6 from Alex Deucher (alexdeuc...@gmail.com) ---
The warning is harmless. As per the commit message, this is fixed properly for
4.19 with the following patches:
This breaks DDC in certain cases. Revert for 4.18 and previous kern
On Fri, Jul 27, 2018 at 11:13:31AM -0600, Rob Herring wrote:
> I don't follow why we need a property rather than being implied by the
> device's (the GPU) compatible string.
There might be devices where either setup works, with or without IOMMU
translation, and the firmware can set the property de
https://bugzilla.kernel.org/show_bug.cgi?id=200667
--- Comment #7 from Christian Widmer (cwid...@umbrox.de) ---
For the sake of completeness I have just tested linux-next which contains all
those patches and the warning is indeed gone. Thank you for your responses!
--
You are receiving this mail
Boris Brezillon writes:
> From: Eric Anholt
In the subject, s/PICTH/PITCH/
signature.asc
Description: PGP signature
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
"(an unmatched left parenthesis
creates an unresolved tension
that will stay with you all day."
-- Randall Munroe
Signed-off-by: Paulo Zanoni
---
drivers/gpu/drm/drm_dp_helper.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_dp_helpe
Boris Brezillon writes:
> From: Eric Anholt
>
> drm_atomic_helper_check_plane_state() takes care of checking the
> scaling capabilities and calculating the clipped X/Y offsets for us.
>
> Rely on this function instead of open-coding the logic. While at it, we
> get rid of a few fields in vc4_pla
On Fri, Jul 27, 2018 at 4:33 PM, Paulo Zanoni wrote:
> "(an unmatched left parenthesis
> creates an unresolved tension
> that will stay with you all day."
>-- Randall Munroe
>
> Signed-off-by: Paulo Zanoni
Reviewed-by: Alex Deucher
> ---
> drivers/gpu/drm/drm_dp_helper.c
1 - 100 of 107 matches
Mail list logo
