From: Takahiro Kuwano <tkuw584924@gmail.com>
To: Tudor.Ambarus@microchip.com, linux-mtd@lists.infradead.org
Cc: miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
p.yadav@ti.com, Bacem.Daassi@infineon.com,
Takahiro.Kuwano@infineon.com
Subject: Re: [PATCH v13 2/4] mtd: spi-nor: spansion: Add support for volatile QE bit
Date: Thu, 21 Apr 2022 19:47:42 +0900 [thread overview]
Message-ID: <f96c55f6-8d27-57f2-892d-d4fd922bd2e4@gmail.com> (raw)
In-Reply-To: <fff074e7-07ca-0334-a6f4-f4c0d57577d8@microchip.com>
On 4/21/2022 7:41 PM, Tudor.Ambarus@microchip.com wrote:
> On 4/21/22 12:40, tkuw584924@gmail.com wrote:
[...]
>> +/**
>> + * cypress_nor_quad_enable_volatile() - enable Quad I/O mode in volatile
>> + * register.
>> + * @nor: pointer to a 'struct spi_nor'
>> + *
>> + * It is recommended to update volatile registers in the field application due
>> + * to a risk of the non-volatile registers corruption by power interrupt. This
>> + * function sets Quad Enable bit in CFR1 volatile. If users set the Quad Enable
>> + * bit in the CFR1 non-volatile in advance (typically by a Flash programmer
>> + * before mounting Flash on PCB), the Quad Enable bit in the CFR1 volatile is
>> + * also set during Flash power-up.
>> + *
>> + * Return: 0 on success, -errno otherwise.
>> + */
>> +static int cypress_nor_quad_enable_volatile(struct spi_nor *nor)
>> +{
>> + struct spi_mem_op op;
>> + u8 cfr1v_written;
>> + int ret;
>> +
>> + op = (struct spi_mem_op)
>> + CYPRESS_NOR_RD_ANY_REG_OP(3, SPINOR_REG_CYPRESS_CFR1V,
> nor->addr_width is 3, isn't it? can we use nor->addr_width instead of 3, please?
>
No, at the time this method is called, nor->addr_width is set to 4 by
spi_nor_set_addr_width().
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-04-21 10:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 9:40 [PATCH v13 0/4] mtd: spi-nor: Add support for Infineon s25hl-t/s25hs-t tkuw584924
2022-04-21 9:40 ` [PATCH v13 1/4] mtd: spi-nor: Retain nor->addr_width at 4BAIT parse tkuw584924
2022-04-21 10:38 ` Tudor.Ambarus
2022-04-21 10:48 ` Takahiro Kuwano
2022-04-21 11:29 ` Michael Walle
2022-04-21 12:06 ` Tudor.Ambarus
2022-04-21 13:01 ` Michael Walle
2022-04-21 13:13 ` Tudor.Ambarus
2022-04-21 13:42 ` Michael Walle
2022-04-21 13:56 ` Tudor.Ambarus
2022-04-21 14:26 ` Takahiro Kuwano
2022-04-27 4:16 ` Takahiro Kuwano
2022-04-27 6:35 ` Tudor.Ambarus
2022-04-21 9:40 ` [PATCH v13 2/4] mtd: spi-nor: spansion: Add support for volatile QE bit tkuw584924
2022-04-21 10:41 ` Tudor.Ambarus
2022-04-21 10:47 ` Takahiro Kuwano [this message]
2022-04-21 10:56 ` Tudor.Ambarus
2022-04-21 11:36 ` Tudor.Ambarus
2022-04-21 11:48 ` Tudor.Ambarus
2022-04-22 9:04 ` Takahiro Kuwano
2022-04-21 9:40 ` [PATCH v13 3/4] mtd: spi-nor: spansion: Add local function to discover page size tkuw584924
2022-04-21 10:43 ` Tudor.Ambarus
2022-04-22 9:14 ` Takahiro Kuwano
2022-04-21 9:40 ` [PATCH v13 4/4] mtd: spi-nor: spansion: Add s25hl-t/s25hs-t IDs and fixups tkuw584924
2022-04-21 10:45 ` Tudor.Ambarus
2022-04-21 10:53 ` Takahiro Kuwano
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=f96c55f6-8d27-57f2-892d-d4fd922bd2e4@gmail.com \
--to=tkuw584924@gmail.com \
--cc=Bacem.Daassi@infineon.com \
--cc=Takahiro.Kuwano@infineon.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=linux-mtd@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox