From patchwork Fri Jun 24 13:12:50 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Liang Yang X-Patchwork-Id: 12894484 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 3DA8BC43334 for ; Fri, 24 Jun 2022 13:14:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-ID:Date:Subject:CC :To:From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=apTxNIu1KrEbOGgUD3nPQz/duVnmlQxE84lFWrJ8A4I=; b=LRJTH7WtOBo7FR k529DRam9TNYAPLcYcqqZVNWM4rMyCipZtzJpERMbtNidfrlSKXCy4P20zigdijMp2ugJUanZthv0 AEGE4U2Ew9EWZ3big6J/7XQ0Xmh/doBILRFu33+jsrAVqw8r9hOKomExZEYUShFkv+ocW5vtXcGvv myYOYREA9/sfc7rRrG6JtOMT65OVIxiBsWpA20HMHbkhncDaKIkYA0GJjiiRp4iFVxp1FX9iRSmk3 Q4Mcew4djtoLt7qRyb7hPWwxMREDz54jU5NgRHcgf1I2YAwcigiEmlu5rrHOBJow+ZsVvNZPsFl4U N8/ArsmvJLRk+jOl3Kvw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1o4j7e-002Jh4-DW; Fri, 24 Jun 2022 13:13:18 +0000 Received: from mail-sz.amlogic.com ([211.162.65.117]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1o4j7X-002Je6-Gm; Fri, 24 Jun 2022 13:13:15 +0000 Received: from droid11-sz.amlogic.com (10.28.8.21) by mail-sz.amlogic.com (10.28.11.5) with Microsoft SMTP Server id 15.1.2176.2; Fri, 24 Jun 2022 21:13:00 +0800 From: Liang Yang To: Miquel Raynal , CC: Liang Yang , Rob Herring , Richard Weinberger , Vignesh Raghavendra , Jerome Brunet , Neil Armstrong , Martin Blumenstingl , Kevin Hilman , Jianxin Pan , Victor Wan , XianWei Zhao , Kelvin Zhang , BiChao Zheng , YongHui Yu , , , , Subject: [PATCH v7 0/5] fix the meson NFC clock Date: Fri, 24 Jun 2022 21:12:50 +0800 Message-ID: <20220624131257.29906-1-liang.yang@amlogic.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 X-Originating-IP: [10.28.8.21] X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220624_061311_599016_B6F273E1 X-CRM114-Status: GOOD ( 10.57 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org EMMC and NAND have the same clock control register named 'SD_EMMC_CLOCK' which is defined in EMMC port internally. bit0~5 of 'SD_EMMC_CLOCK' is the divider and bit6~7 is the mux for fix pll and xtal. At the beginning, a common MMC and NAND sub-clock was discussed and planed to be implemented as NFC clock provider, but now this series of patches of a common MMC and NAND sub-clock are never being accepted and the current binding was never valid. the reasons are: 1. EMMC and NAND, which are mutually exclusive anyway 2. coupling the EMMC and NAND. 3. it seems that a common MMC and NAND sub-clock is over engineered. and let us see the link for more information: https://lore.kernel.org/all/20220121074508.42168-5-liang.yang@amlogic.com so The meson nfc can't work now, let us rework the clock. Changes since v6 [7] - use COMMON_CLK instead of !HAVE_LEGACY_CLK Changes since v5 [6] - add change log for patch 3/5 - add patch 5/5 to fix the reporting error of test robot Changes since v4 [5] - split the dt binding patch into two patches, one for fixing, clock, the other for coverting to yaml - split the nfc driver patch into two patches, one for fixing clock, the other for refining the get nfc resource. Changes since v3 [4] - use devm_platform_ioremap_resource_byname - dt_binding_check for mtd/amlogic,meson-nand.yaml Changes since v2 [3] - use fw_name from dts, instead the wrong way using __clk_get_name - reg resource size change to 0x800 - use reg-names Changes since v1 [2] - use clk_parent_data instead of parent_names - define a reg resource instead of sd_emmc_c_clkc [1] https://lore.kernel.org/r/20220106033130.37623-1-liang.yang@amlogic.com https://lore.kernel.org/r/20220106032504.23310-1-liang.yang@amlogic.com [2] https://lore.kernel.org/all/20220217063346.21691-1-liang.yang@amlogic.com [3] https://lore.kernel.org/all/20220318124121.26117-1-liang.yang@amlogic.com [4] https://lore.kernel.org/all/20220402074921.13316-1-liang.yang@amlogic.com/ [5] https://lore.kernel.org/all/20220513123404.48513-1-liang.yang@amlogic.com/ [6] https://lore.kernel.org/all/20220607064731.13367-1-liang.yang@amlogic.com/ Liang Yang (5): dt-bindings: nand: meson: fix meson nfc clock mtd: rawnand: meson: fix the clock mtd: rawnand: meson: refine resource getting in probe dt-bindings: nand: meson: convert txt to yaml mtd: rawnand: meson: not support legacy clock .../bindings/mtd/amlogic,meson-nand.txt | 60 ------------- .../bindings/mtd/amlogic,meson-nand.yaml | 88 +++++++++++++++++++ drivers/mtd/nand/raw/Kconfig | 2 +- drivers/mtd/nand/raw/meson_nand.c | 86 +++++++++--------- 4 files changed, 131 insertions(+), 105 deletions(-) delete mode 100644 Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt create mode 100644 Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml