https://bugzilla.kernel.org/show_bug.cgi?id=209939
Janpieter Sollie (janpieter.sol...@edpnet.be) changed:
What|Removed |Added
Status|NEW |RESOLVED
On Sun, 22 Sep 2024, Dmitry Baryshkov wrote:
> On Wed, Sep 11, 2024 at 01:23:23PM GMT, Jani Nikula wrote:
>> Thanks, I'll change this to drop the function.
>
> Seeing no updated revisions here, I've posted a patch that drops the
> offending function. If I missed an update, please exuse me.
Thanks
(u64)1920)
> #define HDMI_MHZ_TO_HZ ((u64)100)
> static int pll_get_post_div(struct hdmi_8998_post_divider *pd, u64 bclk)
>
> ---
> base-commit: 32ffa5373540a8d1c06619f52d019c6cdc948bb4
> change-id: 20240922-msm-drop-unused-func-b9e76ad8e0ea
>
> Best regards,
--
Jani Nikula, Intel
Hello Alexander,
We have two gitlab issues[1] where a phantom display is detected by the system
(with i915 driver).
The following patch[2] has been identified as the first bad commit after bisect.
"b49420d6a1 video/aperture: optionally match the device in sysfb_disable()"
Could you please check
Hi,
On Mon, Sep 23, 2024 at 05:21:41AM GMT, hermes...@ite.com.tw wrote:
> Hi
>
> Sorry for the confusion caused
Please don't top post. Answers should come below the original quoted
text, not above it. Otherwise reading the email becomes really hard.
>
> Last patches did not switch to drm-misc
On Mon, Sep 23, 2024 at 05:50:22AM GMT, manikanda...@microchip.com wrote:
> On 20/09/24 9:13 pm, Dmitry Baryshkov wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> > content is safe
> >
> > On Thu, Sep 19, 2024 at 02:45:48PM GMT, Manikandan Muralidharan wrote
Hello,
kernel test robot noticed
"WARNING:at_drivers/gpu/drm/ast/ast_mode.c:#ast_primary_plane_helper_atomic_check[ast]"
on:
commit: 2a2391f857cdc5cf16f8df030944cef8d3d2bc30 ("drm/ast: vga: Transparently
handle BMC support")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git ma
On 20/09/24 9:13 pm, Dmitry Baryshkov wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> On Thu, Sep 19, 2024 at 02:45:48PM GMT, Manikandan Muralidharan wrote:
>> Add support for Microchip AC69T88A 5 inch TFT LCD 800x480
>> Display module wit
https://bugzilla.kernel.org/show_bug.cgi?id=204241
John_H_Smith (derfab...@gmail.com) changed:
What|Removed |Added
CC||derfab...@gmail.com
Hi
Sorry for the confusion caused
Last patches did not switch to drm-misc-nest. And I need re-create patches.
The HDCP patches is now on tow threads.(This one and the one include MCCS
patches with cover letter)
Should I keep on this thread or restart a new thread?
BR,
Hermes
-Original
On Mon, Sep 02, 2024 at 12:53:40PM GMT, Thomas Zimmermann wrote:
> Implement a read function for struct drm_edid and read the EDID data
> with drm_edit_read_custom(). Update the connector data accordingly.
>
> The EDID data comes from the emulator itself and the connector stores
> a copy in its ED
On Mon, Sep 02, 2024 at 11:33:19AM GMT, Liao Chen wrote:
> Add MODULE_DEVICE_TABLE(), so modules could be properly autoloaded based
> on the alias from of_device_id table.
>
> Signed-off-by: Liao Chen
> ---
> drivers/gpu/drm/tegra/drm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/d
On Tue, 03 Sep 2024 13:27:29 -0300, Fabio Estevam wrote:
> i.MX28 has an RX DMA channel associated with the LCDIF controller.
>
> Document the 'dmas' and 'dma-names' properties to fix the following
> dt-schema warnings:
>
> lcdif@8003: 'dma-names', 'dmas' do not match any of the regexes:
> '
Now that we have device wedged event supported by DRM core, make use
of it. With this in place, userspace will be notified of wedged device
on gt reset failure.
Signed-off-by: Raag Jadav
---
drivers/gpu/drm/i915/gt/intel_reset.c | 2 ++
drivers/gpu/drm/i915/i915_driver.c| 10 ++
2 f
This was previously attempted as xe specific reset uevent but dropped
in commit 77a0d4d1cea2 ("drm/xe/uapi: Remove reset uevent for now")
as part of refactoring.
Now that we have device wedged event supported by DRM core, make use
of it. With this in place userspace will be notified of wedged devi
Now that we have device wedged event in place, add wedge_recovery sysfs
attribute which will expose recovery methods supported by the DRM device.
This is useful for userspace consumers in cases where the device supports
multiple recovery methods which can be used as fallbacks.
$ cat /sys/class/drm
Introduce device wedged event, which will notify userspace of wedged
(hanged/unusable) state of the DRM device through a uevent. This is
useful especially in cases where the device is no longer operating as
expected and has become unrecoverable from driver context.
Purpose of this implementation i
This series introduces device wedged event in DRM subsystem and uses
it in xe and i915 drivers. Detailed description in commit message.
This was earlier attempted as xe specific uevent in v1 and v2.
https://patchwork.freedesktop.org/series/136909/
v2: Change authorship to Himal (Aravind)
Add
On Sun, Sep 22, 2024 at 11:14:17PM GMT, Dmitry Baryshkov wrote:
> On Thu, Sep 05, 2024 at 08:44:00AM GMT, Alex Lanzano wrote:
> > Add support for the monochrome Sharp Memory LCDs.
> >
> > Co-developed-by: Mehdi Djait
> > Signed-off-by: Mehdi Djait
> > Signed-off-by: Alex Lanzano
> > ---
> > MA
From: "Dr. David Alan Gilbert"
amdgpu_device_ip_is_idle is unused.
It was renamed from 'amdgpu_is_idle' which was originally added in
commit 5dbbb60ba61e ("drm/amdgpu: add IP helpers for wait_for_idle and is_idle")
but hasn't been used.
Remove it.
Signed-off-by: Dr. David Alan Gilbert
---
dr
From: "Dr. David Alan Gilbert"
amdgpu_gmc_vram_cpu_pa has been unused since commit
087451f372bf ("drm/amdgpu: use generic fb helpers instead of setting up AMD
own's.")
Remove it.
Signed-off-by: Dr. David Alan Gilbert
---
drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c | 12
drivers/gpu/
From: "Dr. David Alan Gilbert"
amdgpu_gfx_bit_to_me_queue has been unused since it was added in
commit 7470bfcf2014 ("drm/amdgpu: add helper function for gfx queue/bitmap
transition")
Remove it.
Signed-off-by: Dr. David Alan Gilbert
---
drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c | 10 --
From: "Dr. David Alan Gilbert"
amdgpu_i2c_add and amdgpu_i2c_init were added in 2015's commit
d38ceaf99ed0 ("drm/amdgpu: add core driver (v4)")
but never used.
Remove them.
Signed-off-by: Dr. David Alan Gilbert
---
drivers/gpu/drm/amd/amdgpu/amdgpu_i2c.c | 25 -
driver
From: "Dr. David Alan Gilbert"
amdgpu_atpx_dgpu_req_power_for_displays has been unused since
commit bdb1ccb080da ("drm/amdgpu: remove ATPX_DGPU_REQ_POWER_FOR_DISPLAYS
check when hotplug-in")
amdgpu_atpx_get_dhandle has been unused since commit
f9b7f3703ff9 ("drm/amdgpu/acpi: make ATPX/ATCS struc
From: "Dr. David Alan Gilbert"
Hi,
This is a bunch of deadcode removal in amdgpu;
some of the functions are ones which were previously
used but haven't been for a while, others are functions
that were added a few years ago and haven't ever been used.
There are some others that I've not remov
在 2024/9/21 8:04, Kasireddy, Vivek 写道:
Hi Huan,
Subject: [PATCH v7 0/7] udmabuf bug fix and some improvements
This patchset attempts to fix some errors in udmabuf and remove the
upin_list structure, also try clean up code.
By this patchset, udmabuf remove page struct relay, only use
pfn and
On Sun, Sep 22, 2024 at 09:12:13AM -0300, Fabio wrote:
> Replaced two lines of calling udelays by usleep_range() functions, adding
> more efficiency due to the need of long-lasting delays of more than 10us.
>
> Signed-off-by: Fabio Bareiro
> ---
> drivers/staging/fbtft/fb_ra8875.c | 4 ++--
> 1
On Fri, Sep 20, 2024 at 04:23:02PM +0800, Andy Yan wrote:
> From: Andy Yan
>
> Add vop found on rk3576, the main difference between rk3576 and the
> previous vop is that each VP has its own interrupt line.
>
> Signed-off-by: Andy Yan
>
> ---
Reviewed-by: Krzysztof Kozlowski
Best regards,
Kr
Replaced two lines of calling udelays by usleep_range() functions, adding
more efficiency due to the need of long-lasting delays of more than 10us.
Signed-off-by: Fabio Bareiro
---
drivers/staging/fbtft/fb_ra8875.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/
On Fri, Sep 13, 2024 at 01:23:01PM -0700, Rob Clark wrote:
> From: Rob Clark
>
> Fixes a race condition reported here:
> https://github.com/AsahiLinux/linux/issues/309#issuecomment-2238968609
>
> The whole premise of lockless access to a single-producer-single-
> consumer queue is that there is
On Sat, Sep 21, 2024 at 09:46:09PM +1200, Ryan Walklin wrote:
> The Allwinner H616 and variants have a new display engine revision
> (DE33).
>
> Add a clock binding for the DE33.
>
> Signed-off-by: Ryan Walklin
> Acked-by: Conor Dooley
> Reviewed-by: Chen-Yu Tsai
>
> --
Ditto
Best regards,
On Sat, Sep 21, 2024 at 09:46:08PM +1200, Ryan Walklin wrote:
> The Allwinner H616 and variants have a new display engine revision
> (DE33).
>
> Add a display engine bus binding for the DE33.
>
> Signed-off-by: Ryan Walklin
> Acked-by: Conor Dooley
> Reviewed-by: Chen-Yu Tsai
>
> --
Please r
On Sat, Sep 21, 2024 at 09:46:10PM +1200, Ryan Walklin wrote:
> The Allwinner H616 and variants have a new display engine revision
> (DE33).
>
> The mixer configuration registers are significantly different to the DE3
> and DE2 revisions, being split into separate top and display blocks,
> therefo
On Sun, Sep 22, 2024 at 4:47 PM Dmitry Baryshkov
wrote:
> > if (ret)
> > return ret;
> > +
> > ret = nt35510_send_long(nt, dsi, NT35510_P1_SETVCL,
> > NT35510_P1_VCL_LEN,
> > nt->conf->vcl);
> > if (ret)
>
On Wed, Sep 04, 2024 at 01:51:35PM GMT, Alexander Stein wrote:
> From: Matthias Schiffer
>
> The PIXCLK needs to be enabled in SCFG before accessing certain DCU
> registers, or the access will hang.
>
> Signed-off-by: Matthias Schiffer
> Signed-off-by: Alexander Stein
> ---
> drivers/gpu/drm/
On Wed, Sep 04, 2024 at 01:51:34PM GMT, Alexander Stein wrote:
> fsl_dcu_drm_modeset_init can return -EPROBE_DEFER, so use dev_err_probe
> to remove an invalid error message and add it to deferral description.
>
> Signed-off-by: Alexander Stein
> ---
> drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c |
On Thu, Sep 05, 2024 at 08:44:00AM GMT, Alex Lanzano wrote:
> Add support for the monochrome Sharp Memory LCDs.
>
> Co-developed-by: Mehdi Djait
> Signed-off-by: Mehdi Djait
> Signed-off-by: Alex Lanzano
> ---
> MAINTAINERS | 6 +
> drivers/gpu/drm/tiny/Kconfig
Hi all,
I am not familiar with the process yet. To get it merged, should I add more
mail-list or how to notify the maintainers?
Thanks in advance for your guide.
Best Regards
Shuicheng
> -Original Message-
> From: Lin, Shuicheng
> Sent: Tuesday, September 17, 2024 7:48 AM
> To: dri-deve
On Fri, 06 Sep 2024 08:38:56 +0200, Alexander Stein wrote:
> When drm/bridge-connector was moved to DRM_DISPLAY_HELPER not all
> users were updated. Add missing Kconfig selections.
Now that drm-misc-next contains both commits...
Applied to drm-misc-next, thanks!
[1/1] drm/imx: Add missing DRM_BR
On Mon, 16 Sep 2024 15:18:49 +0200, tjak...@math.uni-bielefeld.de wrote:
> From: Tobias Jakobi
>
> Hello,
>
> this is a re-submit of panel orientation quirks for some of the handheld
> devices by vendor AYA NEO.
>
> [...]
Applied to drm-misc-next, thanks!
[1/3] drm: panel-orientation-quirks:
On Fri, Sep 06, 2024 at 07:28:17PM GMT, Louis Chauvet wrote:
> Currently drm_writeback_connector are created by
> drm_writeback_connector_init or drm_writeback_connector_init_with_encoder.
> Both of the function uses drm_connector_init and drm_encoder_init, but
> there is no way to properly clean t
QXL supports the drm_panic module, which displays a message to the
screen when a kernel panic occurs.
Signed-off-by: Ryosuke Yasuoka
---
v4
1. Remove unnecessary () and empty lines
2. Remove unlikely() from qxl_panic_bo_create(). This function is
only called in panic handler and it does not need
On Sat, Sep 07, 2024 at 03:13:05PM GMT, He Lugang wrote:
> Use devm_add_action_or_reset() to release resources in case of failure,
> because the cleanup function will be automatically called.
>
> Signed-off-by: He Lugang
> ---
> drivers/gpu/drm/i2c/tda9950.c | 12 +++-
> 1 file changed,
On Sun, Sep 08, 2024 at 02:14:43PM GMT, Heiner Kallweit wrote:
> This device type is set but not used, so remove it.
Please describe how it was used and why you consider it to be unused
now. Hint: d14d2a8453d6 ("drm: Remove dev_pm_ops from drm_class").
> Whilst we're at it, constify device type d
On Sun, Sep 08, 2024 at 02:12:32PM GMT, Heiner Kallweit wrote:
> Annotate few more functions being called from drm_core_init() only
> as __init.
Why? Please describe the reason for the changes, not the changes
themselves.
>
> Signed-off-by: Heiner Kallweit
> ---
> drivers/gpu/drm/drm_cache.c
On Sun, Sep 08, 2024 at 02:11:25PM GMT, Heiner Kallweit wrote:
> Define class drm statically and constify it. This ensure that no user
> of the exported struct class can tamper with it.
>
> Signed-off-by: Heiner Kallweit
> ---
> drivers/gpu/drm/drm_internal.h | 2 +-
> drivers/gpu/drm/drm
On Sun, Sep 08, 2024 at 02:10:30PM GMT, Heiner Kallweit wrote:
> These changes make the error path a little more robust, because exit
> steps in drm_core_exit() don't have to ensure any longer that they
> work properly even if the associated init step wasn't executed.
Please use imperative style w
On Sun, Sep 08, 2024 at 02:09:39PM GMT, Heiner Kallweit wrote:
> These two functions have no user, so remove them.
If there is going to be next iteration please document that the only
user was TTM code which dropped sysfs interfaces in the commit
ed89fff97382 ("drm/ttm: drop sysfs directory")
Oth
On Sun, Sep 08, 2024 at 02:08:58PM GMT, Heiner Kallweit wrote:
> This undocumented attribute returns a version string which hasn't been
> changed for ages. libdrm doesn't use it and I also found no other user.
> So I think we can remove it.
This file is a part of the ABI. Commit 82d5e73f6b79 ("drm
On Sun, Sep 08, 2024 at 11:50:30PM GMT, Linus Walleij wrote:
> The commit introducing the Frida display started to write the
> SETVCMOFF registers unconditionally, and some (not all!) Hydis
> display seem to be affected by ghosting after the commit.
>
> Make SETVCMOFF optional and only send these
On Sun, Sep 22, 2024 at 11:49:49AM GMT, Tejas Vipin wrote:
>
>
> On 9/20/24 9:59 PM, Dmitry Baryshkov wrote:
> > On Tue, Sep 17, 2024 at 12:47:10PM GMT, Tejas Vipin wrote:
> >> Changes the elida-kd35t133 panel to use multi style functions for
> >> improved error handling.
> >>
> >> Signed-off-by:
On Sun, 22 Sept 2024 at 13:11, Hans de Goede wrote:
>
> Hi,
>
> On 21-Sep-24 10:02 PM, Dmitry Baryshkov wrote:
> > On Mon, Sep 16, 2024 at 03:18:51PM GMT, tjak...@math.uni-bielefeld.de wrote:
> >> From: Joaquín Ignacio Aramendía
> >>
> >> Add quirk orientation for AYA NEO 2. The name appears with
Hi,
On 21-Sep-24 10:02 PM, Dmitry Baryshkov wrote:
> On Mon, Sep 16, 2024 at 03:18:51PM GMT, tjak...@math.uni-bielefeld.de wrote:
>> From: Joaquín Ignacio Aramendía
>>
>> Add quirk orientation for AYA NEO 2. The name appears without spaces in
>> DMI strings. That made it difficult to reuse the 20
Hi,
> Maybe ``From: Min-Hua Chen ``?
>
> It's very minor and Min-Hua gave their 'Reviewed-by' tag to your patch,
> but they found the problem and I thought it was just for practical
> reasons you made it part of this patch set.
Yes, you're right. The reason I reply this patch is that I am not
su
On Fri Sep 20, 2024 at 10:21 AM CEST, Andy Yan wrote:
> From: Andy Yan
Maybe ``From: Min-Hua Chen ``?
It's very minor and Min-Hua gave their 'Reviewed-by' tag to your patch,
but they found the problem and I thought it was just for practical
reasons you made it part of this patch set.
> Move roc
>Move rockchip_drm_drv.h in rockchip_drm_vop2.h to fix the follow
>sparse warning:
>
>ARCH=arm64 LLVM=1 make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
>mrproper defconfig all -j12
>
>drivers/gpu/drm/rockchip/rockchip_vop2_reg.c:502:24: sparse:
>warning: symbol 'vop2_platform_driver' was not
On 22/09/2024 00:20, Jonas Karlman wrote:
> The Rockchip RK3288 SoC contain two different Visual Output Processor
> (VOP) blocks, VOP_BIG and VOP_LIT. The VOP blocks support different max
> output resolution, 3840x2160 and 2560x1600.
>
> Add support for the compatible used to differentiate between
On 22/09/2024 00:20, Jonas Karlman wrote:
> The Rockchip RK3288 SoC contain two different Visual Output Processor
> (VOP) blocks, VOP_BIG and VOP_LIT. The VOP blocks support different max
> output resolution, 3840x2160 and 2560x1600.
>
> Add compatible to differentiate between the two VOP blocks.
On 22 September 2024 at 08:48 am, Christian Zigotzky wrote:
On 21 September 2024 at 06:15 am, Christian Zigotzky wrote:
Hi All,
The lastest Git kernel doesn't boot anymore after the latest DRM
updates (drm-next-2024-09-19). [1]
I tested it with an AMD Radeon HD 6970 (Cayman XT) and with an A
60 matches
Mail list logo
