linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: MXS getting AUART to work with DT.
Date: Thu, 14 Jun 2012 03:32:23 +0200	[thread overview]
Message-ID: <201206140332.23485.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5C93a3Cckr_HXm8moW0gafud92qvTXJ=np7MJ3JriR-sw@mail.gmail.com>

Dear Fabio Estevam,

> Hi Subodh,
> 
> On Tue, Jun 12, 2012 at 10:42 PM, Subodh Nijsure <snijsure@grid-net.com> 
wrote:
> > 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?
> 
> I just enabled CONFIG_SERIAL_MXS_AUART and booted my mx28evk (non-DT
> case) that registers
> auart0 and auart2, but I don't see any ttyAPPx node.
> 
> Is there anything I am missing?
> 
> I would like to get ttyAPP0/2 working first on non-DT case.

I think the kernel for non-DT case is already FUBAR ... just do a simple DT 
conversion :-(

> Thanks,
> 
> Fabio Estevam

Best regards,
your utmost DT supporter and friend
Marek Vasut

  reply	other threads:[~2012-06-14  1:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13  1:42 MXS getting AUART to work with DT Subodh Nijsure
2012-06-14  1:23 ` Fabio Estevam
2012-06-14  1:32   ` Marek Vasut [this message]
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=201206140332.23485.marex@denx.de \
    --to=marex@denx.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).