All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Ping-Ke Shih <pkshih@realtek.com>,
	Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: wifi: rtlwifi: Speed up firmware loading for USB
Date: Sun, 14 Jan 2024 00:55:28 +0200	[thread overview]
Message-ID: <d53d8311-efaf-44a2-ac4f-accbbdce2a40@gmail.com> (raw)
In-Reply-To: <87v87x8kft.fsf@kernel.org>

On 13/01/2024 14:52, Kalle Valo wrote:
> Bitterblue Smith <rtl8821cerfe2@gmail.com> writes:
> 
>> On 13/01/2024 08:35, Kalle Valo wrote:
>>
>>> Bitterblue Smith <rtl8821cerfe2@gmail.com> writes:
>>>
>>>> Currently it takes almost 6 seconds to upload the firmware for RTL8192CU
>>>> (and 11 seconds for RTL8192DU). That's because the firmware is uploaded
>>>> one byte at a time.
>>>>
>>>> Also, after plugging the device, the firmware gets uploaded three times
>>>> before a connection to the AP is established.
>>>>
>>>> Maybe this is fine for most users, but when testing changes to the
>>>> driver it's really annoying to wait so long.
>>>>
>>>> Speed up the firmware upload by writing chunks of 64 bytes at a time.
>>>> This way it takes about 110 ms for RTL8192CU (and about 210 ms for
>>>> RTL8192DU).
>>>>
>>>> PCI devices could upload it in chunks of 4 bytes, but I don't have any
>>>> to test and commit 89d32c9071aa ("rtlwifi: Download firmware as bytes
>>>> rather than as dwords") decided otherwise anyway.
>>>>
>>>> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
>>>
>>> There's another version so I assume I can drop this one:
>>>
>>> https://patchwork.kernel.org/project/linux-wireless/patch/0d262acd-4f94-41c2-8d15-83486aeb976b@gmail.com/
>>>
>>
>> Yes, you can drop this one. Sorry about that. I forgot to write
>> "[PATCH]" in the subject. I thought you wouldn't even notice this
>> one because of that.
> 
> I think patchwork assumes that any mail with a diff is a patch, like
> this one:
> 
> https://patchwork.kernel.org/project/linux-wireless/patch/c7b331edd65b66521a6605177d654e55051568a3.camel@toradex.com/
> 
> So "[PATCH]" is more like a visual clue. BTW usually it's a good idea to
> mark the next mail as v2 and explain in changelog what happened/changed,
> that way everyone are on the same page. But no big deal, just trying to
> make this smooth for everyone :)
> 

Ahh, got it. I will remember to do that if something like this happens again.

      reply	other threads:[~2024-01-13 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 19:49 wifi: rtlwifi: Speed up firmware loading for USB Bitterblue Smith
2024-01-13  6:35 ` Kalle Valo
2024-01-13 12:08   ` Bitterblue Smith
2024-01-13 12:52     ` Kalle Valo
2024-01-13 22:55       ` Bitterblue Smith [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=d53d8311-efaf-44a2-ac4f-accbbdce2a40@gmail.com \
    --to=rtl8821cerfe2@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.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.