From: "Mika Penttilä" <mika.penttila@nextfour.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: <linux-serial@vger.kernel.org>, <kernel@pengutronix.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: [regression, bisected] 4.11+ imx uarts broken
Date: Tue, 9 May 2017 10:25:40 +0300 [thread overview]
Message-ID: <a1fa7693-c9e9-fea8-fbb7-a20ebf1dd287@nextfour.com> (raw)
In-Reply-To: <20170509071435.kxt6pjlglzinf2w5@pengutronix.de>
On 05/09/2017 10:14 AM, Uwe Kleine-König wrote:
> Hello Mika,
>
> On Tue, May 09, 2017 at 07:18:09AM +0300, Mika Penttilä wrote:
>> The following commit e61c38d85b7 makes the uarts on i.MX6 nonfunctional (no data transmitted or received).
>> With e61c38d85b7 reverted the uarts work ok.
>>
>> -------------------
>> commit e61c38d85b7392e033ee03bca46f1d6006156175
>> Author: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
>> Date: Tue Apr 4 11:18:51 2017 +0200
>>
>> serial: imx: setup DCEDTE early and ensure DCD and RI irqs to be off
>>
>> --------------------
>
> are you operating the UART in DTE or DCE mode? Does this affect all
> UARTs or only those that are not used in the bootloader?
I am operating in DCE mode. The debug/console uart works ok, but two others don't.
>
> Looking at the patch I wonder if setting IMX21_UCR3_RXDMUXSEL |
> UCR3_ADNIMP is missing for you.
>
Probably yes, but I can verify this later and get back to you.
> Can you please check which hunk of e61c38d85b73 is giving you problems?
>
> Best regards
> Uwe
>
--Mika
next prev parent reply other threads:[~2017-05-09 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 4:18 Mika Penttilä
2017-05-09 7:14 ` Uwe Kleine-König
2017-05-09 7:25 ` Mika Penttilä [this message]
2017-05-09 14:31 ` 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=a1fa7693-c9e9-fea8-fbb7-a20ebf1dd287@nextfour.com \
--to=mika.penttila@nextfour.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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®