From: Dirk Behme <dirk.behme@gmail.com>
To: Beata Michalska <beata.michalska@arm.com>,
dakr@kernel.org, ojeda@kernel.org,
rust-for-linux@vger.kernel.org
Cc: abdiel.janulgue@gmail.com, daniel.almeida@collabora.com,
aliceryhl@google.com, robin.murphy@arm.com,
a.hindborg@kernel.org, boqun.feng@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, lossin@kernel.org, tmgross@umich.edu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rust: dma: allow drivers to tune max segment size
Date: Fri, 23 Jan 2026 17:39:48 +0100 [thread overview]
Message-ID: <70412586-7b40-4230-bc21-504a865e3376@gmail.com> (raw)
In-Reply-To: <20260123131308.3218421-1-beata.michalska@arm.com>
On 23.01.26 14:13, Beata Michalska wrote:
> Make dma_set_max_seg_size() available to Rust so drivers can perform
> standard DMA setup steps.
>
> Signed-off-by: Beata Michalska <beata.michalska@arm.com>
> ---
>
> v2:
> - Aligned safety requirements
>
> rust/helpers/dma.c | 5 +++++
> rust/kernel/dma.rs | 17 +++++++++++++++++
> 2 files changed, 22 insertions(+)
>
> diff --git a/rust/helpers/dma.c b/rust/helpers/dma.c
> index 2afa32c21c94..220b9308830f 100644
> --- a/rust/helpers/dma.c
> +++ b/rust/helpers/dma.c
> @@ -40,3 +40,8 @@ size_t rust_helper_dma_max_mapping_size(struct device *dev)
> {
> return dma_max_mapping_size(dev);
> }
> +
> +void rust_helper_dma_set_max_seg_size(struct device *dev, unsigned int size)
> +{
> + dma_set_max_seg_size(dev, size);
> +}
I was about to ask "please add __rust_helper" [1]. But looking into
driver-core-next it looks like some of the function in dma.c have
__rust_helper (from [1]) and some don't (from [2]). Is this by
intention or was this an omission in [2]?
Best regards
Dirk
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git/commit/rust/helpers/dma.c?h=driver-core-next&id=8a03afe94763108537e33b48378bbc7472b4cc9d
[2]
https://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git/commit/rust/helpers/dma.c?h=driver-core-next&id=d8932355f8c5673106eca49abd142f8fe0c1fe8b
next prev parent reply other threads:[~2026-01-23 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 13:13 Beata Michalska
2026-01-23 16:39 ` Dirk Behme [this message]
2026-01-23 16:48 ` Gary Guo
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=70412586-7b40-4230-bc21-504a865e3376@gmail.com \
--to=dirk.behme@gmail.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=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=robin.murphy@arm.com \
--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®