From: Michal Simek <michal.simek@amd.com>
To: Naresh Kumar Ravulapalli <nareshkumar.ravulapalli@altera.com>,
u-boot@lists.denx.de
Cc: Marek Vasut <marex@denx.de>,
Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>,
Tien Fong Chee <tien.fong.chee@altera.com>,
Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] drivers: fpga: intel_sdm_mb: Check SIP SMC status in send_bitstream()
Date: Wed, 2 Jul 2025 09:40:03 +0200 [thread overview]
Message-ID: <cc13116a-fb7c-40bb-807f-ff80324f71de@amd.com> (raw)
In-Reply-To: <20250701044311.3670-1-nareshkumar.ravulapalli@altera.com>
On 7/1/25 06:43, Naresh Kumar Ravulapalli wrote:
> While sending bitstream via SIP SMC, busy status received does not
> correspond to error, instead it means transfer is accepted but SDM
> doesn't have any more free buffer space. Hence, data transmission
> is continued when busy status is received.
>
> Signed-off-by: Naresh Kumar Ravulapalli <nareshkumar.ravulapalli@altera.com>
> ---
> drivers/fpga/intel_sdm_mb.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/fpga/intel_sdm_mb.c b/drivers/fpga/intel_sdm_mb.c
> index a2f3b160a73..5f4aae47d6d 100644
> --- a/drivers/fpga/intel_sdm_mb.c
> +++ b/drivers/fpga/intel_sdm_mb.c
> @@ -687,7 +687,8 @@ static int send_bitstream(const void *rbf_data, size_t rbf_size)
> debug("wr_ret = %d, rbf_data = %p, buf_size = %08lx\n",
> wr_ret, rbf_data, buf_size);
>
> - if (wr_ret)
> + if (wr_ret != INTEL_SIP_SMC_STATUS_OK &&
> + wr_ret != INTEL_SIP_SMC_STATUS_BUSY)
> continue;
>
> rbf_size -= buf_size;
Applied.
M
prev parent reply other threads:[~2025-07-02 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 4:43 [PATCH] drivers: fpga: intel_sdm_mb: Check SIP SMC status in send_bitstream() Naresh Kumar Ravulapalli
2025-07-02 7:40 ` Michal Simek [this message]
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=cc13116a-fb7c-40bb-807f-ff80324f71de@amd.com \
--to=michal.simek@amd.com \
--cc=marex@denx.de \
--cc=nareshkumar.ravulapalli@altera.com \
--cc=simon.k.r.goldschmidt@gmail.com \
--cc=tien.fong.chee@altera.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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