From: Peter Maydell <peter.maydell@linaro.org>
To: Chris Rauer <crauer@google.com>
Cc: alistair@alistair23.me, qemu-devel@nongnu.org,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: [PATCH] hw/ssi: Fix Linux driver init issue with xilinx_spi
Date: Thu, 30 Mar 2023 10:51:14 +0100 [thread overview]
Message-ID: <CAFEAcA-znULw-5Y=Eaz6Ecsiu1YfcFv_M6aBmSO=a2=FM=AvKg@mail.gmail.com> (raw)
In-Reply-To: <20230323182811.2641044-1-crauer@google.com>
Ping to the Xilinx folks, do you want to review this?
thanks
-- PMM
On Thu, 23 Mar 2023 at 18:28, Chris Rauer <crauer@google.com> wrote:
>
> The problem is that the Linux driver expects the master transaction inhibit
> bit(R_SPICR_MTI) to be set during driver initialization so that it can
> detect the fifo size but QEMU defaults it to zero out of reset. The
> datasheet indicates this bit is active on reset.
>
> See page 25, SPI Control Register section:
> https://www.xilinx.com/content/dam/xilinx/support/documents/ip_documentation/axi_quad_spi/v3_2/pg153-axi-quad-spi.pdf
>
> Signed-off-by: Chris Rauer <crauer@google.com>
> ---
> hw/ssi/xilinx_spi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/ssi/xilinx_spi.c b/hw/ssi/xilinx_spi.c
> index 552927622f..d4de2e7aab 100644
> --- a/hw/ssi/xilinx_spi.c
> +++ b/hw/ssi/xilinx_spi.c
> @@ -156,6 +156,7 @@ static void xlx_spi_do_reset(XilinxSPI *s)
> txfifo_reset(s);
>
> s->regs[R_SPISSR] = ~0;
> + s->regs[R_SPICR] = R_SPICR_MTI;
> xlx_spi_update_irq(s);
> xlx_spi_update_cs(s);
> }
> --
> 2.40.0.348.gf938b09366-goog
>
next prev parent reply other threads:[~2023-03-30 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 18:28 [PATCH] hw/ssi: Fix Linux driver init issue with xilinx_spi Chris Rauer
2023-03-30 9:51 ` Peter Maydell [this message]
2023-03-31 10:09 ` Edgar E. Iglesias
2023-03-31 10:11 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFEAcA-znULw-5Y=Eaz6Ecsiu1YfcFv_M6aBmSO=a2=FM=AvKg@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=alistair@alistair23.me \
--cc=crauer@google.com \
--cc=edgar.iglesias@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).