From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Sai Pavan Boddu <sai.pavan.boddu@xilinx.com>,
Alistair Francis <alistair@alistair23.me>
Cc: edgar.iglesias@xilinx.com,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [QEMU][PATCH v2] ssi: xilinx_spips: Skip update of cs and fifo releated to spips in gqspi
Date: Thu, 17 Oct 2019 12:31:08 +0200 [thread overview]
Message-ID: <20d7bc46-c9fd-dda1-0e8a-2a9b9d5645ef@redhat.com> (raw)
In-Reply-To: <1571307474-16222-1-git-send-email-sai.pavan.boddu@xilinx.com>
Hi,
On 10/17/19 12:17 PM, Sai Pavan Boddu wrote:
> GQSPI handles chip selects and fifos in a different way compared to
> spips. So skip update of cs and fifos related to spips in gqspi mode.
>
> Signed-off-by: Sai Pavan Boddu <sai.pavan.boddu@xilinx.com>
> ---
> Changes for V2:
> Just skip update of spips cs and fifos
> Update commit message accordingly
>
> hw/ssi/xilinx_spips.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/hw/ssi/xilinx_spips.c b/hw/ssi/xilinx_spips.c
> index a309c71..27154b0 100644
> --- a/hw/ssi/xilinx_spips.c
> +++ b/hw/ssi/xilinx_spips.c
> @@ -1022,6 +1022,13 @@ static void xilinx_spips_write(void *opaque, hwaddr addr,
> }
> s->regs[addr] = (s->regs[addr] & ~mask) | (value & mask);
> no_reg_update:
> + /* In GQSPI mode skip update of CS and fifo's related to spips */
> + if (object_dynamic_cast(OBJECT(s), TYPE_XLNX_ZYNQMP_QSPIPS)) {
object_dynamic_cast() is expensive, please add a 'bool is_qpspi' in
XilinxQSPIPS and set it in xlnx_zynqmp_qspips_init().
> + XlnxZynqMPQSPIPS *ss = XLNX_ZYNQMP_QSPIPS(s);
> + if (ARRAY_FIELD_EX32(ss->regs, GQSPI_SELECT, GENERIC_QSPI_EN)) {
> + return;
> + }
> + }
> xilinx_spips_update_cs_lines(s);
> xilinx_spips_check_flush(s);
> xilinx_spips_update_cs_lines(s);
>
next prev parent reply other threads:[~2019-10-17 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 10:17 [QEMU][PATCH v2] ssi: xilinx_spips: Skip update of cs and fifo releated to spips in gqspi Sai Pavan Boddu
2019-10-17 10:31 ` Philippe Mathieu-Daudé [this message]
2019-10-17 13:35 ` Francisco Iglesias
2019-10-18 8:37 ` Sai Pavan Boddu
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=20d7bc46-c9fd-dda1-0e8a-2a9b9d5645ef@redhat.com \
--to=philmd@redhat.com \
--cc=alistair@alistair23.me \
--cc=edgar.iglesias@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sai.pavan.boddu@xilinx.com \
/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).