Unable to handle kernel paging request at virtual address 0x7e005070 解决办法

最新推荐文章于 2024-10-24 18:05:46 发布

原创最新推荐文章于 2024-10-24 18:05:46 发布 · 7.5k 阅读

1 ·

CC 4.0 BY-SA版权

文章标签：

#linux #linux driver

Review Note 同时被 2 个专栏收录

77 篇文章

订阅专栏

Linux Devices Driver

21 篇文章

订阅专栏

本文探讨了在给s3c6410的RTC编写驱动程序时遇到的readl()和inl()读取I/O端口报错问题。该问题是由于虚拟内存技术导致无法直接使用物理地址引发的。文章介绍了通过使用ioremap函数将物理地址映射到虚拟地址空间来解决这一问题的方法。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

有点标题党的味道了~

对于readl() 和 inl() 读取I/O端口报错的探究

给s3c6410的RTC写demo driver的时候遇到这个问题...

如图

这是虚拟内存技术导致的问题，不能直接使用物理地址(不过这里有个疑问，我上次给PC写的CMOS driver貌似用的是物理地址,布吉岛为嘛)

解决办法就是调用ioremap函数转换物理地址，重新映射IO端口到虚拟地址中

Once equipped with ioremap (and iounmap), a device driver can access any I/O memory address, whether or not it is directly mapped to virtual address space. Remember, though, that the addresses returned from ioremap should not be dereferenced directly; instead, accessor functions provided by the kernel should be used. Before we get into those functions, we’d better review the ioremap prototypes and introduce a few details that we passed over in the previous chapter.

The functions are called according to the following definition:

#include <asm/io.h>
void *ioremap(unsigned long phys_addr, unsigned long size);
void *ioremap_nocache(unsigned long phys_addr, unsigned long size);
void iounmap(void * addr);

First of all, you notice the new function ioremap_nocache. We didn’t cover it in Chapter 8, because its meaning is definitely hardware related. Quoting from one of the kernel headers: “It’s useful if some control registers are in such an area, and write combining or read caching is not desirable.” Actually, the function’s implementation
is identical to ioremap on most computer platforms: in situations where all of I/O memory is already visible through noncacheable addresses, there’s no reason to implement a separate, noncaching version of ioremap.

这里我重新改用了ioremap，everything work correctly...