From: Josua Mayer <josua@solid-run.com>
To: Michael Walle <mwalle@kernel.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-mtd@lists.infradead.org
Cc: Yazan Shhady <yazan.shhady@solid-run.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7] dt-bindings: mtd: spi-nor: add optional interrupts property
Date: Wed, 21 Feb 2024 10:13:36 +0100 [thread overview]
Message-ID: <a0144c5b-4095-4a0c-84b6-93dfe9631a6b@solid-run.com> (raw)
In-Reply-To: <CZAM553H2H56.2TDN36QEL90XX@kernel.org>
Hi,
Am 21.02.24 um 09:27 schrieb Michael Walle:
> Hi,
>
> On Mon Feb 19, 2024 at 3:41 PM CET, Josua Mayer wrote:
>> Some spi flash memories have an interrupt signal which can be used for
>> signalling on-chip events such as busy status or ecc errors to the host.
> Do you have an example? Maybe one with a public datasheet?
My example is Infineon S28HS512T, however datasheet download requires
user account.
S26HS512T has interrupt line, too, and datasheet is downloadable without
registration:
https://www.infineon.com/cms/en/product/memories/nor-flash/semper-nor-flash-family/semper-nor-flash/#!documents
>
> -michael
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2024-02-21 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 14:41 [PATCH v7] dt-bindings: mtd: spi-nor: add optional interrupts property Josua Mayer
2024-02-20 12:19 ` Pratyush Yadav
2024-02-20 12:31 ` Josua Mayer
2024-02-20 13:30 ` Pratyush Yadav
2024-02-21 8:27 ` Michael Walle
2024-02-21 9:13 ` Josua Mayer [this message]
2024-02-21 9:23 ` Michael Walle
2024-02-21 10:48 ` Pratyush Yadav
2024-02-21 11:52 ` Michael Walle
2024-02-26 10:02 ` Tudor Ambarus
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=a0144c5b-4095-4a0c-84b6-93dfe9631a6b@solid-run.com \
--to=josua@solid-run.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=vigneshr@ti.com \
--cc=yazan.shhady@solid-run.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