All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Tudor.Ambarus@microchip.com>
To: <mika.westerberg@linux.intel.com>, <broonie@kernel.org>
Cc: <lee.jones@linaro.org>, <boris.brezillon@collabora.com>,
	<michael@walle.cc>, <p.yadav@ti.com>, <miquel.raynal@bootlin.com>,
	<richard@nod.at>, <vigneshr@ti.com>, <corbet@lwn.net>,
	<mauro.lima@eclypsium.com>, <alexander.sverdlin@nokia.com>,
	<andriy.shevchenko@linux.intel.com>, <hans-gert.dahmen@immu.ne>,
	<linux-mtd@lists.infradead.org>, <linux-spi@vger.kernel.org>
Subject: Re: [PATCH v5 0/3] mtd: spi-nor / spi / MFD: Convert intel-spi to SPI MEM
Date: Tue, 11 Jan 2022 07:25:25 +0000	[thread overview]
Message-ID: <e5e7ba2f-b709-3c9d-6560-579e4fa081de@microchip.com> (raw)
In-Reply-To: <Yd0ojpMnSjlguMi1@lahna>

On 1/11/22 8:49 AM, Mika Westerberg wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> Hi Tudor and Mark,

Hi!

> 
> On Mon, Dec 20, 2021 at 07:46:22PM +0300, Mika Westerberg wrote:
>> Hi all,
>>
>> Based on discussion on the patch I sent some time ago here:
>>
>>   http://lists.infradead.org/pipermail/linux-mtd/2021-June/086867.html
>>
>> it turns out that the preferred way to deal with the SPI flash controller
>> drivers is through SPI MEM which is part of Linux SPI subsystem.
>>
>> This series does that for the intel-spi driver. This also renames the
>> driver to follow the convention used in the SPI subsystem. The first patch
>> improves the write protection handling to be slightly more safer. The
>> following two patches do the conversion itself. Note the Intel SPI flash
>> controller only allows commands such as read, write and so on and it
>> internally uses whatever addressing etc. it figured from the SFDP on the
>> flash device.
> 
> Any chance to get this one merged?
> 

Sure, it's a candidate for 5.18. I don't have anything against the move to
SPI, but I didn't get the chance to go through your series. Will try to do
it.

Cheers,
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

WARNING: multiple messages have this Message-ID (diff)
From: <Tudor.Ambarus@microchip.com>
To: <mika.westerberg@linux.intel.com>, <broonie@kernel.org>
Cc: <lee.jones@linaro.org>, <boris.brezillon@collabora.com>,
	<michael@walle.cc>, <p.yadav@ti.com>, <miquel.raynal@bootlin.com>,
	<richard@nod.at>, <vigneshr@ti.com>, <corbet@lwn.net>,
	<mauro.lima@eclypsium.com>, <alexander.sverdlin@nokia.com>,
	<andriy.shevchenko@linux.intel.com>, <hans-gert.dahmen@immu.ne>,
	<linux-mtd@lists.infradead.org>, <linux-spi@vger.kernel.org>
Subject: Re: [PATCH v5 0/3] mtd: spi-nor / spi / MFD: Convert intel-spi to SPI MEM
Date: Tue, 11 Jan 2022 07:25:25 +0000	[thread overview]
Message-ID: <e5e7ba2f-b709-3c9d-6560-579e4fa081de@microchip.com> (raw)
In-Reply-To: <Yd0ojpMnSjlguMi1@lahna>

On 1/11/22 8:49 AM, Mika Westerberg wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> Hi Tudor and Mark,

Hi!

> 
> On Mon, Dec 20, 2021 at 07:46:22PM +0300, Mika Westerberg wrote:
>> Hi all,
>>
>> Based on discussion on the patch I sent some time ago here:
>>
>>   http://lists.infradead.org/pipermail/linux-mtd/2021-June/086867.html
>>
>> it turns out that the preferred way to deal with the SPI flash controller
>> drivers is through SPI MEM which is part of Linux SPI subsystem.
>>
>> This series does that for the intel-spi driver. This also renames the
>> driver to follow the convention used in the SPI subsystem. The first patch
>> improves the write protection handling to be slightly more safer. The
>> following two patches do the conversion itself. Note the Intel SPI flash
>> controller only allows commands such as read, write and so on and it
>> internally uses whatever addressing etc. it figured from the SFDP on the
>> flash device.
> 
> Any chance to get this one merged?
> 

Sure, it's a candidate for 5.18. I don't have anything against the move to
SPI, but I didn't get the chance to go through your series. Will try to do
it.

Cheers,
ta

  reply	other threads:[~2022-01-11  7:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 16:46 [PATCH v5 0/3] mtd: spi-nor / spi / MFD: Convert intel-spi to SPI MEM Mika Westerberg
2021-12-20 16:46 ` Mika Westerberg
2021-12-20 16:46 ` [PATCH v5 1/3] mtd: spi-nor: intel-spi: Disable write protection only if asked Mika Westerberg
2021-12-20 16:46   ` Mika Westerberg
2022-01-28 15:30   ` Tudor.Ambarus
2022-01-28 15:30     ` Tudor.Ambarus
2021-12-20 16:46 ` [PATCH v5 2/3] mtd: spi-nor: intel-spi: Convert to SPI MEM Mika Westerberg
2021-12-20 16:46   ` Mika Westerberg
2022-01-28 16:14   ` Pratyush Yadav
2022-01-28 16:14     ` Pratyush Yadav
2022-02-01 15:24   ` Tudor.Ambarus
2022-02-01 15:24     ` Tudor.Ambarus
2022-02-02 10:54     ` Mika Westerberg
2022-02-02 10:54       ` Mika Westerberg
2021-12-20 16:46 ` [PATCH v5 3/3] Documentation / MTD: Rename the intel-spi driver Mika Westerberg
2021-12-20 16:46   ` Mika Westerberg
2022-02-01 15:28   ` Tudor.Ambarus
2022-02-01 15:28     ` Tudor.Ambarus
2022-01-11  6:49 ` [PATCH v5 0/3] mtd: spi-nor / spi / MFD: Convert intel-spi to SPI MEM Mika Westerberg
2022-01-11  6:49   ` Mika Westerberg
2022-01-11  7:25   ` Tudor.Ambarus [this message]
2022-01-11  7:25     ` 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=e5e7ba2f-b709-3c9d-6560-579e4fa081de@microchip.com \
    --to=tudor.ambarus@microchip.com \
    --cc=alexander.sverdlin@nokia.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=boris.brezillon@collabora.com \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=hans-gert.dahmen@immu.ne \
    --cc=lee.jones@linaro.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mauro.lima@eclypsium.com \
    --cc=michael@walle.cc \
    --cc=mika.westerberg@linux.intel.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=p.yadav@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.