[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <23854752-435e-432e-ba21-caf690c0cecc@t-8ch.de>
Date: Wed, 22 Jan 2025 09:42:27 +0100
From: Thomas Weißschuh <linux@...ssschuh.net>
To: Billy Tsai <billy_tsai@...eedtech.com>
Cc: alexandre.belloni@...tlin.com, pgaj@...ence.com,
miquel.raynal@...tlin.com, conor.culhane@...vaco.com, aniketmaurya@...gle.com,
Shyam-sundar.S-k@....com, jarkko.nikula@...ux.intel.com, wsa+renesas@...g-engineering.com,
xiaopei01@...inos.cn, Guruvendra.Punugupati@....com, linux-i3c@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/2] i3c: Remove the const qualifier from i2c_msg
pointer in i2c_xfers API
On 2025-01-21 19:07:55+0800, Billy Tsai wrote:
> The change is necessary to enable the use of the
> `i2c_get_dma_safe_msg_buf()` API, which requires a non-const
> `struct i2c_msg *` to operate. The `i2c_get_dma_safe_msg_buf()` function
> ensures safe handling of I2C messages when using DMA, making it essential
> for scenarios where DMA transfers are involved. By removing the `const`
> qualifier, this patch allows drivers to prepare and manage DMA-safe
> buffers directly.
Why not modify i2c_get_dma_safe_msg_buf() to accept
'const struct i2c_msg' instead?
> Signed-off-by: Billy Tsai <billy_tsai@...eedtech.com>
> ---
> drivers/i3c/master/dw-i3c-master.c | 2 +-
> drivers/i3c/master/i3c-master-cdns.c | 2 +-
> drivers/i3c/master/mipi-i3c-hci/core.c | 2 +-
> drivers/i3c/master/svc-i3c-master.c | 2 +-
> include/linux/i3c/master.h | 2 +-
> 5 files changed, 5 insertions(+), 5 deletions(-)
Powered by blists - more mailing lists