From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Ian Campbell <ian.campbell@citrix.com>,
Pawel Moll <pawel.moll@arm.com>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Rob Herring <rob.herring@calxeda.com>,
linux-mtd@lists.infradead.org,
Grant Likely <grant.likely@linaro.org>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v4 1/4] mtd: nand: gpio: Add DT property to automatically determine bus width
Date: Mon, 19 Aug 2013 15:09:55 -0600 [thread overview]
Message-ID: <521289A3.5040705@wwwdotorg.org> (raw)
In-Reply-To: <1376637583-12485-1-git-send-email-shc_work@mail.ru>
On 08/16/2013 01:19 AM, Alexander Shiyan wrote:
> This patch adds a property to automatically determine the NAND
> bus width. This property works if the bus width is not specified
> explicitly.
> diff --git a/Documentation/devicetree/bindings/mtd/gpio-control-nand.txt b/Documentation/devicetree/bindings/mtd/gpio-control-nand.txt
> +- gpio-control-nand,bank-width-auto : Device bus width is determined
> + automatically if "bank-width" is omitted (Boolean).
How would a driver determine the bank width automatically; is there some
obvious way a driver should do this based on the/a NAND specification?
Is there more than one way this auto-detection could occur, and if so,
which of those methods is this property indicating will work?
I'd rather expect the property description include details of the
auto-detection mechanism that the DT states will work.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Brian Norris <computersforpeace@gmail.com>,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ian.campbell@citrix.com>,
Grant Likely <grant.likely@linaro.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/4] mtd: nand: gpio: Add DT property to automatically determine bus width
Date: Mon, 19 Aug 2013 15:09:55 -0600 [thread overview]
Message-ID: <521289A3.5040705@wwwdotorg.org> (raw)
In-Reply-To: <1376637583-12485-1-git-send-email-shc_work@mail.ru>
On 08/16/2013 01:19 AM, Alexander Shiyan wrote:
> This patch adds a property to automatically determine the NAND
> bus width. This property works if the bus width is not specified
> explicitly.
> diff --git a/Documentation/devicetree/bindings/mtd/gpio-control-nand.txt b/Documentation/devicetree/bindings/mtd/gpio-control-nand.txt
> +- gpio-control-nand,bank-width-auto : Device bus width is determined
> + automatically if "bank-width" is omitted (Boolean).
How would a driver determine the bank width automatically; is there some
obvious way a driver should do this based on the/a NAND specification?
Is there more than one way this auto-detection could occur, and if so,
which of those methods is this property indicating will work?
I'd rather expect the property description include details of the
auto-detection mechanism that the DT states will work.
next prev parent reply other threads:[~2013-08-19 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 7:19 [PATCH v4 1/4] mtd: nand: gpio: Add DT property to automatically determine bus width Alexander Shiyan
2013-08-16 7:19 ` [PATCH v4 4/4] mtd: nand: gpio: Add support for multichip devices Alexander Shiyan
2013-08-19 21:11 ` Stephen Warren
2013-08-19 21:11 ` Stephen Warren
2013-08-17 21:14 ` [PATCH v4 1/4] mtd: nand: gpio: Add DT property to automatically determine bus width Brian Norris
2013-08-17 21:14 ` Brian Norris
2013-08-17 21:27 ` Alexander Shiyan
2013-08-19 21:09 ` Stephen Warren [this message]
2013-08-19 21:09 ` Stephen Warren
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=521289A3.5040705@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=artem.bityutskiy@linux.intel.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=shc_work@mail.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.