Re: [PATCH 1/5] CF: Change omap_cf.c to use omap_readw/writew instead of __REG for multi-omap

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

 



On Friday 16 May 2008, Tony Lindgren wrote:
> @@ -38,19 +38,19 @@
>  #define        CF_BASE 0xfffe2800
>  
>  /* status; read after IRQ */
> -#define CF_STATUS_REG          __REG16(CF_BASE + 0x00)
> +#define CF_STATUS                      (CF_BASE + 0x00)
>  #      define  CF_STATUS_BAD_READ      (1 << 2)
>  #      define  CF_STATUS_BAD_WRITE     (1 << 1)
>  #      define  CF_STATUS_CARD_DETECT   (1 << 0)
>  
>  /* which chipselect (CS0..CS3) is used for CF (active low) */
> -#define CF_CFG_REG             __REG16(CF_BASE + 0x02)
> +#define CF_CFG                         (CF_BASE + 0x02)
>  
>	...

Trying to understand the plan here.  This first patches
are to remove __REG*() access, we hillater patches will 
be needed to convert things to omap_readl(BASE + OFFSET)
style accessors?  (BASE being SOC-specific, and passed
down from system init code.)

Not that CF is a good example of that.  I don't think
it exists on current chips.  ;)

- Dave
--
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