[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z5Cci6ixvu5ePdlR@ninjato>
Date: Wed, 22 Jan 2025 08:21:47 +0100
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>
Cc: Billy Tsai <billy_tsai@...eedtech.com>, 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
> what we need is only i2c_xfers->buf to be DMA-safe, not the *i2c_xfers.
> Right ?
Yes.
> Also I guess same change is required for all the vendor drivers. But Not
> sure if it's feasible with this patch ?
I also wondered if the I3C core should maybe provide this, but then I
saw that currently only the mipi-hci driver uses DMA and concluded that
per-driver is better. At least for now.
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists