From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
Cc: "Wang, Yong Y" <yong.y.wang@intel.com>,
Vinod Koul <vinod.koul@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org, "Wang, Qi" <qi.wang@intel.com>,
"toshiharu-linux@dsn.okisemi.com"
<toshiharu-linux@dsn.okisemi.com>
Subject: Re: [PATCH] pch_dma: Fix channel locking
Date: Mon, 27 Jun 2011 16:22:52 +0200 [thread overview]
Message-ID: <201106271622.52763.alexander.stein@systec-electronic.com> (raw)
In-Reply-To: <4E04206C.5000008@dsn.okisemi.com>
Hello,
On Friday 24 June 2011 07:28:12 Tomoya MORINAGA wrote:
> Hi Alexander Stein
>
> I couldn't see the issue at all.
>
> (2011/06/23 16:42), Alexander Stein wrote:
> > The close and open is actually needed (I had a separate application for
> > that yesterday).
>
> Does the above mean that we must delete "close" processing from your
> test program, right ?
> (Modifying like this, I couldn't see the issue)
As you've written below, you used setserial to enable DMA mode. I used my own
application for that using 2 ioctls.
> > If all is done without closing again, I get the following bug:
> Does the above mean that executing your test program many times whose 2
> "close" are deleted , did you see the issue ?
The issue is only printed once. steps in short:
* Enable DMA
* Send 270 chars
> My steps like below
> Boot Fedora14
> Install DMA driver
> Install pch_uart driver
> Enable DMA (setserial /dev/ttyPCH0 ^low_latency)
> Modifying your test program
> Delete 2 close() function.
> Compile your test program.
> Execute the tp.
> Execute the tp.
> Execute the tp.
> I couldn't see any error message.
Ok. I have a 2.6.39 kernel with the following patches:
pch_phub: Don't panic if dmi_get_system_info returns NULL
drivers/tty/serial/pch_uart.c: don't oops if dmi_get_system_info returns NULL
pch_uart: Add console support
I need these to get a booting board with console support on pch_uart.
After boot (dma and pch_uart compiled into kernel), I do
* setserial /dev/ttyPCH0 ^low_latency
* ./raise_dma_fault
<- Here I get the message
For the reference the used code for raise_dma_fault:
#include <fcntl.h>
#include <unistd.h>
#include <sys/ioctl.h>
#include <linux/serial.h>
int main(int argc, char *argv[])
{
int fd;
char buf[270];
fd = open ("/dev/ttyPCH0", O_RDWR);
write (fd, buf, 270);
close (fd);
return 0;
}
Maybe you need to enable CONFIG_TRACE_IRQFLAGS and CONFIG_PROVE_LOCKING
additionally to see the messages.
Regards,
Alexander
next prev parent reply other threads:[~2011-06-27 14:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 15:05 Alexander Stein
2011-06-23 0:11 ` Tomoya MORINAGA
2011-06-23 7:42 ` Alexander Stein
2011-06-24 5:28 ` Tomoya MORINAGA
2011-06-27 14:22 ` Alexander Stein [this message]
2011-06-28 10:34 ` Tomoya MORINAGA
2011-06-28 11:14 ` Alexander Stein
2011-06-29 4:04 ` Tomoya MORINAGA
2011-06-29 4:25 ` Tomoya MORINAGA
2011-06-29 6:28 ` Alexander Stein
2011-06-29 10:26 ` Tomoya MORINAGA
2011-07-07 1:38 ` Vinod Koul
2011-07-07 23:51 ` Tomoya MORINAGA
2011-07-08 7:08 ` Tomoya MORINAGA
2011-07-13 22:12 ` Koul, Vinod
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=201106271622.52763.alexander.stein@systec-electronic.com \
--to=alexander.stein@systec-electronic.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=tomoya-linux@dsn.okisemi.com \
--cc=toshiharu-linux@dsn.okisemi.com \
--cc=vinod.koul@intel.com \
--cc=yong.y.wang@intel.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
all inboxes | Powered by JetHome®