From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, "Gole, Dhruva" <d-gole@ti.com>
Subject: Re: [PATCH 0/4] spi: intel: Add support for SFDP opcode
Date: Tue, 22 Nov 2022 14:30:53 +0200 [thread overview]
Message-ID: <Y3zA/THfo2jBglKS@black.fi.intel.com> (raw)
In-Reply-To: <20221025064623.22808-1-mika.westerberg@linux.intel.com>
Hi Mark,
On Tue, Oct 25, 2022 at 09:46:19AM +0300, Mika Westerberg wrote:
> Hi,
>
> This series adds support for SFDP (Serial Flash Discoverable Parameter)
> opcode to the Intel SPI driver. This allows the SPI-NOR core to query
> the flash chip what it supports.
>
> Mika Westerberg (4):
> spi: intel: Use ->replacement_op in intel_spi_hw_cycle()
> spi: intel: Implement adjust_op_size()
> spi: intel: Take possible chip address into account in intel_spi_read/write_reg()
> spi: intel: Add support for SFDP opcode
>
> drivers/spi/spi-intel.c | 78 +++++++++++++++++++++--------------------
> 1 file changed, 40 insertions(+), 38 deletions(-)
Any chance getting this queued for v6.2? Thanks!
next prev parent reply other threads:[~2022-11-22 12:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 6:46 [PATCH 0/4] spi: intel: Add support for SFDP opcode Mika Westerberg
2022-10-25 6:46 ` [PATCH 1/4] spi: intel: Use ->replacement_op in intel_spi_hw_cycle() Mika Westerberg
2022-10-25 6:46 ` [PATCH 2/4] spi: intel: Implement adjust_op_size() Mika Westerberg
2022-10-28 6:12 ` Gole, Dhruva
2022-10-28 6:25 ` Mika Westerberg
2022-10-28 6:46 ` Gole, Dhruva
2022-10-28 7:05 ` Mika Westerberg
2022-10-25 6:46 ` [PATCH 3/4] spi: intel: Take possible chip address into account in intel_spi_read/write_reg() Mika Westerberg
2022-10-25 6:46 ` [PATCH 4/4] spi: intel: Add support for SFDP opcode Mika Westerberg
2022-11-22 12:30 ` Mika Westerberg [this message]
2022-11-22 14:57 ` [PATCH 0/4] " Mark Brown
2022-11-25 21:55 ` Mark Brown
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=Y3zA/THfo2jBglKS@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=broonie@kernel.org \
--cc=d-gole@ti.com \
--cc=linux-spi@vger.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;
as well as URLs for NNTP newsgroup(s).