From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/7] ARM: dts: add I2SE Duckbill common definitions
Date: Wed, 26 Oct 2016 21:53:38 +0800 [thread overview]
Message-ID: <20161026135338.GP30578@tiger> (raw)
In-Reply-To: <1477164150-13553-5-git-send-email-mhei@heimpold.de>
On Sat, Oct 22, 2016 at 09:22:27PM +0200, Michael Heimpold wrote:
> + pinctrl at 80018000 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&hog_pins_a>;
> +
> + mac0_phy_reset_pin: mac0_phy_reset_pin at 0 {
Please use hyphen instead of underscore in node name.
Shawn
> + reg = <0>;
> + fsl,pinmux-ids = <
> + MX28_PAD_GPMI_ALE__GPIO_0_26 /* PHY Reset */
> + >;
> + fsl,drive-strength = <MXS_DRIVE_4mA>;
> + fsl,voltage = <MXS_VOLTAGE_HIGH>;
> + fsl,pull-up = <MXS_PULL_DISABLE>;
> + };
next prev parent reply other threads:[~2016-10-26 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 19:22 [PATCH 0/7] ARM: dts: support I2SE Duckbill device Michael Heimpold
2016-10-22 19:22 ` [PATCH 1/7] ARM: dts: imx28: add alternative pinmuxing for mmc2 Michael Heimpold
2016-10-22 19:22 ` [PATCH 2/7] ARM: dts: imx28: rename mmc2_sck_cfg to prepare for an alternative muxing setup Michael Heimpold
2016-10-22 19:22 ` [PATCH 3/7] ARM: dts: imx28: add alternative muxing for mmc2_sck_cfg Michael Heimpold
2016-10-22 19:22 ` [PATCH 4/7] ARM: dts: add I2SE Duckbill common definitions Michael Heimpold
2016-10-26 13:53 ` Shawn Guo [this message]
2016-10-22 19:22 ` [PATCH 5/7] ARM: dts: duckbill: simplify DT and use " Michael Heimpold
2016-10-22 19:22 ` [PATCH 6/7] ARM: dts: add support for remaining members of Duckbill series Michael Heimpold
2016-10-22 19:22 ` [PATCH 7/7] ARM: dts: add support for Duckbill 2 series devices Michael Heimpold
2016-10-24 13:12 ` [PATCH 0/7] ARM: dts: support I2SE Duckbill device Shawn Guo
2016-10-24 19:45 ` Michael Heimpold
2016-10-26 13:55 ` Shawn Guo
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=20161026135338.GP30578@tiger \
--to=shawnguo@kernel.org \
--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).