From: Heiko Stuebner <heiko@sntech.de> To: Jacob Chen <jacob-chen@iotwrt.com> Cc: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, kever.yang@rock-chips.com, mark.yao@rock-chips.com, zhangqing@rock-chips.com Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Add support for rk3399 excavator main board Date: Sun, 06 Aug 2017 17:44:20 +0200 [thread overview] Message-ID: <1833135.MvGxPPiF9h@phil> (raw) In-Reply-To: <1501756357-10511-2-git-send-email-jacob-chen@iotwrt.com> Am Donnerstag, 3. August 2017, 18:32:37 CEST schrieb Jacob Chen: > Add support for the rk3399 excavator main board. > This board works in a combination with the sapphire SOM. > > This board have been sold as the rk3399 evaluation board for commercial customers. > You can get more info from below link: > http://opensource.rock-chips.com/wiki_Excavator_sapphire_board > > Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com> > +&spdif { > + pinctrl-0 = <&spdif_bus>; part of the core spdif node in rk3399 so dropped this one > + i2c-scl-rising-time-ns = <450>; > + i2c-scl-falling-time-ns = <15>; > + #sound-dai-cells = <0>; > + status = "okay"; > +}; applied for 4.14 with the above and some property reordering. I've also added an entry to Documentation/devicetree/bindings/arm/rockchip.txt for the board. When adding future boards, please always also add an entry for that. 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 2/2] arm64: dts: rockchip: Add support for rk3399 excavator main board Date: Sun, 06 Aug 2017 17:44:20 +0200 [thread overview] Message-ID: <1833135.MvGxPPiF9h@phil> (raw) In-Reply-To: <1501756357-10511-2-git-send-email-jacob-chen@iotwrt.com> Am Donnerstag, 3. August 2017, 18:32:37 CEST schrieb Jacob Chen: > Add support for the rk3399 excavator main board. > This board works in a combination with the sapphire SOM. > > This board have been sold as the rk3399 evaluation board for commercial customers. > You can get more info from below link: > http://opensource.rock-chips.com/wiki_Excavator_sapphire_board > > Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com> > +&spdif { > + pinctrl-0 = <&spdif_bus>; part of the core spdif node in rk3399 so dropped this one > + i2c-scl-rising-time-ns = <450>; > + i2c-scl-falling-time-ns = <15>; > + #sound-dai-cells = <0>; > + status = "okay"; > +}; applied for 4.14 with the above and some property reordering. I've also added an entry to Documentation/devicetree/bindings/arm/rockchip.txt for the board. When adding future boards, please always also add an entry for that. Thanks Heiko
next prev parent reply other threads:[~2017-08-06 15:44 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-08-03 10:32 [PATCH 1/2] arm64: dts: rockchip: Add support for rk3399 sapphire SOM Jacob Chen 2017-08-03 10:32 ` Jacob Chen 2017-08-03 10:32 ` [PATCH 2/2] arm64: dts: rockchip: Add support for rk3399 excavator main board Jacob Chen 2017-08-03 10:32 ` Jacob Chen 2017-08-03 21:28 ` kbuild test robot 2017-08-03 21:28 ` kbuild test robot 2017-08-03 21:28 ` kbuild test robot 2017-08-06 15:46 ` Heiko Stuebner 2017-08-06 15:46 ` Heiko Stuebner 2017-08-06 15:44 ` Heiko Stuebner [this message] 2017-08-06 15:44 ` Heiko Stuebner 2017-08-03 10:34 ` [PATCH 1/2] arm64: dts: rockchip: Add support for rk3399 sapphire SOM Jacob Chen 2017-08-03 10:34 ` Jacob Chen 2017-08-03 10:34 ` Jacob Chen 2017-08-04 9:51 ` Jacob Chen 2017-08-04 9:51 ` Jacob Chen 2017-08-04 9:51 ` Jacob Chen 2017-08-06 15:41 ` Heiko Stuebner 2017-08-06 15:41 ` Heiko Stuebner
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=1833135.MvGxPPiF9h@phil \ --to=heiko@sntech.de \ --cc=devicetree@vger.kernel.org \ --cc=jacob-chen@iotwrt.com \ --cc=kever.yang@rock-chips.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rockchip@lists.infradead.org \ --cc=mark.yao@rock-chips.com \ --cc=zhangqing@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: linkBe 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.