From: Heiko Stuebner <heiko@sntech.de>
To: Wadim Egorov <w.egorov@phytec.de>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] ARM: dts: rockchip: Add support for phyCORE-RK3288 SoM
Date: Fri, 07 Apr 2017 00:21:43 +0200 [thread overview]
Message-ID: <2316800.SYqXzj6arr@phil> (raw)
In-Reply-To: <1491483866-18368-1-git-send-email-w.egorov@phytec.de>
Am Donnerstag, 6. April 2017, 15:04:24 CEST schrieb Wadim Egorov:
> The phyCORE-RK3288 is a SoM (System on Module) containing a RK3288 SoC.
> The module can be connected to different carrier boards.
> It can be also equipped with different RAM, SPI flash and eMMC variants.
> The Rapid Development Kit option is using the following setup:
>
> - 1 GB DDR3 RAM (2 Banks)
> - 1x 4 KB EEPROM
> - DP83867 Gigabit Ethernet PHY
> - 16 MB SPI Flash
> - 4 GB eMMC Flash
>
> Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
applied all 3 for 4.12 .
One minor change was making the touchscreen node name in patch2 read
touchscreen@44
Same rationale as before, nodes should be named after the device-category
Heiko
next prev parent reply other threads:[~2017-04-06 22:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 13:04 [PATCH v2 1/3] ARM: dts: rockchip: Add support for phyCORE-RK3288 SoM Wadim Egorov
2017-04-06 13:04 ` [PATCH v2 2/3] ARM: dts: rockchip: Add support for PCM-947 carrier board Wadim Egorov
2017-04-06 13:04 ` [PATCH v2 3/3] dt-bindings: Document Phytec phyCORE-RK3288 RDK Wadim Egorov
2017-04-10 18:26 ` Rob Herring
2017-04-06 22:21 ` Heiko Stuebner [this message]
2017-04-18 10:15 ` [PATCH v2 1/3] ARM: dts: rockchip: Add support for phyCORE-RK3288 SoM Jacob Chen
2017-04-18 15:01 ` Wadim Egorov
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=2316800.SYqXzj6arr@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=w.egorov@phytec.de \
/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).