From: Kathiravan T <kathirav@codeaurora.org>
To: agross@kernel.org, miquel.raynal@bootlin.com, richard@nod.at,
vigneshr@ti.com, robh+dt@kernel.org, sivaprak@codeaurora.org,
peter.ujfalusi@ti.com, boris.brezillon@collabora.com,
linux-arm-msm@vger.kernel.org, linux-mtd@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kathirav@codeaurora.org
Subject: [PATCH 0/3] Add QPIC NAND support for IPQ6018
Date: Tue, 13 Oct 2020 10:45:21 +0530 [thread overview]
Message-ID: <1602566124-13456-1-git-send-email-kathirav@codeaurora.org> (raw)
IPQ6018 has the QPIC NAND controller of version 1.5.0, which
uses the BAM DMA. Add support for the QPIC BAM, QPIC NAND and
enable the same in the board DTS file.
Kathiravan T (3):
dt-bindings: qcom_nandc: IPQ6018 QPIC NAND documentation
mtd: rawnand: qcom: Support for IPQ6018 QPIC NAND controller
arm64: dts: ipq6018: Add the QPIC peripheral nodes
.../devicetree/bindings/mtd/qcom_nandc.txt | 2 +
arch/arm64/boot/dts/qcom/ipq6018-cp01-c1.dts | 16 ++++++++
arch/arm64/boot/dts/qcom/ipq6018.dtsi | 41 +++++++++++++++++++
drivers/mtd/nand/raw/qcom_nandc.c | 4 ++
4 files changed, 63 insertions(+)
base-commit: bbf5c979011a099af5dc76498918ed7df445635b
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2020-10-13 5:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 5:15 Kathiravan T [this message]
2020-10-13 5:15 ` [PATCH 1/3] dt-bindings: qcom_nandc: IPQ6018 QPIC NAND documentation Kathiravan T
2020-10-13 17:23 ` Rob Herring
2020-10-30 17:27 ` Miquel Raynal
2020-10-13 5:15 ` [PATCH 2/3] mtd: rawnand: qcom: Support for IPQ6018 QPIC NAND controller Kathiravan T
2020-10-30 17:27 ` Miquel Raynal
2020-10-13 5:15 ` [PATCH 3/3] arm64: dts: ipq6018: Add the QPIC peripheral nodes Kathiravan T
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=1602566124-13456-1-git-send-email-kathirav@codeaurora.org \
--to=kathirav@codeaurora.org \
--cc=agross@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=peter.ujfalusi@ti.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=sivaprak@codeaurora.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;
as well as URLs for NNTP newsgroup(s).