From patchwork Wed Oct 23 10:13:06 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?q?Andreas_F=C3=A4rber?= X-Patchwork-Id: 177253 Delivered-To: patch@linaro.org Received: by 2002:a92:409a:0:0:0:0:0 with SMTP id d26csp502501ill; Wed, 23 Oct 2019 03:13:30 -0700 (PDT) X-Google-Smtp-Source: APXvYqxSkJV/wvkM2x3qeLJTnRFWM6AtDCi9cXHk6RT66E4040diLx+nAX8ijR3AnfJ/r9F316z3 X-Received: by 2002:a17:906:a0f:: with SMTP id w15mr11536383ejf.321.1571825610186; Wed, 23 Oct 2019 03:13:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571825610; cv=none; d=google.com; s=arc-20160816; b=rxGUph2yObb/XXUzScXKLA4g90W8zC3C/AxrjHzz8jFQ6O5pK2Nzh7fZbWRcMcXLf2 j1UH0oKWY5UGho4aWVqS1JA/3Nl5aMnrcjtUTvu92w4MU1ugq+CBmZNpTP2ueq1MRUUc pcA8sJuKZzZ1IG5ltYHkQJRWuRNuo1zL1YeLiuwYZuEb2c0tXbeVFgRsV+r2ZP89xfA2 ODh/Gi+F9IC2mRdK4NoXAR5q6ghle03vYpDw7NGr5hcDw/ImsHUZT1TNAXWOdkthsD1e 1Ey8vcw7cLKNoAy4MaFmik9OF6rjG/KUQ8IBIWPn6ALx1ab2Nh/JyqkOXIzag69pOA2J x1vw== 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:mime-version :message-id:date:subject:cc:to:from; bh=Sx4xLEu5H0FCF5s+Cth7KssLjgIuMEWp8F3GVC41GWE=; b=Z4Dz6mgXF60inzRUBmmK7eHUsoNsY8pA0NJtOkHEAtTugbWkoIsdgs0ea0oCASl7jz dZOxTanMX5z/bPf9h1s6+HQnNvrpx7K72Lww/xDKwWWaOdK3k88xCPY3/zijFw8Jv4Sn 9IN9Zyl+kV8r0ci6y7UMfY8N9kPHm6jluCdAx1yFWdbk93Gl6qF731RyfrvqKxKdQ1kM 2zISFjjIkhy/q6jEZ5fFEtOHRH2xLmXBBHSE1OyjECo3kvslldF/rUhoHp+llD51xYjF Fp27OTd4kHplL1Fjg85Xy0cYStMt0Fggdt1YYKXEKmLJ5Nx6wpanDXM+dpdWUjxDQ/O6 ulBg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of devicetree-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=devicetree-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 h50si14138213ede.423.2019.10.23.03.13.29; Wed, 23 Oct 2019 03:13:30 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of devicetree-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 devicetree-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=devicetree-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391068AbfJWKN3 (ORCPT + 8 others); Wed, 23 Oct 2019 06:13:29 -0400 Received: from mx2.suse.de ([195.135.220.15]:53770 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2390935AbfJWKN3 (ORCPT ); Wed, 23 Oct 2019 06:13:29 -0400 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 546CEB4D6; Wed, 23 Oct 2019 10:13:27 +0000 (UTC) From: =?utf-8?q?Andreas_F=C3=A4rber?= To: linux-realtek-soc@lists.infradead.org Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, =?utf-8?q?Andreas_F=C3=A4rber?= , Philipp Zabel , devicetree@vger.kernel.org Subject: [PATCH v2 00/11] arm64: Realtek RTD1295 reset controllers Date: Wed, 23 Oct 2019 12:13:06 +0200 Message-Id: <20191023101317.26656-1-afaerber@suse.de> X-Mailer: git-send-email 2.16.4 MIME-Version: 1.0 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Hello, This series adds reset controllers for the Realtek RTD1295 and RTD1195 SoCs. v2 adopts reset-simple driver and DesignWare bindings as simplification and covers RTD1195, too. Note that reset-simple driver would allow to cover RTD1195's reset1-3 in one DT node, but it only maps the first resource, so RTD1295's reset4 would need to remain separate due to a gap in between. I've therefore left them all as separate nodes for now. Also note that my initial 32-bit arm patch already selects RESET_CONTROLLER, to avoid needing a separate patch here to add that one line as done for arm64. If I can take the bindings patches through the Realtek tree then I can squash the two final DT patches depending on them into the patches added the resets, otherwise they need to go into v5.6 or be merged via a topic branch. More experimental patches at: https://github.com/afaerber/linux/commits/rtd1295-next Have a lot of fun! Cheers, Andreas v1 -> v2: * Drop custom reset driver * Drop "realtek,rtd1295-reset" binding * Reordered to not depend on irqchip or clk patches * Extended with RTD1195 patches Cc: Philipp Zabel Cc: devicetree@vger.kernel.org Andreas Färber (11): dt-bindings: reset: Add Realtek RTD1295 dt-bindings: reset: Add Realtek RTD1195 reset: simple: Keep alphabetical order reset: simple: Add Realtek RTD1195/RTD1295 arm64: realtek: Select reset controller arm64: dts: realtek: Add RTD129x reset controller nodes arm64: dts: realtek: Add RTD129x UART resets ARM: dts: rtd1195: Add reset nodes ARM: dts: rtd1195: Add UART resets arm64: dts: realtek: Adopt RTD129x reset constants ARM: dts: rtd1195: Adopt reset constants arch/arm/boot/dts/rtd1195.dtsi | 27 +++++++ arch/arm64/Kconfig.platforms | 1 + arch/arm64/boot/dts/realtek/rtd129x.dtsi | 34 +++++++++ drivers/reset/Kconfig | 5 +- include/dt-bindings/reset/realtek,rtd1195.h | 74 +++++++++++++++++++ include/dt-bindings/reset/realtek,rtd1295.h | 111 ++++++++++++++++++++++++++++ 6 files changed, 250 insertions(+), 2 deletions(-) create mode 100644 include/dt-bindings/reset/realtek,rtd1195.h create mode 100644 include/dt-bindings/reset/realtek,rtd1295.h -- 2.16.4 Reviewed-by: Rob Herring