All of lore.kernel.org
 help / color / mirror / Atom feed
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 1/3] ARM: dts: rockchip: Add support for phyCORE-RK3288 SoM
Date: Thu, 06 Apr 2017 10:30:46 +0200	[thread overview]
Message-ID: <1872284.4EEa8KbvLF@phil> (raw)
In-Reply-To: <1491214985-18331-1-git-send-email-w.egorov@phytec.de>

Am Montag, 3. April 2017, 12:23:03 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 for 4.12 with the following minor changes:

- moved phy-handle property up a bit
- switches compatible and #address+#size-cells in mdio0
- dropped rockchip,grf from &io_domains (grf is a simple-mfd and can
  get the grf syscon on its own via its parent)
- vdd_cpu: regulator@60 (from fan53555@60)
- serial_flash: flash@0 (from m25p80@0)
  Nodes should be named after their "category" not the actual device

Thanks
Heiko

WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: dts: rockchip: Add support for phyCORE-RK3288 SoM
Date: Thu, 06 Apr 2017 10:30:46 +0200	[thread overview]
Message-ID: <1872284.4EEa8KbvLF@phil> (raw)
In-Reply-To: <1491214985-18331-1-git-send-email-w.egorov@phytec.de>

Am Montag, 3. April 2017, 12:23:03 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 for 4.12 with the following minor changes:

- moved phy-handle property up a bit
- switches compatible and #address+#size-cells in mdio0
- dropped rockchip,grf from &io_domains (grf is a simple-mfd and can
  get the grf syscon on its own via its parent)
- vdd_cpu: regulator at 60 (from fan53555 at 60)
- serial_flash: flash at 0 (from m25p80 at 0)
  Nodes should be named after their "category" not the actual device

Thanks
Heiko

  parent reply	other threads:[~2017-04-06  8:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03 10:23 [PATCH 1/3] ARM: dts: rockchip: Add support for phyCORE-RK3288 SoM Wadim Egorov
2017-04-03 10:23 ` Wadim Egorov
2017-04-03 10:23 ` Wadim Egorov
2017-04-03 10:23 ` [PATCH 2/3] ARM: dts: rockchip: Add support for PCM-947 carrier board Wadim Egorov
2017-04-03 10:23   ` Wadim Egorov
     [not found] ` <1491214985-18331-1-git-send-email-w.egorov-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2017-04-03 10:23   ` [PATCH 3/3] dt-bindings: Document Phytec phyCORE-RK3288 RDK Wadim Egorov
2017-04-03 10:23     ` Wadim Egorov
2017-04-03 10:23     ` Wadim Egorov
2017-04-06  8:30 ` Heiko Stuebner [this message]
2017-04-06  8:30   ` [PATCH 1/3] ARM: dts: rockchip: Add support for phyCORE-RK3288 SoM Heiko Stuebner
2017-04-06  8:47   ` Heiko Stübner
2017-04-06  8:47     ` Heiko Stübner

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=1872284.4EEa8KbvLF@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.