From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Naga Sureshkumar Relli <nagasure@xilinx.com>
Cc: "miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"richard@nod.at" <richard@nod.at>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"kyungmin.park@samsung.com" <kyungmin.park@samsung.com>,
"absahu@codeaurora.org" <absahu@codeaurora.org>,
"peterpandong@micron.com" <peterpandong@micron.com>,
"frieder.schrempf@exceet.de" <frieder.schrempf@exceet.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michal Simek <michals@xilinx.com>,
"nagasureshkumarrelli@gmail.com" <nagasureshkumarrelli@gmail.com>
Subject: Re: [LINUX PATCH v10 1/2] dt-bindings: mtd: arasan: Add device tree binding documentation
Date: Tue, 21 Aug 2018 07:59:48 +0200 [thread overview]
Message-ID: <20180821075948.28962170@bbrezillon> (raw)
In-Reply-To: <MWHPR02MB2623F315C6D4C9775CDA08D8AF310@MWHPR02MB2623.namprd02.prod.outlook.com>
On Tue, 21 Aug 2018 05:47:18 +0000
Naga Sureshkumar Relli <nagasure@xilinx.com> wrote:
> > > +Required properties:
> > > +- compatible: Should be "xlnx,zynqmp-nand" or "arasan,nfc-v3p10"
> >
> > In your example it's not an "or" since both are defined.
> In our previous discussion (https://lore.kernel.org/patchwork/patch/748901/)
> We decided to have compatible strings like " compatible = "<soc-vendor>,<ip-revision>", "arasan,<ip-revision>";"
> So it should be either of these.
> so I will write something like below
> "Possible values are "xlnx,zynqmp-nand"
> "arasan,nfc-v3p10"
> And in example I will mention any one compatible.
> Is it ok?
Hm, why do you need arasan,nfc-v3p10 at all if it's supposed to be
overloaded by a soc specific compat?
> > > +
> > > +Optional properties:
> > > +- arasan,has-mdma: Enables DMA support
> >
> > Can't you detect that based on the compatible (or thanks to a register). If it's something you
> > choose when configuring the IP and can't detect at runtime I guess it's fine.
> There is no way to select DMA when configuring the IP.
> But it has internal DMA and there is a register to select PIO or DMA while starting a transfer.
> So if user really don't want DMA, then we will never set DMA in the code based on DT property.
If it's a purely SW choice, then is shouldn't be described in the DT.
You can use a module param, but I'm not even sure why one would want to
disable DMA.
next prev parent reply other threads:[~2018-08-21 5:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 13:19 [LINUX PATCH v10 0/2] Add support for Arasan NAND Flash controller Naga Sureshkumar Relli
2018-08-17 13:19 ` [LINUX PATCH v10 1/2] dt-bindings: mtd: arasan: Add device tree binding documentation Naga Sureshkumar Relli
2018-08-20 12:33 ` Boris Brezillon
2018-08-21 5:47 ` Naga Sureshkumar Relli
2018-08-21 5:59 ` Boris Brezillon [this message]
2018-08-21 9:22 ` Naga Sureshkumar Relli
2018-08-21 9:52 ` Miquel Raynal
2018-08-21 10:44 ` Naga Sureshkumar Relli
2018-08-21 10:52 ` Boris Brezillon
2018-08-21 11:10 ` Boris Brezillon
2018-08-17 13:19 ` [LINUX PATCH v10 2/2] mtd: rawnand: arasan: Add support for Arasan NAND Flash Controller Naga Sureshkumar Relli
2018-08-17 14:37 ` Miquel Raynal
2018-08-18 4:48 ` Naga Sureshkumar Relli
2018-08-17 15:30 ` kbuild test robot
2018-08-17 17:59 ` Boris Brezillon
2018-08-18 5:49 ` Naga Sureshkumar Relli
2018-08-20 8:53 ` Boris Brezillon
2018-08-20 10:49 ` Naga Sureshkumar Relli
2018-08-20 12:10 ` Boris Brezillon
2018-08-20 12:21 ` Naga Sureshkumar Relli
2018-08-20 12:24 ` Boris Brezillon
2018-08-20 16:40 ` Boris Brezillon
2018-08-21 6:40 ` Naga Sureshkumar Relli
2018-08-21 7:31 ` Miquel Raynal
2018-09-11 5:23 ` Naga Sureshkumar Relli
2018-09-22 7:53 ` Miquel Raynal
2018-09-22 8:13 ` Boris Brezillon
2018-09-24 8:42 ` Naga Sureshkumar Relli
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=20180821075948.28962170@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=absahu@codeaurora.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=frieder.schrempf@exceet.de \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=michals@xilinx.com \
--cc=miquel.raynal@bootlin.com \
--cc=nagasure@xilinx.com \
--cc=nagasureshkumarrelli@gmail.com \
--cc=peterpandong@micron.com \
--cc=richard@nod.at \
/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).