Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp4591855imm; Mon, 25 Jun 2018 19:40:42 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLqqP97QEkGnxhw+A3AKHqrhD77/8uqwvi9Fu53Pza1tWSJCrzGoFlDm7atMM1MgKbaVDle X-Received: by 2002:a17:902:7688:: with SMTP id m8-v6mr14660996pll.54.1529980842406; Mon, 25 Jun 2018 19:40:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529980842; cv=none; d=google.com; s=arc-20160816; b=V62XpnwVi80+hLHQZfbNm8nPaCisayX9nf5MwmD0D/uAFFcJXlzQFFVu+/KX8u/8XK ijVoEe9boTsOzmnJSr8+WKitR3NBJ+9rjGx69ko8Kx5oSHVQkrQRLNGo+FTBZo6IhXSB jJXC62T5mQySu79ZsO9JPPgbALpYg5xTjtv4n5ki/1m9NZwAhjNRFidRQ9E2yJn79ilL rTAvQoEOA2NOFEItYQboEDNx1I43e6/fEXS/uiNAqKUNIqx8rSm9fESSJJFzlf7Ztui2 X14KZ8ubGXVk/euPaw35VfP3AKdtfTcI4wG1UyG+Q/r8ITR1AQW0G5C/1mysu/Gzaszz u9TQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature:dkim-filter :arc-authentication-results; bh=+3SThStuenbMYTdh+CVRdC5wXFzQKsVaZcH56ZF2jRw=; b=XGUlykywXBJR7LVhyH0fkXP/LHO22gYQBdZm5wazJvfHxf8suqtg0LDyW1cAeA5xbw RUKabpWOVjfF5yQ8BXsKiJEZCxa5wpcLGrL/TSDMQIdqkm8+WNJ9SH3b5cnki+uRcjl7 t5tOUBAvTYAHRCSzWkzmXfBlAWodtn3e7AvLvFYjaRrf+SioaqiBmkfpepoxGhflM3oF mulfWXfPHWJ2oyxJKRKWKzsb3DSZ1veB7LH03mj4IwPgunUUdmHQZ9ANkaGKkJE/TbpS D1fxp27O7xtIyAdpS6ddN7+hqRYMhhSaDpczo16qgZJaXlOztLrGGjI9OSEzGlZkwHIs M2jg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=U7Q9LIaw; 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 j85-v6si623048pfa.232.2018.06.25.19.40.28; Mon, 25 Jun 2018 19:40:42 -0700 (PDT) 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=@nifty.com header.s=dec2015msa header.b=U7Q9LIaw; 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 S965330AbeFZCjN (ORCPT + 99 others); Mon, 25 Jun 2018 22:39:13 -0400 Received: from conssluserg-06.nifty.com ([210.131.2.91]:36704 "EHLO conssluserg-06.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965281AbeFZCjJ (ORCPT ); Mon, 25 Jun 2018 22:39:09 -0400 Received: from mail-ua0-f182.google.com (mail-ua0-f182.google.com [209.85.217.182]) (authenticated) by conssluserg-06.nifty.com with ESMTP id w5Q2d2p0017638; Tue, 26 Jun 2018 11:39:03 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-06.nifty.com w5Q2d2p0017638 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1529980743; bh=+3SThStuenbMYTdh+CVRdC5wXFzQKsVaZcH56ZF2jRw=; h=In-Reply-To:References:From:Date:Subject:To:Cc:From; b=U7Q9LIawFapIxx6NbHMWftTprer4BZtQB3ynSniLO1KhJ0iZCGFhDI8dv88BMOwgo /56MktB0usMFGmBHKagC6XA8ne1iemOa2XA425rpOAEBb+7RUTEnTBjYuO6Nzq617T zMhwdnnXiS05BcgYyDfXNr9ciqKN/y6MrIQ3jSSJ9vwQomrQKeucUzYYMYXDol2gW0 i2e24NPLLKxtUWJKj/rVY1uTaChsXc5OwIbyIVljOZibqTfF5uPLmcgppKXuDCYA8R keUmZBDL8WAEmYF9qxxzxopPelM50PQnH5Ot/KDnY2D0rVhnjxkLHuvrvMdWc1JK4h q9V2GsRGLGbUA== X-Nifty-SrcIP: [209.85.217.182] Received: by mail-ua0-f182.google.com with SMTP id a5-v6so9957980uao.8; Mon, 25 Jun 2018 19:39:02 -0700 (PDT) X-Gm-Message-State: APt69E0g4/Z1j/bH3ZkzBNExV2WCHG/ThlmDq7tVy4/kcrzSH7M1u9AE ga4RwyqpHUEd3e5kL5tTVUgS9emX5h2yk+mmO+Y= X-Received: by 2002:ab0:13c8:: with SMTP id n8-v6mr9402189uae.140.1529980741685; Mon, 25 Jun 2018 19:39:01 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ab0:3308:0:0:0:0:0 with HTTP; Mon, 25 Jun 2018 19:38:21 -0700 (PDT) In-Reply-To: <20180625165506.484e025f@bbrezillon> References: <20180619120719.26921-1-richard@nod.at> <3320422.EJ8D6C0VHL@blindfold> <20180625165506.484e025f@bbrezillon> From: Masahiro Yamada Date: Tue, 26 Jun 2018 11:38:21 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] arm: dts: socfpga: denali needs nand_x_clk too To: Boris Brezillon Cc: Dinh Nguyen , Richard Weinberger , DTML , Linux Kernel Mailing List , linux-mtd , Rob Herring , Mark Rutland , =?UTF-8?B?TWFyZWsgVmHFoXV0?= , Brian Norris , David Woodhouse , Miquel Raynal Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2018-06-25 23:55 GMT+09:00 Boris Brezillon : > On Mon, 25 Jun 2018 09:50:18 -0500 > Dinh Nguyen wrote: > >> On 06/22/2018 10:58 AM, Richard Weinberger wrote: >> > Masahiro, >> > >> > Am Freitag, 22. Juni 2018, 16:37:21 CEST schrieb Masahiro Yamada: >> >> Hi Richard, >> >> >> >> >> >> 2018-06-19 21:07 GMT+09:00 Richard Weinberger : >> >>> The denali NAND flash controller needs at least two clocks to operate, >> >>> nand_clk and nand_x_clk. >> >>> Since 1bb88666775e ("mtd: nand: denali: handle timing parameters by >> >>> setup_data_interface()") nand_x_clk is used to derive timing settings. >> >>> >> >>> Signed-off-by: Richard Weinberger >> >>> --- >> >>> Strictly speaking denali needs a ecc_clk too, but AFAIK such a clock >> >>> is not present on this SoC. >> >>> But my SoCFPGA knowledge is very limited. >> >>> >> >>> Thanks, >> >>> //richard >> >>> --- >> >>> arch/arm/boot/dts/socfpga.dtsi | 3 ++- >> >>> 1 file changed, 2 insertions(+), 1 deletion(-) >> >>> >> >>> diff --git a/arch/arm/boot/dts/socfpga.dtsi b/arch/arm/boot/dts/socfpga.dtsi >> >>> index 486d4e7433ed..562f7b375bbd 100644 >> >>> --- a/arch/arm/boot/dts/socfpga.dtsi >> >>> +++ b/arch/arm/boot/dts/socfpga.dtsi >> >>> @@ -754,7 +754,8 @@ >> >>> reg-names = "nand_data", "denali_reg"; >> >>> interrupts = <0x0 0x90 0x4>; >> >>> dma-mask = <0xffffffff>; >> >>> - clocks = <&nand_clk>; >> >>> + clocks = <&nand_clk>, <&nand_x_clk>; >> >>> + clock-names = "nand", "nand_x"; >> >> >> >> >> >> IMHO, this should be >> >> >> >> clocks = <&nand_clk>, <&nand_x_clk>, <&nand_x_clk>; >> >> clock-names = "nand", "nand_x", "ecc"; >> >> No, it should be just the nand_x and ecc. >> >> There's already a patch to use the nand_x_clk and not the nand_clk. Different people try to fix the problem in different ways. I think it is due to miscommunication across sub-systems. >> >> https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git/commit/?h=socfpga_for_next_v4.19_fixes_v1&id=1709ab58eb79b19bceb2287d111bf1bd2df1cf6d This does not break your board. However, it is not helpful any more. I already fix the Denali driver to use the hard-coded clock frequency if the old binding is used. BTW, Marek issued Reviewed-by to this patch. > Hm, are you sure this is accurate? I might be wrong but I find it weird > that the denali NAND controller IP has been adapted by Xilinx to only Xilinx? Do you mean Altera (Intel)? > take one clk. Isn't that the same clk is feeding all clk inputs of the > denali block? -- Best Regards Masahiro Yamada