All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Youghandhar Chintala <quic_youghand@quicinc.com>
Cc: <ath10k@lists.infradead.org>,  <linux-wireless@vger.kernel.org>,
	 Douglas Anderson <dianders@chromium.org>
Subject: Re: [PATCH] wifi: ath10k: Delay the unmapping of the buffer
Date: Tue, 11 Oct 2022 12:08:36 +0300	[thread overview]
Message-ID: <87lepmohgr.fsf@kernel.org> (raw)
In-Reply-To: <20220816044310.19101-1-quic_youghand@quicinc.com> (Youghandhar Chintala's message of "Tue, 16 Aug 2022 10:13:10 +0530")

Youghandhar Chintala <quic_youghand@quicinc.com> writes:

> We are seeing a corner case where host receiving copy completion for WMI
> command though copy engine is processing it. Once host receives the
> copy completion, host is unmapping corresponding memory which results
> in SMMU fault. To avoid such conditions though host receives copy
> completion, as a work around we are adding a delay to unmap the memory
> for WMI end point.
>
> Tested-on: WCN3990 hw1.0 SNOC WLAN.HL.2.0-01387-QCAHLSWMTPLZ-1
>
> Tested-by: Douglas Anderson <dianders@chromium.org>
> Signed-off-by: Youghandhar Chintala <quic_youghand@quicinc.com>

Please describe the actual bug in more detail (symptoms etc). Basically
I would like to see information so that if there's a bug report I can
easily pinpoint that this patch fixes it. Currently I have no idea how
this bug affects the users.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Youghandhar Chintala <quic_youghand@quicinc.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
	Douglas Anderson <dianders@chromium.org>
Subject: Re: [PATCH] wifi: ath10k: Delay the unmapping of the buffer
Date: Tue, 11 Oct 2022 12:08:36 +0300	[thread overview]
Message-ID: <87lepmohgr.fsf@kernel.org> (raw)
In-Reply-To: <20220816044310.19101-1-quic_youghand@quicinc.com> (Youghandhar Chintala's message of "Tue, 16 Aug 2022 10:13:10 +0530")

Youghandhar Chintala <quic_youghand@quicinc.com> writes:

> We are seeing a corner case where host receiving copy completion for WMI
> command though copy engine is processing it. Once host receives the
> copy completion, host is unmapping corresponding memory which results
> in SMMU fault. To avoid such conditions though host receives copy
> completion, as a work around we are adding a delay to unmap the memory
> for WMI end point.
>
> Tested-on: WCN3990 hw1.0 SNOC WLAN.HL.2.0-01387-QCAHLSWMTPLZ-1
>
> Tested-by: Douglas Anderson <dianders@chromium.org>
> Signed-off-by: Youghandhar Chintala <quic_youghand@quicinc.com>

Please describe the actual bug in more detail (symptoms etc). Basically
I would like to see information so that if there's a bug report I can
easily pinpoint that this patch fixes it. Currently I have no idea how
this bug affects the users.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2022-10-11  9:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16  4:43 [PATCH] wifi: ath10k: Delay the unmapping of the buffer Youghandhar Chintala
2022-08-16  4:43 ` Youghandhar Chintala
2022-10-11  9:08 ` Kalle Valo [this message]
2022-10-11  9:08   ` Kalle Valo

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=87lepmohgr.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=dianders@chromium.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_youghand@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.