From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: <linux-mtd@lists.infradead.org>, <p.yadav@ti.com>,
<inux-kernel@vger.kernel.org>, <miquel.raynal@bootlin.com>,
<patrice.chotard@foss.st.com>, <vigneshr@ti.com>,
<richard@nod.at>
Cc: Tudor Ambarus <tudor.ambarus@microchip.com>,
<christophe.kerello@foss.st.com>
Subject: Re: mtd: spi-nor: fix spi_nor_spimem_setup_op() call in spi_nor_erase_{sector,chip}()
Date: Thu, 28 Jul 2022 05:38:58 +0300 [thread overview]
Message-ID: <165897588859.58160.1276614701145818210.b4-ty@microchip.com> (raw)
In-Reply-To: <20220629133013.3382393-1-patrice.chotard@foss.st.com>
On Wed, 29 Jun 2022 15:30:13 +0200, patrice.chotard@foss.st.com wrote:
> From: Patrice Chotard <patrice.chotard@foss.st.com>
>
> For erase operations, reg_proto must be used as indicated in
> struct spi_nor description in spi-nor.h.
>
> This issue was found when DT property spi-tx-bus-width is set to 4.
> In this case the spi_mem_op->addr.buswidth is set to 4 for erase command
> which is not correct.
>
> [...]
Used nor->reg_proto in spi_nor_controller_ops_erase() and applied to
spi-nor/next, thanks!
[1/1] mtd: spi-nor: fix spi_nor_spimem_setup_op() call in spi_nor_erase_{sector,chip}()
https://git.kernel.org/mtd/c/7f5ee1a113a9
Best regards,
--
Tudor Ambarus <tudor.ambarus@microchip.com>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-07-28 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 13:30 mtd: spi-nor: fix spi_nor_spimem_setup_op() call in spi_nor_erase_{sector,chip}() patrice.chotard
2022-07-05 7:36 ` Pratyush Yadav
2022-07-18 16:47 ` Tudor.Ambarus
2022-07-25 14:50 ` Alexander Sverdlin
2022-07-28 2:38 ` Tudor Ambarus [this message]
2022-07-28 2:47 ` Tudor.Ambarus
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=165897588859.58160.1276614701145818210.b4-ty@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=christophe.kerello@foss.st.com \
--cc=inux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=patrice.chotard@foss.st.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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).