From: Robin Murphy <robin.murphy@arm.com>
To: Beata Michalska <beata.michalska@arm.com>,
dakr@kernel.org, ojeda@kernel.org, gary@garyguo.net,
rust-for-linux@vger.kernel.org, dirk.behme@gmail.com
Cc: abdiel.janulgue@gmail.com, daniel.almeida@collabora.com,
aliceryhl@google.com, a.hindborg@kernel.org,
boqun.feng@gmail.com, bjorn3_gh@protonmail.com,
lossin@kernel.org, tmgross@umich.edu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] rust: dma: allow drivers to tune max segment size
Date: Wed, 28 Jan 2026 14:39:31 +0000 [thread overview]
Message-ID: <ad8ce64b-0291-4322-b8db-a8b351e2e75f@arm.com> (raw)
In-Reply-To: <20260128135320.689046-1-beata.michalska@arm.com>
On 2026-01-28 1:53 pm, Beata Michalska wrote:
> Make dma_set_max_seg_size() available to Rust so drivers can perform
> standard DMA setup steps.
Yup, API-wise this goes hand-in-hand with dma_set_mask calls, so keeping
all the requirements in sync is the right thing to do. FWIW,
Acked-by: Robin Murphy <robvin.murphy@arm.com>
> Signed-off-by: Beata Michalska <beata.michalska@arm.com>
> ---
> Apologies for delay.
>
> v3:
> - Added __rust_helper
>
> v2:
> - Aligned safety requirements
>
> rust/helpers/dma.c | 6 ++++++
> rust/kernel/dma.rs | 17 +++++++++++++++++
> 2 files changed, 23 insertions(+)
>
> diff --git a/rust/helpers/dma.c b/rust/helpers/dma.c
> index e7defeecda71..20232ac64850 100644
> --- a/rust/helpers/dma.c
> +++ b/rust/helpers/dma.c
> @@ -43,3 +43,9 @@ size_t rust_helper_dma_max_mapping_size(struct device *dev)
> {
> return dma_max_mapping_size(dev);
> }
> +
> +__rust_helper void rust_helper_dma_set_max_seg_size(struct device *dev,
> + unsigned int size)
> +{
> + dma_set_max_seg_size(dev, size);
> +}
> diff --git a/rust/kernel/dma.rs b/rust/kernel/dma.rs
> index acc65b1e0f24..909d56fd5118 100644
> --- a/rust/kernel/dma.rs
> +++ b/rust/kernel/dma.rs
> @@ -85,6 +85,23 @@ unsafe fn dma_set_mask_and_coherent(&self, mask: DmaMask) -> Result {
> bindings::dma_set_mask_and_coherent(self.as_ref().as_raw(), mask.value())
> })
> }
> +
> + /// Set the maximum size of a single DMA segment the device may request.
> + ///
> + /// This method is usually called once from `probe()` as soon as the device capabilities are
> + /// known.
> + ///
> + /// # Safety
> + ///
> + /// This method must not be called concurrently with any DMA allocation or mapping primitives,
> + /// such as [`CoherentAllocation::alloc_attrs`].
> + unsafe fn dma_set_max_seg_size(&self, size: u32) {
> + // SAFETY:
> + // - By the type invariant of `device::Device`, `self.as_ref().as_raw()` is valid.
> + // - The safety requirement of this function guarantees that there are no concurrent calls
> + // to DMA allocation and mapping primitives using this parameter.
> + unsafe { bindings::dma_set_max_seg_size(self.as_ref().as_raw(), size) }
> + }
> }
>
> /// A DMA mask that holds a bitmask with the lowest `n` bits set.
next prev parent reply other threads:[~2026-01-28 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 13:53 Beata Michalska
2026-01-28 14:11 ` Alice Ryhl
2026-01-28 14:39 ` Robin Murphy [this message]
2026-01-28 17:17 ` Danilo Krummrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad8ce64b-0291-4322-b8db-a8b351e2e75f@arm.com \
--to=robin.murphy@arm.com \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=aliceryhl@google.com \
--cc=beata.michalska@arm.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dirk.behme@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®