From: Christian Jann <christian.jann@ymail.com>
To: linux-serial@vger.kernel.org
Subject: Re: Need some help with auart on imx23
Date: Fri, 13 Sep 2013 21:28:58 +0200 [thread overview]
Message-ID: <1523739.AE3jKYTuqA@thinkpad> (raw)
In-Reply-To: <1485573.VUJ6COcddm@thinkpad>
On Tuesday 10 September 2013 19:58:01 you wrote:
> On Tuesday 10 September 2013 12:26:32 you wrote:
> > Hi, I could really need some help to get the second application uart
> > working on my imx23 based board.
> >
So I've finally solved the issue after reading
Documentation/devicetree/bindings/pinctrl/fsl,mxs-pinctrl.txt again, the
pinmux-ids were wrong.
Required subnode-properties:
- fsl,pinmux-ids: An integer array. Each integer in the array specify a pin
with given mux function, with bank, pin and mux packed as below.
[15..12] : bank number
[11..4] : pin number
[3..0] : mux selection
0000000000000000
[ ][ ][ ]
bank pin mux
0000000011100000 0x00e0 /* MX23_PAD_GPMI_D14__GPMI_D14 */
0000000011110000 0x00f0 /* MX23_PAD_GPMI_D15__GPMI_D15 */
0b00001110 = 14
0b00001111 = 15
Looking at the datasheet, mux for auart should be 01:
0000000011100001 0x00e1 /* MX23_PAD_GPMI_D14__AUART2_TX */
0000000011110001 0x00f1 /* MX23_PAD_GPMI_D15__AUART2_RX */
Before I haven't understood the exact functioning of fsl,pinmux-ids but now
I've corrected arch/arm/boot/dts/imx23.dtsi:
auart1_2pins_a: auart1-2pins@0 {
reg = <0>;
fsl,pinmux-ids = <
0x00e1 /* MX23_PAD_GPMI_D14__AUART2_TX */
0x00f1 /* MX23_PAD_GPMI_D15__AUART2_RX */
>;
fsl,drive-strength = <0>;
fsl,voltage = <1>;
fsl,pull-up = <0>;
};
--
chris
prev parent reply other threads:[~2013-09-13 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 10:26 Need some help with auart on imx23 Christian Jann
2013-09-10 17:58 ` Christian Jann
2013-09-13 19:28 ` Christian Jann [this message]
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=1523739.AE3jKYTuqA@thinkpad \
--to=christian.jann@ymail.com \
--cc=linux-serial@vger.kernel.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).