qemu-devel
[Top][All Lists]
Advanced

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

[Qemu-devel] [PATCH v3] [i.MX] Remove MSGDATA register support.


From: Jean-Christophe Dubois
Subject: [Qemu-devel] [PATCH v3] [i.MX] Remove MSGDATA register support.
Date: Sat, 7 Jan 2017 13:20:47 +0100

>From the documentation it is not clear what this SPI register is about.

Moreover, neither linux driver nor xvisor driver are using this SPI register.

For now we just remove it and issue a log on register write access.

Signed-off-by: Jean-Christophe Dubois <address@hidden>
---

Changes since v1:
* Fix coding style issue.

Changes since v2:
* change log form LOG_GUEST_ERROR to LOG_UNIMP..

 hw/ssi/imx_spi.c | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/hw/ssi/imx_spi.c b/hw/ssi/imx_spi.c
index e57cb9a..b8f416c 100644
--- a/hw/ssi/imx_spi.c
+++ b/hw/ssi/imx_spi.c
@@ -345,9 +345,6 @@ static void imx_spi_write(void *opaque, hwaddr offset, 
uint64_t value,
                       TYPE_IMX_SPI, __func__);
         break;
     case ECSPI_TXDATA:
-    case ECSPI_MSGDATA:
-        /* Is there any difference between TXDATA and MSGDATA ? */
-        /* I'll have to look in the linux driver */
         if (!imx_spi_is_enabled(s)) {
             /* Ignore writes if device is disabled */
             break;
@@ -398,6 +395,14 @@ static void imx_spi_write(void *opaque, hwaddr offset, 
uint64_t value,
         }
 
         break;
+    case ECSPI_MSGDATA:
+        /* it is not clear from the spec what MSGDATA is for */
+        /* Anyway it is not used by Linux driver */
+        /* So for now we just ignore it */
+        qemu_log_mask(LOG_UNIMP,
+                      "[%s]%s: Trying to write to MSGDATA, ignoring\n",
+                      TYPE_IMX_SPI, __func__);
+        break;
     default:
         s->regs[index] = value;
 
-- 
2.9.3




reply via email to

[Prev in Thread] Current Thread [Next in Thread]