Help with ioremap() and driver development

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Can anybody short explain why I need to use ioremap()?
I'm talking about I2C driver for ARM920T based MCU.

I've read several another drivers, and found, that I2C registers are not read/write directly, but via writel() and readl() functions.
In platform driver probe routine, ioremap() is called.

Why I should do that? Why not read and write directly?
As I understand, drivers in kernel space can access registers directly?
Because I have tested this with simple driver for LED control.
I set some bits in my GPIO register directly:

GPIO_DATA_REG = 0x01;

It is correct or not?

I'm asking, because I want understand this and maybe make my driver simpler and faster without these "virtual" read and write functions.

Darius.


--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux