From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Bean Huo <beanhuo@outlook.com>
Cc: "dwmw2@infradead.org" <dwmw2@infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"boris.brezillon@free-elections.com"
<boris.brezillon@free-elections.com>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"richard@nod.at" <richard@nod.at>,
"cyrille.pitchen@wedev4u.fr" <cyrille.pitchen@wedev4u.fr>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
beanhuo <beanhuo@micron.com>
Subject: Re: [PATCH v1 1/3] mtd: physmap: add dual die entry in devicetree binding
Date: Thu, 22 Feb 2018 14:05:42 +0100 [thread overview]
Message-ID: <20180222140542.47340842@bbrezillon> (raw)
In-Reply-To: <DM2PR12MB001463BD62775C388AEBFD3FA6CE0@DM2PR12MB0014.namprd12.prod.outlook.com>
On Wed, 21 Feb 2018 19:32:32 +0000
Bean Huo <beanhuo@outlook.com> wrote:
> From: beanhuo <beanhuo@micron.com>
>
> This commit adds the dual die entry in the devicetree binding
> for the daul die stacked parallel NOR.
>
> Signed-off-by: beanhuo <beanhuo@micron.com>
> ---
> Documentation/devicetree/bindings/mtd/mtd-physmap.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
> index 4a0a48b..782bacc 100644
> --- a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
> +++ b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
> @@ -29,6 +29,8 @@ file systems on embedded devices.
> - use-advanced-sector-protection: boolean to enable support for the
> advanced sector protection (Spansion: PPB - Persistent Protection
> Bits) locking.
> + - dual-die-stack: boolean to enable support for the devices with the
> + two dies in stack.
How about making that more future proof and adding a property that
directly contains the number of dies (num-dies)?
>
> For JEDEC compatible devices, the following additional properties
> are defined:
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-02-22 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1519241514-6466-1-git-send-email-beanhuo@outlook.com>
2018-02-21 19:32 ` [PATCH v1 1/3] mtd: physmap: add dual die entry in devicetree binding Bean Huo
2018-02-22 13:05 ` Boris Brezillon [this message]
2018-02-23 11:07 ` Bean Huo
2018-02-23 15:53 ` Boris Brezillon
2018-02-21 19:32 ` [PATCH v1 2/3] mtd: probe: probe dual die entry from " Bean Huo
2018-02-22 13:02 ` Boris Brezillon
2018-02-23 11:14 ` Bean Huo
2018-02-21 19:32 ` [PATCH v1 3/3] drivers: mtd: chips: add support for the dual die stacked PNOR Bean Huo
2018-02-22 13:33 ` Boris Brezillon
2018-02-23 11:43 ` Bean Huo
2018-02-23 15:49 ` Boris Brezillon
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=20180222140542.47340842@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=beanhuo@micron.com \
--cc=beanhuo@outlook.com \
--cc=boris.brezillon@free-elections.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.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