devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Dinh Nguyen <dinguyen@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	<devicetree@vger.kernel.org>
Subject: [BUG] build error due to AGILEX_NAND_X_CLK
Date: Wed, 19 Aug 2020 11:22:51 +0800	[thread overview]
Message-ID: <1597807371.5429.28.camel@mhfsdcap03> (raw)

Hi Dinh,

   There is build error for arm64:
arch/arm64/boot/dts/intel/socfpga_agilex.dtsi:313.15-16 syntax error
FATAL ERROR: Unable to parse input tree

it's introduced by patch:

commit d4ae4dd346cd49302d157b129ead2f60d3a82534
Author: Dinh Nguyen <dinguyen@kernel.org>
Date:   Tue Jun 30 13:44:37 2020 -0500

    arm64: dts: agilex: add nand clocks

    Add the clock properties for the NAND dts node.

    Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>

diff --git a/arch/arm64/boot/dts/intel/socfpga_agilex.dtsi
b/arch/arm64/boot/dts/intel/socfpga_agilex.dtsi
index e300330..ac1b242 100644
--- a/arch/arm64/boot/dts/intel/socfpga_agilex.dtsi
+++ b/arch/arm64/boot/dts/intel/socfpga_agilex.dtsi
@@ -309,6 +309,10 @@
                              <0xffb80000 0x1000>;
                        reg-names = "nand_data", "denali_reg";
                        interrupts = <0 97 4>;
+                       clocks = <&clkmgr AGILEX_NAND_CLK>,
+                                <&clkmgr AGILEX_NAND_X_CLK>,
+                                <&clkmgr AGILEX_NAND_ECC_CLK>;
+                       clock-names = "nand", "nand_x", "ecc";
                        resets = <&rst NAND_RESET>, <&rst
NAND_OCP_RESET>;
                        status = "disabled";
                };


             reply	other threads:[~2020-08-19  3:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19  3:22 Chunfeng Yun [this message]
2020-08-19 16:30 ` [BUG] build error due to AGILEX_NAND_X_CLK Dinh Nguyen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1597807371.5429.28.camel@mhfsdcap03 \
    --to=chunfeng.yun@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mediatek@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).