This patch series is to constify the following API:
struct device *device_find_child(struct device *dev, void *data,
int (*match)(struct device *dev, void *data));
To :
struct device *device_find_child(struct device *dev, const void *data,
device_mat
From: Zijun Hu
Simplify nd_namespace_store() implementation by device_find_child_by_name()
Signed-off-by: Zijun Hu
---
drivers/nvdimm/claim.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/drivers/nvdimm/claim.c b/drivers/nvdimm/claim.c
index
030dbde6b0882050c90fb
From: Zijun Hu
bool slim_eaddr_equal(struct slim_eaddr *a, struct slim_eaddr *b)
does not modify @*a or @*b.
Constify it by simply changing its parameter type to
'const struct slim_eaddr *'.
Signed-off-by: Zijun Hu
---
drivers/slimbus/core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletio
From: Zijun Hu
cable_match(), as matching function of device_find_child(), is to match
a device with device type @typec_cable_dev_type, and is unnecessary.
partner_match() is similar with cable_match() but with different device
type @typec_partner_dev_type.
Remove both functions and directly us
From: Zijun Hu
match_nvdimm_bridge(), as matching function of device_find_child(), is to
match a device with device type @cxl_nvdimm_bridge_type, and is unnecessary
Remove it and use API device_match_type() plus the device type instead.
Signed-off-by: Zijun Hu
---
drivers/cxl/core/pmem.c | 9
Hi Sebastian,
On 2024/12/2 22:41, Sebastian Reichel wrote:
Hi,
On Mon, Dec 02, 2024 at 11:28:13AM +0800, Damon Ding wrote:
Hi,
On 2024/12/2 6:59, Sebastian Reichel wrote:
Hi,
On Sat, Nov 30, 2024 at 09:25:12PM +0100, Heiko Stübner wrote:
Am Freitag, 29. November 2024, 03:43:57 CET schrieb
On 2024/12/5 00:42, James Bottomley wrote:
introduce extra device_find_child_new() which is constified ->
use *_new() replace ALL device_find_child() instances one by one
-> remove device_find_child() -> rename *_new() to
device_find_child() once.
>>> Why bother with the last
https://bugzilla.kernel.org/show_bug.cgi?id=219563
Bug ID: 219563
Summary: amdgpu graphical glitches on Thinkpad E14 G6 with
panel self-refresh enabled
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
On 12/4/2024 15:37, Lizhi Hou wrote:
Add SET_STATE ioctl to configure device power mode for aie2 device.
Three modes are supported initially.
POWER_MODE_DEFAULT: Enable clock gating and set DPM (Dynamic Power
Management) level to value which has been set by resource solver or
maximum DPM level t
From: Zijun Hu
fsl_mc_device_match() does not modify caller's inputs.
Constify it by simply changing its parameter types to const pointer.
Signed-off-by: Zijun Hu
---
drivers/bus/fsl-mc/dprc-driver.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/bus/fsl-mc/dp
Hi Heiko,
On 12/4/24 00:54, Heiko Stuebner wrote:
From: Heiko Stuebner
The Display Serial Interface 2 (DSI-2) is part of a group of communication
protocols defined by the MIPI Alliance. The RK3588 implements this
specification in its two MIPI DSI-2 Host Controllers that are based on a
new Syno
Hi Maarten,
kernel test robot noticed the following build errors:
[auto build test ERROR on tj-cgroup/for-next]
[also build test ERROR on akpm-mm/mm-everything linus/master v6.13-rc1
next-20241204]
[cannot apply to drm-misc/drm-misc-next drm-tip/drm-tip]
[If your patch is applied to the wrong
From: Zijun Hu
Constify the following API:
struct device *device_find_child(struct device *dev, void *data,
int (*match)(struct device *dev, void *data));
To :
struct device *device_find_child(struct device *dev, const void *data,
device_match_t ma
From: Zijun Hu
Introduce device_match_type() for purposes below:
- Test if a device matches with a specified device type.
- As argument of various device finding APIs to find a device with
specified type.
device_find_child() will use it to simplify operations later.
Signed-off-by: Zijun Hu
From: Zijun Hu
gpio_sim_dev_match_fwnode() is a simple wrapper of device_match_fwnode()
Remvoe the unnecessary wrapper.
Signed-off-by: Zijun Hu
---
drivers/gpio/gpio-sim.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/gpio/gpio-sim.c b/drivers/gpio/gpio-sim.
From: Zijun Hu
Simplify of_find_slim_device() implementation by device_match_of_node().
Signed-off-by: Zijun Hu
---
drivers/slimbus/core.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/slimbus/core.c b/drivers/slimbus/core.c
index
ab927fd077cb4fe1e29c00
From: Zijun Hu
Static match_any() is same as API device_match_any()
Remove the former and use the later instead.
Signed-off-by: Zijun Hu
---
drivers/base/core.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index
8116bc8dd6
From: Zijun Hu
Simplify device_find_child_by_name() implementation by both existing
API device_find_child() and device_match_name().
Signed-off-by: Zijun Hu
---
drivers/base/core.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/drivers/base/core.c b/drivers/b
On 2024/12/5 08:10, Zijun Hu wrote:
> This patch series is to constify the following API:
This patch series is based on the lasted mainline commit
Commit: feffde684ac2 ("Merge tag 'for-6.13-rc1-tag' of
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux")
to avoid potential conflict as much
On 2024/11/30 2:55, Dmitry Baryshkov wrote:
On Wed, Nov 27, 2024 at 03:05:03PM +0800, Yongxing Mou wrote:
Add Mobile Display Subsystem (MDSS) support for the QCS8300 platform.
Signed-off-by: Yongxing Mou
---
drivers/gpu/drm/msm/msm_mdss.c | 11 +++
1 file changed, 11 insertions(+
Hello,
Just a gentle ping, this patch was never applied.
Is there something more that needs to be done?
Thanks and regards,
Advait
On Mon, 14 Oct 2024 at 13:08, Dmitry Baryshkov
wrote:
>
> On Mon, Oct 07, 2024 at 08:39:04PM +0530, Advait Dhamorikar wrote:
> > atmel_hlcdc_plane_update_buffers: m
Hi Laurent,
On 03/12/2024 12:48, Laurent Pinchart wrote:
On Tue, Dec 03, 2024 at 11:22:15AM +0200, Tomi Valkeinen wrote:
On 03/12/2024 10:56, Laurent Pinchart wrote:
On Tue, Dec 03, 2024 at 10:01:40AM +0200, Tomi Valkeinen wrote:
From: Tomi Valkeinen
Add support for r8a779h0. It is very sim
On 04/12/2024 14:54, Michal Wilczynski wrote:
>
>
> On 12/3/24 20:56, Stephen Boyd wrote:
>> Quoting Michal Wilczynski (2024-12-03 05:41:24)
>>> diff --git a/drivers/clk/thead/Makefile b/drivers/clk/thead/Makefile
>>> index 7ee0bec1f251..d7cf88390b69 100644
>>> --- a/drivers/clk/thead/Makefile
>>
On 04/12/2024 11:09, Dmitry Baryshkov wrote:
> On Wed, Dec 04, 2024 at 09:02:18AM +0100, Krzysztof Kozlowski wrote:
>> On Tue, Dec 03, 2024 at 03:41:48PM +0200, Dmitry Baryshkov wrote:
>>> On Tue, Dec 03, 2024 at 09:01:31AM +0100, Krzysztof Kozlowski wrote:
On 03/12/2024 04:31, Abhinav Kumar w
Am 04.12.24 um 15:31 schrieb Jani Nikula:
drm_dev_register() already prints the same information on successful
init. Remove the redundant prints.
Acked-by: Alex Deucher
Signed-off-by: Jani Nikula
---
Note: I prefer to merge this together with the next patch via
drm-misc-next.
Cc: Oleksa
Hi Heiko,
On 12/4/24 00:54, Heiko Stuebner wrote:
From: Heiko Stuebner
The Display Serial Interface 2 (DSI-2) is part of a group of communication
protocols defined by the MIPI Alliance. The RK3588 implements this
specification in its two MIPI DSI-2 Host Controllers that are based on a
new Syno
On Tue, 03 Dec 2024, Thomas Zimmermann wrote:
> Hi
>
>
> Am 03.12.24 um 15:19 schrieb Jocelyn Falempe:
>> On 03/12/2024 15:08, Jani Nikula wrote:
>>> On Tue, 03 Dec 2024, Jocelyn Falempe wrote:
On 03/12/2024 12:06, Jani Nikula wrote:
> On Fri, 15 Nov 2024, Jocelyn Falempe wrote:
>>
Hi Jann,
> Subject: [PATCH 1/3] udmabuf: fix racy memfd sealing check
>
> The current check_memfd_seals() is racy: Since we first do
> check_memfd_seals() and then udmabuf_pin_folios() without holding any
> relevant lock across both, F_SEAL_WRITE can be set in between.
> This is problematic becau
> Subject: [PATCH 2/3] udmabuf: also check for F_SEAL_FUTURE_WRITE
>
> When F_SEAL_FUTURE_WRITE was introduced, it was overlooked that
> udmabuf
> must reject memfds with this flag, just like ones with F_SEAL_WRITE.
> Fix it by adding F_SEAL_FUTURE_WRITE to SEALS_DENIED.
>
> Fixes: ab3948f58ff8 (
On Tue, Dec 03, 2024 at 10:01:35AM +0200, Tomi Valkeinen wrote:
> From: Tomi Valkeinen
>
> Extend the Renesas DSI display bindings to support the r8a779h0 V4M.
>
> Signed-off-by: Tomi Valkeinen
> ---
> .../devicetree/bindings/display/bridge/renesas,dsi-csi2-tx.yaml | 1
> +
> 1 file
Hi Jann,
> Subject: [PATCH 3/3] udmabuf: fix memory leak on last export_udmabuf()
> error path
>
> In export_udmabuf(), if dma_buf_fd() fails because the FD table is full, a
> dma_buf owning the udmabuf has already been created; but the error
> handling
> in udmabuf_create() will tear down the ud
Am 03.12.24 um 18:44 schrieb Thomas Hellström:
On Tue, 2024-12-03 at 17:46 +0100, Christian König wrote:
Am 03.12.24 um 17:43 schrieb Thomas Hellström:
On Tue, 2024-12-03 at 17:39 +0100, Christian König wrote:
Am 03.12.24 um 17:31 schrieb Thomas Hellström:
On Tue, 2024-12-03 at 17:20 +0100, C
Add variables for histogram drm_property, its corrsponding crtc_state
variables and define the structure pointed by the blob property.
struct drm_histogram defined in include/uapi/drm/drm_mode.h
The blob data pointer will be the address of the struct drm_histogram.
The struct drm_histogram will be
Check for any updates on drm_crtc property histogram_enable and
histogram_iet_updated and call/act accordingly to update histogram or
update the image enhancement LUT data API defined in i915 histogram.
v2: corrected the FORTIFY_SOURCE error
Signed-off-by: Arun R Murthy
---
drivers/gpu/drm/i915
Add two new pixel formats:
DRM_FORMAT_XV15 ("XV15")
DRM_FORMAT_XV20 ("XV20")
The formats are 2 plane 10 bit per component YCbCr, with the XV15 2x2
subsampled whereas XV20 is 2x1 subsampled.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/drm_fourcc.c | 8
include/uapi/drm/drm_fourc
Add Y10_LE32, a 10 bit greyscale format, with 3 pixels packed into
32-bit container.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/drm_fourcc.c | 4
include/uapi/drm/drm_fourcc.h | 1 +
2 files changed, 5 insertions(+)
diff --git a/drivers/gpu/drm/drm_fourcc.c b/drivers/gpu/drm/drm_fo
Add support for Y8 and Y10_LE32 formats. We also need to add new csc
matrices for the y-only formats.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/xlnx/zynqmp_disp.c | 26 +-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xlnx/zynqmp_di
Add support for XV15 & XV20 formats.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/xlnx/zynqmp_disp.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/gpu/drm/xlnx/zynqmp_disp.c
b/drivers/gpu/drm/xlnx/zynqmp_disp.c
index 57221575cbd6..3998754e367e 100644
--- a/drivers
Use drm helpers, drm_format_info_plane_width(),
drm_format_info_plane_height() and drm_format_info_min_pitch() to
calculate sizes for the DMA.
This cleans up the code, but also makes it possible to support more
complex formats (like XV15, XV20).
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm
Add greyscale Y8 format.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/drm_fourcc.c | 1 +
include/uapi/drm/drm_fourcc.h | 3 +++
2 files changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/drm_fourcc.c b/drivers/gpu/drm/drm_fourcc.c
index adb2d44630ee..d721d9fdbe98 100644
--- a/drivers/
Fix "mapping sg segment longer than device claims to support" warning by
setting the max segment size.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/xlnx/zynqmp_dpsub.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/xlnx/zynqmp_dpsub.c
b/drivers/gpu/drm/xlnx/zynqmp_dp
Add new DRM pixel formats and add support for those in the Xilinx zynqmp
display driver.
All of these formats are already supported in upstream gstreamer, except
in the gstreamer kmssink, which obviously cannot support the formats
without kernel having the formats.
Xilinx has support for these fo
On Wed, 2024-12-04 at 10:16 +0100, Christian König wrote:
> Am 03.12.24 um 18:44 schrieb Thomas Hellström:
> > On Tue, 2024-12-03 at 17:46 +0100, Christian König wrote:
> > > Am 03.12.24 um 17:43 schrieb Thomas Hellström:
> > > > On Tue, 2024-12-03 at 17:39 +0100, Christian König wrote:
> > > > > A
On Wed, Dec 04, 2024 at 09:02:18AM +0100, Krzysztof Kozlowski wrote:
> On Tue, Dec 03, 2024 at 03:41:48PM +0200, Dmitry Baryshkov wrote:
> > On Tue, Dec 03, 2024 at 09:01:31AM +0100, Krzysztof Kozlowski wrote:
> > > On 03/12/2024 04:31, Abhinav Kumar wrote:
> > > > Document the assigned-clock-paren
https://bugzilla.kernel.org/show_bug.cgi?id=219556
Artem S. Tashkinov (a...@gmx.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
On Tue, Dec 03, 2024 at 07:24:46PM -0800, Abhinav Kumar wrote:
>
>
> On 12/3/2024 5:53 AM, Dmitry Baryshkov wrote:
> > On Mon, Dec 02, 2024 at 04:39:01PM -0800, Abhinav Kumar wrote:
> > > The checks in msm_dp_display_prepare() for making sure that we are in
> > > ST_DISPLAY_OFF OR ST_MAINLINK_REA
On Tue, Dec 03, 2024 at 07:57:25PM -0800, Abhinav Kumar wrote:
>
>
> On 12/3/2024 3:38 PM, Dmitry Baryshkov wrote:
> > On Mon, Dec 02, 2024 at 12:42:00PM -0800, Abhinav Kumar wrote:
> > > DP test pattern generator is a very useful tool to debug issues
> > > where monitor is showing incorrect outp
"^display-controller@[0-9a-f]+$":
---
base-commit: 667ff2368867af7000ce32a8b3fc025c2b3226b3
change-id: 20241204-topic-misc-sm8350-mdss-bindings-fix-1701baffc1aa
Best regards,
--
Neil Armstrong
Hi Liu Ying,
Thanks for your review.
On Wed, Dec 04, 2024 at 11:34:23AM +0800, Liu Ying wrote:
> On 12/04/2024, tomm.merc...@gmail.com wrote:
> > From: Tommaso Merciai
> >
> > Introduce it6263_is_input_bus_fmt_valid() and refactor the
> > it6263_bridge_atomic_get_input_bus_fmts() function to sup
Hi Marek,
On 03.12.2024 21:15, Marek Vasut wrote:
On 12/3/24 8:09 PM, Nikolaus Voss wrote:
LDB clock has to be a fixed multiple of the pixel clock.
As LDB and pixel clock are derived from different clock sources
Can you please share the content of /sys/kernel/debug/clk/clk_summary ?
Sure. W
If there's going to be another version (to fix this) ...
On Wed Dec 4, 2024 at 3:16 AM CET, Kever Yang wrote:
> On 2024/12/4 00:54, Heiko Stuebner wrote:
> > From: Heiko Stuebner
> >
> > This adds the glue code for the MIPI DSI2 bridge on Rockchip SoCs and
> > enables its use on the RK3588.
> >
>
Hi Julia,
sorry I totally missed your mail.
The basic problem for P2P is what I already described in my previous mail:
Well the problem is the virtualized environment. pci_p2pdma_distance()
checks if two physical PCI devices can communicate with each other
(and returns how many hops are in be
Hi Marek,
On 04.12.2024 00:40, Marek Vasut wrote:
On 12/3/24 8:20 AM, Nikolaus Voss wrote:
On 03.12.2024 04:12, Marek Vasut wrote:
On 12/3/24 3:22 AM, Liu Ying wrote:
[...]
I doubt that pixel clock tree cannot find appropriate division
ratios
for some pixel clock rates, especially for dual-
https://bugzilla.kernel.org/show_bug.cgi?id=219556
--- Comment #2 from Hanabishi (i.r.e.c.c.a.k.u.n+bugzilla.kernel@gmail.com)
---
https://gitlab.freedesktop.org/drm/amd/-/issues/3811
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the
These drivers don't use the driver_data member of struct i2c_device_id,
so don't explicitly initialize this member.
This prepares putting driver_data in an anonymous union which requires
either no initialization or named designators. But it's also a nice
cleanup on its own.
While add it, also rem
Am 04.12.24 um 10:56 schrieb Thomas Hellström:
On Wed, 2024-12-04 at 10:16 +0100, Christian König wrote:
Am 03.12.24 um 18:44 schrieb Thomas Hellström:
On Tue, 2024-12-03 at 17:46 +0100, Christian König wrote:
Am 03.12.24 um 17:43 schrieb Thomas Hellström:
On Tue, 2024-12-03 at 17:39 +0100, C
On Wed, 2024-12-04 at 11:56 +0100, Christian König wrote:
> Am 04.12.24 um 10:56 schrieb Thomas Hellström:
> > On Wed, 2024-12-04 at 10:16 +0100, Christian König wrote:
> > > Am 03.12.24 um 18:44 schrieb Thomas Hellström:
> > > > On Tue, 2024-12-03 at 17:46 +0100, Christian König wrote:
> > > > > A
+ misc maintainers
On Tue, Dec 03, 2024 at 11:18:00AM +0100, Christian König wrote:
> Am 03.12.24 um 06:00 schrieb Raag Jadav:
> > On Mon, Dec 02, 2024 at 10:07:59AM +0200, Raag Jadav wrote:
> > > On Fri, Nov 29, 2024 at 10:40:14AM -0300, André Almeida wrote:
> > > > Hi Raag,
> > > >
> > > > Em 2
On Wed, Dec 04, 2024 at 11:36:37AM +0100, Neil Armstrong wrote:
> Document the missing third "cpu-cfg" interconnect path for the MDSS hardware
> found on the Qualcomm SM8350 platform.
>
> This fixes:
> display-subsystem@ae0: interconnects: [[121, 7, 0, 77, 1, 0], [121, 8, 0,
> 77, 1, 0], [78,
Am 04.12.24 um 12:09 schrieb Thomas Hellström:
[SNIP]
BTW I really dislike that tt->restore is allocated dynamically.
That
is
just another allocation which can cause problems.
We should probably have all the state necessary for the operation
in
the
TT object.
Initially it was done this way. B
Add X403, a 3 plane non-subsampled YCbCr format.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/drm_fourcc.c | 4
include/uapi/drm/drm_fourcc.h | 8
2 files changed, 12 insertions(+)
diff --git a/drivers/gpu/drm/drm_fourcc.c b/drivers/gpu/drm/drm_fourcc.c
index 6048e0a191dc..2
cumentation/devicetree/bindings/display/msm/qcom,sm8350-mdss.example.dtb:
display-subsystem@ae0: interconnect-names: ['mdp0-mem', 'mdp1-mem'] is too
short
from schema $id:
http://devicetree.org/schemas/display/msm/qcom,sm8350-mdss.yaml#
doc reference errors
On Wed, Dec 04, 2024 at 02:44:56PM +0530, Arun R Murthy wrote:
> Add variables for histogram drm_property, its corrsponding crtc_state
> variables and define the structure pointed by the blob property.
> struct drm_histogram defined in include/uapi/drm/drm_mode.h
> The blob data pointer will be the
On 02/12/24 11:06, Christian Gmeiner wrote:
From: Christian Gmeiner
Add a new ioctl, DRM_IOCTL_V3D_PERFMON_SET_GLOBAL, to allow
configuration of a global performance monitor (perfmon).
Use the global perfmon for all jobs to ensure consistent
performance tracking across submissions. This feature
On Wed, Dec 04, 2024 at 11:37:05AM +0100, Tommaso Merciai wrote:
> Hi Liu Ying,
> Thanks for your review.
>
> On Wed, Dec 04, 2024 at 11:34:23AM +0800, Liu Ying wrote:
> > On 12/04/2024, tomm.merc...@gmail.com wrote:
> > > From: Tommaso Merciai
> > >
> > > Introduce it6263_is_input_bus_fmt_valid
drm_format_info_bpp() cannot be used for formats which do not have an
integer bits-per-pixel. Handle wrong calls by printing a warning and
returning 0.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/drm_fourcc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/gpu/drm/drm_fo
Add support for X403 format.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/xlnx/zynqmp_disp.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/gpu/drm/xlnx/zynqmp_disp.c
b/drivers/gpu/drm/xlnx/zynqmp_disp.c
index 44cfee6a0e32..622d1dfac42d 100644
--- a/drivers/gpu/drm/xlnx/z
Hi
Am 03.12.24 um 20:51 schrieb Matthew Wilcox:
I've pushed out a new tree to
git://git.infradead.org/users/willy/pagecache.git shrunk-page
aka
http://git.infradead.org/?p=users/willy/pagecache.git;a=shortlog;h=refs/heads/shrunk-page
The observant will notice that it doesn't actually shrink st
drm_panel_init() was made to initialize the fields in |struct drm_panel|.
There is no need to separately initialize them again.
Drop the separate assignments that are redundant. Also fix up any uses
of `ctx->panel.dev` to use `dev` directly.
Signed-off-by: Chen-Yu Tsai
---
Changes since v1:
- Al
On Wed, 2024-12-04 at 12:24 +0100, Christian König wrote:
> Am 04.12.24 um 12:09 schrieb Thomas Hellström:
> > [SNIP]
>
> > > > > BTW I really dislike that tt->restore is allocated
> > > > > dynamically.
> > > > > That
> > > > > is
> > > > > just another allocation which can cause problems.
> > >
On 2024/12/3 23:34, James Bottomley wrote:
>>> This also enables an incremental migration.
>> change the API prototype from:
>> device_find_child(..., void *data_0, int (*match)(struct device *dev,
>> void *data));
>>
>> to:
>> device_find_child(..., const void *data_0, int (*match)(struct device
>
On the Raspberry Pi 5, performance counters are not being cleared
when `v3d_perfmon_start()` is called, even though we write to the
CLR register. As a result, their values accumulate until they
overflow.
The expected behavior is for performance counters to reset to zero
at the start of a job. When
ke refcheckdocs):
See
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20241204-topic-misc-sm8350-mdss-bindings-fix-v1-1-aa492a306...@linaro.org
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'm
Reviewed-by: Iago Toral Quiroga
El mié, 04-12-2024 a las 09:28 -0300, Maíra Canal escribió:
> On the Raspberry Pi 5, performance counters are not being cleared
> when `v3d_perfmon_start()` is called, even though we write to the
> CLR register. As a result, their values accumulate until they
> ove
drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Nikolaus-Voss/drm-bridge-fsl-ldb-fixup-mode-on-freq-mismatch/20241204-115306
bas
Hi Heiko,
On 12/4/24 00:54, Heiko Stuebner wrote:
From: Heiko Stuebner
This adds the glue code for the MIPI DSI2 bridge on Rockchip SoCs and
enables its use on the RK3588.
Right now the DSI2 controller is always paired with a DC-phy based on a
Samsung IP, so the interface values are set stati
e' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Fei-Shao/drm-mediatek-dp-Support-flexible-length-of-DP-calibration-data/20241204-133854
base: linus/master
patch link:
https://lore.ke
Hi Dmitry,
On Wed, Dec 04, 2024 at 01:53:44PM +0200, Dmitry Baryshkov wrote:
> On Wed, Dec 04, 2024 at 11:37:05AM +0100, Tommaso Merciai wrote:
> > Hi Liu Ying,
> > Thanks for your review.
> >
> > On Wed, Dec 04, 2024 at 11:34:23AM +0800, Liu Ying wrote:
> > > On 12/04/2024, tomm.merc...@gmail.co
While receiving an MST up request message from one thread in
drm_dp_mst_handle_up_req(), the MST topology could be removed from
another thread via drm_dp_mst_topology_mgr_set_mst(false), freeing
mst_primary and setting drm_dp_mst_topology_mgr::mst_primary to NULL.
This could lead to a NULL deref/us
On Wed, Dec 04, 2024 at 02:11:28PM +0100, Tommaso Merciai wrote:
> Hi Dmitry,
>
> On Wed, Dec 04, 2024 at 01:53:44PM +0200, Dmitry Baryshkov wrote:
> > On Wed, Dec 04, 2024 at 11:37:05AM +0100, Tommaso Merciai wrote:
> > > Hi Liu Ying,
> > > Thanks for your review.
> > >
> > > On Wed, Dec 04, 202
On Wed, Dec 04, 2024 at 03:33:09PM +0200, Dmitry Baryshkov wrote:
> On Wed, Dec 04, 2024 at 02:11:28PM +0100, Tommaso Merciai wrote:
> > Hi Dmitry,
> >
> > On Wed, Dec 04, 2024 at 01:53:44PM +0200, Dmitry Baryshkov wrote:
> > > On Wed, Dec 04, 2024 at 11:37:05AM +0100, Tommaso Merciai wrote:
> > >
Similar to xe, enable some simple management of VRAM only.
Co-developed-by: Maxime Ripard
Signed-off-by: Maxime Ripard
Signed-off-by: Maarten Lankhorst
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vra
This code is based on the RDMA and misc cgroup initially, but now
uses page_counter. It uses the same min/low/max semantics as the memory
cgroup as a result.
There's a small mismatch as TTM uses u64, and page_counter long pages.
In practice it's not a problem. 32-bits systems don't really come wit
Add vram based cgroup eviction to Xe.
Most hardware with VRAM uses TTM for its management, and can be
similarly trivially enabled.
Co-developed-by: Maxime Ripard
Signed-off-by: Maxime Ripard
Signed-off-by: Maarten Lankhorst
---
drivers/gpu/drm/xe/xe_ttm_vram_mgr.c | 8
1 file changed,
On Tue, 3 Dec 2024 at 20:04, Greg Kroah-Hartman
wrote:
>
> --
> Note, this is the LAST 4.19.y kernel to be released. After this one, it
> is end-of-life. It's been 6 years, everyone should have moved off of it
> by now.
> --
>
> This is the start of the stable rev
: 44cff6c5b0b17a78bc0b30372bcd816cf6dd282a
patch link:
https://lore.kernel.org/r/20241203092836.426422-2-jfalempe%40redhat.com
patch subject: [PATCH v2 1/5] drm/i915/fbdev: Add intel_fbdev_get_vaddr()
config: i386-randconfig-062-20241204
(https://download.01.org/0day-ci/archive/20241204/202412042119.5erpnlau
Hi Dave, Simona
Two xe fixes for -rc2
Thanks,
Thomas
drm-xe-fixes-2024-12-04:
Driver Changes:
- Missing init value and 64-bit write-order check (Zhanjung)
- Fix a memory allocation issue causing lockdep violation (John)
The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
On Tue, Dec 03, 2024 at 10:02:00AM -0600, Gax-c wrote:
> From: Zichen Xie
>
> Like commit b0b0d811eac6 ("drm/mediatek: Fix coverity issue with
> unintentional integer overflow"), directly multiply pitch and
> height may lead to integer overflow. Add a cast to avoid it.
>
> Fixes: 6d1782919dc9 ("
New update. Instead of calling it the 'dev' cgroup, it's now the 'dmem' cgroup.
Because it only deals with memory regions, the UAPI has been updated to use
dmem.min/low/max/current, and to make the API cleaner, the names are changed
too.
dmem.current could contain a line like:
"drm/:03:00.0
From: Maxime Ripard
This allows any driver using the VRAM helper to set limits on VRAM using
cgroup.
Signed-off-by: Maxime Ripard
Signed-off-by: Maarten Lankhorst
---
drivers/gpu/drm/drm_gem_vram_helper.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/driv
We will probably want to make this a proper region in TTM for
everything, so that we can charge VRAM twice, once for mapped
in sysmem, once for mapped in vram. That way we don't need to
deal with evict failing from lack of available memory in mapped.
Signed-off-by: Maxime Ripard
Signed-off-by: Ma
From: Maxime Ripard
Drivers will need to register dmem regions at probe time, so let's
give them a drm-managed helper.
Signed-off-by: Maxime Ripard
Signed-off-by: Maarten Lankhorst
---
drivers/gpu/drm/drm_drv.c | 32
include/drm/drm_drv.h | 5 +
2 fil
On Sun, Nov 24, 2024 at 08:06:48PM +0530, Aradhya Bhatia wrote:
> From: Aradhya Bhatia
>
> The OLDI transmitters (TXes) do not have registers of their own, and are
> dependent on the source video-ports (VPs) from the DSS to provide
> configuration data. This hardware doesn't directly sit on the i
On 29-10-24, 14:02, Sandor Yu wrote:
> Allow HDMI PHYs to be configured through the generic
> functions through a custom structure added to the generic union.
>
> The parameters added here are based on HDMI PHY
> implementation practices. The current set of parameters
> should cover the potential
1 - 100 of 190 matches
Mail list logo
