From: Dmitry Dunaev <dunaev@tecon.ru>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: "open list:SPI NOR SUBSYSTEM" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v2] mtd: spi-nor: Add Puya Semiconductor chips driver
Date: Mon, 26 Feb 2024 15:11:47 +0300 [thread overview]
Message-ID: <ZdyAA7+OmFcBgOuR@tm38l> (raw)
In-Reply-To: <cb237d49-6f0b-4f3b-8f84-7b23495a61be@linaro.org>
On Mon, Feb 26, 2024 at 01:27:35PM +0200, Tudor Ambarus wrote:
> + linux-mtd
>
> Please do not send private emails on matters that are not private.
>
> On 26.02.2024 13:09, Dmitry Dunaev wrote:
> > On Mon, Feb 26, 2024 at 12:43:58PM +0200, Tudor Ambarus wrote:
> >>
> >>
> >> On 26.02.2024 12:40, Dmitry Dunaev wrote:
> >>> Add a SPI NOR manufacturer driver for Puya Semiconductor chips
> >>>
> >>> Signed-off-by: Dmitry Dunaev <dunaev@tecon.ru>
> >>> ---
> >>> drivers/mtd/spi-nor/Makefile | 1 +
> >>> drivers/mtd/spi-nor/core.c | 1 +
> >>> drivers/mtd/spi-nor/core.h | 1 +
> >>> drivers/mtd/spi-nor/puya.c | 64 ++++++++++++++++++++++++++++++++++++
> >>> 4 files changed, 67 insertions(+)
> >>> create mode 100644 drivers/mtd/spi-nor/puya.c
> >>
> >> what changed in v2? why do you need these entries? Can you rely instead
> >> on SFDP to initialize these flashes?
> >
> > In first patch I missed core.{c,h} with Puya flashes structures.
> >
> > And about SFDP on Puya flashes. We try to call DP command on p25q16uc
>
> what's DP command? SFDP read?
Yes, SFDP (0x5A)
>
> > flash and got no answer. It may be a bad chip pack or other matter but
> > now we need a manual description for this chips.
> >
> > If this issue occured only in my case we can skip this patch.
>
> It's first time I hear about puya semiconductor. Please follow the
> documentation that I've sent in the previous email and dump all the
> required data.
I can't send sfdp data block because I can't get it from my Puya chips.
The datasheets for Puya chips can be found at it's original site https://www.puyasemi.com/h_xilie715.html
but at now there is an error to access to any pdf files on this site. The saved datasheets can be
downloaded from sellers, for example https://datasheet.lcsc.com/lcsc/2304140030_PUYA--P25Q16H-SUH-IR_C559219.pdf
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2024-02-26 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 9:23 [PATCH] mtd: spi-nor: Add Puya Semiconductor chips driver Dmitry Dunaev
2024-02-26 9:28 ` Tudor Ambarus
2024-02-26 10:40 ` [PATCH v2] " Dmitry Dunaev
2024-02-26 10:43 ` Tudor Ambarus
[not found] ` <ZdxxZb+fbzXv7ZNk@tm38l>
2024-02-26 11:27 ` Tudor Ambarus
2024-02-26 12:11 ` Dmitry Dunaev [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=ZdyAA7+OmFcBgOuR@tm38l \
--to=dunaev@tecon.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=tudor.ambarus@linaro.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).