From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jassi Brar <jassisinghbrar@gmail.com>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mailbox: tegra-hsp: Flush whole channel
Date: Tue, 22 Mar 2022 18:29:17 +0000 [thread overview]
Message-ID: <a32c7181-79b1-07e7-81c5-9c692e4f958d@nvidia.com> (raw)
In-Reply-To: <c84a0362-8cb0-2925-5a74-ad9c6c3ffe5f@nvidia.com>
Jassi,
On 10/03/2022 17:37, Jon Hunter wrote:
>
>
> On 10/03/2022 16:51, Jon Hunter wrote:
>> Hi Jassi,
>>
>> On 02/03/2022 15:04, Thierry Reding wrote:
>>> From: Pekka Pessi <ppessi@nvidia.com>
>>>
>>> The txdone can re-fill the mailbox. Keep polling the mailbox during the
>>> flush until all the messages have been delivered.
>>>
>>> This fixes an issue with the Tegra Combined UART (TCU) where output can
>>> get truncated under high traffic load.
>>>
>>> Signed-off-by: Pekka Pessi <ppessi@nvidia.com>
>>> Tested-by: Jon Hunter <jonathanh@nvidia.com>
>>> Fixes: 91b1b1c3da8a ("mailbox: tegra-hsp: Add support for shared
>>> mailboxes")
>>> Cc: stable@vger.kernel.org
>>> Signed-off-by: Thierry Reding <treding@nvidia.com>
>>> ---
>>> Changes in v2:
>>> - add Fixes: line
>>> - Cc stable
>>>
>>> drivers/mailbox/tegra-hsp.c | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/drivers/mailbox/tegra-hsp.c b/drivers/mailbox/tegra-hsp.c
>>> index acd0675da681..78f7265039c6 100644
>>> --- a/drivers/mailbox/tegra-hsp.c
>>> +++ b/drivers/mailbox/tegra-hsp.c
>>> @@ -412,6 +412,11 @@ static int tegra_hsp_mailbox_flush(struct
>>> mbox_chan *chan,
>>> value = tegra_hsp_channel_readl(ch, HSP_SM_SHRD_MBOX);
>>> if ((value & HSP_SM_SHRD_MBOX_FULL) == 0) {
>>> mbox_chan_txdone(chan, 0);
>>> +
>>> + /* Wait until channel is empty */
>>> + if (chan->active_req != NULL)
>>> + continue;
>>> +
>>> return 0;
>>> }
>>
>>
>> Any feedback on this? Can we queue this up for v5.18?
>
> Feel free to add my ...
>
> Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Any feedback?
Jon
--
nvpublic
next prev parent reply other threads:[~2022-03-22 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 15:04 Thierry Reding
2022-03-10 16:51 ` Jon Hunter
2022-03-10 17:37 ` Jon Hunter
2022-03-22 18:29 ` Jon Hunter [this message]
2022-03-22 18:50 ` Jassi Brar
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=a32c7181-79b1-07e7-81c5-9c692e4f958d@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®