gpmc_cs_request behaviour

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

 



Hi,

I am new on kernel module programming for a OMAP2. I want to access a external device through nCS3 of an OMAP3530. I expect that the function "gpmc_cs_request" enables you the access to that memoryregion and that the variable "cs_mem_base" is set to the memory starting point of the requested nCSx.

But in my case the variable has the value of the requested memory size (SZ_16M).

What do I wrong?

Henk 


snipped of the code:

  if (register_chrdev(MYDEV_MAJOR,"Device",&mydev_fops))
  {
    printk("\rFiFo: Failed to get major %d\n\r", MYDEV_MAJOR);
    return -EIO;
  }

  if (gpmc_cs_request(3, SZ_16M, &cs_mem_base) < 0) {
	printk("CM-T35: Failed request CS3 for GPMC mem for Device\n");
	return -ENODEV;
  }
  printk("\rMemory Address: %lx\n\r",cs_mem_base);

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux