From: icenowy@aosc.xyz (Icenowy Zheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: sun8i: Add extra UART pinmux settings for A23/33
Date: Tue, 23 Aug 2016 21:51:05 +0800 [thread overview]
Message-ID: <69271471960265@web26h.yandex.ru> (raw)
In-Reply-To: <20160823114251.GL2598@lukather>
23.08.2016, 19:42, "Maxime Ripard" <maxime.ripard@free-electrons.com>:
> Hi,
>
> On Tue, Aug 23, 2016 at 01:58:26PM +0800, Icenowy Zheng wrote:
>> ?A23/33 have 4 UART controllers outside PRCM. However, the devicetree used
>> ?to mentioned only UART0's pinmux settings. Some extra UART controllers have
>> ?RTS/CTS, and is suitable for using as bluetooth UART controller.
>>
>> ?Add the pinmux settings for the UART controller, to make use of the
>> ?bluetooth function of some tablets.
>>
>> ?Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz>
>
> Our policy is that we avoid adding unused pinctrl nodes to not cripple
> the DT for no particular reason.
>
> So please add only the nodes you'll need in your tablet.
Then... if what I needs is the PG group of uart1, should I name it as
uart1_pins_a or uart1_pins_b?
>
> Thanks!
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
next prev parent reply other threads:[~2016-08-23 13:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 5:58 [PATCH 1/2] pinctrl: sunxi: fix uart1 CTS/RTS pins at PG on A23/A33 Icenowy Zheng
2016-08-23 5:58 ` [PATCH 2/2] ARM: dts: sun8i: Add extra UART pinmux settings for A23/33 Icenowy Zheng
2016-08-23 11:42 ` Maxime Ripard
2016-08-23 13:51 ` Icenowy Zheng [this message]
2016-08-26 20:18 ` Maxime Ripard
2016-08-23 6:47 ` [PATCH 1/2] pinctrl: sunxi: fix uart1 CTS/RTS pins at PG on A23/A33 Maxime Ripard
2016-08-23 6:50 ` Icenowy Zheng
2016-08-23 9:27 ` Linus Walleij
2016-08-23 9:54 ` Maxime Ripard
2016-08-23 10:29 ` Linus Walleij
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=69271471960265@web26h.yandex.ru \
--to=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.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).