[PATCH] fbdev: fbmem: Fix the implicit type casting

2022-01-30 Thread Yizhuo Zhai
In function do_fb_ioctl(), the "arg" is the type of unsigned long, and in "case FBIOBLANK:" this argument is casted into an int before passig to fb_blank(). In fb_blank(), the comparision if (blank > FB_BLANK_POWERDOWN) would be bypass if the original "arg" is a large number, which is possible

Re: [PATCH v5 01/10] mm: add zone device coherent type memory support

2022-01-30 Thread Alistair Popple
Looks good, feel free to add: Reviewed-by: Alistair Popple On Saturday, 29 January 2022 7:08:16 AM AEDT Alex Sierra wrote: > Device memory that is cache coherent from device and CPU point of view. > This is used on platforms that have an advanced system bus (like CAPI > or CXL). Any page of a

Re: [PATCH v5 02/10] mm: add device coherent vma selection for memory migration

2022-01-30 Thread Alistair Popple
On Saturday, 29 January 2022 7:08:17 AM AEDT Alex Sierra wrote: [...] > struct migrate_vma { > diff --git a/mm/migrate.c b/mm/migrate.c > index cd137aedcfe5..d3cc3589e1e8 100644 > --- a/mm/migrate.c > +++ b/mm/migrate.c > @@ -2264,7 +2264,8 @@ static int migrate_vma_collect_pmd(pmd_t *pmdp, >

RE: [PATCH 3/3] drm/vkms: change vkms driver to use drm_writeback_connector.base pointer

2022-01-30 Thread Kandpal, Suraj
Hi All, Gentle Reminder! Any Review comments? > Changing vkms driver to accomadate the change of > drm_writeback_connector.base to a pointer the reason for which is > explained in the Patch(drm: add writeback pointers to drm_connector). > > Signed-off-by: Kandpal, Suraj > --- >

Re: [PATCH] drm/amdgpu: initialize reg_access_ctrl

2022-01-30 Thread Lazar, Lijo
[Public] Thanks, the patch is already submitted. https://www.spinics.net/lists/amd-gfx/msg73613.html Thanks, Lijo

Re: [PATCH 2/4] drm/panel: feiyang-fy07024di26a30d: make reset gpio optional

2022-01-30 Thread Heiko Stübner
Hi Peter, Am Freitag, 7. Januar 2022, 06:13:33 CET schrieb Peter Geis: > Some implementations do not use the reset signal, instead tying it to dvdd. > Make the reset gpio optional to permit this. > > Signed-off-by: Peter Geis > --- > drivers/gpu/drm/panel/panel-feiyang-fy07024di26a30d.c | 11

[PATCH v3 3/3] drm/panel: simple: Add support for HannStar HSD101PWW2 panel

2022-01-30 Thread Dmitry Osipenko
From: Svyatoslav Ryhel Add definition of the HannStar HSD101PWW2 Rev0-A00/A01 LCD SuperIPS+ HD panel. Signed-off-by: Svyatoslav Ryhel Signed-off-by: Dmitry Osipenko --- drivers/gpu/drm/panel/panel-simple.c | 28 1 file changed, 28 insertions(+) diff --git

[PATCH v3 2/3] dt-bindings: display: simple: Add HannStar HSD101PWW2

2022-01-30 Thread Dmitry Osipenko
From: Svyatoslav Ryhel Add HannStar HSD101PWW2 10.1" WXGA (1280x800) TFT-LCD LVDS panel to the list of compatibles. Acked-by: Rob Herring Signed-off-by: Svyatoslav Ryhel Signed-off-by: Dmitry Osipenko --- .../devicetree/bindings/display/panel/panel-simple.yaml | 2 ++ 1 file

[PATCH v3 1/3] dt-bindings: sharp, lq101r1sx01: Add compatible for LQ101R1SX03

2022-01-30 Thread Dmitry Osipenko
From: Anton Bambura LQ101R1SX03 is compatible with LQ101R1SX01 from software perspective, document it. The LQ101R1SX03 is a newer revision of LQ101R1SX01, it has minor differences in hardware pins in comparison to the older version. The newer version of the panel can be found on Android tablets,

[PATCH v3 0/3] Support Sharp LQ101R1SX03 and HannStar HSD101PWW2 panels

2022-01-30 Thread Dmitry Osipenko
This series adds support for Sharp LQ101R1SX03 and HannStar HSD101PWW2 display panels that are used by Asus Transformer tablets, which we're planning to support since 5.17 kernel. Changelog: v3: - No changes. Re-sending for 5.18. Device-trees of devices that use these panels were merge to

Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/uapi: Add query for hwconfig table

2022-01-30 Thread Jordan Justen
John, Rodrigo, It is now clear to me just how dependent i915 is going to be on the closed source guc software, and that's just a fact of life for our graphics stack going forward. In that context, it seems kind of pointless for me to make a big deal out of this peripheral "query item" commit

fbdev git tree update

2022-01-30 Thread Helge Deller
Hello DRI and fbdev developers, I've now mostly checked all queued-up patches on the fbdev mailing list: https://patchwork.kernel.org/project/linux-fbdev/list/ and applied the ones which seemed appropriate. IMHO there is nothing really critical/important/conflicting in there. Shortlog is below,

[v5 0/3] drm/msm/dsi: Add 10nm dsi phy tuning configuration support

2022-01-30 Thread Rajeev Nandan
This series is to add DSI PHY tuning support in Qualcomm Snapdragon SoCs with 10nm DSI PHY e.g. SC7180 In most cases the default values of DSI PHY tuning registers should be sufficient as they are fully optimized. However, in some cases (for example, where extreme board parasitics cause the eye

[v5 1/3] dt-bindings: msm/dsi: Add 10nm dsi phy tuning properties

2022-01-30 Thread Rajeev Nandan
In most cases, the default values of DSI PHY tuning registers should be sufficient as they are fully optimized. However, in some cases where extreme board parasitics cause the eye shape to degrade, the override bits can be used to improve the signal quality. The general guidelines for DSI PHY

[v5 3/3] drm/msm/dsi: Add 10nm dsi phy tuning configuration support

2022-01-30 Thread Rajeev Nandan
The clock and data lanes of the DSI PHY have a calibration circuitry feature. As per the MSM DSI PHY tuning guidelines, the drive strength tuning can be done by adjusting rescode offset for hstop/hsbot, and the drive level tuning can be done by adjusting the LDO output level for the HSTX drive.

[v5 2/3] drm/msm/dsi: Add dsi phy tuning configuration support

2022-01-30 Thread Rajeev Nandan
Add support for MSM DSI PHY tuning configuration. Current design is to support drive strength and drive level/amplitude tuning for 10nm PHY version, but this can be extended to other PHY versions. Signed-off-by: Rajeev Nandan Reviewed-by: Dmitry Baryshkov --- Changes in v2: - New. - Split

Re: [PATCH v3 1/1] drm/lsdc: add drm driver for loongson display controller

2022-01-30 Thread Randy Dunlap
Hi, The Kconfig text is looking good. Just one minor nit below: On 1/30/22 11:37, Sui Jingfeng wrote: > diff --git a/drivers/gpu/drm/lsdc/Kconfig b/drivers/gpu/drm/lsdc/Kconfig > new file mode 100644 > index ..8c908787b4aa > --- /dev/null > +++ b/drivers/gpu/drm/lsdc/Kconfig > @@ -0,0

[v4 2/3] drm/msm/dsi: Add dsi phy tuning configuration support

2022-01-30 Thread Rajeev Nandan
Add support for MSM DSI PHY tuning configuration. Current design is to support drive strength and drive level/amplitude tuning for 10nm PHY version, but this can be extended to other PHY versions. Signed-off-by: Rajeev Nandan Reviewed-by: Dmitry Baryshkov --- Changes in v2: - New. - Split

[v4 0/3] drm/msm/dsi: Add 10nm dsi phy tuning configuration support

2022-01-30 Thread Rajeev Nandan
This series is to add DSI PHY tuning support in Qualcomm Snapdragon SoCs with 10nm DSI PHY e.g. SC7180 In most cases the default values of DSI PHY tuning registers should be sufficient as they are fully optimized. However, in some cases (for example, where extreme board parasitics cause the eye

[v4 1/3] dt-bindings: msm/dsi: Add 10nm dsi phy tuning properties

2022-01-30 Thread Rajeev Nandan
In most cases, the default values of DSI PHY tuning registers should be sufficient as they are fully optimized. However, in some cases where extreme board parasitics cause the eye shape to degrade, the override bits can be used to improve the signal quality. The general guidelines for DSI PHY

[v4 3/3] drm/msm/dsi: Add 10nm dsi phy tuning configuration support

2022-01-30 Thread Rajeev Nandan
The clock and data lanes of the DSI PHY have a calibration circuitry feature. As per the MSM DSI PHY tuning guidelines, the drive strength tuning can be done by adjusting rescode offset for hstop/hsbot, and the drive level tuning can be done by adjusting the LDO output level for the HSTX drive.

[PATCH v3 1/1] drm/lsdc: add drm driver for loongson display controller

2022-01-30 Thread Sui Jingfeng
From: suijingfeng There is a display controller in loongson's LS2K1000 SoC and LS7A1000 bridge, and the DC in those chip is a PCI device. This display controller have two display pipes but with only one hardware cursor. Each way has a DVO output interface and the CRTC is able to scanout from

[PATCH v3 0/1] drm/lsdc: add drm driver for loongson display controller

2022-01-30 Thread Sui Jingfeng
v3: fix more grammar mistakes in Kconfig reported by Randy Dunlap and give more details about lsdc. v2: fixup warnings reported by kernel test robot There is a display controller in loongson's LS2K1000 SoC and LS7A1000 bridge, and the DC in those chip is a PCI device. This display controller

[Bug 215549] My 6900XT can't recover while it's idle (but not asleep), and sometimes doesn't show at boot

2022-01-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215549 --- Comment #1 from techxga...@outlook.com --- Created attachment 300353 --> https://bugzilla.kernel.org/attachment.cgi?id=300353=edit Xorg log -- You may reply to this email to add a comment. You are receiving this mail because: You are

[Bug 215549] My 6900XT can't recover while it's idle (but not asleep), and sometimes doesn't show at boot

2022-01-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215549 techxga...@outlook.com changed: What|Removed |Added Hardware|All |x86-64 -- You may reply to

[Bug 215549] New: My 6900XT can't recover while it's idle (but not asleep), and sometimes doesn't show at boot

2022-01-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=215549 Bug ID: 215549 Summary: My 6900XT can't recover while it's idle (but not asleep), and sometimes doesn't show at boot Product: Drivers Version: 2.5 Kernel Version:

Linux 5.16.3 breaks headless Raspberry Pi 3 boot, again

2022-01-30 Thread Michael Stapelberg
Hello again, I am facing the exact same symptoms as last September: https://lists.freedesktop.org/archives/dri-devel/2021-September/324008.html …meaning my (headless) Raspberry Pi 3 B and Raspberry Pi 3 B+ no longer boot with Linux 5.16.3, while the (headless) Raspberry Pi 4 still boots. This

[Bug 214197] [Asus G713QY] RX6800M not usable after exiting Vulkan application

2022-01-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214197 vele...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 214197] [Asus G713QY] RX6800M not usable after exiting Vulkan application

2022-01-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=214197 --- Comment #8 from vele...@gmail.com --- Recent kernels in 5.15.* and 5.16.* fix the issue for me. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

Re: [PATCH 2/2] drm/radeon/uvd: Fix forgotten unmap buffer objects

2022-01-30 Thread Christian König
Am 29.01.22 um 08:35 schrieb zhanglianjie: after the buffer object is successfully mapped, call radeon_bo_kunmap before the function returns. Signed-off-by: zhanglianjie diff --git a/drivers/gpu/drm/radeon/radeon_uvd.c b/drivers/gpu/drm/radeon/radeon_uvd.c index