From: xuejiancheng <xuejiancheng@huawei.com>
To: Rob Herring <robh@kernel.org>
Cc: pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
dwmw2@infradead.org, computersforpeace@gmail.com,
shijie.huang@intel.com, pengbinquan@huawei.com,
han.xu@freescale.com, ezequiel@vanguardiasur.com.ar,
fabio.estevam@freescale.com, manabian@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, yanhaifeng@hisilicon.com,
yanghongwei@hisilicon.com, suwenping@hisilicon.com,
ml.yang@hisilicon.com, gaofei@hisilicon.com,
zhangzhenxing@hisilicon.com, xuejiancheng@hisilicon.com
Subject: Re: [PATCH v2] mtd: spi-nor: add hisilicon spi-nor flash controller driver
Date: Mon, 11 Jan 2016 09:20:41 +0800 [thread overview]
Message-ID: <56930369.1050000@huawei.com> (raw)
In-Reply-To: <20160109154249.GA28102@rob-hp-laptop>
Hi Rob,
On 2016/1/9 23:42, Rob Herring wrote:
> On Fri, Jan 08, 2016 at 09:26:45AM +0800, Jiancheng Xue wrote:
>> add hisilicon spi-nor flash controller driver
>>
>> Signed-off-by: Binquan Peng <pengbinquan@huawei.com>
>> Signed-off-by: Jiancheng Xue <xuejiancheng@huawei.com>
>> ---
>
> Next time, please include changes in v2 here.
>
OK. I will remember it. Thank you.
In v2, I mainly fixed some compile warnings.
>> .../devicetree/bindings/spi/spi-hisi-sfc.txt | 24 +
>> drivers/mtd/spi-nor/Kconfig | 6 +
>> drivers/mtd/spi-nor/Makefile | 1 +
>> drivers/mtd/spi-nor/hisi-sfc.c | 498 +++++++++++++++++++++
>> 4 files changed, 529 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/spi/spi-hisi-sfc.txt
>> create mode 100644 drivers/mtd/spi-nor/hisi-sfc.c
>>
>> diff --git a/Documentation/devicetree/bindings/spi/spi-hisi-sfc.txt b/Documentation/devicetree/bindings/spi/spi-hisi-sfc.txt
>> new file mode 100644
>> index 0000000..a0d1e04
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/spi/spi-hisi-sfc.txt
>> @@ -0,0 +1,24 @@
>> +HiSilicon SPI-NOR Flash Controller
>> +
>> +Required properties:
>> +- compatible : Should be "hisilicon,hisi-sfc".
>
> I missed this last time, but you also need a more specific compatible
> string with the SOC name in it.
>
This IP block is used in many SOCs. Do I need to add a specific compatible
string for every SOC? Thank you.
>> +- address-cells : number of cells required to define a chip select
>> + address on the SPI bus. Should be set to 1. See spi-bus.txt.
>> +- size-cells : Should be 0.
>> +- reg : Offset and length of the register set for the controller device.
>> +- reg-names : Must include the following two entries: "control", "memory".
>> +- clocks : handle to spi-nor flash controller clock.
>> +
>> +Example:
>> +spi-nor-controller@10000000 {
>> + compatible = "hisilicon,hisi-sfc";
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + reg = <0x10000000 0x1000>, <0x14000000 0x1000000>;
>> + reg-names = "control", "memory";
>> + clocks = <&clock HI3519_FMC_CLK>;
>> + spi-nor@0 {
>> + compatible = "jedec,spi-nor";
>> + reg = <0>;
>> + };
>> +};
>
> .
>
next prev parent reply other threads:[~2016-01-11 1:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 1:26 [PATCH v2] mtd: spi-nor: add hisilicon spi-nor flash controller driver Jiancheng Xue
[not found] ` <1452216405-10826-1-git-send-email-xuejiancheng-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-01-09 15:42 ` Rob Herring
2016-01-11 1:20 ` xuejiancheng [this message]
2016-01-11 3:09 ` Rob Herring
[not found] ` <CAL_Jsq+K-tF=snhq+w9yYQKmAxbxDSLq6cv5fLfWjHTgdJxQWQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-11 3:53 ` xuejiancheng
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=56930369.1050000@huawei.com \
--to=xuejiancheng@huawei.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=fabio.estevam@freescale.com \
--cc=galak@codeaurora.org \
--cc=gaofei@hisilicon.com \
--cc=han.xu@freescale.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=manabian@gmail.com \
--cc=mark.rutland@arm.com \
--cc=ml.yang@hisilicon.com \
--cc=pawel.moll@arm.com \
--cc=pengbinquan@huawei.com \
--cc=robh@kernel.org \
--cc=shijie.huang@intel.com \
--cc=suwenping@hisilicon.com \
--cc=xuejiancheng@hisilicon.com \
--cc=yanghongwei@hisilicon.com \
--cc=yanhaifeng@hisilicon.com \
--cc=zhangzhenxing@hisilicon.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).