Received: by 2002:a05:6602:18e:0:0:0:0 with SMTP id m14csp816950ioo; Thu, 26 May 2022 15:57:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyLgPLZqPh7Uc5LHeF1I+Fw/HIvZ4s5t4NMdCAgxR0KVwvtHsTKqtuZBemJOIO4lN0uMIp2 X-Received: by 2002:a17:907:7b8f:b0:6fe:fcae:615a with SMTP id ne15-20020a1709077b8f00b006fefcae615amr17143200ejc.658.1653605843321; Thu, 26 May 2022 15:57:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1653605843; cv=none; d=google.com; s=arc-20160816; b=BnmIGpCkTsFNuHa7qZtlboSGq+CapMXtRe1PdurIpG+IYH8OEy0EDcvIGKGLMJ39hb DbBoBRfvZPvwOoZvc1Io47kKwJfUBl9Zfcr1CmQZ68rh/QNArhDoArqQ6GcQbPKUD6gl Yt95wbWv3i5D1u2+P1+T4TyhDKFHrXCCWKgRCNdqsdJsA8Yi2dgC5t+7hNeTiVW45P4E 705ueO+QY+wpuYPWhzbaZso/GmizqtL4jwjdvw01YBz+2Hyok1p9+5R2Ys2P2bAkBA+1 TsqWFy8mgzd0RTEhCXlwIctZXYS6c+HlV+2sNcU6jaA/OGkT6pjk5uTUpvqBMjj48h1N UFOA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=ZV2y77FSAdklT7BKF+Tws43T4buN/hfHfm1U5B1OUTY=; b=lGyVgbuRe454XruhLotAh6RjglNUYid9zgZVzHrSMJoqTkO4236vy71LeGkNTuhcHT k78MtIDbGgeIXXq7GoFNKNEav4BTfefC7cc4iHLRe1BOtJ7srM7gs31R7LM78L2K4ULV f7Dl97J9uycRZ8FLxflfWXCX2Z3HJUGjua+WJCdIhgpzWs/WBZZI7eWnrNjg8eYRKbSJ o/N7V/SNh66ulR1wJ0/ctWnL+QVSBMObX4loXnnjW1A0vrKpU9PZmKdhgNToQFq8en9x Ezo5mE2gOTee2YIdZmsY3Lt1xTGEHPah36pGEDp5swx9tI0Lb17LrdV62wR8adK+6q06 lY0A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=2l+TLfCq; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id i18-20020a1709064fd200b006ff040f9138si2976927ejw.586.2022.05.26.15.56.57; Thu, 26 May 2022 15:57:23 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=2l+TLfCq; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346695AbiEZQ2z (ORCPT + 99 others); Thu, 26 May 2022 12:28:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54920 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229780AbiEZQ2w (ORCPT ); Thu, 26 May 2022 12:28:52 -0400 Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E494C7B9FF for ; Thu, 26 May 2022 09:28:50 -0700 (PDT) Received: by mail-pg1-x52f.google.com with SMTP id 137so1719888pgb.5 for ; Thu, 26 May 2022 09:28:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=ZV2y77FSAdklT7BKF+Tws43T4buN/hfHfm1U5B1OUTY=; b=2l+TLfCq3eeZ8fnL4KvNPyIePz/kfWJ3xDqUw9rjbwjbepocHIx4xOokRfKmQZXcjq sB5yKd3QPZI5WpbmUONnogFtTwkfTufAtkNQonFhta858pKIj2mrLBfwaThv1XLZ5qUw HKIfY772DkudNhL4y/3qsv/BKNLOeELnYiOseGovKA4UxOyeMFRh4NyVQGIC8uqaGZim 9DhOn5r6/7Sk/fsjJsyGjQPLb6Cq8vkxTNiyMwYleEyaUXMu9ZHZuHnsnYj9aY4063pL anmx7dkc0QrcCB3o/tKUCMuIy3+/gM0QRdQoNMrZ6w6nZ8SVa+ajkscjDC/GqA7XbnmK m6rg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=ZV2y77FSAdklT7BKF+Tws43T4buN/hfHfm1U5B1OUTY=; b=Fpv8ZKh8VUrAMgBiHveCgyzsIhWSmq8Okwf9QMY7egsGaLTWcyEXYfsBIjurZAa9xb AmYFHi1Qk4RuHDfdM65dL5JtUzBqoR354kpwD/lXH3fhKN/zOVQbqRO4DoMWjfq+mcJR rWvw6WifTJT6u3ISgDtnu9+NhLkXau4FJmsw4lWAe2vIpjJDZKRWFd9GDQraaPqJTyr9 qmMQ1e+n3uBVAkHOWQjnafWUZ0hWBP41zw0/0tX4djpVGpgteqvb/49PJJyP75BsVooW 98GKM2hg5uHOknmzklDEWBb5JL3RSlP8tLgnVIiY96MZzCPwzHJSU1ww1B9WX9wGz2ES dU6g== X-Gm-Message-State: AOAM532csenTrC6+QMAsTvDc20V/tpNZhTRlsXJKHNobtkMBz619nROS haLcVZByXQeVCf9eLZTB3h/ZfA== X-Received: by 2002:a05:6a00:15c2:b0:518:9911:4952 with SMTP id o2-20020a056a0015c200b0051899114952mr22033146pfu.64.1653582530334; Thu, 26 May 2022 09:28:50 -0700 (PDT) Received: from localhost (c-71-197-186-152.hsd1.wa.comcast.net. [71.197.186.152]) by smtp.gmail.com with ESMTPSA id z12-20020aa785cc000000b0050dc762818bsm1714033pfn.101.2022.05.26.09.28.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 26 May 2022 09:28:49 -0700 (PDT) From: Kevin Hilman To: Liang Yang , Miquel Raynal , linux-mtd@lists.infradead.org Cc: Liang Yang , Rob Herring , Richard Weinberger , Vignesh Raghavendra , Jerome Brunet , Neil Armstrong , Martin Blumenstingl , Jianxin Pan , Victor Wan , XianWei Zhao , Kelvin Zhang , BiChao Zheng , YongHui Yu , linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 2/4] mtd: rawnand: meson: fix the clock In-Reply-To: <20220513123404.48513-3-liang.yang@amlogic.com> References: <20220513123404.48513-1-liang.yang@amlogic.com> <20220513123404.48513-3-liang.yang@amlogic.com> Date: Thu, 26 May 2022 09:28:49 -0700 Message-ID: <7hwne88dha.fsf@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Liang, Liang Yang writes: > 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. the reasons for giving up 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 fot 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. > > Signed-off-by: Liang Yang Reviewed-by: Kevin Hilman Thank you for your persistence in working on multiple iterations of this until we came to a final agreement. Kevin