From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Arseniy Krasnov <avkrasnov@salutedevices.com>
Cc: 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>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
<linux-mtd@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-amlogic@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <oxffffaa@gmail.com>,
<kernel@sberdevices.ru>
Subject: Re: [PATCH v3 1/2] dt-bindings: mtd: amlogic,meson-nand: support fields for boot ROM code
Date: Wed, 10 Apr 2024 17:00:40 +0200 [thread overview]
Message-ID: <20240410170040.37a59ff6@xps-13> (raw)
In-Reply-To: <588551c9-3426-e623-e2aa-70b040c9324a@salutedevices.com>
Hi Arseniy,
avkrasnov@salutedevices.com wrote on Wed, 10 Apr 2024 17:48:02 +0300:
> Hi,
>
> On 10.04.2024 13:23, Miquel Raynal wrote:
> > Hi Arseniy,
> >
> > avkrasnov@salutedevices.com wrote on Tue, 9 Apr 2024 21:10:24 +0300:
> >
> >> Boot ROM code on Meson requires that some pages on NAND must be written
> >> in special mode: "short" ECC mode where each block is 384 bytes and
> >> scrambling mode is on. Such pages located with the specified interval
> >> within specified offset. Both interval and offset are located in the
> >> device tree and used by driver if 'nand-is-boot-medium' is set for
> >> NAND chip.
> >>
> >> Signed-off-by: Arseniy Krasnov <avkrasnov@salutedevices.com>
> >> ---
> >> .../bindings/mtd/amlogic,meson-nand.yaml | 14 ++++++++++++++
> >> 1 file changed, 14 insertions(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml b/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml
> >> index 57b6957c8415..b86a1953056b 100644
> >> --- a/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml
> >> +++ b/Documentation/devicetree/bindings/mtd/amlogic,meson-nand.yaml
> >> @@ -64,11 +64,25 @@ patternProperties:
> >> items:
> >> maximum: 0
> >>
> >> + amlogic,boot-page-last:
> >> + $ref: /schemas/types.yaml#/definitions/uint32
> >> + description:
> >> + The NFC driver needs this information to select ECC
> >> + algorithms supported by the boot ROM.
> >
> > Shall we have a length rather than the last page?
>
> You mean rename it to "amlogic,boot-pages-length" or something like that ? But I think
> length in bytes is useless here:
> 1) boot rom needs that only some single pages are written in special mode (and as I see in
> vendor's driver it also works in pages).
> 2) NAND driver operates in pages during write/read such pages.
>
> So length in bytes will be converted to pages anyway.
>
> What do You think ?
I didn't talk about units :-)
Maybe: amlogic,boot-pages would make sense? But pointing at the last
page seems weird.
Miquèl
next prev parent reply other threads:[~2024-04-10 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 18:10 [PATCH v3 0/2] Meson: R/W support for pages used by boot ROM Arseniy Krasnov
2024-04-09 18:10 ` [PATCH v3 1/2] dt-bindings: mtd: amlogic,meson-nand: support fields for boot ROM code Arseniy Krasnov
2024-04-10 10:23 ` Miquel Raynal
2024-04-10 14:48 ` Arseniy Krasnov
2024-04-10 15:00 ` Miquel Raynal [this message]
2024-04-10 14:51 ` Arseniy Krasnov
2024-04-09 18:10 ` [PATCH v3 2/2] mtd: rawnand: meson: support R/W mode for boot ROM Arseniy Krasnov
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=20240410170040.37a59ff6@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=avkrasnov@salutedevices.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=kernel@sberdevices.ru \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=oxffffaa@gmail.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