| Message ID | 20200623183030.26591-1-p.yadav@ti.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | mtd: spi-nor: add xSPI Octal DTR support | expand |
Hi, Mark, On 6/23/20 9:30 PM, Pratyush Yadav wrote: > Pratyush Yadav (17): > spi: spi-mem: allow specifying whether an op is DTR or not > spi: spi-mem: allow specifying a command's extension > spi: atmel-quadspi: reject DTR ops > spi: spi-mtk-nor: reject DTR ops These four patches are looking good, I had just few minor comments. If you too think that they are ok, would you take them through the SPI tree? If so, I would need an immutable tag on top of v5.8-rc1 preferably, so I can merge them back to SPI NOR and continue the development on top of them. Let us know if you want us to resubmit for those minor comments. Cheers, ta
On Wed, 24 Jun 2020 00:00:13 +0530, Pratyush Yadav wrote: > This series adds support for octal DTR flashes in the spi-nor framework, > and then adds hooks for the Cypress Semper and Mircom Xcella flashes to > allow running them in octal DTR mode. This series assumes that the flash > is handed to the kernel in Legacy SPI mode. > > Tested on TI J721e EVM with 1-bit ECC on the Cypress flash. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/4] spi: spi-mem: allow specifying whether an op is DTR or not commit: 4c5e2bba30e49b970a0fd07b43e0b7a3b5fd5ea7 [2/4] spi: spi-mem: allow specifying a command's extension commit: caf72df48be32c39f74287976ae843501ae06949 [3/4] spi: atmel-quadspi: reject DTR ops commit: 5c81c275582c9d9c66d2f928591a2065f2528231 [4/4] spi: spi-mtk-nor: reject DTR ops commit: 4728f073bfc66b8b555274ef0d7741d7f5a48947 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
On Mon, Jul 13, 2020 at 06:34:12AM +0000, Tudor.Ambarus@microchip.com wrote: > These four patches are looking good, I had just few minor comments. > If you too think that they are ok, would you take them through the > SPI tree? If so, I would need an immutable tag on top of v5.8-rc1 > preferably, so I can merge them back to SPI NOR and continue the > development on top of them. The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407: Linux 5.8-rc1 (2020-06-14 12:45:04 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-mem-dtr for you to fetch changes up to 4728f073bfc66b8b555274ef0d7741d7f5a48947: spi: spi-mtk-nor: reject DTR ops (2020-07-14 17:29:40 +0100) ---------------------------------------------------------------- spi: Support for DTR ops ---------------------------------------------------------------- Pratyush Yadav (4): spi: spi-mem: allow specifying whether an op is DTR or not spi: spi-mem: allow specifying a command's extension spi: atmel-quadspi: reject DTR ops spi: spi-mtk-nor: reject DTR ops drivers/spi/atmel-quadspi.c | 6 ++++++ drivers/spi/spi-mem.c | 16 ++++++++++------ drivers/spi/spi-mtk-nor.c | 10 ++++++++-- drivers/spi/spi-mxic.c | 3 ++- drivers/spi/spi-zynq-qspi.c | 11 ++++++----- include/linux/spi/spi-mem.h | 14 +++++++++++++- 6 files changed, 45 insertions(+), 15 deletions(-)
On 7/14/20 10:19 PM, Mark Brown wrote: > On Mon, Jul 13, 2020 at 06:34:12AM +0000, Tudor.Ambarus@microchip.com wrote: > >> These four patches are looking good, I had just few minor comments. >> If you too think that they are ok, would you take them through the >> SPI tree? If so, I would need an immutable tag on top of v5.8-rc1 >> preferably, so I can merge them back to SPI NOR and continue the >> development on top of them. > > The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407: > > Linux 5.8-rc1 (2020-06-14 12:45:04 -0700) > > are available in the Git repository at: > > https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-mem-dtr > > for you to fetch changes up to 4728f073bfc66b8b555274ef0d7741d7f5a48947: > > spi: spi-mtk-nor: reject DTR ops (2020-07-14 17:29:40 +0100) > > ---------------------------------------------------------------- > spi: Support for DTR ops > > ---------------------------------------------------------------- > Pratyush Yadav (4): > spi: spi-mem: allow specifying whether an op is DTR or not > spi: spi-mem: allow specifying a command's extension > spi: atmel-quadspi: reject DTR ops > spi: spi-mtk-nor: reject DTR ops > > drivers/spi/atmel-quadspi.c | 6 ++++++ > drivers/spi/spi-mem.c | 16 ++++++++++------ > drivers/spi/spi-mtk-nor.c | 10 ++++++++-- > drivers/spi/spi-mxic.c | 3 ++- > drivers/spi/spi-zynq-qspi.c | 11 ++++++----- > include/linux/spi/spi-mem.h | 14 +++++++++++++- > 6 files changed, 45 insertions(+), 15 deletions(-) > Merged into spi-nor/next. Thank you!