From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: jorik@kippendief.biz
Cc: wens@csie.org, mark.rutland@arm.com, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/8] dts: sun8i-h3: move uart0 pinmux/peripheral assocation to DSTI
Date: Thu, 8 Sep 2016 08:22:15 +0200 [thread overview]
Message-ID: <20160908062215.GC8913@lukather> (raw)
In-Reply-To: <1473235141-12768-4-git-send-email-jorik@kippendief.biz>
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
On Wed, Sep 07, 2016 at 09:58:56AM +0200, jorik@kippendief.biz wrote:
> From: Jorik Jonker <jorik@kippendief.biz>
>
> This is the only sensible pinmux/peripheral association for uart0, so I have
> moved it from the board specific DTS to the DTSI. It is still up to the boards
> to enable it, though.
>
> Signed-off-by: Jorik Jonker <jorik@kippendief.biz>
There's really several options for the UART0 to be muxed, so it's
better if we leave that to the board entirely.
That's useful only for pins where you truely have only a single
option in the entire SoC.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-08 6:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 7:58 [PATCH v4 0/8] dts: sun8i-h3: complete UART I2C definitions for H3 jorik
2016-09-07 7:58 ` [PATCH v4 1/8] dts: sun8i-h3: drop _a and address suffix from uart0 pinmux jorik
2016-09-08 6:17 ` Maxime Ripard
2016-09-07 7:58 ` [PATCH v4 2/8] dts: sun8i-h3: clarify uart1 pinmux definition name jorik
2016-09-08 6:18 ` Maxime Ripard
2016-09-07 7:58 ` [PATCH v4 3/8] dts: sun8i-h3: move uart0 pinmux/peripheral assocation to DSTI jorik
2016-09-08 6:22 ` Maxime Ripard [this message]
2016-09-07 7:58 ` [PATCH v4 4/8] dts: sun8i-h3: move uart1 " jorik
2016-09-07 8:54 ` Chen-Yu Tsai
2016-09-08 6:23 ` Maxime Ripard
2016-09-08 8:02 ` Jorik Jonker
2016-09-08 9:01 ` Maxime Ripard
2016-09-08 9:51 ` Jorik Jonker
2016-09-12 9:47 ` Maxime Ripard
2016-09-07 7:58 ` [PATCH v4 5/8] dts: sun8i-h3: add pinmux definitions for UART2-3 jorik
2016-09-07 7:58 ` [PATCH v4 6/8] dts: sun8i-h3: associate pinmux/peripherals " jorik
2016-09-07 7:59 ` [PATCH v4 7/8] dts: sun8i-h3: add pinmux definitions for I2C0-2 jorik
2016-09-07 7:59 ` [PATCH v4 8/8] dts: sun8i-h3: add I2C0-2 peripherals to H3 SOC 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=20160908062215.GC8913@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=jorik@kippendief.biz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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).