From: swexru@gmail.com (Alexey Mednyy)
To: linux-arm-kernel@lists.infradead.org
Subject: iMX53 UART2 suspend freeze
Date: Tue, 13 Sep 2016 00:47:40 +0300 [thread overview]
Message-ID: <1385a087-44c6-1785-f74b-27bddbf8f3ac@gmail.com> (raw)
We've met strange bug with mx53-qsb based board.
We use all 5 UART ports and I can say that on current UART2 with next
configuration in device-tree :
pinctrl_uart2: uart2grp {
fsl,pins = <
MX53_PAD_PATA_BUFFER_EN__UART2_RXD_MUX 0x1e4
MX53_PAD_PATA_DMARQ__UART2_TXD_MUX 0x1e4
>;
};
&uart2 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_uart2>;
status = "okay";
};
prevents board from suspend.
That's happening at least since commit
29add68d16474b7e8e3eadd94da4e909533b99d2 which is also suspend fixing
commit.
All other ports UART1,3,4,5 suspending/resuming fine.
I don't know where do dig next I double checked pinctl settings and it
seems like everything good there.
I've found that most of mx53 based boards with uart2 using the same
muxing configuration.
I wonder if anybody else experiencing this issue?
same configured boards are:
imx53-smd.dts
imx53-tx53.dtsi - based
imx53-tqma53.dtsi - based
imx53-m53evk.dts
_________________________________
Best regards, Mednyy Alexey.
reply other threads:[~2016-09-12 21:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1385a087-44c6-1785-f74b-27bddbf8f3ac@gmail.com \
--to=swexru@gmail.com \
--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