From: niravkumar.l.rabara@intel.com
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>,
nirav.rabara@altera.com, devicetree@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] add clock-names property to nand node
Date: Wed, 12 Feb 2025 19:25:33 +0800 [thread overview]
Message-ID: <20250212112535.2674256-1-niravkumar.l.rabara@intel.com> (raw)
From: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
1) Document the required clock-names property because the driver
requests the clock by name and not the index.
2) Add required clock-names property to the nand node in device tree.
Changes in v3:
* Include missing Fixes tag.
Changes in v2:
* Document clock-names property for Cadence NAND controller.
link to v1:
- https://lore.kernel.org/all/20250107084955.2750154-1-niravkumar.l.rabara@intel.com/
Niravkumar L Rabara (2):
dt-bindings: mtd: cadence: document required clock-names
arm64: dts: socfpga: agilex5: add clock-names property to nand node
Documentation/devicetree/bindings/mtd/cdns,hp-nfc.yaml | 8 +++++++-
arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi | 1 +
2 files changed, 8 insertions(+), 1 deletion(-)
--
2.25.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2025-02-12 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 11:25 niravkumar.l.rabara [this message]
2025-02-12 11:25 ` [PATCH v3 1/2] dt-bindings: mtd: cadence: document required clock-names niravkumar.l.rabara
2025-02-12 11:25 ` [PATCH v3 2/2] arm64: dts: socfpga: agilex5: add clock-names property to nand node niravkumar.l.rabara
2025-02-14 18:25 ` [PATCH v3 0/2] " Miquel Raynal
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=20250212112535.2674256-1-niravkumar.l.rabara@intel.com \
--to=niravkumar.l.rabara@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=nirav.rabara@altera.com \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
/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