linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: snijsure@grid-net.com (Subodh Nijsure)
To: linux-arm-kernel@lists.infradead.org
Subject: MXS getting AUART to work with DT.
Date: Tue, 12 Jun 2012 18:42:20 -0700	[thread overview]
Message-ID: <4FD7EFFC.8010204@grid-net.com> (raw)

Hi,

I am testing my mx28 hardware with arm-soc/for-next branch. I have made  
additions shown below to my dt file.

What I see is only ttyAPP0 device gets created but not the ttyAPP1, do 
folks who know DT much better than I, see any issues with this DT 
definition below?

auart0_pins_a: auart0 at 0 {
         reg = <0>;
         fsl,pinmux-ids = <0x3000 0x3010 0x3020 0x3030>;
         fsl,drive-strength = <0>;
         fsl,voltage = <1>;
         fsl,pull-up = <0>;
};
auart1_pins_a: auart1 at 0 {
         reg = <0>;
         fsl,pinmux-ids = <0x3040 0x3050>;
         fsl,drive-strength = <0>;
         fsl,voltage = <1>;
         fsl,pull-up = <0>;
};
auart0: serial at 8006a000 {
          pinctrl-names = "default";
          pinctrl-0 = <&auart0_pins_a>;
          status = "okay";
};
auart1: serial at 8006c000 {
           pinctrl-names = "default";
           pinctrl-0 = <&auart1_pins_a>;
           status = "okay";
  };

-Subodh

             reply	other threads:[~2012-06-13  1:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13  1:42 Subodh Nijsure [this message]
2012-06-14  1:23 ` MXS getting AUART to work with DT Fabio Estevam
2012-06-14  1:32   ` Marek Vasut
2012-06-14  2:33     ` Fabio Estevam
2012-06-14  4:23       ` Fabio Estevam
2012-06-14 10:54         ` Marek Vasut
2012-06-14  1:34 ` Marek Vasut
2012-06-14  2:57 ` Fabio Estevam
2012-06-14  4:40   ` Subodh Nijsure
2012-06-14  4:54     ` Fabio Estevam
2012-06-14 16:49       ` Matt Burtch
2012-06-15  1:38         ` Fabio Estevam

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=4FD7EFFC.8010204@grid-net.com \
    --to=snijsure@grid-net.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;
as well as URLs for NNTP newsgroup(s).