From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6C60ACA9EB3 for ; Thu, 17 Oct 2019 23:30:49 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3DBC221D7C for ; Thu, 17 Oct 2019 23:30:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="W5yRO3H6" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3DBC221D7C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=sntech.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Date:Subject:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=RVlWqjz64a7FfE8koqCxBYPkRKjum5mB0125cu2tZbk=; b=W5yRO3H6DpHwOa 7a52dFv96t4AqkQtjj42X6IXvUJAmcDGsndJpSVWR+Bw2EdVB38nBwM1auaH5M9MbQi51OMttOQqc LuVYtN8v/sL2MfWeHgjfyUUyU0vk6HKma7Xcc8khZMWB4phMBZ/47Yc+aquiZgCC4ck8os/Jc4GRe ka9/wfu0RvX8p8H8b2MqBkQa/aF6c/xSxTUAQpjUCN35HnzsrN5MZl7N6fmqg5Wm2/TPDxPDI+NYF brx6KZydfs3ia4yZOuE3xbNPWxoAAb5EzMhiiS2jxatbVBfFygWUwvQ2KsIfrKw3xfwxfbl0JIFwA tSWollBd5/x7XIHqsT8g==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1iLFE6-0000tp-GK; Thu, 17 Oct 2019 23:30:38 +0000 Received: from gloria.sntech.de ([185.11.138.130]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1iLFE3-0000sc-5Y; Thu, 17 Oct 2019 23:30:36 +0000 Received: from remote.shanghaihotelholland.com ([46.44.148.63] helo=phil.localnet) by gloria.sntech.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iLFDw-0004Li-P4; Fri, 18 Oct 2019 01:30:28 +0200 From: Heiko Stuebner To: Andy Yan Subject: Re: [PATCH 1/2] arm64: dts: rockchip: Add core dts for RK3308 SOC Date: Fri, 18 Oct 2019 01:30:22 +0200 Message-ID: <5242916.cCMrPAA6xQ@phil> In-Reply-To: <20191017030449.32289-1-andy.yan@rock-chips.com> References: <20191017030242.32219-1-andy.yan@rock-chips.com> <20191017030449.32289-1-andy.yan@rock-chips.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20191017_163035_362990_40481B02 X-CRM114-Status: GOOD ( 18.16 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: devicetree@vger.kernel.org, kever.yang@rock-chips.com, linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org, robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Andy, Am Donnerstag, 17. Oktober 2019, 05:04:49 CEST schrieb Andy Yan: > + psci { > + compatible = "arm,psci-1.0"; > + method = "smc"; > + }; Please also provide a ATF implementation for the rk3308 :-) [Not a requirement for getting this merged, but it would be really cool to have sources for the full stack] > + > + ramoops_mem: ramoops_mem { > + reg = <0x0 0x110000 0x0 0xf0000>; > + reg-names = "ramoops_mem"; > + }; > + > + ramoops: ramoops { > + compatible = "ramoops"; > + record-size = <0x0 0x30000>; > + console-size = <0x0 0xc0000>; > + ftrace-size = <0x0 0x00000>; > + pmsg-size = <0x0 0x00000>; > + memory-region = <&ramoops_mem>; > + }; I think ramoops are more a per-board thing, like for the evb. As they'll require cooperation with bootloaders to not mangle that memory area. For this please also coordinate with Kever because I somehow remember we have u-boot sometimes at 0x100000. > + grf: grf@ff000000 { > + compatible = "rockchip,rk3308-grf", "syscon", "simple-mfd"; Please add a patch adding the rockchip,rk3308-grf compatible to Documentation/devicetree/bindings/soc/rockchip/grf.txt > + reg = <0x0 0xff000000 0x0 0x10000>; > + > + reboot-mode { > + compatible = "syscon-reboot-mode"; > + offset = <0x500>; > + mode-bootloader = ; > + mode-loader = ; > + mode-normal = ; > + mode-recovery = ; > + mode-fastboot = ; > + }; > + }; > + > + detect_grf: syscon@ff00b000 { > + compatible = "syscon", "simple-mfd"; compatible = "rockchip,rk3308-detect-grf", "syscon" + add the rk3308-detect-grf to the binding > + reg = <0x0 0xff00b000 0x0 0x1000>; > + #address-cells = <1>; > + #size-cells = <1>; > + }; > + > + core_grf: syscon@ff00c000 { > + compatible = "syscon", "simple-mfd"; same as detect_grf > + reg = <0x0 0xff00c000 0x0 0x1000>; > + #address-cells = <1>; > + #size-cells = <1>; > + > + }; > + > + i2c0: i2c@ff040000 { > + compatible = "rockchip,rk3399-i2c"; compatible = "rockchip,rk3308-i2c", "rockchip,rk3399-i2c"; Same for all i2c controllers. > + reg = <0x0 0xff040000 0x0 0x1000>; > + clocks = <&cru SCLK_I2C0>, <&cru PCLK_I2C0>; > + clock-names = "i2c", "pclk"; > + interrupts = ; > + pinctrl-names = "default"; > + pinctrl-0 = <&i2c0_xfer>; > + #address-cells = <1>; > + #size-cells = <0>; > + status = "disabled"; > + }; > + spi0: spi@ff120000 { > + compatible = "rockchip,rk3308-spi", "rockchip,rk3066-spi"; > + reg = <0x0 0xff120000 0x0 0x1000>; > + interrupts = ; > + #address-cells = <1>; > + #size-cells = <0>; > + clocks = <&cru SCLK_SPI0>, <&cru PCLK_SPI0>; > + clock-names = "spiclk", "apb_pclk"; > + dmas = <&dmac0 0>, <&dmac0 1>; > + dma-names = "tx", "rx"; > + pinctrl-names = "default", "high_speed"; there is no high_speed pinctrl defined for the Rockchip spi driver in mainline, so this part should go away in a first step. Same for the other spi controllers. > + pinctrl-0 = <&spi0_clk &spi0_csn0 &spi0_miso &spi0_mosi>; > + pinctrl-1 = <&spi0_clk_hs &spi0_csn0 &spi0_miso_hs &spi0_mosi_hs>; > + status = "disabled"; > + }; > + rktimer: rktimer@ff1a0000 { > + compatible = "rockchip,rk3288-timer"; compatible = "rockchip,rk3308-timer", "rockchip,rk3288-timer"; > + reg = <0x0 0xff1a0000 0x0 0x20>; > + interrupts = ; > + clocks = <&cru PCLK_TIMER>, <&cru SCLK_TIMER0>; > + clock-names = "pclk", "timer"; > + }; > + amba { > + compatible = "arm,amba-bus"; compatible = "simple-bus"; > + #address-cells = <2>; > + #size-cells = <2>; > + ranges; > + > + dmac0: dma-controller@ff2c0000 { > + compatible = "arm,pl330", "arm,primecell"; > + reg = <0x0 0xff2c0000 0x0 0x4000>; > + interrupts = , > + ; > + #dma-cells = <1>; > + clocks = <&cru ACLK_DMAC0>; > + clock-names = "apb_pclk"; > + peripherals-req-type-burst; peripherals-req-type-burst is undocumented so likely some change to the dma driver not yet upstream? > + }; > + > + dmac1: dma-controller@ff2d0000 { > + compatible = "arm,pl330", "arm,primecell"; > + reg = <0x0 0xff2d0000 0x0 0x4000>; > + interrupts = , > + ; > + #dma-cells = <1>; > + clocks = <&cru ACLK_DMAC1>; > + clock-names = "apb_pclk"; > + peripherals-req-type-burst; > + }; > + }; > + > + i2s_2ch_0: i2s@ff350000 { > + compatible = "rockchip,rk3308-i2s", "rockchip,rk3066-i2s"; > + reg = <0x0 0xff350000 0x0 0x1000>; > + interrupts = ; > + clocks = <&cru SCLK_I2S0_2CH>, <&cru HCLK_I2S0_2CH>; > + clock-names = "i2s_clk", "i2s_hclk"; > + dmas = <&dmac1 8>, <&dmac1 9>; > + dma-names = "tx", "rx"; > + resets = <&cru SRST_I2S0_2CH_M>, <&cru SRST_I2S0_2CH_H>; > + reset-names = "reset-m", "reset-h"; These resets don't seem to be defined in driver or binding? Same for other i2s > + pinctrl-names = "default"; > + pinctrl-0 = <&i2s_2ch_0_sclk > + &i2s_2ch_0_lrck > + &i2s_2ch_0_sdi > + &i2s_2ch_0_sdo>; > + status = "disabled"; > + }; > + > + mac: ethernet@ff4e0000 { > + compatible = "rockchip,rk3308-mac"; Was this support to the network driver already submitted? Because I wasn't able to find it in the gmac driver. > + reg = <0x0 0xff4e0000 0x0 0x10000>; > + rockchip,grf = <&grf>; > + interrupts = ; > + interrupt-names = "macirq"; > + clocks = <&cru SCLK_MAC>, <&cru SCLK_MAC_RX_TX>, > + <&cru SCLK_MAC_RX_TX>, <&cru SCLK_MAC_REF>, > + <&cru SCLK_MAC>, <&cru ACLK_MAC>, > + <&cru PCLK_MAC>, <&cru SCLK_MAC_RMII>; > + clock-names = "stmmaceth", "mac_clk_rx", > + "mac_clk_tx", "clk_mac_ref", > + "clk_mac_refout", "aclk_mac", > + "pclk_mac", "clk_mac_speed"; > + phy-mode = "rmii"; > + pinctrl-names = "default"; > + pinctrl-0 = <&rmii_pins &mac_refclk_12ma>; > + resets = <&cru SRST_MAC_A>; > + reset-names = "stmmaceth"; > + status = "disabled"; > + }; Heiko _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel