From: Michael Walle <michael@walle.cc>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Pratyush Yadav <pratyush@kernel.org>,
linux-mtd@lists.infradead.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: [PATCH 2/2] mtd: spi-nor: Add support for sst26vf032b flash
Date: Wed, 14 Jun 2023 09:25:09 +0200 [thread overview]
Message-ID: <504066732cbcda957ddefd746151d108@walle.cc> (raw)
In-Reply-To: <5a3b770b-45af-5d66-2596-c7d2ef8d70b1@linaro.org>
>>>>> + { "sst26vf032b", INFO(0xbf2642, 0, 64 * 1024, 64)
>>>>
>>>> Please try with INFO(0xbf2642, 0, 0, 0). You can also have a look
>>>
>>> Oh, yes, I forgot about this. Will you send a new version of
>>> https://patchwork.ozlabs.org/project/linux-mtd/patch/20220510140232.3519184-2-michael@walle.cc/
>>> or you'd like someone else to take over?
>>
>> Now that I'm back from vacation, I'll get back to it soon :)
>>
>
> Welcome back! Ok, thanks, we will all benefit of it. Specifying zeroes
> is a non-sense, but it helps us when we transition to SFDP_ID macro
> (or whatever it will be called).
Sure, that was always the plan. I just want to make sure, no new flashes
are added with this unneeded information and thus it would require
retesting when moving to the new macro.
-michael
next prev parent reply other threads:[~2023-06-14 7:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 14:43 [PATCH 0/2] mtd: spi-nor: Support for another sst flash Miquel Raynal
2023-06-09 14:43 ` [PATCH 1/2] dt-bindings: mtd: spi-nor: Document sst26vf0xxb flash series Miquel Raynal
2023-06-12 10:00 ` Tudor Ambarus
2023-06-15 14:42 ` Miquel Raynal
2023-06-09 14:43 ` [PATCH 2/2] mtd: spi-nor: Add support for sst26vf032b flash Miquel Raynal
2023-06-12 9:57 ` Tudor Ambarus
2023-06-13 13:34 ` Michael Walle
2023-06-14 6:56 ` Tudor Ambarus
2023-06-14 7:04 ` Michael Walle
2023-06-14 7:13 ` Tudor Ambarus
2023-06-14 7:25 ` Michael Walle [this message]
2023-06-12 10:03 ` [PATCH 0/2] mtd: spi-nor: Support for another sst flash Tudor Ambarus
2023-06-12 17:06 ` Miquel Raynal
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=504066732cbcda957ddefd746151d108@walle.cc \
--to=michael@walle.cc \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tudor.ambarus@linaro.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