From: Darren Hart <dvhart@linux.intel.com>
To: Yocto Project <yocto@yoctoproject.org>,
Bruce Ashfield <bruce.ashfield@windriver.com>,
Tom Zanussi <tom.zanussi@intel.com>
Subject: [PATCH 0/2][linux-yocto-3.2] fri2 serial port fixes for preempt-rt
Date: Thu, 31 May 2012 11:04:57 -0700 [thread overview]
Message-ID: <cover.1338487192.git.dvhart@linux.intel.com> (raw)
These patches address are lockup when attempting login over serial on the fri2
when running the preempt-rt kernel. I have sent the first patch out for review,
but have not yet heard back. The serial port works and appears fairly stable.
However, I would prefer to keep these patches in yocto/preempt-rt/fri2 until
they are merged upstream in their final form. Please apply to a new branch:
yocto/preempt-rt/fri2
The following changes since commit c004dd798ce68af4d7677939426b083575523db5:
pch_uart: Add eg20t_port lock field, avoid recursive spinlock on port->lock (2012-05-30 23:22:37 -0700)
are available in the git repository at:
git://git.yoctoproject.org/linux-yocto-2.6.37-contrib dvhart/standard/preempt-rt/fri2
http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=dvhart/standard/preempt-rt/fri2
Darren Hart (2):
pch_uart: Add eg20t_port lock field, avoid recursive spinlocks
[RT] pch_uart: Correct spin_lock and irqsave usage in pch_console_write
drivers/tty/serial/pch_uart.c | 26 ++++++++++++++++++--------
1 files changed, 18 insertions(+), 8 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-05-31 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 18:04 Darren Hart [this message]
2012-05-31 18:04 ` [PATCH 1/2] pch_uart: Add eg20t_port lock field, avoid recursive spinlocks Darren Hart
2012-05-31 18:04 ` [PATCH 2/2] [RT] pch_uart: Correct spin_lock and irqsave usage in pch_console_write Darren Hart
2012-05-31 18:57 ` [PATCH 0/2][linux-yocto-3.2] fri2 serial port fixes for preempt-rt Bruce Ashfield
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=cover.1338487192.git.dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=tom.zanussi@intel.com \
--cc=yocto@yoctoproject.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 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.