From: Jorik Jonker <jorik@kippendief.biz>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
wens@csie.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/7] dts: sun8i-h3: add UART1-3 to Orange Pi Plus
Date: Sat, 3 Sep 2016 14:09:32 +0200 [thread overview]
Message-ID: <20160903120932.GA6289@carbon.kippendief.biz> (raw)
In-Reply-To: <20160902070425.GB6313@lukather>
On Fri, Sep 02, 2016 at 09:04:25AM +0200, Maxime Ripard wrote:
>Unfortunately, these pins can be used for other purposes as well, so
>we cannot make force that decision down to our users.
Yes, but since the associated peripheral is disabled, the users are free
to configure other functions/peripherals, right? I mean something like
this in pseudo-DT:
/soc/pio: pinctrl@01c20800/uart1_pins:
allwinner,pins = "PG6, PG7";
/soc/pio: pinctrl@01c20800/foo0_pins:
allwinner,pins = "PG6, PG7";
..
/soc/uart1: serial@serial@01c28400:
pinctrl-0 = <&uart1_pins>;
status = "disabled";
/soc/bar:
pinctrl-0 = <&uart1_pins>;
status = "disabled";
Assuming Linux/DT allows this, this would force nothing, only offer
choice and ease of use.
Best,
Jorik
next prev parent reply other threads:[~2016-09-03 12:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 19:30 [PATCH v2 0/7] dts: sun8i: add extra uart/i2c to H3 jorik
2016-08-31 19:30 ` [PATCH v2 1/7] dts: sun8i-h3: add pinmux definitions for uart2/uart3 jorik
2016-08-31 19:30 ` [PATCH v2 2/7] dts: sun8i-h3: add pinmux definitions for i2c0/i2c1 jorik
2016-09-01 2:45 ` Chen-Yu Tsai
2016-08-31 19:30 ` [PATCH v2 3/7] dts: sun8i-h3: add i2c0/i2c1 SoC peripherals jorik
2016-09-01 2:42 ` Chen-Yu Tsai
2016-09-01 6:34 ` Jorik Jonker
[not found] ` <CAKqGPHwBqWn05SQqEPUQiwxi=WyBJ2LFto2Ucbh8w=Eqe49eTA@mail.gmail.com>
2016-09-01 6:42 ` Chen-Yu Tsai
2016-08-31 19:30 ` [PATCH v2 4/7] dts: sun8i-h3: add UART1-3 to Orange Pi Plus jorik
2016-09-02 7:04 ` Maxime Ripard
2016-09-03 12:09 ` Jorik Jonker [this message]
2016-09-05 19:31 ` Maxime Ripard
2016-09-06 3:04 ` Chen-Yu Tsai
2016-09-06 8:52 ` Jorik Jonker
2016-09-06 20:01 ` Maxime Ripard
2016-09-06 20:02 ` Maxime Ripard
2016-08-31 19:30 ` [PATCH v2 5/7] dts: sun8i-h3: add UART1-3 to Orange Pi PC jorik
2016-08-31 19:30 ` [PATCH v2 6/7] dts: sun8i-h3: add I2C0-1 to Orange Pi Plus jorik
2016-08-31 19:30 ` [PATCH v2 7/7] dts: sun8i-h3: add I2C0-1 to Orange Pi PC jorik
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=20160903120932.GA6289@carbon.kippendief.biz \
--to=jorik@kippendief.biz \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).