From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/3] doc: dt: add documentation for Mediatek spi-nor controller
Date: Thu, 15 Oct 2015 18:19:47 -0700 [thread overview]
Message-ID: <20151016011947.GA28158@localhost> (raw)
In-Reply-To: <1444729160-26433-2-git-send-email-bayi.cheng@mediatek.com>
Hi Bayi,
On Tue, Oct 13, 2015 at 05:39:18PM +0800, Bayi Cheng wrote:
> Add device tree binding documentation for serial flash with
> Mediatek serial flash controller
>
> Signed-off-by: Bayi Cheng <bayi.cheng@mediatek.com>
> ---
> .../devicetree/bindings/mtd/mtk-quadspi.txt | 30 ++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mtd/mtk-quadspi.txt
>
> diff --git a/Documentation/devicetree/bindings/mtd/mtk-quadspi.txt b/Documentation/devicetree/bindings/mtd/mtk-quadspi.txt
> new file mode 100644
> index 0000000..8fff0ed
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mtd/mtk-quadspi.txt
> @@ -0,0 +1,30 @@
> +* MTD SPI nor driver for MTK MT81xx (and similar) serial flash controller
> +
> +Required properties:
> +- compatible: should be "mediatek,mt8173-nor";
> +- reg: physical base address and length of the controller's register
> +- clocks: the phandle of the clock needed by the nor controller
> +- clock-names: the name of the clocks
> + the clocks needed "spi" and "sf". "spi" is used for spi bus,
> + and "sf" is used for controller, these are the clocks witch
> + hardware needs to enabling nor flash and nor flash controller.
> + See Documentation/devicetree/bindings/clock/clock-bindings.txt for details.
> +- #address-cells: should be <1>
> +- #size-cells: should be <0>
> +
> +Example:
> +
> +nor_flash: spi at 1100d000 {
> + compatible = "mediatek,mt8173-nor";
> + reg = <0 0x1100d000 0 0xe0>;
> + clocks = <&pericfg CLK_PERI_SPI>,
> + <&topckgen CLK_TOP_SPINFI_IFR_SEL>;
> + clock-names = "spi", "sf";
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + flash at 0 {
I see you've added the 'flash' node as I requested, but you didn't
document it above, and your driver doesn't use it.
Brian
> + ....
> + };
> +};
> +
> --
> 1.8.1.1.dirty
>
next prev parent reply other threads:[~2015-10-16 1:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 9:39 [PATCH v4 0/3] Mediatek SPI-NOR flash driver Bayi Cheng
2015-10-13 9:39 ` [PATCH v4 1/3] doc: dt: add documentation for Mediatek spi-nor controller Bayi Cheng
2015-10-16 1:19 ` Brian Norris [this message]
2015-10-13 9:39 ` [PATCH v4 2/3] mtd: mtk-nor: mtk serial flash controller driver Bayi Cheng
2015-10-13 12:44 ` kbuild test robot
2015-10-16 7:39 ` Brian Norris
2015-10-18 14:20 ` bayi.cheng
2015-10-29 1:52 ` Brian Norris
2015-10-29 3:28 ` bayi.cheng
2015-10-29 13:56 ` bayi.cheng
2015-10-29 16:03 ` Brian Norris
2015-10-30 2:12 ` bayi.cheng
2015-10-30 5:02 ` Brian Norris
2015-10-13 9:39 ` [PATCH v4 3/3] arm64: dts: mt8173: Add nor flash node Bayi Cheng
2015-10-13 14:33 ` Sergei Shtylyov
2015-10-14 1:07 ` Daniel Kurtz
2015-10-14 11:05 ` Sergei Shtylyov
2015-10-14 11:26 ` Daniel Kurtz
2015-10-14 13:59 ` bayi.cheng
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=20151016011947.GA28158@localhost \
--to=computersforpeace@gmail.com \
--cc=linux-arm-kernel@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).