devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Wang <sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
To: Matthias Brugger <matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	mark.rutland-5wv7dgnIgG8@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] arm: dts: mt7623: enable all four available UARTs on bananapi-r2
Date: Fri, 9 Feb 2018 11:55:46 +0800	[thread overview]
Message-ID: <1518148546.9025.20.camel@mtkswgap22> (raw)
In-Reply-To: <cd1df7f9-89f4-06d5-5384-9f3b9f7ade48-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Wed, 2018-02-07 at 17:01 +0100, Matthias Brugger wrote:
> 
> On 01/23/2018 09:51 AM, Sean Wang wrote:
> > On Sat, 2017-12-23 at 23:35 +0800, Sean Wang wrote:
> >> On Sat, 2017-12-23 at 08:52 +0100, Matthias Brugger wrote:
> >>>
> >>> On 12/22/2017 07:06 AM, sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org wrote:
> >>>> From: Sean Wang <sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
> >>>>
> >>>> On bpi-r2 board, totally there're four uarts which we usually called
> >>>> uart[0-3] helpful to extend slow I/O devices. Among those ones, uart2 has
> >>>> dedicated pin slot which is used to conolse log. uart[0-1] appear at the
> >>>> 40-pins connector and uart3 has no pinout, but just has test points (TP47
> >>>> for TX and TP48 for RX, respectively) nearby uart2. Also, some missing
> >>>> pinctrl is being complemented for those devices.
> >>>>
> >>>> Signed-off-by: Sean Wang <sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
> >>>> ---
> >>>>  arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts | 26 ++++++++++++++++++++++++--
> >>>>  1 file changed, 24 insertions(+), 2 deletions(-)
> >>>>
> >>>> diff --git a/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts b/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
> >>>> index 7bf5aa2..64bf5db 100644
> >>>> --- a/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
> >>>> +++ b/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
> >>>> @@ -409,6 +409,20 @@
> >>>>  				 <MT7623_PIN_82_UTXD1_FUNC_UTXD1>;
> >>>>  		};do you like it or quite want me to remove the uart3 node?
> >>>>  	};
> >>>> +
> >>>> +	uart2_pins_a: uart@2 {
> >>>> +		pins_dat {
> >>>> +			pinmux = <MT7623_PIN_14_GPIO14_FUNC_URXD2>,
> >>>> +				 <MT7623_PIN_15_GPIO15_FUNC_UTXD2>;
> >>>> +		};
> >>>> +	};
> >>>> +
> >>>> +	uart3_pins_a: uart@3 {
> >>>> +		pins_dat {
> >>>> +			pinmux = <MT7623_PIN_242_URTS2_FUNC_URTS2>,
> >>>> +				 <MT7623_PIN_243_UCTS2_FUNC_UTXD3>;
> >>>> +		};
> >>>> +	};
> >>>>  };
> >>>>  
> >>>>  &pwm {
> >>>> @@ -454,16 +468,24 @@
> >>>>  &uart0 {
> >>>>  	pinctrl-names = "default";
> >>>>  	pinctrl-0 = <&uart0_pins_a>;
> >>>> -	status = "disabled";
> >>>> +	status = "okay";
> >>>>  };
> >>>>  
> >>>>  &uart1 {
> >>>>  	pinctrl-names = "default";
> >>>>  	pinctrl-0 = <&uart1_pins_a>;
> >>>> -	status = "disabled";
> >>>> +	status = "okay";
> >>>>  };
> >>>>  
> >>>>  &uart2 {
> >>>> +	pinctrl-names = "default";
> >>>> +	pinctrl-0 = <&uart2_pins_a>;
> >>>> +	status = "okay";
> >>>> +};
> >>>> +
> >>>> +&uart3 {
> >>>> +	pinctrl-names = "default";
> >>>> +	pinctrl-0 = <&uart3_pins_a>;
> >>>>  	status = "okay";
> >>>>  };
> >>>>  
> >>>
> >>> Why do we want to enable uart3 when there are only test points?
> >>> It is not very useful, or do I oversee something?
> >>>
> > 
> >> I have been listening to the sound from potential users of bpi-r2 to
> >> understand what assistance I have to provide to them. Something could
> >> be seen through [1] in the forum to know they had been trying hard to
> >> explore all available UARTs from the SoC in the last weeks. The patch
> >> should be really useful for these people and for the extra soldering
> >> it shouldn't become a problem for these makers.
> >>
> >> [1] http://forum.banana-pi.org/t/gpio-uart-not-the-debug-port/3748
> >>
> >> 	Sean 
> >>
> > 
> > Hi, Matthias
> > 
> > do you like it or quite want me to remove the uart3 node?
> > 
> > I can take it into account along with other pending dts changes in my
> > queue.
> > 
> 
> Sorry for the late answer.
> Do I understand correctly that uart3 is routed to TP47 and TP48, and these test
> points are accessible through the SATA connector? Doesn't they break SATA then?
> 

TP47 and TP48 are directly pins out from SoC, not through the SATA
connector.

> I think as they are only available through a non-documented test point, we
> shouldn't enable it.
> 

Okay, let's drop uart 3 setting here.

> Regards,
> Matthias


--
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:[~2018-02-09  3:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22  6:06 [PATCH] arm: dts: mt7623: enable all four available UARTs on bananapi-r2 sean.wang-NuS5LvNUpcJWk0Htik3J/w
     [not found] ` <b4e84a68da76c1ca538150a730777ff530c1db5a.1513922513.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-12-22  6:24   ` Sean Wang
2017-12-23  7:52   ` Matthias Brugger
     [not found]     ` <dc3c28c7-03c3-f1c6-39c1-b8df8be4fac3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-23 15:35       ` Sean Wang
2018-01-23  8:51         ` Sean Wang
2018-02-07 16:01           ` Matthias Brugger
     [not found]             ` <cd1df7f9-89f4-06d5-5384-9f3b9f7ade48-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-09  3:55               ` Sean Wang [this message]

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=1518148546.9025.20.camel@mtkswgap22 \
    --to=sean.wang-nus5lvnupcjwk0htik3j/w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=matthias.bgg-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;
as well as URLs for NNTP newsgroup(s).