From: Aapo Vienamo <aapo.vienamo@linux.intel.com>
To: mwalle@kernel.org, miquel.raynal@bootlin.com, richard@nod.at,
vigneshr@ti.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: mika.westerberg@linux.intel.com,
Aapo Vienamo <aapo.vienamo@linux.intel.com>
Subject: [PATCH v2 0/2] mtd: core: Handle unsupported OTP operations
Date: Wed, 13 Mar 2024 19:34:23 +0200 [thread overview]
Message-ID: <20240313173425.1325790-1-aapo.vienamo@linux.intel.com> (raw)
Make MTD core tolerate SPI controllers without OTP support.
These changes address the issue that occurs when an OTP capable
SPI NOR device is initialized with the Intel SPI controller. The limited
supported opcode set of the SPI controller leads to failure in the OTP
initialization, which in turn fails the probe for the MTD device. By
allowing the MTD core to tolerate unsupported OTP, the rest of the MTD
functionality remains intact even if OTP initialization is unsupported.
v2 changes:
- Move handling of -EOPNOTSUPP to mtd_otp_nvmem_add()
- Omit error message if -EOPNOTSUPP is returned
Aapo Vienamo (2):
mtd: core: Report error if first mtd_otp_size() call fails in
mtd_otp_nvmem_add()
mtd: core: Don't fail mtd_otp_nvmem_add() if OTP is unsupported
drivers/mtd/mtdcore.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
--
2.41.0
next reply other threads:[~2024-03-13 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 17:34 Aapo Vienamo [this message]
2024-03-13 17:34 ` [PATCH v2 1/2] mtd: core: Report error if first mtd_otp_size() call fails in mtd_otp_nvmem_add() Aapo Vienamo
2024-03-25 10:18 ` Miquel Raynal
2024-03-13 17:34 ` [PATCH v2 2/2] mtd: core: Don't fail mtd_otp_nvmem_add() if OTP is unsupported Aapo Vienamo
2024-03-18 14:07 ` Michael Walle
2024-03-25 10:18 ` Miquel Raynal
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=20240313173425.1325790-1-aapo.vienamo@linux.intel.com \
--to=aapo.vienamo@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mika.westerberg@linux.intel.com \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--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
all inboxes | Powered by JetHome®