From: Arnd Bergmann <arnd@arndb.de>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-serial@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
uclinux-dist-devel@blackfin.uclinux.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: char: hvc: add Blackfin JTAG console support
Date: Tue, 11 Jan 2011 04:41:33 +0100 [thread overview]
Message-ID: <201101110441.33841.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTinnuxvx9+eNvCqjK2GW2XQPn4LjK4WfMj=f20Xw@mail.gmail.com>
On Tuesday 11 January 2011, Mike Frysinger wrote:
> throughput seems to be a bit lower. the Blackfin JTAG hardware has
> basically a 4 byte fifo that is filled/consumed in a single shot. and
> the Blackfin can produce much faster than the host can consume. so
> atm, i have it send out 4 bytes, and the hvc layers take care of
> calling back into me at some point. if i add a busy loop to run a few
> hundred milliseconds (like HZ/4), it runs much nicer. but obviously
> doesnt give anyone else time to run. i cant schedule or anything as
> the write layers are called with a spin_lock_irqsave. any tips for
> how to speed this up a bit ? or is it a wash with hvc ?
You could try lowering the hvc MIN_TIMEOUT value. If you want to
change it for blackfin, you could probably make it a configuration
option. However, if it really takes a few milliseconds that you need
to wait between two accesses, MIN_TIMEOUT should already be small
enough.
You should really not need to sleep in your output function, as
the khvcd() timeout logic tries handling this in the best way.
There may be a bug in that logic though (wouldn't be the first one
there), so try to see what the timeouts are when you get into
this problem.
Arnd
next prev parent reply other threads:[~2011-01-11 3:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 2:43 [PATCH] drivers: char: hvc: add Blackfin JTAG console support Mike Frysinger
2011-01-11 3:08 ` Mike Frysinger
2011-01-11 3:41 ` Arnd Bergmann [this message]
2011-01-11 5:31 ` Mike Frysinger
2011-02-03 22:20 ` Greg KH
2011-02-04 0:14 ` [uclinux-dist-devel] " Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2011-01-12 1:00 [PATCH] backlight: new driver for the ADP8870 backlight devices Mike Frysinger
2011-01-12 1:00 ` [PATCH] drivers: char: hvc: add Blackfin JTAG console support Mike Frysinger
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=201101110441.33841.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.org \
/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