Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp1807811ybc; Sun, 17 Nov 2019 07:45:57 -0800 (PST) X-Google-Smtp-Source: APXvYqxHozhmgaXyZx9i/TTFetEnRkIYeScBGUmKvqmdmcG3bwRyKoa0UiDLY4mpTYUfRTGbJZhh X-Received: by 2002:a17:907:36e:: with SMTP id rs14mr19421008ejb.330.1574005557141; Sun, 17 Nov 2019 07:45:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574005557; cv=none; d=google.com; s=arc-20160816; b=AyBIuXz0OYFXNFehHL7K9cD4nrUCahsw/Ri0rBwAo+MAKQF7Xj/V/5ZmXk/NKYZTHo tiCWa3te8IfKAmV+VyfbLtgb38Tqi+BI6R45wssA+Td8ohXGwaOUa8OM4ByAf2OTuSII 17EEpcz9e22eeCvHKa3/+4Diy/jix/q9g3CKuazUauGIXH7UYV42laCV1VHY6j0JXxTW khX72qhvk3xGA/CVYzVWvpLxkzWWF14Z2HfTgLC5q9VKnKmulZbrz6QyBMB9K9nNgEEz UgWXb6AipXYOlc6g+ep9WtdDywxGPxKne83j2s+UnCOC87q/bMMjslvvdUzwbGrD7UVs PEuw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:cc:to:subject; bh=rPPZgL/jzG6RiRnbeOikah/L0fuhNIUWCkSEPqG9zag=; b=SyTWeSvC8uBhN9/nQ+KLs7gSpuwShJ7fOMuGOO516vLp4du3MdcoO4VBW4hqfL7x/9 i1Qmv2kYAINpGuGldX0SwskmlLroCBrtnsb5ueQ8QwPSg7Hs0Vs7a7q/9Aa5KgeYB+7U Oii8boM7PYfFRvR7cAqgkt8tdlG6MFHjbY5UFEKufolLV5AFJi4cDOTmt/IxIwp8AwkQ pKazavXUiRVObxomad7KjOD14PZMiVThgj8MnUq3W0TgnaefeMmO8JzXTPSLuAxCzFVh mGpREBS4vJv9CCqCcjNv4LD2kdxL1Y2YZ9BYialcdFP7KZOpW7WJCOSri9Hf9Vxo1AHr lt4w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l23si5430224edc.279.2019.11.17.07.45.18; Sun, 17 Nov 2019 07:45:57 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726304AbfKQPlE (ORCPT + 99 others); Sun, 17 Nov 2019 10:41:04 -0500 Received: from mx2.suse.de ([195.135.220.15]:34108 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726069AbfKQPlD (ORCPT ); Sun, 17 Nov 2019 10:41:03 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 77297ACA5; Sun, 17 Nov 2019 15:41:00 +0000 (UTC) Subject: Re: [PATCH v3 3/8] ARM: dts: Prepare Realtek RTD1195 and MeLE X1000 To: Marc Zyngier Cc: linux-realtek-soc@lists.infradead.org, Mark Rutland , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Rob Herring , linux-arm-kernel@lists.infradead.org, James Tai References: <20191117072109.20402-1-afaerber@suse.de> <20191117072109.20402-4-afaerber@suse.de> <20191117104726.2b1fccb8@why> From: =?UTF-8?Q?Andreas_F=c3=a4rber?= Organization: SUSE Software Solutions Germany GmbH Message-ID: <61bf74ad-b4a1-f443-bf99-be354b4d942b@suse.de> Date: Sun, 17 Nov 2019 16:40:59 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: <20191117104726.2b1fccb8@why> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Marc, Am 17.11.19 um 11:47 schrieb Marc Zyngier: > On Sun, 17 Nov 2019 08:21:04 +0100 > Andreas Färber wrote: >> Add Device Trees for Realtek RTD1195 SoC and MeLE X1000 TV box. >> >> Reuse the existing RTD1295 watchdog compatible for now. >> >> Reviewed-by: Rob Herring >> [AF: Fixed r-bus size, fixed GIC CPU mask, updated memreserve] >> Signed-off-by: Andreas Färber >> --- >> v2 -> v3: >> * Fixed r-bus size in /soc ranges from 0x1000000 to 0x70000 (James) >> * Adjusted /memreserve/ to close gap from 0xa800 to 0xc000 for full 0x100000 >> * Changed arch timer from GIC_CPU_MASK_RAW(0xf) to GIC_CPU_MASK_SIMPLE(2) >> squashed from RTD1395 v1 series >> >> v1 -> v2: >> * Dropped /memreserve/ and reserved-memory nodes for peripherals and NOR (Rob) >> * Carved them out from memory reg instead (Rob) >> * Converted some /memreserve/s to reserved-memory nodes >> >> arch/arm/boot/dts/Makefile | 2 + >> arch/arm/boot/dts/rtd1195-mele-x1000.dts | 31 ++++++++ >> arch/arm/boot/dts/rtd1195.dtsi | 127 +++++++++++++++++++++++++++++++ >> 3 files changed, 160 insertions(+) >> create mode 100644 arch/arm/boot/dts/rtd1195-mele-x1000.dts >> create mode 100644 arch/arm/boot/dts/rtd1195.dtsi >> >> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile >> index 08011dc8c7a6..4853a13c8cf2 100644 >> --- a/arch/arm/boot/dts/Makefile >> +++ b/arch/arm/boot/dts/Makefile >> @@ -865,6 +865,8 @@ dtb-$(CONFIG_ARCH_QCOM) += \ >> dtb-$(CONFIG_ARCH_RDA) += \ >> rda8810pl-orangepi-2g-iot.dtb \ >> rda8810pl-orangepi-i96.dtb >> +dtb-$(CONFIG_ARCH_REALTEK) += \ >> + rtd1195-mele-x1000.dtb >> dtb-$(CONFIG_ARCH_REALVIEW) += \ >> arm-realview-pb1176.dtb \ >> arm-realview-pb11mp.dtb \ >> diff --git a/arch/arm/boot/dts/rtd1195-mele-x1000.dts b/arch/arm/boot/dts/rtd1195-mele-x1000.dts >> new file mode 100644 >> index 000000000000..834b430e6250 >> --- /dev/null >> +++ b/arch/arm/boot/dts/rtd1195-mele-x1000.dts >> @@ -0,0 +1,31 @@ >> +// SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause) >> +/* >> + * Copyright (c) 2017-2019 Andreas Färber >> + */ >> + >> +/dts-v1/; >> + >> +#include "rtd1195.dtsi" >> + >> +/ { >> + compatible = "mele,x1000", "realtek,rtd1195"; >> + model = "MeLE X1000"; >> + >> + aliases { >> + serial0 = &uart0; >> + }; >> + >> + chosen { >> + stdout-path = "serial0:115200n8"; >> + }; >> + >> + memory@0 { >> + device_type = "memory"; >> + reg = <0x0 0x18000000>, >> + <0x19100000 0x26f00000>; >> + }; >> +}; >> + >> +&uart0 { >> + status = "okay"; >> +}; >> diff --git a/arch/arm/boot/dts/rtd1195.dtsi b/arch/arm/boot/dts/rtd1195.dtsi >> new file mode 100644 >> index 000000000000..4e3866fe8f6e >> --- /dev/null >> +++ b/arch/arm/boot/dts/rtd1195.dtsi >> @@ -0,0 +1,127 @@ >> +// SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause) >> +/* >> + * Copyright (c) 2017-2019 Andreas Färber >> + */ >> + >> +/memreserve/ 0x00000000 0x0000a800; /* boot code */ >> +/memreserve/ 0x0000a800 0x000f5800; >> +/memreserve/ 0x17fff000 0x00001000; >> + >> +#include >> + >> +/ { >> + compatible = "realtek,rtd1195"; >> + interrupt-parent = <&gic>; >> + #address-cells = <1>; >> + #size-cells = <1>; >> + >> + cpus { >> + #address-cells = <1>; >> + #size-cells = <0>; >> + >> + cpu0: cpu@0 { >> + device_type = "cpu"; >> + compatible = "arm,cortex-a7"; >> + reg = <0x0>; >> + clock-frequency = <1000000000>; >> + }; >> + >> + cpu1: cpu@1 { >> + device_type = "cpu"; >> + compatible = "arm,cortex-a7"; >> + reg = <0x1>; >> + clock-frequency = <1000000000>; >> + }; >> + }; >> + >> + reserved-memory { >> + #address-cells = <1>; >> + #size-cells = <1>; >> + ranges; >> + >> + rpc_comm: rpc@b000 { >> + reg = <0x0000b000 0x1000>; >> + }; >> + >> + audio@1b00000 { >> + reg = <0x01b00000 0x400000>; >> + }; >> + >> + rpc_ringbuf: rpc@1ffe000 { >> + reg = <0x01ffe000 0x4000>; >> + }; >> + >> + secure@10000000 { >> + reg = <0x10000000 0x100000>; >> + no-map; >> + }; >> + }; >> + >> + arm-pmu { >> + compatible = "arm,cortex-a7-pmu"; >> + interrupts = , >> + ; >> + interrupt-affinity = <&cpu0>, <&cpu1>; >> + }; >> + >> + timer { >> + compatible = "arm,armv7-timer"; >> + interrupts = > + (GIC_CPU_MASK_SIMPLE(2) | IRQ_TYPE_LEVEL_LOW)>, >> + > + (GIC_CPU_MASK_SIMPLE(2) | IRQ_TYPE_LEVEL_LOW)>, >> + > + (GIC_CPU_MASK_SIMPLE(2) | IRQ_TYPE_LEVEL_LOW)>, >> + > + (GIC_CPU_MASK_SIMPLE(2) | IRQ_TYPE_LEVEL_LOW)>; >> + clock-frequency = <27000000>; > > This is 2019, and yet it feels like 2011. This should be setup in the > bootloader, not in DT... What exactly - the whole node, the GIC CPU mask, the clock-frequency? Please compare previous submissions: It's a v2012.07 based downstream U-Boot that I don't have GPL sources of. It doesn't even fill in the /memory@0 node. >> + }; >> + >> + osc27M: osc { >> + compatible = "fixed-clock"; >> + clock-frequency = <27000000>; >> + #clock-cells = <0>; >> + clock-output-names = "osc27M"; >> + }; >> + >> + soc { >> + compatible = "simple-bus"; >> + #address-cells = <1>; >> + #size-cells = <1>; >> + ranges = <0x18000000 0x18000000 0x00070000>, >> + <0x18100000 0x18100000 0x01000000>, >> + <0x40000000 0x40000000 0xc0000000>; >> + >> + wdt: watchdog@18007680 { >> + compatible = "realtek,rtd1295-watchdog"; >> + reg = <0x18007680 0x100>; >> + clocks = <&osc27M>; >> + }; >> + >> + uart0: serial@18007800 { >> + compatible = "snps,dw-apb-uart"; >> + reg = <0x18007800 0x400>; >> + reg-shift = <2>; >> + reg-io-width = <4>; >> + clock-frequency = <27000000>; >> + status = "disabled"; >> + }; >> + >> + uart1: serial@1801b200 { >> + compatible = "snps,dw-apb-uart"; >> + reg = <0x1801b200 0x100>; >> + reg-shift = <2>; >> + reg-io-width = <4>; >> + clock-frequency = <27000000>; >> + status = "disabled"; >> + }; >> + >> + gic: interrupt-controller@ff011000 { >> + compatible = "arm,cortex-a7-gic"; >> + reg = <0xff011000 0x1000>, >> + <0xff012000 0x2000>; >> + interrupt-controller; >> + #interrupt-cells = <3>; > > You know what I'm going to say: GICH and GI[C]V are missing, as well as > the maintenance interrupt. This is all bog-standard HW (most probably a > GIC400), so there is no reason for this information not to be present. Yes, and if you look at my rtd1295-next branch referenced in the cover letter, you will find that I do have follow-up patches adding GICH and GICV, also a guess for the GICV interrupt, and in a different patch [1] I have specifically reminded Realtek to review the v2 of this patch please, which still hasn't happened yet... I inquired for the RTD1619 patch, and James replied that for its GICv3 they supposedly do _not_ have the optional GICH and GICV [1]. Thus I am waiting on their input for whether they have it on RTD1195. The U-Boot that I have on this device does not boot the kernel in HYP mode, so I cannot test KVM myself. Same issue on the Horseradish EVB. On the Buffalo LinkStation LS520 I still don't have a serial console (probably my bad soldering skills), but I doubt it's any different. Regards, Andreas [1] https://patchwork.kernel.org/patch/11227113/ -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)