From: Heiko Stuebner <heiko@sntech.de>
To: Andy Yan <andy.yan@rock-chips.com>
Cc: kever.yang@rock-chips.com, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: rockchip: Add core dts for RK3308 SOC
Date: Fri, 18 Oct 2019 01:30:22 +0200 [thread overview]
Message-ID: <5242916.cCMrPAA6xQ@phil> (raw)
In-Reply-To: <20191017030449.32289-1-andy.yan@rock-chips.com>
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 = <BOOT_BL_DOWNLOAD>;
> + mode-loader = <BOOT_BL_DOWNLOAD>;
> + mode-normal = <BOOT_NORMAL>;
> + mode-recovery = <BOOT_RECOVERY>;
> + mode-fastboot = <BOOT_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 = <GIC_SPI 11 IRQ_TYPE_LEVEL_HIGH>;
> + 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 = <GIC_SPI 15 IRQ_TYPE_LEVEL_HIGH>;
> + #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 = <GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>;
> + 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 = <GIC_SPI 0 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 1 IRQ_TYPE_LEVEL_HIGH>;
> + #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 = <GIC_SPI 2 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 3 IRQ_TYPE_LEVEL_HIGH>;
> + #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 = <GIC_SPI 52 IRQ_TYPE_LEVEL_HIGH>;
> + 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 = <GIC_SPI 64 IRQ_TYPE_LEVEL_HIGH>;
> + 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
next prev parent reply other threads:[~2019-10-17 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 3:02 [PATCH 0/2] Add basic dts support for RK3308 Andy Yan
2019-10-17 3:04 ` [PATCH 1/2] arm64: dts: rockchip: Add core dts for RK3308 SOC Andy Yan
2019-10-17 23:30 ` Heiko Stuebner [this message]
2019-10-21 9:09 ` Andy Yan
2019-10-17 3:05 ` [PATCH 2/2] arm64: dts: rockchip: Add basic dts for RK3308 EVB Andy Yan
2019-10-17 23:39 ` 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=5242916.cCMrPAA6xQ@phil \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--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=robh+dt@kernel.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).