Hi
Am 11.01.21 um 04:30 schrieb Tian Tao:
Use drm_crtc_mask() where appropriate.
Signed-off-by: Tian Tao
Looks like the right thing to do.
Acked-by: Thomas Zimmermann
Best regards
Thomas
---
drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_vdac.c | 3 ++-
1 file changed, 2 insertions(+), 1
Hi
Am 11.01.21 um 07:43 schrieb KuoHsiang Chou:
[Bug][AST2500]
When AST2500 acts as stand-alone VGA so that DRAM and DVO initialization
have to be achieved by VGA driver with P2A (PCI to AHB) enabling.
However, HW suggests disable Fast reset mode after DRAM initializaton,
because fast reset
[Bug][AST2500]
When AST2500 acts as stand-alone VGA so that DRAM and DVO initialization
have to be achieved by VGA driver with P2A (PCI to AHB) enabling.
However, HW suggests disable Fast reset mode after DRAM initializaton,
because fast reset mode is mainly designed for ARM ICE debugger.
Once
There are minor differences in the values for the threshold value and
the scan line size between families of ASPEED SoC. Additionally the SCU
register for the output control differs between families.
This adds device tree matching to parameterise these values, allowing us
to add support for the
This scales better to multiple families of SoC. The lookup by compatible
can be removed in a future change.
Signed-off-by: Joel Stanley
---
drivers/gpu/drm/aspeed/aspeed_gfx_drv.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git
The out of tree vendor driver was recently updated to support the
ast2400 and ast2600. These patches begin to add that support to the
mainline driver.
With these two cleanups it should be easier to support different
families of BMC system on chip with this driver.
I will merge them through
Hi all,
After merging the amdgpu tree, today's linux-next build (htmldocs)
produced these warnings:
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:340: warning: Incorrect use
of kernel-doc format: * @active_vblank_irq_count
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:379:
https://bugzilla.kernel.org/show_bug.cgi?id=211033
--- Comment #10 from Artur Bac (arturbac...@gmail.com) ---
5.10.6 works ok again with 2 monitors and Sapphire Nitro+ Radeon RX 5700 XT
here is dmesg output of drm on 5.10.6
[3.471791] systemd[1]: Starting Load Kernel Module drm...
[
Hi all,
On Fri, 8 Jan 2021 12:25:40 +1100 Stephen Rothwell
wrote:
>
> On Fri, 8 Jan 2021 11:55:18 +1100 Stephen Rothwell
> wrote:
> >
> > After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> > failed like this:
> >
> > error: the following would cause module name
On Sun, Jan 10, 2021 at 5:09 PM Oliver Graute wrote:
> here the schematics and my dts. The board is using a LVDS connector for
> the display.
The schematics shows the GKTW70SDAD1SD panel in the J4 connector, not
the LVDS J7 connector.
>
https://bugzilla.kernel.org/show_bug.cgi?id=208947
--- Comment #21 from JerryD (jvdeli...@charter.net) ---
Created attachment 294599
--> https://bugzilla.kernel.org/attachment.cgi?id=294599=edit
dmesg from 5.10.5 kernel
I bummped up to the 5.10.5 kernel. The laptop suspends on lid close and
Hi folks,
today I joined to testing Kernel 5.11 and saw that the kernel log was
flooded with BUG messages:
BUG: sleeping function called from invalid context at mm/vmalloc.c:1756
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 266, name: kswapd0
INFO: lockdep is turned off.
CPU: 15 PID: 266
https://bugzilla.kernel.org/show_bug.cgi?id=209987
--- Comment #10 from youling...@gmail.com ---
I can't stand memory leak, i will revert "Revert "drm/amd/display: Fix memory
leaks in S3 resume""
revert 5efc1f4b454c6179d35e7b0c3eda0ad5763a00fc in today linux 5.11-rc3.
i use rc kernel every week.
Hi Oliver,
On Sun, Jan 10, 2021 at 12:35 PM Oliver Graute wrote:
> the first two errors are gone. But I still get this:
>
> [ 42.387107] mxsfb 21c8000.lcdif: Cannot connect bridge: -517
>
> The panel is still off perhaps I miss something else.
Some suggestions:
- Take a look at
Update vkms documentation to contain usage of `modinfo`
command and steps to load vkms with module options enabled.
Signed-off-by: Sumera Priyadarsini
---
Documentation/gpu/vkms.rst | 10 ++
1 file changed, 10 insertions(+)
diff --git a/Documentation/gpu/vkms.rst
Add enable_writeback feature to vkms_config as a module.
Signed-off-by: Sumera Priyadarsini
---
drivers/gpu/drm/vkms/vkms_drv.c| 5 +
drivers/gpu/drm/vkms/vkms_drv.h| 1 +
drivers/gpu/drm/vkms/vkms_output.c | 9 ++---
3 files changed, 12 insertions(+), 3 deletions(-)
diff --git
Currently, data for the device instance is held by vkms_device.
Add a separate type, vkms_config to contain configuration details
for the device and various modes to be later used by configfs.
This config data stays constant once the device is created.
Accordingly, add vkms_create and
This patchset aims to lay down some prep work before configfs can be
implemented for the vkms driver. The first patch in the series adds a
new type vkms_config to track device configuration. The second and third
patch add module testing support for writeback operations.
The first patch is
The comment says the layout and options use 8 bits, and the shift
uses 8 bits. However the mask is 0xf, ie. 0b (4 bits).
This could be surprising when introducing new layouts or options
that take more than 4 bits, as this would silently drop the high
bits.
Make the masks consistent with
This converts the lms283gf05 backlight driver to use GPIO
descriptors and switches the single PXA Palm Z2 device
over to defining these.
Since the platform data was only used to convey GPIO
information we can delete the platform data header.
Notice that we define the proper active low semantics
20 matches
Mail list logo
