linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: briannorris@chromium.org (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: dts: rockchip: add core dtsi file for rk3399 SoCs
Date: Thu, 21 Apr 2016 14:48:26 -0700	[thread overview]
Message-ID: <20160421214826.GA69116@google.com> (raw)
In-Reply-To: <1461122150-9042-1-git-send-email-jay.xu@rock-chips.com>

Hi,

On Wed, Apr 20, 2016 at 11:15:50AM +0800, Jianqun Xu wrote:
> This patch adds core dtsi file for rk3399 found on Rockchip
> rk3399 SoCs, tested on rk3399 evb.
> 
> Signed-off-by: Jianqun Xu <jay.xu@rock-chips.com>
> ---
>  arch/arm64/boot/dts/rockchip/rk3399.dtsi | 1744 ++++++++++++++++++++++++++++++
>  1 file changed, 1744 insertions(+)
>  create mode 100644 arch/arm64/boot/dts/rockchip/rk3399.dtsi
> 
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> new file mode 100644
> index 0000000..fa6fc2c
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> @@ -0,0 +1,1744 @@
[...]

> +	emmc_phy: phy {
> +		compatible = "rockchip,rk3399-emmc-phy";
> +		reg-offset = <0xf780>;

This property is not documented. The current doc says we "require" reg,
but you're kinda misusing it, I believe. At any rate, the current phy
driver won't probe without 'reg'.

> +		#phy-cells = <0>;
> +		rockchip,grf = <&grf>;
> +		status = "disabled";
> +	};

[...]

Brian

  parent reply	other threads:[~2016-04-21 21:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20  3:15 [PATCH] ARM64: dts: rockchip: add core dtsi file for rk3399 SoCs Jianqun Xu
2016-04-21  3:58 ` [PATCH] ARM64: dts: rockchip: add core dtsi file for RK3399 SoCs Jianqun Xu
2016-04-21 10:19   ` Mark Rutland
2016-04-21 10:47     ` Huang, Tao
2016-04-21 11:30       ` Marc Zyngier
2016-04-21 20:24         ` Heiko Stübner
2016-04-21 21:12           ` Marc Zyngier
2016-04-22  1:50             ` jay.xu
2016-04-22  7:44               ` Marc Zyngier
2016-04-25  9:48         ` Huang, Tao
2016-04-25 10:05           ` Mark Rutland
2016-04-25 10:19             ` Huang, Tao
2016-04-25 10:47               ` Mark Rutland
2016-04-25 12:27                 ` Huang, Tao
2016-04-25 10:06           ` Marc Zyngier
2016-04-25 10:39             ` Marc Zyngier
2016-04-25 11:50               ` Huang, Tao
2016-04-25 12:04                 ` Marc Zyngier
2016-04-21 21:02   ` Rob Herring
2016-04-21 22:02   ` Heiko Stübner
2016-04-21 22:38     ` Doug Anderson
2016-04-21 22:49       ` Heiko Stübner
2016-04-22  4:23       ` Huang, Tao
2016-04-21 21:48 ` Brian Norris [this message]
2016-04-21 22:32   ` [PATCH] ARM64: dts: rockchip: add core dtsi file for rk3399 SoCs Heiko Stübner
2016-04-22  5:21 ` [PATCH v2 0/4] ARM64: dts: rockchip: add support for RK3399 Jianqun Xu
2016-04-22  5:25 ` [PATCH v2 1/4] Documentation: rockchip-dw-mshc: add description for rk3399 Jianqun Xu
2016-04-22  5:28 ` [PATCH v2 2/4] ARM64: dts: rockchip: add core dtsi file for RK3399 SoCs Jianqun Xu
2016-04-22  5:31 ` [PATCH 3/4] ARM64: dts: rockchip: add RK3399 evaluation board Jianqun Xu
2016-04-22  5:36 ` [PATCH v2 4/4] ARM64: dts: rockchip: add dts file for " Jianqun Xu

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=20160421214826.GA69116@google.com \
    --to=briannorris@chromium.org \
    --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).