From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Martin Kurbanov <mmkurbanov@sberdevices.ru>
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Dmitry Rokosov <ddrokosov@sberdevices.ru>,
Chuanhong Guo <gch981213@gmail.com>,
Aidan MacDonald <aidanmacdonald.0x0@gmail.com>,
Felix Matouschek <felix@matouschek.org>, <kernel@kempniu.pl>,
<linux-kernel@vger.kernel.org>, <linux-mtd@lists.infradead.org>,
<kernel@sberdevices.ru>
Subject: Re: [PATCH v3] mtd: spinand: add support for ESMT F50x1G41LB
Date: Tue, 28 Mar 2023 14:56:39 +0200 [thread overview]
Message-ID: <20230328145639.1aef44e2@xps-13> (raw)
In-Reply-To: <20230322151625.791131-1-mmkurbanov@sberdevices.ru>
Hi Martin,
mmkurbanov@sberdevices.ru wrote on Wed, 22 Mar 2023 18:16:25 +0300:
> From: Chuanhong Guo <gch981213@gmail.com>
>
> This patch adds support for ESMT F50L1G41LB and F50D1G41LB.
> It seems that ESMT likes to use random JEDEC ID from other vendors.
> Their 1G chips uses 0xc8 from GigaDevice and 2G/4G chips uses 0x2c from
> Micron. For this reason, the ESMT entry is named esmt_c8 with explicit
> JEDEC ID in variable name.
I was about to merge this patch but it turns out there are conflicts in
the tree. Can you please rebase on top of nand/next and send a v4?
>
> Datasheets:
> https://www.esmt.com.tw/upload/pdf/ESMT/datasheets/F50L1G41LB(2M).pdf
> https://www.esmt.com.tw/upload/pdf/ESMT/datasheets/F50D1G41LB(2M).pdf
>
> Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
> Signed-off-by: Martin Kurbanov <mmkurbanov@sberdevices.ru>
> Signed-off-by: Dmitry Rokosov <ddrokosov@sberdevices.ru>
> Tested-by: Martin Kurbanov <mmkurbanov@sberdevices.ru>
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-03-28 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 15:16 [PATCH v3] mtd: spinand: add support for ESMT F50x1G41LB Martin Kurbanov
2023-03-28 12:56 ` Miquel Raynal [this message]
2023-03-28 13:06 ` Martin Kurbanov
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=20230328145639.1aef44e2@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=aidanmacdonald.0x0@gmail.com \
--cc=ddrokosov@sberdevices.ru \
--cc=felix@matouschek.org \
--cc=gch981213@gmail.com \
--cc=kernel@kempniu.pl \
--cc=kernel@sberdevices.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mmkurbanov@sberdevices.ru \
--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