Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: <Takahiro.Kuwano@infineon.com>
To: <mwalle@kernel.org>, <pratyush@kernel.org>,
	<miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>,
	<stayer.opt1f@icloud.com>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] mtd: spi-nor: xmc: add locking to XM25QH128A
Date: Thu, 13 Aug 2026 00:48:11 +0000	[thread overview]
Message-ID: <ead6aa2a38c64ed78e6c9972a8dfc2fe@infineon.com> (raw)
In-Reply-To: <20260811064512.42520-1-mwalle@kernel.org>

> Add support for locking to the XM25QH128A part.
> 
> Reported-by: Takino <stayer.opt1f@icloud.com>
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=221825
> Signed-off-by: Michael Walle <mwalle@kernel.org>

Reviewed-by: Takahiro Kuwano <takahiro.kuwano@infineon.com>

> ---
> Hi Takino,
> 
> please test it and reply with a "Tested-by" tag. With your full name if
> you like. I didn't get that from the bug report.
> ---
>  drivers/mtd/spi-nor/xmc.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/mtd/spi-nor/xmc.c b/drivers/mtd/spi-nor/xmc.c
> index d5a06054b0dd..d3b52eb93e2c 100644
> --- a/drivers/mtd/spi-nor/xmc.c
> +++ b/drivers/mtd/spi-nor/xmc.c
> @@ -19,6 +19,7 @@ static const struct flash_info xmc_nor_parts[] = {
>                 .name = "XM25QH128A",
>                 .size = SZ_16M,
>                 .no_sfdp_flags = SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ,
> +               .flags = SPI_NOR_HAS_LOCK | SPI_NOR_4BIT_BP | SPI_NOR_HAS_TB,
>         },
>  };
> 
> --
> 2.47.3


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

      parent reply	other threads:[~2026-08-13  0:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11  6:44 [PATCH] mtd: spi-nor: xmc: add locking to XM25QH128A Michael Walle
2026-08-12 15:18 ` fonkism
2026-08-13  0:48 ` Takahiro.Kuwano [this message]

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=ead6aa2a38c64ed78e6c9972a8dfc2fe@infineon.com \
    --to=takahiro.kuwano@infineon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=mwalle@kernel.org \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=stayer.opt1f@icloud.com \
    --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