From: Hayes Wang <hayeswang@realtek•com>
To: Andrew Lunn <andrew@lunn•ch>
Cc: "kuba@kernel•org" <kuba@kernel•org>,
"davem@davemloft•net" <davem@davemloft•net>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
nic_swsd <nic_swsd@realtek•com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"linux-usb@vger•kernel.org" <linux-usb@vger•kernel.org>
Subject: RE: [PATCH net-next v2 2/2] r8152: set bp in bulk
Date: Wed, 26 Jul 2023 09:50:18 +0000 [thread overview]
Message-ID: <41b998e0222c49d8bbc9eadf1611eb74@realtek.com> (raw)
In-Reply-To: <0c42418b-7271-415d-991a-a4564cb3fad5@lunn.ch>
Andrew Lunn <andrew@lunn•ch>
> Sent: Wednesday, July 26, 2023 4:39 PM
[...]
> > /* wait 3 ms to make sure the firmware is stopped */
> > usleep_range(3000, 6000);
>
> How much time do you save compared to this 3ms - 6ms sleep?
I think it depends on the CPU and the USB host controller.
Take the PC produced this year for example, I think it saves less than 3ms normally.
However, I think saving the number of control transfer is better for both software and hardware.
Best Regards,
Hayes
next prev parent reply other threads:[~2023-07-26 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 3:08 [PATCH net-next v2 0/2] r8152: reduce control transfer Hayes Wang
2023-07-26 3:08 ` [PATCH net-next v2 1/2] r8152: adjust generic_ocp_write function Hayes Wang
2023-07-26 8:36 ` Andrew Lunn
2023-07-26 9:50 ` Hayes Wang
2023-07-26 3:08 ` [PATCH net-next v2 2/2] r8152: set bp in bulk Hayes Wang
2023-07-26 8:39 ` Andrew Lunn
2023-07-26 9:50 ` Hayes Wang [this message]
2023-07-29 1:10 ` [PATCH net-next v2 0/2] r8152: reduce control transfer patchwork-bot+netdevbpf
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=41b998e0222c49d8bbc9eadf1611eb74@realtek.com \
--to=hayeswang@realtek$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nic_swsd@realtek$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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