|
From: | Jean-Christophe DUBOIS |
Subject: | Re: [Qemu-devel] [PATCH v4] [i.MX] fix CS handling during SPI access. |
Date: | Wed, 11 Jan 2017 19:47:24 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 |
Le 11/01/2017 à 19:08, mar.krzeminski a écrit :
W dniu 11.01.2017 o 17:12, Jean-Christophe DUBOIS pisze:I think the simplest solution in this case is to go back what you had before: set each CS line state at the beginning of each new transfer - then at first transfer you will properly set all CS line before transfer begin. After transfer end just negateLe 10/01/2017 à 00:02, Peter Maydell a écrit :On 9 January 2017 at 22:27, Jean-Christophe DUBOIS <address@hidden> wrote:I might be wrong but I think they are coming out of reset with their CS line set to low (so they are selected by default) because this is the default level at reset.If that's true then you're in difficulties, because there's no guarantee about device reset order. So even if your SPI controller calls qemu_set_irq in its reset function, if the devices on the other end happen to have their reset called after the controller then they'll still reset into selected...active CS line.
OK, let's do this then ... JC
How does it work for platforms that would have pull-up resistors on some signals? Is it something we cannot model in QEMU?On a related note, it seems quite a few SPI controller emulator are actually calling qemu_set_irq() in their reset handler.I also have the same problem. Thanks, MarcinJCthanks -- PMM
[Prev in Thread] | Current Thread | [Next in Thread] |