From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Stuart Yoder <stuart.yoder-3arQi8VN3Tc@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH 1/2] arm64: dts: updates serial aliases for ls1043a rdb and qds boards
Date: Mon, 29 Aug 2016 13:01:20 +0200 [thread overview]
Message-ID: <8035333.yr2FRs5mHk@wuerfel> (raw)
In-Reply-To: <1472244381-1766-2-git-send-email-stuart.yoder-3arQi8VN3Tc@public.gmane.org>
On Friday, August 26, 2016 3:46:20 PM CEST Stuart Yoder wrote:
> - serial0 = &lpuart0;
> - serial1 = &lpuart1;
> - serial2 = &lpuart2;
> - serial3 = &lpuart3;
> - serial4 = &lpuart4;
> - serial5 = &lpuart5;
> + serial0 = &duart0;
> + serial1 = &duart1;
> + serial2 = &duart2;
> + serial3 = &duart3;
It looks like your board has six uarts that are all driven with the
lpuart driver, but after the change, you only list four. Should
the serial4 and serial5 aliases keep pointing at lpuart devices
so you can still drive all physical connectors?
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:[~2016-08-29 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 20:46 [PATCH 0/2] arm64: dts: ls1043a/ls2080a serial updates Stuart Yoder
2016-08-26 20:46 ` [PATCH 1/2] arm64: dts: updates serial aliases for ls1043a rdb and qds boards Stuart Yoder
[not found] ` <1472244381-1766-2-git-send-email-stuart.yoder-3arQi8VN3Tc@public.gmane.org>
2016-08-29 11:01 ` Arnd Bergmann [this message]
2016-08-29 18:30 ` Stuart Yoder
2016-08-29 20:38 ` Arnd Bergmann
2016-08-29 21:10 ` Stuart Yoder
2016-08-29 14:01 ` Shawn Guo
2016-08-26 20:46 ` [PATCH 2/2] arm64: dts: add stdout-path to chosen node for ls2080a/ls1043a boards Stuart Yoder
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=8035333.yr2FRs5mHk@wuerfel \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=stuart.yoder-3arQi8VN3Tc@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