From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Denis Carikli" <denis@eukrea.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
"Sascha Hauer" <kernel@pengutronix.de>,
"Pawel Moll" <pawel.moll@arm.com>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Rob Herring" <rob.herring@calxeda.com>,
"Eric Bénard" <eric@eukrea.com>,
"Grant Likely" <grant.likely@linaro.org>,
"Shawn Guo" <shawn.guo@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv2][ 2/2] ARM: dts: Add support for the cpuimx53 board from Eukrea and its baseboard.
Date: Fri, 06 Dec 2013 14:11:45 +0400 [thread overview]
Message-ID: <1386324705.359638944@f208.i.mail.ru> (raw)
In-Reply-To: <1386323958-783-2-git-send-email-denis@eukrea.com>
Hello.
> The following devices/functionalities were added:
> * Main and secondary UARTs.
> * i2c and the pcf8563 device.
> * Ethernet.
> * NAND.
> * The BP1 button.
> * The LED.
> * Watchdog.
> * SD.
> * USB host.
...
> + reg_3p3v: regulator@0 {
> + reg = <0>;
> + compatible = "regulator-fixed";
> + regulator-name = "3P3V";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + regulator-always-on;
"regulator-always-on" make no sense for virtual supplies.
...
> + pinctrl_uart1: uart1grp {
> + fsl,pins = <MX53_UART1_PINGRP2>;
> + };
> +
> + pinctrl_uart2: uart2grp {
> + fsl,pins = <MX53_UART2_PINGRP2>;
> + };
> + };
> +};
> +
> +&uart1 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_uart1>;
> + fsl,uart-has-rtscts;
So if you use "fsl,uart-has-rtscts", should you add MX53_UART1_PINGRP3
into pinctls too?
---
prev parent reply other threads:[~2013-12-06 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1386323958-783-1-git-send-email-denis@eukrea.com>
[not found] ` <1386323958-783-1-git-send-email-denis-fO0SIAKYzcbQT0dZR+AlfA@public.gmane.org>
2013-12-06 9:59 ` [PATCHv2][ 2/2] ARM: dts: Add support for the cpuimx53 board from Eukrea and its baseboard Denis Carikli
2013-12-06 10:11 ` Alexander Shiyan [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=1386324705.359638944@f208.i.mail.ru \
--to=shc_work@mail.ru \
--cc=denis@eukrea.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@eukrea.com \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@linaro.org \
--cc=swarren@wwwdotorg.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