From: Ranjit Waghmode <ranjit.waghmode@xilinx.com>
To: <broonie@kernel.org>, <dwmw2@infradead.org>,
<computersforpeace@gmail.com>, <swarren@nvidia.com>,
<geert+renesas@glider.be>, <afd@ti.com>, <jic23@kernel.org>,
<marex@denx.de>, <jteki@openedev.com>, <zajec5@gmail.com>,
<juhosg@openwrt.org>, <mika.westerberg@linux.intel.com>,
<sean.nyekjaer@prevas.dk>, <beanhuo@micron.com>,
<furquan@google.com>, <michal.simek@xilinx.com>,
<soren.brinkmann@xilinx.com>
Cc: harinik@xilinx.com, Ranjit Waghmode <ranjit.waghmode@xilinx.com>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
linux-mtd@lists.infradead.org, punnaia@xilinx.com,
ran27jit@gmail.com, linux-arm-kernel@lists.infradead.org
Subject: [LINUX RFC v3 2/4] mtd: add spi_device instance to spi_nor struct
Date: Mon, 14 Dec 2015 18:39:43 +0530 [thread overview]
Message-ID: <1450098585-3129-3-git-send-email-ranjit.waghmode@xilinx.com> (raw)
In-Reply-To: <1450098585-3129-1-git-send-email-ranjit.waghmode@xilinx.com>
This patch adds struct spi_device instacne to the spi_nor structure.
Signed-off-by: Ranjit Waghmode <ranjit.waghmode@xilinx.com>
---
V3 Changes:
- No change in this patch
V2 Changes:
- This is new patch, basically splitted on request of Mark Brown
---
drivers/mtd/devices/m25p80.c | 1 +
include/linux/mtd/spi-nor.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/mtd/devices/m25p80.c b/drivers/mtd/devices/m25p80.c
index fe9ceb7..bab4939 100644
--- a/drivers/mtd/devices/m25p80.c
+++ b/drivers/mtd/devices/m25p80.c
@@ -204,6 +204,7 @@ static int m25p_probe(struct spi_device *spi)
spi_set_drvdata(spi, flash);
flash->spi = spi;
+ nor->spi = spi;
if (spi->mode & SPI_RX_QUAD)
mode = SPI_NOR_QUAD;
diff --git a/include/linux/mtd/spi-nor.h b/include/linux/mtd/spi-nor.h
index c8723b6..872b2b4 100644
--- a/include/linux/mtd/spi-nor.h
+++ b/include/linux/mtd/spi-nor.h
@@ -155,6 +155,7 @@ struct spi_nor {
struct mtd_info mtd;
struct mutex lock;
struct device *dev;
+ struct spi_device *spi;
struct device_node *flash_node;
u32 page_size;
u8 addr_width;
--
2.1.2
next prev parent reply other threads:[~2015-12-14 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 13:09 [LINUX RFC v3 0/4] spi: add dual parallel mode support in Zynq MPSoC GQSPI controller Ranjit Waghmode
2015-12-14 13:09 ` [LINUX RFC v3 1/4] spi: addng support for data stripe feature in core Ranjit Waghmode
2015-12-14 13:09 ` Ranjit Waghmode [this message]
2015-12-14 13:09 ` [LINUX RFC v3 3/4] mtd: spi-nor: add dual parallel mode support Ranjit Waghmode
2015-12-14 13:09 ` [LINUX RFC v3 4/4] spi: zynqmp: gqspi: add support for dual parallel mode configuration Ranjit Waghmode
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=1450098585-3129-3-git-send-email-ranjit.waghmode@xilinx.com \
--to=ranjit.waghmode@xilinx.com \
--cc=afd@ti.com \
--cc=beanhuo@micron.com \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=furquan@google.com \
--cc=geert+renesas@glider.be \
--cc=harinik@xilinx.com \
--cc=jic23@kernel.org \
--cc=jteki@openedev.com \
--cc=juhosg@openwrt.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=marex@denx.de \
--cc=michal.simek@xilinx.com \
--cc=mika.westerberg@linux.intel.com \
--cc=punnaia@xilinx.com \
--cc=ran27jit@gmail.com \
--cc=sean.nyekjaer@prevas.dk \
--cc=soren.brinkmann@xilinx.com \
--cc=swarren@nvidia.com \
--cc=zajec5@gmail.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).