From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Joachim Eastwood <manabian-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Greg Kroah-Hartman
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: 8250-based SoC serial ports and features
Date: Sat, 25 Apr 2015 22:08 +0200 [thread overview]
Message-ID: <6085099.eeiYtUGZgl@wuerfel> (raw)
In-Reply-To: <CAGhQ9VyrnPrgzqtkTN5V7zpSQQ6QhmQdpQi5Sc1eTkcQnxKZXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Saturday 25 April 2015 16:33:18 Joachim Eastwood wrote:
>
> One other question: What is the preferred way of describing different
> UART SoC features in DT?
> 16550a is used as base on most NXP Cortex-M devices, but each UART can
> have different features like; IRDA, Smart card, RS485, sync mode
> (USART), DMA, hardware RTS/CTS pins and full modem pins.
> Features also differ between UARTs on the same device.
>
> I am thinking about either using different comp strings or some kind
> of feature flags in DT. (Freescale UART already uses feature flags
> like: "fsl,irda-mode" and "fsl,uart-has-rtscts")
I would probably specify both then, to give more flexibility to the
driver in implementing it one way or the other.
> All UARTs on LPC1850 have RS485 and DMA support. In additional you have:
> UART0,2,3: sync mode and smart card.
> UART3: IRDA
> UART1: full modem control pin set.
>
> Comp strings could be something like:
> "nxp,lpc1850-usart" <- sync+smart card
> "nxp,lpc1850-usart-irda" <- sync+smart card+irda
> "nxp,lpc1850-uart-modem" <- modem-pins
>
> or feature flags like:
> nxp,sync-mode;
> nxp,rs485-mode;
> nxp,smart-card;
> nxp,irda-mode;
> nxp,full-modem;
For cases where a single chip has uarts with different features,
using feature flags makes most sense, you can probably skip
assigning different compatible strings there.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-04-25 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGhQ9Vw5hJKX+wrhV91mGmB00eUJKaR8Astns8rpk465BQnv1Q@mail.gmail.com>
[not found] ` <9563845.vZY1xECvNe@wuerfel>
2015-04-25 14:33 ` 8250-based SoC serial ports and features Joachim Eastwood
[not found] ` <CAGhQ9VyrnPrgzqtkTN5V7zpSQQ6QhmQdpQi5Sc1eTkcQnxKZXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-25 20:08 ` Arnd Bergmann [this message]
2015-04-27 14:07 ` Rob Herring
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=6085099.eeiYtUGZgl@wuerfel \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=manabian-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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