On 25/02/10 05:41AM, Dmitry Baryshkov wrote:
> On Sun, Feb 09, 2025 at 10:32:33PM -0500, Ethan Carter Edwards wrote:
> > There is a possibility for an uninitialized *ret* variable to be
> > returned in some code paths.
> >
> > Fix this by initializing *ret* to 0.
> >
> > Addresses-Coverity-ID: 16
There is a possibility for an uninitialized *ret* variable to be
returned in some code paths.
Fix this by initializing *ret* to 0.
Addresses-Coverity-ID: 1642546 ("Uninitialized scalar variable")
Fixes: 774bcfb731765d ("drm/msm/dpu: add support for virtual planes")
Signed-off-by: Ethan Carter Edw
On Mon, Feb 10, 2025 at 07:24:59AM +0100, Greg KH wrote:
> On Sun, Feb 09, 2025 at 06:30:24PM +0100, Danilo Krummrich wrote:
> > +config NOVA_CORE
> > + tristate "Nova Core GPU driver"
> > + depends on PCI
> > + depends on RUST
> > + depends on RUST_FW_LOADER_ABSTRACTIONS
> > + default n
Change the visionox-r66451 panel to use multi style functions for
improved error handling. Additionally, always drop LPM flag after
sending init sequence.
Signed-off-by: Tejas Vipin
---
Changes in v2:
- Fixed visionox_r66451_enable to return dsi_ctx.accum_err
- Mentioned changed handling
Hi
Am 08.02.25 um 01:51 schrieb Kajtár Zsolt:
Hello Thomas!
No it's not. Major code abstractions behind preprocessor tokens are
terrible to maintain.
Hmm, don't get me wrong but I'm not sure if the changes were really
checked in detail. At first sight it might look like I'm adding tons of
new
The mdp1-mem is not supported on the SM8550 SoCs, and having maxItems=2
makes the bindings not clear if mdp0-mem/mdp1-mem or mdp0-mem/cpu-cfg
is required, so explicitly document the mdp0-mem/cpu-cfg interconnect
paths and complete the example with the missing interconnect paths.
Suggested-by: Dmit
The bindings requires the mdp0-mem and the cpu-cfg interconnect path,
add the missing cpu-cfg path to fix the dtbs check error.
Fixes: b8591df49cde ("arm64: dts: qcom: sm8550: correct MDSS interconnects")
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/qcom/sm8550.dtsi | 5 +++--
1 file ch
The mdp1-mem is not supported on the SM8550 & SM8650 SoCs, so properly document
the mdp0-mem and cpu-cfg interconnect entries.
This fixes the following errors:
display-subsystem@ae0: interconnects: [[200, 3, 7, 32, 1, 7]] is too short
from schema $id:
http://devicetree.org/schemas/dis
The mdp1-mem is not supported on the SM8550 SoCs, and having maxItems=2
makes the bindings not clear if mdp0-mem/mdp1-mem or mdp0-mem/cpu-cfg is
required, so explicitly document the mdp0-mem/cpu-cfg interconnect and
add the cpu-cfg path in the example.
Suggested-by: Dmitry Baryshkov
Signed-off-by
The bindings requires the mdp0-mem and the cpu-cfg interconnect path,
add the missing cpu-cfg path to fix the dtbs check error.
Fixes: 9fa33cbca3d2 ("arm64: dts: qcom: sm8650: correct MDSS interconnects")
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/qcom/sm8650.dtsi | 7 +--
1 file
On 1/29/2025 4:53 PM, Dmitry Baryshkov wrote:
> On Wed, Jan 29, 2025 at 11:13:05AM +0530, Ekansh Gupta wrote:
>>
>>
>> On 1/29/2025 5:00 AM, Dmitry Baryshkov wrote:
>>> On Mon, Jan 27, 2025 at 10:12:39AM +0530, Ekansh Gupta wrote:
DSP needs last 4 bits of context id to be 0 for polling mod
Hi Herve,
Am Freitag, 7. Februar 2025, 19:08:16 CET schrieb Herve Codina:
> Hi Alexander,
>
> On Thu, 06 Feb 2025 16:39:09 +0100
> Alexander Stein wrote:
>
> > Hi Herve,
> >
> > Am Donnerstag, 6. Februar 2025, 16:20:48 CET schrieb Herve Codina:
> > > Hi Alexander,
> > >
> > > On Thu, 06 Feb 2
Il 07/02/25 16:18, Louis-Alexis Eyraud ha scritto:
Add a compatible for the MediaTek MT8370 SoC, with an
integrated ARM Mali G57 MC2 GPU (Valhall-JM, dual core),
with the same platform data as MT8186 (one regulator, two power
domains).
Despite their different GPU architecture (making them not bei
Il 07/02/25 16:18, Louis-Alexis Eyraud ha scritto:
Add a new gpu node in mt8370.dtsi to enable support for the
ARM Mali G57 MC2 GPU (Valhall-JM) found on the MT8370 SoC, using the
Panfrost driver.
On a Mediatek Genio 510 EVK board, the panfrost driver probed with the
following message:
```
panfr
Il 07/02/25 16:18, Louis-Alexis Eyraud ha scritto:
Add a compatible for the MediaTek MT8370 SoC, with an
integrated ARM Mali G57 MC2 GPU (Valhall-JM, dual core).
This new compatible is needed for this SoC support, as the other
existing compatibles for the same GPU architecture (MT8188, MT8192) do
https://bugzilla.kernel.org/show_bug.cgi?id=213145
Artem S. Tashkinov (a...@gmx.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
On Sat, Feb 08, 2025 at 06:53:24PM +0800, Langyan Ye wrote:
> Add a new compatible for the panels KINGDISPLAY KD110N11-51IE and
> STARRY 2082109QFH040022-50E. Both panels use the HX83102 IC, so
> add the compatible to the hx83102 bindings file.
Your subject does not fit at all at any reasonable li
On 04/02/2025 18:44, Cristian Ciocaltea wrote:
Commit d3d6b1bf85ae ("drm: bridge: dw_hdmi: fix preference of RGB modes
over YUV420") changed the order of the output bus formats, but missed to
update accordingly the "Possible output formats" comment section above
dw_hdmi_bridge_atomic_get_output_b
drivers/gpu/drm/imagination/ includes local headers with the double-quote
form (#include "...").
Hence, the header search path addition is unneeded.
Signed-off-by: Masahiro Yamada
---
drivers/gpu/drm/imagination/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/imag
On Mon, Feb 10, 2025 at 05:41:30PM +0800, Icenowy Zheng wrote:
> Furtherly, the monorepo nature of Linux kernel means to refactor an
> interface, it's usually the person changing the callee that need to
> change all callers to satify the interface change; having Rust code in
> tree calling the inte
Hi,
please move the header to the include block above an keep it sorted:
#include
-->#include <--
#include
On 2/8/2025 9:05 AM, Su Hui wrote:
> When compiling without CONFIG_IA32_EMULATION, there are some errors:
>
> drivers/accel/amdxdna/amdxdna_mailbox.c: In function ‘mailbox_release_msg’:
在 2025-02-08星期六的 17:31 +0900,Hector Martin写道:
>
> By kernel and mesa policy, while a drm/ kernel driver is not merged
> with
> a stable UAPI, the mesa side cannot be merged/enabled either. That
> means
> that every day the driver isn't upstream, our users suffer due to
> various container technolo
Applied to drm-misc-next
On 2/4/2025 9:46 AM, Jacek Lawrynowicz wrote:
> Add possibility to import single buffer into multiple contexts,
> fix locking when aborting contexts and add some debug features.
>
> Andrzej Kacprowski (2):
> accel/ivpu: Add missing locks around mmu queues
> accel/ivpu
On Thu, Feb 06, 2025 at 02:45:48PM +0800, Andy Yan wrote:
> From: Andy Yan
>
> The clock polarity of RGB signal output is controlled by GRF, this
> property is already being used in the current device tree, but
> forgot to describe it as a required property in the binding file.
>
> Signed-off-by
On Thu, Feb 06, 2025 at 02:44:38PM +0800, Andy Yan wrote:
> From: Andy Yan
>
> As more SoCs variants are introduced, each SoC brings its own
> unique set of constraints, describe this constraints SoC by
> SoC will make things easier.
>
> Signed-off-by: Andy Yan
>
> ---
Reviewed-by: Krzysztof
On Thu, Feb 06, 2025 at 02:46:03PM +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
On Mon, 10 Feb 2025 at 11:05, Ekansh Gupta wrote:
>
>
>
>
> On 1/29/2025 4:53 PM, Dmitry Baryshkov wrote:
> > On Wed, Jan 29, 2025 at 11:13:05AM +0530, Ekansh Gupta wrote:
> >>
> >>
> >> On 1/29/2025 5:00 AM, Dmitry Baryshkov wrote:
> >>> On Mon, Jan 27, 2025 at 10:12:39AM +0530, Ekansh Gupta wrot
Hi Philipp,
On 07/02/25 08:02, Philipp Stanner wrote:
drm_sched_init() has a great many parameters and upcoming new
functionality for the scheduler might add even more. Generally, the
great number of parameters reduces readability and has already caused
one missnaming in:
commit 6f1cacf4eba7 ("
On 09/02/2025 18:45, Dmitry Osipenko wrote:
On 2/6/25 13:42, Ryosuke Yasuoka wrote:
Virtio gpu supports the drm_panic module, which displays a message to
the screen when a kernel panic occurs. It is supported where it has
vmapped shmem BO.
Signed-off-by: Jocelyn Falempe
Signed-off-by: Ryosuke
Il 07/02/25 06:46, CK Hu (胡俊光) ha scritto:
Hi, Angelo:
On Mon, 2025-01-13 at 15:52 +0100, AngeloGioacchino Del Regno wrote:
External email : Please do not click links or open attachments until you have
verified the sender or the content.
In preparation for moving the common bits of this driv
Il 07/02/25 07:04, CK Hu (胡俊光) ha scritto:
Hi, Angelo:
On Mon, 2025-01-13 at 15:52 +0100, AngeloGioacchino Del Regno wrote:
External email : Please do not click links or open attachments until you have
verified the sender or the content.
Remove the error print in case of mtk_hdmi_clk_enable_
On 2025-02-10 01:11:59, Dmitry Baryshkov wrote:
> On Sun, Feb 09, 2025 at 10:42:53PM +0100, Marijn Suijten wrote:
> > Ordering issues here cause an uninitialized (default STANDALONE)
> > usecase to be programmed (which appears to be a MUX) in some cases
> > when msm_dsi_host_register() is called, l
Hi
Am 07.02.25 um 15:53 schrieb Alex Lanzano:
I saw that Noralf has to unfortunately step down from maintaining the
repaper and mi0283qt drivers. I would be more than happy to maintain
these two if need be. The repaper device is very similar to the
sharp-memory display I currently maintain and I
Hi Janusz,
On Thu, Feb 06, 2025 at 07:07:38PM +0100, Janusz Krzysztofik wrote:
> We return immediately from i915_driver_register() if drm_dev_register()
> fails, skipping remaining registration steps. However, the _unregister()
> counterpart called at device remove knows nothing about that skip a
On Thu, 06 Feb 2025 15:17:13 +0800, oushixiong1...@163.com wrote:
> convert to use devm_platform_ioremap_resource().
>
>
Applied, thanks!
[1/1] drm/bridge: convert to use devm_platform_ioremap_resource()
https://gitlab.freedesktop.org/drm/misc/kernel/-/commit/aaad45cfaa1b
Rob
On Mon, 10 Feb 2025 12:41:59 +
Adrián Larumbe wrote:
> Panthor's fdinfo handler is routed through the /proc file system, which
> executes in an atomic context. That means we cannot use mutexes because
> they might sleep.
>
> This bug was uncovered by enabling some of the kernel's mutex-debug
On 04/02/2025 14:26, Thomas Zimmermann wrote:
Add dedicated connector state for ASTDP connectors. The state will
store values for programming the transmitter chip.
Thanks, it looks good to me.
Reviewed-by: Jocelyn Falempe
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/ast/ast_dp.c
This is a note to let you know that I've just added the patch titled
drm/rockchip: cdn-dp: Use drm_connector_helper_hpd_irq_event()
to the 6.6-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch i
This is a note to let you know that I've just added the patch titled
m68k: vga: Fix I/O defines
to the 6.6-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
m68k-vga-fix-i-o-defines.pat
The current code uses a the reset_pipe() local function to reset the
CRTC outputs.
drm_atomic_helper_reset_crtc() has been introduced recently and it
performs exact same operations.
In order to avoid code duplication, use the new helper instead of the
local function.
Signed-off-by: Herve Codina
Hi Alexander,
On Mon, 10 Feb 2025 11:42:09 +0100
Alexander Stein wrote:
> Hi Herve,
>
> Am Freitag, 7. Februar 2025, 19:08:16 CET schrieb Herve Codina:
> > Hi Alexander,
> >
> > On Thu, 06 Feb 2025 16:39:09 +0100
> > Alexander Stein wrote:
> >
> > > Hi Herve,
> > >
> > > Am Donnerstag, 6.
In some cases observed during ESD tests, the TI SN65DSI83 cannot recover
from errors by itself. A full restart of the bridge is needed in those
cases to have the bridge output LVDS signals again.
Also, during tests, cases were observed where reading the status of the
bridge was not even possible.
Hi,
Usually the TI SN65DSI83 recovers from error by itself but during ESD
tests, we have some cases where the TI SN65DSI83 didn't recover.
In order to handle those cases, this series adds support for a recovery
mechanism.
Compare to the previous iteration, this v6 series fixes a NULL
pointer der
drm_atomic_helper_reset_crtc() allows to reset the CRTC active outputs.
This resets all active components available between the CRTC and
connectors.
Signed-off-by: Herve Codina
Reviewed-by: Dmitry Baryshkov
Reviewed-by: Maxime Ripard
---
drivers/gpu/drm/drm_atomic_helper.c | 41 ++
Both the TI SN65DSI83 and SN65DSI84 bridges have an IRQ pin to signal
errors using interrupt.
This interrupt is not documented in the binding.
Add the missing interrupts property.
Signed-off-by: Herve Codina
Reviewed-by: Laurent Pinchart
Acked-by: Conor Dooley
---
.../devicetree/bindings/dis
Hi Maíra,
Am 10.02.25 um 13:23 schrieb Maíra Canal:
Hi Stefan,
Thanks for your patch!
On 01/02/25 09:50, Stefan Wahren wrote:
Since the initial commit 57692c94dcbe ("drm/v3d: Introduce a new DRM
driver
for Broadcom V3D V3.x+") the struct v3d_dev reserved a pointer for
an optional V3D clock. B
This is a note to let you know that I've just added the patch titled
drm/ast: astdp: Fix timeout for enabling video signal
to the 6.13-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
This is a note to let you know that I've just added the patch titled
drm/rockchip: cdn-dp: Use drm_connector_helper_hpd_irq_event()
to the 6.13-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch
This is a note to let you know that I've just added the patch titled
m68k: vga: Fix I/O defines
to the 6.13-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
m68k-vga-fix-i-o-defines.pa
On Mon, 10 Feb 2025 13:43:17 +
Liviu Dudau wrote:
> On Mon, Feb 10, 2025 at 02:18:07PM +0100, Boris Brezillon wrote:
> > On Mon, 10 Feb 2025 12:42:00 +
> > Adrián Larumbe wrote:
> >
> > > A previous commit dealt with a similar situation, whereby upon enabling
> > > some mutex debug fe
On Mon, 10 Feb 2025 at 14:31, Maxime Ripard wrote:
>
> On Fri, Feb 07, 2025 at 09:54:06PM +0200, Dmitry Baryshkov wrote:
> > On Fri, Feb 07, 2025 at 12:47:51PM +0100, Maxime Ripard wrote:
> > > Hi,
> > >
> > > On Thu, Feb 06, 2025 at 07:14:29PM +0100, Luca Ceresoli wrote:
> > > > DRM bridges are c
On Mon, Feb 10, 2025 at 01:54:29PM +0100, Marijn Suijten wrote:
> On 2025-02-10 01:11:59, Dmitry Baryshkov wrote:
> > On Sun, Feb 09, 2025 at 10:42:53PM +0100, Marijn Suijten wrote:
> > > Ordering issues here cause an uninitialized (default STANDALONE)
> > > usecase to be programmed (which appears
From: Saurabh Singh Sengar Sent: Monday, February
10, 2025 4:41 AM
>
> On Sun, Feb 09, 2025 at 03:52:52PM -0800, mhkelle...@gmail.com wrote:
> > From: Michael Kelley
> >
> > When a Hyper-V framebuffer device is removed, or the driver is unbound
> > from a device, any allocated and/or mapped mem
On 10/02/25 - 13:30, Greg Kroah-Hartman wrote:
> The vkms driver does not need to create a platform device, as there is
> no real platform resources associated it, it only did so because it was
> simple to do that in order to get a device to use for resource
> management of drm resources. Change
Hi,
On Mon, Feb 10, 2025 at 1:24 AM Tejas Vipin wrote:
>
> Change the visionox-r66451 panel to use multi style functions for
> improved error handling. Additionally, always drop LPM flag after
> sending init sequence.
>
> Signed-off-by: Tejas Vipin
> ---
> Changes in v2:
> - Fixed visionox_r
Hi,
On Mon, Feb 10, 2025 at 2:16 AM Krzysztof Kozlowski wrote:
>
> On Sat, Feb 08, 2025 at 06:53:24PM +0800, Langyan Ye wrote:
> > Add a new compatible for the panels KINGDISPLAY KD110N11-51IE and
> > STARRY 2082109QFH040022-50E. Both panels use the HX83102 IC, so
> > add the compatible to the hx
Hi,
On Sat, Feb 8, 2025 at 12:25 PM Doug Anderson wrote:
>
> Hi,
>
> On Sat, Feb 8, 2025 at 2:53 AM Langyan Ye
> wrote:
> >
> > The kingdisplay-kd110n11-51ie is a 10.95" TFT panel. The MIPI controller
> > on this panel is the same as the other panels here, so add this panel
> > to this driver.
>
Hi,
On Sat, Feb 8, 2025 at 12:25 PM Doug Anderson wrote:
>
> Hi,
>
> On Sat, Feb 8, 2025 at 2:53 AM Langyan Ye
> wrote:
> >
> > The starry-2082109qfh040022-50e is a 10.95" TFT panel. The MIPI controller
> > on this panel is the same as the other panels here, so add this panel to
> > this driver.
Il 07/02/25 07:10, CK Hu (胡俊光) ha scritto:
Hi, Angelo:
On Mon, 2025-01-13 at 15:52 +0100, AngeloGioacchino Del Regno wrote:
External email : Please do not click links or open attachments until you have
verified the sender or the content.
Since the SIMPLE_DEV_PM_OPS macro and the pm pointer a
The vgem driver does not need to create a platform device, as there is
no real platform resources associated it, it only did so because it was
simple to do that in order to get a device to use for resource
management of drm resources. Change the driver to use the faux device
instead as this is NO
The vkms driver does not need to create a platform device, as there is
no real platform resources associated it, it only did so because it was
simple to do that in order to get a device to use for resource
management of drm resources. Change the driver to use the faux device
instead as this is NO
On Fri, Feb 07, 2025 at 09:54:06PM +0200, Dmitry Baryshkov wrote:
> On Fri, Feb 07, 2025 at 12:47:51PM +0100, Maxime Ripard wrote:
> > Hi,
> >
> > On Thu, Feb 06, 2025 at 07:14:29PM +0100, Luca Ceresoli wrote:
> > > DRM bridges are currently considered as a fixed element of a DRM card, and
> > > t
On 04/02/2025 14:26, Thomas Zimmermann wrote:
Programming the astdp transmitter chip requires a magic value for
individual modes. Inline the helper for calculating the value into
its only caller (i.e., the encoder's atomic_mode_set).
With further refactoring, the atomic check will be able to det
On 04/02/2025 14:26, Thomas Zimmermann wrote:
Look up the mode index for the astdp transmitter ship in the encoder's
atomic check and report an error if the display mode is not supported.
The lookup uses the DRM display mode instead of the driver's internal
VBIOS mode. Both are be equivalent. Th
On 04/02/2025 14:26, Thomas Zimmermann wrote:
Validate each display mode against the astdp transmitter chips. Filters
out modes that the chip does not support.
Thanks, it looks good to me.
Reviewed-by: Jocelyn Falempe
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/ast/ast_dp.c | 14
https://bugzilla.kernel.org/show_bug.cgi?id=213145
--- Comment #36 from MasterCATZ (masterc...@hotmail.com) ---
6.12.3-061203-generic
seems to be ok
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
This is a note to let you know that I've just added the patch titled
m68k: vga: Fix I/O defines
to the 5.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
m68k-vga-fix-i-o-defines.pat
This is a note to let you know that I've just added the patch titled
drm/rockchip: cdn-dp: Use drm_connector_helper_hpd_irq_event()
to the 5.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch i
This is a note to let you know that I've just added the patch titled
m68k: vga: Fix I/O defines
to the 5.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
m68k-vga-fix-i-o-defines.pa
This is a note to let you know that I've just added the patch titled
m68k: vga: Fix I/O defines
to the 5.15-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
m68k-vga-fix-i-o-defines.pa
This is a note to let you know that I've just added the patch titled
drm/rockchip: cdn-dp: Use drm_connector_helper_hpd_irq_event()
to the 6.1-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch i
This is a note to let you know that I've just added the patch titled
m68k: vga: Fix I/O defines
to the 6.1-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
m68k-vga-fix-i-o-defines.pat
On Mon, Feb 10, 2025 at 03:37:42PM +0100, Louis Chauvet wrote:
> On 10/02/25 - 13:30, Greg Kroah-Hartman wrote:
> > The vkms driver does not need to create a platform device, as there is
> > no real platform resources associated it, it only did so because it was
> > simple to do that in order to g
On 10/02/2025 12:41, Adrián Larumbe wrote:
Panthor's fdinfo handler is routed through the /proc file system, which
executes in an atomic context. That means we cannot use mutexes because
they might sleep.
Have the debug splat at hand? I am thinking it is not because of fdinfo
reads, which ar
On Tue, Jan 28, 2025 at 7:57 AM wrote:
>
> From: Shixiong Ou
>
> Convert platform_get_resource(), devm_ioremap_resource() to a single
> call to devm_platform_ioremap_resource().
>
> Signed-off-by: Shixiong Ou
> ---
> drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 5 +
> 1 file changed
On Thu, 06 Feb 2025 18:02:32 +0100, Luca Ceresoli wrote:
> This series removes some unnecessary #includes and and unused forward
> declarations, which I noticed while preparing a way more complex series
> (bridge hotplug). I decided to split these trivial patches to a separate
> series to limit the
Hi Tvrtko,
[18153.770244] BUG: sleeping function called from invalid context at
kernel/locking/mutex.c:562
[18153.771059] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 203412,
name: cat
[18153.771757] preempt_count: 1, expected: 0
[18153.772164] RCU nest depth: 0, expected: 0
[18153.772
Hi,
On 2024-12-16 12:34:46+0100, Thomas Weißschuh wrote:
> The sysfs core now allows instances of 'struct bin_attribute' to be
> moved into read-only memory. Make use of that to protect them against
> accidental or malicious modifications.
Can anybody pick up these patches?
Except for lima they a
On Mon, Feb 10, 2025 at 06:58:25AM -0800, Saurabh Singh Sengar wrote:
> On Mon, Feb 10, 2025 at 02:28:35PM +, Michael Kelley wrote:
> > From: Saurabh Singh Sengar Sent: Monday,
> > February 10, 2025 4:41 AM
> > >
> > > On Sun, Feb 09, 2025 at 03:52:52PM -0800, mhkelle...@gmail.com wrote:
> >
This is the debug log for the second patch in the series:
[18325.029172] BUG: sleeping function called from invalid context at
kernel/locking/mutex.c:562
[18325.029947] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 203483,
name: cat
[18325.030646] preempt_count: 1, expected: 0
[18325.03
Il 10/02/25 07:58, CK Hu (胡俊光) ha scritto:
Hi, Angelo:
On Mon, 2025-01-13 at 15:52 +0100, AngeloGioacchino Del Regno wrote:
External email : Please do not click links or open attachments until you have
verified the sender or the content.
In preparation for splitting out the common bits from
On Fri, Feb 07, 2025 at 10:06:44AM +0100, Thomas Hellström wrote:
> On Wed, 2025-01-29 at 11:51 -0800, Matthew Brost wrote:
> > This patch introduces support for GPU Shared Virtual Memory (SVM) in
> > the
> > Direct Rendering Manager (DRM) subsystem. SVM allows for seamless
> > sharing of memory be
On Sun, Feb 09, 2025 at 03:25:26AM -0500, Neal Gompa wrote:
> On Friday, February 7, 2025 1:16:11 PM Eastern Standard Time Konstantin
> Ryabitsev wrote:
> > It is my goal to be able to give subsystems a way to use forges without it
> > impacting how they interact with upstream or handle tree-wide
On Mon, Feb 10, 2025 at 10:49:53PM +0800, Yongbang Shi wrote:
> From: Baihan Li
>
> This serdes is inited and configured for dp, and integrating them into dp
> init and dp link training process.
> For rate changing, we can change from 1.62-8.2Gpbs by cfg reg.
> For voltage and pre-emphasis levels
On 2/8/25 00:05, Su Hui wrote:
When compiling without CONFIG_IA32_EMULATION, there are some errors:
drivers/accel/amdxdna/amdxdna_mailbox.c: In function ‘mailbox_release_msg’:
drivers/accel/amdxdna/amdxdna_mailbox.c:197:2: error: implicit declaration
of function ‘kfree’.
197 | kfree(mb_msg
On 10.02.2025 10:32 AM, Neil Armstrong wrote:
> The bindings requires the mdp0-mem and the cpu-cfg interconnect path,
> add the missing cpu-cfg path to fix the dtbs check error.
>
> Fixes: 9fa33cbca3d2 ("arm64: dts: qcom: sm8650: correct MDSS interconnects")
> Signed-off-by: Neil Armstrong
> ---
On 10.02.2025 10:32 AM, Neil Armstrong wrote:
> The bindings requires the mdp0-mem and the cpu-cfg interconnect path,
> add the missing cpu-cfg path to fix the dtbs check error.
>
> Fixes: b8591df49cde ("arm64: dts: qcom: sm8550: correct MDSS interconnects")
> Signed-off-by: Neil Armstrong
> ---
Hi Thomas,
On Mon, Dec 16, 2024 at 12:34:47PM +0100, Thomas Weißschuh wrote:
> The sysfs core now allows instances of 'struct bin_attribute' to be
> moved into read-only memory. Make use of that to protect them against
> accidental or malicious modifications.
>
> Signed-off-by: Thomas Weißschuh
Hello Maxime, Dmitry,
On Mon, 10 Feb 2025 16:23:44 +0200
Dmitry Baryshkov wrote:
> On Mon, 10 Feb 2025 at 14:31, Maxime Ripard
> wrote:
> >
> > On Fri, Feb 07, 2025 at 09:54:06PM +0200, Dmitry Baryshkov wrote:
> > > On Fri, Feb 07, 2025 at 12:47:51PM +0100, Maxime Ripard wrote:
> > > > Hi,
Il 10/02/25 03:18, CK Hu (胡俊光) ha scritto:
Hi, Angelo:
On Mon, 2025-01-13 at 15:52 +0100, AngeloGioacchino Del Regno wrote:
External email : Please do not click links or open attachments until you have
verified the sender or the content.
In preparation for adding a new driver for the HDMI TX
Hi Dmitry,
On Fri, 7 Feb 2025 21:43:26 +0200
Dmitry Baryshkov wrote:
> > > > @@ -1018,6 +1067,11 @@ struct drm_bridge
> > > > *devm_drm_panel_bridge_add_typed(struct device *dev,
> > > > {
> > > > struct drm_bridge **ptr, *bridge;
> > > >
> > > > + if (panel->bridge) {
> > > >
On 8.02.2025 11:09 PM, Marijn Suijten wrote:
> On 2025-02-03 21:14:26, Danila Tikhonov wrote:
>> From: Eugene Lepshy
>>
>> DRM DSC helper has parameters for various bpc values other than 8:
>
> Weird zero-width \u200b spaces here between "values" and "other", please
> delete
> those.
>
>> (8/
Hello Maxime,
On Fri, 7 Feb 2025 12:47:51 +0100
Maxime Ripard wrote:
> > diff --git a/include/drm/drm_bridge.h b/include/drm/drm_bridge.h
> > index
> > ad7ba444a13e5ecf16f996de3742e4ac67dc21f1..43cef0f6ccd36034f64ad2babfebea62db1d9e43
> > 100644
> > --- a/include/drm/drm_bridge.h
> > +++ b/inc
Hi Maxime, Dmitry
On Fri, 7 Feb 2025 21:54:06 +0200
Dmitry Baryshkov wrote:
> > > +/* Internal function (for refcounted bridges) */
> > > +void __drm_bridge_free(struct kref *kref)
> > > +{
> > > + struct drm_bridge *bridge = container_of(kref, struct drm_bridge,
> > > refcount);
> > > + void *
Hi Thomas,
On Mon, Dec 16, 2024 at 12:34:48PM +0100, Thomas Weißschuh wrote:
> The sysfs core now allows instances of 'struct bin_attribute' to be
> moved into read-only memory. Make use of that to protect them against
> accidental or malicious modifications.
>
> Signed-off-by: Thomas Weißschuh
On 10.02.2025 6:10 PM, Konrad Dybcio wrote:
> On 8.02.2025 11:09 PM, Marijn Suijten wrote:
>> On 2025-02-03 21:14:26, Danila Tikhonov wrote:
>>> From: Eugene Lepshy
>>>
>>> DRM DSC helper has parameters for various bpc values other than 8:
>>
>> Weird zero-width \u200b spaces here between "value
Hi Thomas,
On Mon, Dec 16, 2024 at 12:34:49PM +0100, Thomas Weißschuh wrote:
> The sysfs core now allows instances of 'struct bin_attribute' to be
> moved into read-only memory. Make use of that to protect them against
> accidental or malicious modifications.
>
> Signed-off-by: Thomas Weißschuh
On Thu, 21 Nov 2024, Manikandan Muralidharan wrote:
> The XLCDC IP supports DSI, parallel RGB and LVDS Display.
> sys_clk(Generic clock) is used for DSI and Parallel RGB displays;
> And LVDS PLL is used with LVDS displays.
> obtain anyone of the clocks for the LCD to operate
Maybe say something a
Hi Dmitry,
On Fri, 7 Feb 2025 21:57:30 +0200
Dmitry Baryshkov wrote:
> On Fri, Feb 07, 2025 at 11:44:01AM +0100, Luca Ceresoli wrote:
> > On Fri, 7 Feb 2025 05:17:43 +0200
> > Dmitry Baryshkov wrote:
> >
> > > On Thu, Feb 06, 2025 at 07:14:30PM +0100, Luca Ceresoli wrote:
> > > > Add a dev
This tablet does not have dpio-common-bc powerwell init.
i915 :00:02.0: [drm] *ERROR* timeout setting power well state
(f3ff)
i915 :00:02.0: [drm] *ERROR* Display PHY 0 is not power up
Signed-off-by: Qs315490
---
.../drm/i915/display/intel_display_driver.c | 4 ++--
...
1 - 100 of 220 matches
Mail list logo