On 20/11/2013 18:27, Jean-Christophe PLAGNIOL-VILLARD :
On 17:31 Wed 20 Nov , boris brezillon wrote:
On 20/11/2013 16:02, Jean-Christophe PLAGNIOL-VILLARD wrote:
On 14:37 Wed 28 Aug , Boris BREZILLON wrote:
Add a new at91rm9200ek_mmc board (based on at91rm9200ek board) which enables
mmc0/slot0.
no for multiple dts
this need to handle at user space level
You mean, by controlling the regulator using the sysfs interface, or
by loading
only the appropriate driver ?
load the partial dts via userspace
Right, but Jean-Christophe, we know that DT fragments are not available
in mainline yet (even if the effort is ongoing). So what should we do in
the meantime?
What if both drivers are loaded (or not compiled as modules) ?
This will lead to one device being unusable (and maybe even worst)...
this will never be the case
Can you please elaborate? It is a bit frustrating to have to ask you
again and again to explain more your thoughts...
Bye,
Best Regards,
J.
Please explain what you had in mind ?
Best Regards,
J.
Signed-off-by: Boris BREZILLON <b.brezillon@xxxxxxxxxxx>
---
arch/arm/boot/dts/at91rm9200ek_mmc.dts | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
create mode 100644 arch/arm/boot/dts/at91rm9200ek_mmc.dts
diff --git a/arch/arm/boot/dts/at91rm9200ek_mmc.dts b/arch/arm/boot/dts/at91rm9200ek_mmc.dts
new file mode 100644
index 0000000..c87a861
--- /dev/null
+++ b/arch/arm/boot/dts/at91rm9200ek_mmc.dts
@@ -0,0 +1,23 @@
+/*
+ * at91rm9200ek.dts - Device Tree file for Atmel AT91RM9200 evaluation kit with
+ * an MMC slot
+ *
+ * Copyright (C) 2013 Boris BREZILLON <b.brezillon@xxxxxxxxxxx>
+ *
+ * Licensed under GPLv2 only
+ */
+/dts-v1/;
+#include "at91rm9200ek.dts"
+
+/ {
+ model = "Atmel AT91RM9200 evaluation kit with MMC slot";
+ compatible = "atmel,at91rm9200ek-mmc", "atmel,at91rm9200ek", "atmel,at91rm9200";
+
+ ahb {
+ apb {
+ mmc0: mmc@fffb4000 {
+ status = "okay";
+ };
+ };
+ };
+};
--
1.7.9.5
--
Nicolas Ferre
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
