From: gregory.clement@bootlin.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] arm64: dts: marvell: mcbin: enable uart headers
Date: Wed, 14 Feb 2018 12:06:27 +0100 [thread overview]
Message-ID: <87k1vfomoc.fsf@bootlin.com> (raw)
In-Reply-To: <b4dc178abd765426e0d0e3aa3be9d8ac7d1301d6.1517381798.git.baruch@tkos.co.il> (Baruch Siach's message of "Wed, 31 Jan 2018 08:56:38 +0200")
Hi Baruch,
On mer., janv. 31 2018, Baruch Siach <baruch@tkos.co.il> wrote:
> Add description of the J25 and J27 UART headers of the Macchiatobin. They use
> uart peripherals that the CP0 (J25) and CP1 (J27) provide.
>
> Even though J25 and J27 are labeled as UART header, the pins on these headers
> can be muxed for other purposes. But the UART functionality is useful when the
> board is mounted in an ATX style enclosure, since the console UART is not
> accessible through the microUSB at CON9.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Applied on mvebu/dt64
Thanks,
Gregory
> ---
> v2:
> Add comments to indicate the headers board labels (Thomas)
> Explain in the commit log why we want the UART functionality (RMK)
> ---
> arch/arm64/boot/dts/marvell/armada-8040-mcbin.dts | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/marvell/armada-8040-mcbin.dts b/arch/arm64/boot/dts/marvell/armada-8040-mcbin.dts
> index 626e9d0462c3..122d2257ebc4 100644
> --- a/arch/arm64/boot/dts/marvell/armada-8040-mcbin.dts
> +++ b/arch/arm64/boot/dts/marvell/armada-8040-mcbin.dts
> @@ -163,6 +163,13 @@
> };
> };
>
> +/* J25 UART header */
> +&cp0_uart1 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&cp0_uart1_pins>;
> + status = "okay";
> +};
> +
> &cp0_mdio {
> pinctrl-names = "default";
> pinctrl-0 = <&cp0_ge_mdio_pins>;
> @@ -195,6 +202,10 @@
> marvell,pins = "mpp37", "mpp38";
> marvell,function = "i2c0";
> };
> + cp0_uart1_pins: uart1-pins {
> + marvell,pins = "mpp40", "mpp41";
> + marvell,function = "uart1";
> + };
> cp0_xhci_vbus_pins: xhci0-vbus-pins {
> marvell,pins = "mpp47";
> marvell,function = "gpio";
> @@ -290,6 +301,17 @@
> marvell,pins = "mpp12", "mpp13", "mpp14", "mpp15", "mpp16";
> marvell,function = "spi1";
> };
> + cp1_uart0_pins: uart0-pins {
> + marvell,pins = "mpp6", "mpp7";
> + marvell,function = "uart0";
> + };
> +};
> +
> +/* J27 UART header */
> +&cp1_uart0 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&cp1_uart0_pins>;
> + status = "okay";
> };
>
> &cp1_sata0 {
> --
> 2.15.1
>
--
Gregory Clement, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-14 11:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 6:56 [PATCH v2 1/2] arm64: dts: marvell: add CP110 uart peripherals Baruch Siach
2018-01-31 6:56 ` [PATCH v2 2/2] arm64: dts: marvell: mcbin: enable uart headers Baruch Siach
2018-02-14 11:06 ` Gregory CLEMENT [this message]
2018-02-14 10:42 ` [PATCH v2 1/2] arm64: dts: marvell: add CP110 uart peripherals Gregory CLEMENT
2018-02-14 10:42 ` Gregory CLEMENT
2018-02-14 10:56 ` Baruch Siach
2018-02-14 11:07 ` Gregory CLEMENT
2018-02-14 11:07 ` Russell King - ARM Linux
2018-02-14 11:17 ` Baruch Siach
2018-02-14 11:30 ` Russell King - ARM Linux
2018-02-14 12:14 ` Gregory CLEMENT
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=87k1vfomoc.fsf@bootlin.com \
--to=gregory.clement@bootlin.com \
--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).