From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Kevin Lo <kevlo@kevlo.org>, John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [rt2x00-users] [PATCH] rt2x00: rt2800lib: update RF registers for RT5390
Date: Sun, 27 Oct 2013 17:29:08 +0100 [thread overview]
Message-ID: <526D3F54.5020808@01019freenet.de> (raw)
In-Reply-To: <5269D154.5000606@kevlo.org>
Hello Kevin!
Kevin Lo wrote:
> Andreas Hartmann wrote:
[...]
>> In a nutshell: Use a few, but big USB packets instead of a lot of small
>> ones, which needs a lot of interrupts / s and therefore needs a lot of
>> CPU resources - which aren't available on the PI at all.
>
> I have a lot of embedded devices (Freescale imx5/imx6, Marvell armanda xp
> ... etc) here and I've also noticed usb performance issues.
>
> Firstly, I want to sync register settings, which is obtained from the
> vendor driver. When it's done, I will take a look at how usb is handled by
> the vendor driver and fix performance issues. Since I don't have
> datasheets,
> I'm not sure updating register values won't help much...
The problem is: as long as the USB interface "filters" as bottleneck
each small change, it's hard to tell if the change was successful or not.
But I'm happy to hear that you see the same problems and I would be
happy if you could fix them. I can test the fixes you hopefully provide
with big (SMP hardware) and small (ARM) hardware and with rt3572 and rt3573.
Thanks,
kind regards,
Andreas
prev parent reply other threads:[~2013-10-27 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 5:24 [PATCH] rt2x00: rt2800lib: update RF registers for RT5390 Kevin Lo
2013-10-24 16:40 ` [rt2x00-users] " Andreas Hartmann
2013-10-25 2:03 ` Kevin Lo
2013-10-27 16:29 ` Andreas Hartmann [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=526D3F54.5020808@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=kevlo@kevlo.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.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;
as well as URLs for NNTP newsgroup(s).