devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karl Beldan <kbeldan-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
Cc: Sekhar Nori <nsekhar-l0cyMroinI0@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>,
	karl.beldan+oss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] ARM: dts: da850: Add missing pin muxing for the UARTs
Date: Thu, 4 Aug 2016 21:00:45 +0000	[thread overview]
Message-ID: <20160804210045.GD15013@gobelin> (raw)
In-Reply-To: <m2eg64pchw.fsf-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>

On Thu, Aug 04, 2016 at 12:20:27PM -0700, Kevin Hilman wrote:
> Karl Beldan <kbeldan-rdvid1DuHRBWk0Htik3J/w@public.gmane.org> writes:
> 
> > This adds 2 pinctrl groups (rtscts, rxtx) for each of the 3 UARTs.
> >
> > Signed-off-by: Karl Beldan <kbeldan-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
> 
> Should da850-evm be updated to use the serial2_rxtx_pins also?
> 
I could not find the EVM schematics on the net and I only have an LCDK,
but according to the code it should, however I can't tell whether flow
control pins are used.
 
Karl
--
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

  parent reply	other threads:[~2016-08-04 21:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 11:06 [PATCH] ARM: dts: da850: Add missing pin muxing for the UARTs Karl Beldan
     [not found] ` <20160804110656.25318-1-kbeldan-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2016-08-04 19:04   ` Kevin Hilman
2016-08-04 19:20   ` Kevin Hilman
2016-08-04 19:40     ` Karl Beldan
     [not found]     ` <m2eg64pchw.fsf-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2016-08-04 21:00       ` Karl Beldan [this message]
2016-08-04 23:00         ` Kevin Hilman
     [not found]           ` <m2fuqknnqk.fsf-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2016-08-23 11:09             ` Sekhar Nori
2016-08-23 11:16               ` Sekhar Nori
2016-08-24  8:38                 ` Karl Beldan
2016-08-25 13:42                   ` Sekhar Nori
     [not found]                     ` <354081bd-653d-ec98-f18e-eb0b1b1ee7e3-l0cyMroinI0@public.gmane.org>
2016-08-25 14:15                       ` Karl Beldan
2016-08-26 11:42                         ` Sekhar Nori
2016-08-26 12:25                   ` Sekhar Nori
2016-08-26 17:17                     ` Karl Beldan
2016-08-30  8:54                       ` Sekhar Nori
2016-08-09 10:19   ` Sekhar Nori

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=20160804210045.GD15013@gobelin \
    --to=kbeldan-rdvid1duhrbwk0htik3j/w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=karl.beldan+oss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
    --cc=linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=nsekhar-l0cyMroinI0@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;
as well as URLs for NNTP newsgroup(s).