[PATCH 4/4] at91_mci: Add timing to read_ivar.

Christian Mauderer christian.mauderer at embedded-brains.de
Wed Nov 8 12:37:00 UTC 2017


From: Christian Mauderer <Christian.Mauderer at embedded-brains.de>

---
 freebsd/sys/arm/at91/at91_mci.c | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/freebsd/sys/arm/at91/at91_mci.c b/freebsd/sys/arm/at91/at91_mci.c
index 5d448d1cc5c..b34f86f56ac 100644
--- a/freebsd/sys/arm/at91/at91_mci.c
+++ b/freebsd/sys/arm/at91/at91_mci.c
@@ -1570,6 +1570,11 @@ at91_mci_read_ivar(device_t bus, device_t child, int which, uintptr_t *result)
 		}
 		*(int *)result = sc->host.caps;
 		break;
+#ifdef __rtems__
+	case MMCBR_IVAR_TIMING:
+		*result = sc->host.ios.timing;
+		break;
+#endif /* __rtems__ */
 	case MMCBR_IVAR_MAX_DATA:
 		/*
 		 * Something is wrong with the 2x parts and multiblock, so
@@ -1617,6 +1622,11 @@ at91_mci_write_ivar(device_t bus, device_t child, int which, uintptr_t value)
 	case MMCBR_IVAR_VDD:
 		sc->host.ios.vdd = value;
 		break;
+#ifdef __rtems__
+	case MMCBR_IVAR_TIMING:
+		sc->host.ios.timing = value;
+		break;
+#endif /* __rtems__ */
 	/* These are read-only */
 	case MMCBR_IVAR_CAPS:
 	case MMCBR_IVAR_HOST_OCR:
-- 
2.12.3




More information about the devel mailing list