From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM i.MX51: Add Digi ConnectCore devicetree
Date: Wed, 2 Apr 2014 19:39:35 +0800 [thread overview]
Message-ID: <20140402113934.GH8753@dragon> (raw)
In-Reply-To: <1396075706-25384-2-git-send-email-shc_work@mail.ru>
On Sat, Mar 29, 2014 at 10:48:26AM +0400, Alexander Shiyan wrote:
> This patch adds support for Digi ConnectCore? i.MX51/Wi-i.MX51 SOM
> and basic support for the ConnectCore for i.MX51 JumpStart Kit.
>
> Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
> ---
...
> +#include "imx51-digi-connectcore-som.dtsi"
> +
> +/ {
> + model = "Digi ConnectCore CC(W)-MX51 JSK";
> + compatible = "digi,connectcore-ccxmx51-jsk",
> + "digi,connectcore-ccxmx51-som", "fsl,imx51";
You may want to send another patch to DT maintainers to add 'digi' into
Documentation/devicetree/bindings/vendor-prefixes.txt.
> +
> + chosen {
> + linux,stdout-path = &uart1;
> + };
> +};
...
> +&nfc {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_nfc>;
> + nand-bus-width = <8>;
> + nand-ecc-mode = "hw";
> + nand-on-flash-bbt;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + status = "okay";
> +
> + partition at 0 {
> + label = "boot";
> + reg = <0x00000 0x80000>;
> + };
> +
> + partition at 1 {
> + label = "env";
> + reg = <0x80000 0x40000>;
> + };
@Sascha, does the argument that we shouldn't have partition table in the
mainline dtb still stands?
> +};
> +
> +&usbotg {
> + phy_type = "utmi_wide";
> + disable-over-current;
> + /* Device role is not known, keep status disabled */
> +};
> +
> +&weim {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_weim>;
> + status = "okay";
> +
> + lan9221: lan9221 at ce000000 {
How does 'ce000000' in the node name comes?
Shawn
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_lan9221>;
> + compatible = "smsc,lan9221", "smsc,lan9115";
> + reg = <5 0x00000000 0x1000>;
> + fsl,weim-cs-timing = <
> + 0x00420081 0x00000000
> + 0x32260000 0x00000000
> + 0x72080f00 0x00000000
> + >;
> + clocks = <&clks IMX5_CLK_DUMMY>;
> + interrupt-parent = <&gpio1>;
> + interrupts = <9 IRQ_TYPE_LEVEL_LOW>;
> + phy-mode = "mii";
> + reg-io-width = <2>;
> + smsc,irq-push-pull;
> + vdd33a-supply = <&gpo2_reg>;
> + vddvario-supply = <&gpo2_reg>;
> + };
> +};
next prev parent reply other threads:[~2014-04-02 11:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 6:48 [PATCH] ARM: dts: imx27-phytec-phycore-rdk: Add display control signal definitions Alexander Shiyan
2014-03-29 6:48 ` [PATCH] ARM i.MX51: Add Digi ConnectCore devicetree Alexander Shiyan
2014-04-02 11:39 ` Shawn Guo [this message]
2014-04-02 11:45 ` Alexander Shiyan
2014-04-02 11:56 ` Shawn Guo
2014-04-02 12:06 ` Alexander Shiyan
2014-04-02 12:47 ` Shawn Guo
2014-04-02 12:56 ` Alexander Shiyan
2014-04-02 13:20 ` Shawn Guo
2014-04-02 12:53 ` Sascha Hauer
2014-04-02 17:44 ` Robert Schwebel
2014-04-02 17:59 ` Dirk Behme
2014-04-02 18:08 ` Alexander Shiyan
2014-04-03 6:49 ` Sascha Hauer
2014-04-02 11:25 ` [PATCH] ARM: dts: imx27-phytec-phycore-rdk: Add display control signal definitions 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=20140402113934.GH8753@dragon \
--to=shawn.guo@freescale.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).