Thread (12 messages) 12 messages, 2 authors, 2011-05-16
STALE5496d
Revisions (17)
  1. v1 [diff vs current]
  2. v2 [diff vs current]
  3. v3 [diff vs current]
  4. v4 [diff vs current]
  5. v4 [diff vs current]
  6. v4 [diff vs current]
  7. v4 current
  8. v5 [diff vs current]
  9. v5 [diff vs current]
  10. v5 [diff vs current]
  11. v5 [diff vs current]
  12. v6 [diff vs current]
  13. v6 [diff vs current]
  14. v5 [diff vs current]
  15. v6 [diff vs current]
  16. v6 [diff vs current]
  17. v6 [diff vs current]

[PATCH v4 1/7] MTD: Add integrator-flash feature to physmap

From: Russell King - ARM Linux <hidden>
Date: 2011-05-16 13:00:23

On Mon, May 16, 2011 at 01:52:44PM +0100, Marc Zyngier wrote:
On Sun, 2011-05-15 at 08:41 +0100, Russell King - ARM Linux wrote:
quoted
On Thu, Mar 17, 2011 at 01:03:42PM +0000, Marc Zyngier wrote:
quoted
diff --git a/include/linux/mtd/physmap.h b/include/linux/mtd/physmap.h
index bcfd9f7..d37cca0 100644
--- a/include/linux/mtd/physmap.h
+++ b/include/linux/mtd/physmap.h
@@ -22,6 +22,8 @@ struct map_info;
 
 struct physmap_flash_data {
 	unsigned int		width;
+	int			(*init)(struct platform_device *);
+	void			(*exit)(struct platform_device *);
 	void			(*set_vpp)(struct map_info *, int);
Does anything use the map_info argument to set_vpp?  If not, passing a
platform_device pointer would be more consistent and useful here.
Good point. How about the following (untested) patch (on top of this
serie)? It helps getting rid of a bit of code in the pismo driver.
Yup.

Now, I'd like to have acks from folk for the series - especially the mtd
folk who apparantly haven't yet done anything with this series.  I'm
happy to take it through my tree if they are.

This patch should get acks from the relevant platform people too.

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