From: <Tudor.Ambarus@microchip.com>
To: <Alexander.Stein@tq-systems.com>, <miquel.raynal@bootlin.com>,
<richard@nod.at>, <vigneshr@ti.com>, <robh+dt@kernel.org>,
<p.yadav@ti.com>, <michael@walle.cc>
Cc: <alexander.stein@ew.tq-group.com>,
<linux-mtd@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] mtd: spi-nor: micron-st: Add support for output-driver-strength
Date: Mon, 4 Oct 2021 11:26:26 +0000 [thread overview]
Message-ID: <c3490462-9f07-9f69-ecc1-e51b61622ff9@microchip.com> (raw)
In-Reply-To: <20211004111529.211089-2-Alexander.Stein@tq-systems.com>
On 10/4/21 2:15 PM, Alexander Stein wrote:
> [You don't often get email from alexander.stein@tq-systems.com. Learn why this is important at http://aka.ms/LearnAboutSenderIdentification.]
>
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> From: Alexander Stein <alexander.stein@ew.tq-group.com>
>
> Micron flashes support this by the Bits [2:0] in the Enhanced Volatile
> Configuration Register.
> Checked datasheets:
> - n25q_128mb_3v_65nm.pdf
> - mt25t-qljs-L512-xBA-xxT.pdf
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
Does the micron flash define the SCCR SFDP map?
next prev parent reply other threads:[~2021-10-04 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 11:15 [PATCH 1/2] dt-bindings: mtd: spi-nor: Add output-driver-strength property Alexander Stein
2021-10-04 11:15 ` [PATCH 2/2] mtd: spi-nor: micron-st: Add support for output-driver-strength Alexander Stein
2021-10-04 11:26 ` Tudor.Ambarus [this message]
2021-10-08 11:18 ` Pratyush Yadav
2021-10-04 11:25 ` [PATCH 1/2] dt-bindings: mtd: spi-nor: Add output-driver-strength property Tudor.Ambarus
2021-10-05 12:26 ` Rob Herring
2021-10-12 12:52 ` Rob Herring
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=c3490462-9f07-9f69-ecc1-e51b61622ff9@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Alexander.Stein@tq-systems.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).