linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xing Zheng <zhengxing@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org,
	radek.dostal@streamunlimited.com, devicetree@vger.kernel.org,
	roger.chen@rock-chips.com, Kumar Gala <galak@codeaurora.org>,
	linux-kernel@vger.kernel.org,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH v2 0/4] Add support i2s/spdif/gmac features for RK322x SoCs
Date: Tue, 28 Jun 2016 17:53:06 +0800	[thread overview]
Message-ID: <57724902.2060802@rock-chips.com> (raw)
In-Reply-To: <16135166.EFsm9ojsF0@phil>

Thanks Heiko. :-)

On 2016年06月28日 03:43, Heiko Stuebner wrote:
> Am Mittwoch, 22. Juni 2016, 11:16:49 schrieb Xing Zheng:
>> Hi,
>>    We have the brother chipset product that RK3228 and RK3229,
>> They have many common configuration, but there are a number
>> of different features. In order to develop the future when they
>> are easy to distinguish, we need them to be independent.
>>    And, these patchset add i2s/gmac dts nodes for RK322x SoCs,
>> and add the new dts file of the rk3229 evb board.
> applied to my dts32 branch for 4.8 with the following changes
>
>> Xing Zheng (4):
>>    ARM: dts: rockchip: rename rk3228.dtsi to rk322x.dtsi
> we'll refrain from adding empty rk3228.dtsi files until we have actual things
> to fill it with.
>
>>    ARM: dts: rockchip: add i2s nodes for RK322x SoCs
> moved i2s node to correct position according to register map
>
>>    ARM: dts: rockchip: add GMAC nodes for RK322x SoCs
> dropped phy-mode and pinctrl settings, as rgmii <-> rmii is a per-board
> thing
>
>>    ARM: dts: rockchip: add support rk3229 evb board
> again dropped the empty rk3229.dtsi, we can add that once there are
> additions not shared between rk3228/rk3229.
>
>
> Heiko
>
>
>

-- 
- Xing Zheng

      reply	other threads:[~2016-06-28  9:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22  3:16 [RESEND PATCH v2 0/4] Add support i2s/spdif/gmac features for RK322x SoCs Xing Zheng
2016-06-22  3:16 ` [RESEND PATCH v2 1/4] ARM: dts: rockchip: rename rk3228.dtsi to rk322x.dtsi Xing Zheng
2016-06-22  3:16 ` [RESEND PATCH v2 2/4] ARM: dts: rockchip: add i2s nodes for RK322x SoCs Xing Zheng
2016-06-22  3:16 ` [RESEND PATCH v2 3/4] ARM: dts: rockchip: add GMAC " Xing Zheng
2016-06-22  3:16 ` [RESEND PATCH v2 4/4] ARM: dts: rockchip: add support rk3229 evb board Xing Zheng
2016-06-27 19:43 ` [RESEND PATCH v2 0/4] Add support i2s/spdif/gmac features for RK322x SoCs Heiko Stuebner
2016-06-28  9:53   ` Xing Zheng [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=57724902.2060802@rock-chips.com \
    --to=zhengxing@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=heiko@sntech.de \
    --cc=ijc+devicetree@hellion.org.uk \
    --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=pawel.moll@arm.com \
    --cc=radek.dostal@streamunlimited.com \
    --cc=robh+dt@kernel.org \
    --cc=roger.chen@rock-chips.com \
    /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).