linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: DCD interrupt for i.MX25 UART
Date: Wed, 23 Mar 2016 16:36:38 +0100	[thread overview]
Message-ID: <20160323153638.GO6191@pengutronix.de> (raw)

Hello,

I have a problem with an UART on an i.MX25 based machine. I implemented
DCD (and other handshake lines) irq handling[1].

Now a user of this patch noticed that DCD handling (at least) is broken.
The problem is that the USR2_DCDDELT bit doesn't clear:

	root at hostname:~ memtool md 0x43f90080+0x34  
	43f90080: 00000000 00004021 0000078c 00004002                ....!@....... at ..
	43f90090: 00000b41 00002040 00005268 0000002b                A...@ ..hR..+...
	43f900a0: 00000000 000000bf 00002e62 00000008                ........b.......
	43f900b0: 0000251c                                           .%..

	root at hostname:~ memtool mw 0x43f90098 0x0x40

	root at hostname:~ memtool md 0x43f90080+0x34  
	43f90080: 00000000 00004021 0000078c 00004002                ....!@....... at ..
	43f90090: 00000b41 00002040 00005268 0000002b                A...@ ..hR..+...
	43f900a0: 00000000 000000bf 00002e62 00000008                ........b.......
	43f900b0: 0000251c                                           .%..

In fact even writing 0xffff doesn't change the register, where I would expect
that the DCDDELT bit (0x40) disappears. I'm sure there is nothing toggling this
line.

The net effect is that the irq blocks the machine until it is disabled with

	[   51.885987] irq 61: nobody cared (try booting with the "irqpoll" option)

.

This is on an i.MX25 and I checked the erratas also of the newer i.MX
cpus, but I didn't find anything.

Did I miss something? Is this a known bug? Do you have a recommendation
other than not to set UCR3_DCD? I cannot test the same problem for RI
because my hardware doesn't use it, but I wouldn't be surprised if that
had the same problem.

It would be great to get a statement from you on this topic.

Best regards
Uwe

[1] Message-Id: 1457605569-7828-3-git-send-email-u.kleine-koenig at pengutronix.de

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

             reply	other threads:[~2016-03-23 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 15:36 Uwe Kleine-König [this message]
2016-03-29 11:14 ` DCD interrupt for i.MX25 UART Lothar Waßmann
2016-04-04 20:49   ` Uwe Kleine-König

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=20160323153638.GO6191@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).