Thread (51 messages) 51 messages, 8 authors, 2011-08-25
STALE5395d
Revisions (27)
  1. v1 [diff vs current]
  2. v1 [diff vs current]
  3. v1 [diff vs current]
  4. v1 [diff vs current]
  5. v1 [diff vs current]
  6. v1 [diff vs current]
  7. v1 [diff vs current]
  8. v1 [diff vs current]
  9. v1 [diff vs current]
  10. v1 [diff vs current]
  11. v1 [diff vs current]
  12. v1 [diff vs current]
  13. v1 [diff vs current]
  14. v1 [diff vs current]
  15. v1 [diff vs current]
  16. v1 [diff vs current]
  17. v1 [diff vs current]
  18. v1 [diff vs current]
  19. v1 [diff vs current]
  20. v1 [diff vs current]
  21. v1 [diff vs current]
  22. v1 [diff vs current]
  23. v1 [diff vs current]
  24. v1 [diff vs current]
  25. v1 [diff vs current]
  26. v1 current
  27. v2 [diff vs current]

[PATCH 2/6] ARM: add Highbank core platform support

From: arnd@arndb.de (Arnd Bergmann)
Date: 2011-08-25 16:02:29

On Saturday 20 August 2011, Rob Herring wrote:
quoted
quoted
+#ifndef _MACH_HIGHBANK__SYSREGS_H_
+#define _MACH_HIGHBANK__SYSREGS_H_
+
+extern void __iomem *sregs_base;
+
+#define HB_SREG_A9_PWR_REQ          0xf00
+#define HB_SREG_A9_BOOT_STAT                0xf04
+#define HB_SREG_A9_BOOT_DATA                0xf08
+
+#define HB_PWR_SUSPEND                      0
+#define HB_PWR_SOFT_RESET           1
+#define HB_PWR_HARD_RESET           2
+#define HB_PWR_SHUTDOWN                     3
+
+#endif
Do these really need to be global?

I think it's better to put the base address and register definitions into a
single file and export functions to be used from elsewhere.
Yes, sregs are a random collection of functions, so it's going to be a
mixture of various users. Just HB_PWR_* alone are in 2 or 3 different
places.
Sorry, I'm not following.

Do you mean 'yes, they need to be global' or 'yes, it's better to export
the functions'?

	Arnd
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help