The preceding patches added support for resources, and for a general
IoMem abstraction, but thus far there is no way to access said IoMem
from drivers, as its creation is unsafe and depends on a resource that
must be acquired from some device first.
Now, allow the ioremap of platform resources themselves, thereby making
the IoMem available to platform drivers.
Signed-off-by: Daniel Almeida <daniel.almeida@collabora.com>
---
rust/kernel/platform.rs | 123 +++++++++++++++++++++++++++++++++++++++-
1 file changed, 122 insertions(+), 1 deletion(-)
diff --git a/rust/kernel/platform.rs b/rust/kernel/platform.rs
index 50e6b0421813..0ab10d2dfd5e 100644
--- a/rust/kernel/platform.rs
+++ b/rust/kernel/platform.rs
@@ -5,8 +5,14 @@
//! C header: [`include/linux/platform_device.h`](srctree/include/linux/platform_device.h)
use crate::{
- bindings, container_of, device, driver,
+ bindings, container_of, device,
+ devres::Devres,
+ driver,
error::{to_result, Result},
+ io::{
+ mem::{ExclusiveIoMem, IoMem},
+ resource::Resource,
+ },
of,
prelude::*,
str::CStr,
@@ -191,6 +197,121 @@ fn as_raw(&self) -> *mut bindings::platform_device {
// embedded in `struct platform_device`.
unsafe { container_of!(self.0.as_raw(), bindings::platform_device, dev) }.cast_mut()
}
+
+ /// Maps a platform resource through ioremap() where the size is known at
+ /// compile time.
+ ///
+ /// # Examples
+ ///
+ /// ```no_run
+ /// use kernel::{bindings, c_str, platform};
+ ///
+ /// fn probe(pdev: &mut platform::Device, /* ... */) -> Result<()> {
+ /// let offset = 0; // Some offset.
+ ///
+ /// // If the size is known at compile time, use `ioremap_resource_sized`.
+ /// // No runtime checks will apply when reading and writing.
+ /// let resource = pdev.resource(0).ok_or(ENODEV)?;
+ /// let iomem = pdev.ioremap_resource_sized::<42>(&resource)?;
+ ///
+ /// // Read and write a 32-bit value at `offset`. Calling `try_access()` on
+ /// // the `Devres` makes sure that the resource is still valid.
+ /// let data = iomem.try_access().ok_or(ENODEV)?.readl(offset);
+ ///
+ /// iomem.try_access().ok_or(ENODEV)?.writel(data, offset);
+ ///
+ /// # Ok::<(), Error>(())
+ /// }
+ /// ```
+ pub fn ioremap_resource_sized<const SIZE: usize>(
+ &self,
+ resource: &Resource,
+ ) -> Result<Devres<IoMem<SIZE>>> {
+ IoMem::new(resource, self.as_ref())
+ }
+
+ /// Same as [`Self::ioremap_resource_sized`] but with exclusive access to the
+ /// underlying region.
+ pub fn ioremap_resource_exclusive_sized<const SIZE: usize>(
+ &self,
+ resource: &Resource,
+ ) -> Result<Devres<ExclusiveIoMem<SIZE>>> {
+ ExclusiveIoMem::new(resource, self.as_ref())
+ }
+
+ /// Maps a platform resource through ioremap().
+ ///
+ /// # Examples
+ ///
+ /// ```no_run
+ /// # use kernel::{bindings, c_str, platform};
+ ///
+ /// fn probe(pdev: &mut platform::Device, /* ... */) -> Result<()> {
+ /// let offset = 0; // Some offset.
+ ///
+ /// // Unlike `ioremap_resource_sized`, here the size of the memory region
+ /// // is not known at compile time, so only the `try_read*` and `try_write*`
+ /// // family of functions are exposed, leading to runtime checks on every
+ /// // access.
+ /// let resource = pdev.resource(0).ok_or(ENODEV)?;
+ /// let iomem = pdev.ioremap_resource(&resource)?;
+ ///
+ /// let data = iomem.try_access().ok_or(ENODEV)?.try_readl(offset)?;
+ ///
+ /// iomem.try_access().ok_or(ENODEV)?.try_writel(data, offset)?;
+ ///
+ /// # Ok::<(), Error>(())
+ /// }
+ /// ```
+ pub fn ioremap_resource(&self, resource: &Resource) -> Result<Devres<IoMem<0>>> {
+ self.ioremap_resource_sized::<0>(resource)
+ }
+
+ /// Same as [`Self::ioremap_resource`] but with exclusive access to the underlying
+ /// region.
+ pub fn ioremap_resource_exclusive(
+ &self,
+ resource: &Resource,
+ ) -> Result<Devres<ExclusiveIoMem<0>>> {
+ self.ioremap_resource_exclusive_sized::<0>(resource)
+ }
+
+ /// Returns the resource at `index`, if any.
+ pub fn resource(&self, index: u32) -> Option<&Resource> {
+ // SAFETY: `self.as_raw()` returns a valid pointer to a `struct platform_device`.
+ let resource = unsafe {
+ bindings::platform_get_resource(self.as_raw(), bindings::IORESOURCE_MEM, index)
+ };
+
+ if resource.is_null() {
+ return None;
+ }
+
+ // SAFETY: `resource` is a valid pointer to a `struct resource` as
+ // returned by `platform_get_resource`.
+ Some(unsafe { Resource::from_ptr(resource) })
+ }
+
+ /// Returns the resource with a given `name`, if any.
+ pub fn resource_by_name(&self, name: &CStr) -> Option<&Resource> {
+ // SAFETY: `self.as_raw()` returns a valid pointer to a `struct
+ // platform_device` and `name` points to a valid C string.
+ let resource = unsafe {
+ bindings::platform_get_resource_byname(
+ self.as_raw(),
+ bindings::IORESOURCE_MEM,
+ name.as_char_ptr(),
+ )
+ };
+
+ if resource.is_null() {
+ return None;
+ }
+
+ // SAFETY: `resource` is a valid pointer to a `struct resource` as
+ // returned by `platform_get_resource`.
+ Some(unsafe { Resource::from_ptr(resource) })
+ }
}
impl AsRef<device::Device> for Device {
--
2.48.0
Hi, On 1/30/25 11:05 PM, Daniel Almeida wrote: > + > + /// Same as [`Self::ioremap_resource`] but with exclusive access to the underlying > + /// region. > + pub fn ioremap_resource_exclusive( > + &self, > + resource: &Resource, > + ) -> Result<Devres<ExclusiveIoMem<0>>> { > + self.ioremap_resource_exclusive_sized::<0>(resource) > + } > + > + /// Returns the resource at `index`, if any. > + pub fn resource(&self, index: u32) -> Option<&Resource> { Maybe we could utilize the Index [1] trait to make the API more rust~ish? Or at least name it `resource_by_index` to keep consistency with `resource_by_name`? Link: https://doc.rust-lang.org/core/ops/trait.Index.html [1] > + // SAFETY: `self.as_raw()` returns a valid pointer to a `struct platform_device`. > + let resource = unsafe { > + bindings::platform_get_resource(self.as_raw(), bindings::IORESOURCE_MEM, index) > + }; > + > + if resource.is_null() { > + return None; > + } > + > + // SAFETY: `resource` is a valid pointer to a `struct resource` as > + // returned by `platform_get_resource`. > + Some(unsafe { Resource::from_ptr(resource) }) > + } > + > + /// Returns the resource with a given `name`, if any. > + pub fn resource_by_name(&self, name: &CStr) -> Option<&Resource> { > + // SAFETY: `self.as_raw()` returns a valid pointer to a `struct > + // platform_device` and `name` points to a valid C string. > + let resource = unsafe { > + bindings::platform_get_resource_byname( > + self.as_raw(), > + bindings::IORESOURCE_MEM, > + name.as_char_ptr(), > + ) > + }; > + > + if resource.is_null() { > + return None; > + } > + > + // SAFETY: `resource` is a valid pointer to a `struct resource` as > + // returned by `platform_get_resource`. > + Some(unsafe { Resource::from_ptr(resource) }) > + } > } > > impl AsRef<device::Device> for Device { Daniel
On Fri, Jan 31, 2025 at 11:19 AM Daniel Sedlak <daniel@sedlak.dev> wrote: > > Hi, > > On 1/30/25 11:05 PM, Daniel Almeida wrote: > > + > > + /// Same as [`Self::ioremap_resource`] but with exclusive access to the underlying > > + /// region. > > + pub fn ioremap_resource_exclusive( > > + &self, > > + resource: &Resource, > > + ) -> Result<Devres<ExclusiveIoMem<0>>> { > > + self.ioremap_resource_exclusive_sized::<0>(resource) > > + } > > + > > + /// Returns the resource at `index`, if any. > > + pub fn resource(&self, index: u32) -> Option<&Resource> { > > Maybe we could utilize the Index [1] trait to make the API more rust~ish? > Or at least name it `resource_by_index` to keep consistency with > `resource_by_name`? > > Link: https://doc.rust-lang.org/core/ops/trait.Index.html [1] Using the index trait would result in syntax like device[7] to get the resource at index 7. I think that would be unclear because it's not obvious that devices should behave like an array of resources. Alice
© 2016 - 2025 Red Hat, Inc.