From: Kamal Dasu <kdasu.kdev@gmail.com>
To: linux-spi@vger.kernel.org, cyrille.pitchen@atmel.com,
marex@denx.de, broonie@kernel.org
Cc: bcm-kernel-feedback-list@broadcom.com, f.fainelli@gmail.com,
linux-mtd@lists.infradead.org, Kamal Dasu <kdasu.kdev@gmail.com>
Subject: [PATCH v5 0/2] Added support for spi-nor device pm in m25p80
Date: Wed, 22 Feb 2017 14:19:31 -0500 [thread overview]
Message-ID: <1487791173-22159-1-git-send-email-kdasu.kdev@gmail.com> (raw)
Changes since v4 based on review comments:
spi-nor.c
- Added comments to make it clear that spi_nor_init() sends all spi-nor
flash configuration commands based on nor stucture settings for read
in the refactored code
m25p80.c:
- fix typos
- Updated description
The V4 changes below implements power management support in m25p80 driver.
m25p80 pm resume() calls newly a implemented spi_nor_init() function
that sets up the spi-nor flash to its pre-suspend state. This is needed on
platfroms that turn off power to the spi-nor flash on pm suspend.
The code has been rebased to git://github.com/spi-nor/linux.git next
branch.
Kamal Dasu (2):
mtd: spi-nor: Added spi-nor init function
mtd: m25p80: Added pm ops support
drivers/mtd/devices/m25p80.c | 11 +++++++
drivers/mtd/spi-nor/spi-nor.c | 77 ++++++++++++++++++++++++++++---------------
include/linux/mtd/spi-nor.h | 18 +++++++++-
3 files changed, 78 insertions(+), 28 deletions(-)
--
1.9.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2017-02-22 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 19:19 Kamal Dasu [this message]
2017-02-22 19:19 ` [PATCH v5 1/2] mtd: spi-nor: Added spi-nor init function Kamal Dasu
2017-02-22 20:56 ` Cyrille Pitchen
2017-02-23 22:06 ` Kamal Dasu
2017-02-22 19:19 ` [PATCH v5 2/2] mtd: m25p80: Added pm ops support Kamal Dasu
2017-02-22 20:38 ` Cyrille Pitchen
2017-02-22 21:26 ` Kamal Dasu
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=1487791173-22159-1-git-send-email-kdasu.kdev@gmail.com \
--to=kdasu.kdev@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=cyrille.pitchen@atmel.com \
--cc=f.fainelli@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=marex@denx.de \
/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).