[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z5AdQ9UZWbW_1Dj_@ninjato>
Date: Tue, 21 Jan 2025 23:18:43 +0100
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
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, 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 Tue, Jan 21, 2025 at 07:07:55PM +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.
>
> Signed-off-by: Billy Tsai <billy_tsai@...eedtech.com>
Makes sense to me:
Reviewed-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists