Changes the boe-bf060y8m-aj0 panel to use multi style functions for
improved error handling. Additionally the MIPI_DSI_MODE_LPM flag is set
after the off commands are run in boe_bf060y8m_aj0_off regardless of any
failures, and regulators are disabled if the boe_bf060y8m_aj0_on call in
boe_bf060y8m_
On 4/13/25 3:40 AM, Doug Anderson wrote:
> Hi,
>
> On Fri, Apr 11, 2025 at 9:30 PM Tejas Vipin wrote:
>>
>> Changes the boe-bf060y8m-aj0 panel to use multi style functions for
>> improved error handling. Additionally the MIPI_DSI_MODE_LPM flag is set
>> after the off commands are run in boe_bf
Hi,
On Fri, Apr 11, 2025 at 2:23 AM Jayesh Choudhary wrote:
>
> Enable NO_EOT and SYNC flags for DSI to use VIDEO_SYNC_PULSE_MODE
> with EOT disabled.
Any chance you could add some details to this commit message? Your
subject says that these flags are "necessary", but people have been
using this
Hi,
On Fri, Apr 11, 2025 at 9:30 PM Tejas Vipin wrote:
>
> Changes the boe-bf060y8m-aj0 panel to use multi style functions for
> improved error handling. Additionally the MIPI_DSI_MODE_LPM flag is set
> after the off commands are run in boe_bf060y8m_aj0_off regardless of any
> failures, and regul
The return value of drm_mode_duplicate() is assigned to mode,
which will lead to a NULL pointer dereference on
failure of drm_mode_duplicate(). Add a check to avoid npd.
Signed-off-by: Chenyuan Yang
Fixes: 6ee738610f41 ("drm/nouveau: Add DRM driver for NVIDIA GPUs")
---
drivers/gpu/drm/nouveau/d
: /example-1/localbus@e0005000/flash@0,0: simple-bus
unit address format error, expected "0"
Documentation/devicetree/bindings/memory-controllers/fsl,elbc.example.dts:91.22-97.15:
Warning (simple_bus_reg): /example-1/localbus@e0005000/nand@1,0: simple-bus
unit address format error, expec
The goto frees "fence_drv" so this is a double free bug. There is no
need to call amdgpu_seq64_free(adev, fence_drv->va) since the seq64
allocation failed so change the goto to goto free_fence_drv. Also
propagate the error code from amdgpu_seq64_alloc() instead of hard coding
it to -ENOMEM.
Fixe
1) Checkpatch complains if we print an error message for kzalloc()
failure. The kzalloc() failure already has it's own error messages
built in. Also this allocation is small enough that it is guaranteed
to succeed.
2) Return directly instead of doing a goto free_fence_drv. The
"fence
Hello Boris Brezillon,
Commit 7d5a3b22f5b5 ("drm/panthor: Call panthor_gpu_coherency_init()
after PM resume()") from Apr 4, 2025 (linux-next), leads to the
following Smatch static checker warning:
drivers/gpu/drm/panthor/panthor_device.c:248 panthor_device_init()
warn: missing unw
This fixes a double free on one error path in
amdgpu_userq_fence_driver_alloc() and cleans up another error path.
v2:
Did some additional cleanup
Dan Carpenter (2):
drm/amdgpu: Fix double free in amdgpu_userq_fence_driver_alloc()
drm/amdgpu: Clean up error handling in
amdgpu_userq_fence_d
On Thu, Apr 10, 2025 at 10:29:31PM +0530, Yadav, Arvind wrote:
> Please change this also instead of 'goto free_fence_drv' just return err.
>
> fence_drv = kzalloc(sizeof(*fence_drv), GFP_KERNEL);
> if (!fence_drv) {
> DRM_ERROR("Failed to allocate memory for fence d
Pass array of pages of the scanout buffer [1] to shmem BO, allowing
drm_panic to work even if the BO is not vmapped.
[1] https://lore.kernel.org/all/20250407140138.162383-3-jfale...@redhat.com/
Signed-off-by: Jocelyn Falempe
Signed-off-by: Ryosuke Yasuoka
---
drivers/gpu/drm/virtio/virtgpu_pla
This series converts the fsl,elbc binding to YAML and adds new bindings
for related devices (particular kinds of chip on the eLBC).
For readability, the existing unit address syntax of ,
(e.g. nand@1,0) is kept. This results in a few dtc validation warnings,
when combined with other choices in thi
From: "J. Neuschäfer"
Convert the Freescale localbus controller bindings from text form to
YAML. Compared to the .txt version, the YAML binding contains a new
usage example with FCM NAND flash, and a full list of compatible strings
based on current usage in arch/powerpc/boot/dts/.
Note that the
From: "J. Neuschäfer"
Formalize the binding already supported by the fsl_elbc_nand.c driver
and used in several device trees in arch/powerpc/boot/dts/.
raw-nand-chip.yaml is referenced in order to accommodate situations in
which the ECC parameters settings are set in the device tree. One such
ex
From: "J. Neuschäfer"
Formalize the binding already supported by the uio_fsl_elbc_gpcm.c
driver.
Reviewed-by: Frank Li
Reviewed-by: Rob Herring (Arm)
Signed-off-by: J. Neuschäfer
---
V4,V5:
- no changes
V3:
- add review tags
V2:
- split out from fsl,elbc patch
- add description
- remove "d
From: "J. Neuschäfer"
In some scenarios, such as under the Freescale eLBC bus, there are raw
NAND chips with a unit address that has a comma in it (cs,offset).
For reasons of compatibility with historical device trees and
readability of the unit addresses, this format is kept.
Relax the $nodenam
This series introduces a new kernel configuration option NO_AUTO_INLINE,
which can be used to disable the automatic inlining of functions.
This will allow the function tracer to trace more functions
because it only traces functions that the compiler has not inlined.
Previous discussions can be fo
On x86_64 with gcc version 13.3.0, I compile kernel with:
make defconfig
./scripts/kconfig/merge_config.sh .config <(
echo CONFIG_COMPILE_TEST=y
)
make KCFLAGS="-fno-inline-functions -fno-inline-small-functions
-fno-inline-functions-called-once"
Then I get a linker error:
ld: vmli
This series introduces a new kernel configuration option NO_AUTO_INLINE,
which can be used to disable the automatic inlining of functions.
This will allow the function tracer to trace more functions
because it only traces functions that the compiler has not inlined.
Previous discussions can be fo
Hi Prabhakar,
Thanks for the patch.
> -Original Message-
> From: Prabhakar
> Sent: 08 April 2025 21:09
> Subject: [PATCH v2 15/15] drm: renesas: rz-du: mipi_dsi: Add support for
> RZ/V2H(P) SoC
>
> From: Lad Prabhakar
>
> Add DSI support for Renesas RZ/V2H(P) SoC.
>
> Co-developed-b
On Fri, Apr 11, 2025 at 10:26:47AM +0200, Javier Martinez Canillas wrote:
> Marcus Folkesson writes:
>
> Hello Marcus,
>
> [...]
>
> >> static const struct of_device_id st7571_of_match[] = {
> >>/* monochrome displays */
> >>{
> >>.compatible = "sinocrystal,sc128128012-v01",
From: Thierry Reding
Recent generations of Tegra have moved the display components outside of
host1x, leading to a device that has no CRTCs attached and hence doesn't
support any of the modesetting functionality. When this is detected, the
driver clears the DRIVER_MODESET and DRIVER_ATOMIC flags
23 matches
Mail list logo
