From: Karl Beldan <kbeldan-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: Sekhar Nori <nsekhar-l0cyMroinI0@public.gmane.org>
Cc: Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
karl.beldan+oss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] ARM: dts: da850: Add missing pin muxing for the UARTs
Date: Thu, 25 Aug 2016 14:15:10 +0000 [thread overview]
Message-ID: <20160825140507.GA13734@gobelin> (raw)
In-Reply-To: <354081bd-653d-ec98-f18e-eb0b1b1ee7e3-l0cyMroinI0@public.gmane.org>
On Thu, Aug 25, 2016 at 07:12:16PM +0530, Sekhar Nori wrote:
> On Wednesday 24 August 2016 02:08 PM, Karl Beldan wrote:
> > On Tue, Aug 23, 2016 at 04:46:03PM +0530, Sekhar Nori wrote:
> >> On Tuesday 23 August 2016 04:39 PM, Sekhar Nori wrote:
> >>> On Friday 05 August 2016 04:30 AM, Kevin Hilman wrote:
> >>>> Karl Beldan <kbeldan-rdvid1DuHRBWk0Htik3J/w@public.gmane.org> writes:
> >>>>
> >>>>> 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.
> >>>>
> >>>> Ok, let's just leave it for now, since it's working fine. Sekhar can
> >>>> fix that up if he can dig up the schematics.
> >>>
> >>> Looks like the flow control pins are being used for McASP also on the
> >>> EVM. So lets leave the EVM as-is.
> >>
> >> Rather, the EVM dts file should be updated to use serial2_rxtx_pins like
> >> the LCDK. Right now it seems to be relying on bootloader to serial2
> >> setup pimux correctly. I can make a patch to fix that. Or if you can do
> >> it, that will be great too.
> >>
> >
> > Indeed ATM the EVM relies on the bootloader to setup the pin muxing.
> >
> > I just checked the uart pins routing of the EVM, the dts:
> > - should reclaim serial2_rxtx_pins and serial2_rtscts_pins
>
> Can you please clarify what you mean by dts should "reclaim". You mean
> move the pins from da850.dtsi to da850-evm.dts or something else?
>
No, in the part you are replying to I am not referring to moving the
pins but reclaiming them. The pins are declared in the dtsi, as they
should. Eg. the LCDK dts reclaims serial2_rxtx_pins but doesn't reclaim
serial2_rtscts_pins while their declarations remain in the dtsi.
The purpose of this part was to clarify what I saw on the schematics
because your emails include the following 2 statements:
> >>> Looks like the flow control pins are being used for McASP also on the
> >>> EVM. So lets leave the EVM as-is.
> >> Rather, the EVM dts file should be updated to use serial2_rxtx_pins like
> >> the LCDK. Right now it seems to be relying on bootloader to serial2
My email was to inform that it concerns the flow control pins of the
UART1 only and that the UART2 flow control pins are not concerned and,
since they are dedicated to the UART2, should be reclaimed unlike
in the LCDK.
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
next prev parent reply other threads:[~2016-08-25 14:15 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
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 [this message]
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=20160825140507.GA13734@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).