Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp665256imb; Fri, 1 Mar 2019 10:34:58 -0800 (PST) X-Google-Smtp-Source: APXvYqz6Rr7KnTJEvSPAFcMld3XbYsRZtMbPzzucd6CTmaoM8ohR+oX5zswXzoP42MlAiSxPrh3x X-Received: by 2002:a17:902:650b:: with SMTP id b11mr6902414plk.293.1551465297931; Fri, 01 Mar 2019 10:34:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551465297; cv=none; d=google.com; s=arc-20160816; b=Mc5P86wctEah7PMKzAyTzPgNxqG9L2RP1LxXau6a8kn1lNdrTK8yv73RNTmKq8CfXV 9Oi6ybbT0NN46CDfQ9mrrsxeC4o2igXF/gQT1NHYDVdWu3YIGpBK7JO0k5yz8MDDZcla /Wvvmvl8K+UQHFblMnmHVEM2c/WH6gak7TdQoozlIrgCl2ffdugx9JXO8R+Fc3Yq8+g2 E3jd7Au7luKmK15fbooPSZtTtLkWqPPZUKz+Mz96TADkdDKGYHzOj38tb3Bv1ZCWAA5G 6iAXKrr9rbXzdUCOSKrOwmX1I4qV6lYLXLqCsb9+lCiM+z1VtwWXbXCG21G+NgL91upK JW3Q== 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 :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=ncNcJQwDfiPhDXs8lF0Szc4vWY35aZvZb7KgVFzyX5I=; b=SF2h/n1KUbFkX+EZNFl4Yx8vHu+3FQBQIAFEzl4haryuOBLmHP0T6L/x1TP/tV6UKz vQfUluQyYzwEydsmKKhZZCMUX1Ag2KRNmOi769VcnIYlchVnICZS/AAiu33h4/RFJrUh SandsjuR6zcudGVW8fli35op5kgtQOjaTP6bSvLNY+tmc+JsR87rx31t9CppIDkMXUfq iAqeOCCkQVGtIVxWQZvSiFvMSicIFY2OEzUmh5Kk7hgg09FFWQUQcMAXXEM2CYb1VYOu u8IHjya8WiCcEAz1w4vmLKSxAzu3cRW4G9/vHEncO3H4lqoyUN+Os3uY9hcBiHuehz3U 4X0Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@googlemail.com header.s=20161025 header.b="URExq/Md"; 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; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=googlemail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h7si13201766pll.172.2019.03.01.10.34.42; Fri, 01 Mar 2019 10:34: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; dkim=pass header.i=@googlemail.com header.s=20161025 header.b="URExq/Md"; 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; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=googlemail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389304AbfCAS3t (ORCPT + 99 others); Fri, 1 Mar 2019 13:29:49 -0500 Received: from mail-wm1-f67.google.com ([209.85.128.67]:39936 "EHLO mail-wm1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389201AbfCAS3s (ORCPT ); Fri, 1 Mar 2019 13:29:48 -0500 Received: by mail-wm1-f67.google.com with SMTP id g20so12346121wmh.5; Fri, 01 Mar 2019 10:29:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=ncNcJQwDfiPhDXs8lF0Szc4vWY35aZvZb7KgVFzyX5I=; b=URExq/MdU1CtB9n0eev3RNX3Z8rgbn1RYMpZ2oI5fDT+J5pVKYLAhSyO4OX1jSj+7m 6OIXVKnWOaax2masO02Kx3eNwMHCic6tZj++1PUutHSBfngBvr0gtl6DZM2X7JfW2FBV 3sTzOcQ/bE64OGaGAjZvpa6H4zK9WUq/qVAvX3GE5fSU5OhLo9iKFwjhFbv1cKPt083q UZcq8NKgIZF9aPnYkyP7B1sdDZowrbirUcb+evU78pKhsByLxOYabGNXV6GCcLlHWDns 8GXCvpAB3uGK8dSU2UH2zjTpNLO8jD0pyHn/vgydwrrOJ1FFAf2PojP1aHIpo4csPH5H GqAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=ncNcJQwDfiPhDXs8lF0Szc4vWY35aZvZb7KgVFzyX5I=; b=W0Seuec7TCgE3tjhbtcnvrc8zmIhRJveUbMrQIDmkzGBCF2vt/hjMvFXfcKekfVwwR Co3qpNAg9MdJ9RV2nzkCUcs5799ig4g/F1Gote43CAcHscczN3u9AsIeqvQX4AmnqUMr V+olqFyV8fu7y4Cu3VNu2Wv/fdhsCKt2x30RMqa2JQPjaU3I803qlFTBadaVbZSwZMrn RG7K5Eqpm6cdQcBcs8UEOH7aW8edf5SliQvJK64x+kRsodso6ASrrpZxE0K45h86PgfJ chfX9Mmi1W6nG0RePKL4DHOpqcZ938wdVnoJdKchBE9bOFlIGWyJDL6BbqVWf0e6bMoA zprw== X-Gm-Message-State: AHQUAuZt7sjyO/J/tIxrZqaeoimESFXKeTFBiqB7iBl7BZq8Q2jzejtP UhpVY7HqbScRtzTt+6cm1eE= X-Received: by 2002:a1c:f901:: with SMTP id x1mr4125319wmh.51.1551464985881; Fri, 01 Mar 2019 10:29:45 -0800 (PST) Received: from blackbox.darklights.net (p200300DCD7109200428D5CFFFEB99DB8.dip0.t-ipconnect.de. [2003:dc:d710:9200:428d:5cff:feb9:9db8]) by smtp.googlemail.com with ESMTPSA id l18sm21221367wrv.20.2019.03.01.10.29.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Mar 2019 10:29:45 -0800 (PST) From: Martin Blumenstingl To: liang.yang@amlogic.com Cc: linux-mtd@lists.infradead.org, linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org, robh+dt@kernel.org, mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, jianxin.pan@amlogic.com, Martin Blumenstingl Subject: [RFC PATCH nand-next 1/2] dt-bindings: nand: meson: add support for more SoCs Date: Fri, 1 Mar 2019 19:29:21 +0100 Message-Id: <20190301182922.8309-2-martin.blumenstingl@googlemail.com> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190301182922.8309-1-martin.blumenstingl@googlemail.com> References: <20190301182922.8309-1-martin.blumenstingl@googlemail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Older Amlogic SoCs have a slightly different integration of the NFC (NAND flash controller) than the new ones (GXL, GXM, AXG). On GXL, AXG and newer the "NAND device clock" is shared with sd_emmc_c. This requires muxing the signal of that clock between the sd_emmc_c controller and the NAND controller. The "amlogic,mmc-syscon" property exists for this purpose. Older SoCs (Meson8, Meson8b, Meson8m2 and GXBB) have a dedicated "NAND device clock". Thus we don't need to "amlogic,mmc-syscon" property for muxing the clock on these older SoCs. The clock implementation itself is also more advanced on newer SoCs because the phase of the RX and TX clock can be controlled. Older SoCs cannot change the phase of the "NAND device clock". Thus the "rx" and "tx" clock-names are only required for the GXL, GXM and AXG SoCs. Signed-off-by: Martin Blumenstingl --- .../devicetree/bindings/mtd/amlogic,meson-nand.txt | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt b/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt index 3983c11e062c..8766d4e82a74 100644 --- a/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt +++ b/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt @@ -5,6 +5,9 @@ the MTD NAND bindings. Required properties: - compatible : contains one of: + - "amlogic,meson8-nfc" + - "amlogic,meson8b-nfc" + - "amlogic,meson-gxbb-nfc" - "amlogic,meson-gxl-nfc" - "amlogic,meson-axg-nfc" - clocks : @@ -13,12 +16,13 @@ Required properties: - clock-names: Should contain the following: "core" - NFC module gate clock - "device" - device clock from eMMC sub clock controller - "rx" - rx clock phase - "tx" - tx clock phase + "device" - NAND device clock + "rx" - rx clock phase, only used on the GXL, GXM and AXG SoCs. + "tx" - tx clock phase, only used on the GXL, GXM and AXG SoCs. -- amlogic,mmc-syscon : Required for NAND clocks, it's shared with SD/eMMC - controller port C +- amlogic,mmc-syscon : Only used on the GXL, GXM and AXG SoCs. + Required for NAND clocks, it's shared with SD/eMMC + controller port C Optional children nodes: Children nodes represent the available nand chips. -- 2.21.0