From: Matthias Brugger <matthias.bgg@gmail.com>
To: Daniel Golle <daniel@makrotopia.org>,
devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH 1/2] arm64: dts: mt7622: declare SPI-NAND present on BPI-R64
Date: Mon, 29 May 2023 16:23:14 +0200 [thread overview]
Message-ID: <64b7c2ed-ccbe-8313-8a46-1adf57deb0df@gmail.com> (raw)
In-Reply-To: <ZEA96dmaXqTpk8u8@makrotopia.org>
On 19/04/2023 21:15, Daniel Golle wrote:
> The SPI-NOR node in the device tree of the BananaPi R64 has most likely
> been copied from the reference board's device tree even though the R64
> comes with an SPI-NAND chip rather than SPI-NOR.
>
> Setup the Serial NAND Flash Interface (SNFI) controller, enable
> hardware BCH error detection and correction engine and add the SPI-NAND
> chip including basic partitions,
>
> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Applied, thanks
> ---
> .../dts/mediatek/mt7622-bananapi-bpi-r64.dts | 39 ++++++++++++++++---
> 1 file changed, 34 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt7622-bananapi-bpi-r64.dts b/arch/arm64/boot/dts/mediatek/mt7622-bananapi-bpi-r64.dts
> index af3fe61e40938..d583e816684cf 100644
> --- a/arch/arm64/boot/dts/mediatek/mt7622-bananapi-bpi-r64.dts
> +++ b/arch/arm64/boot/dts/mediatek/mt7622-bananapi-bpi-r64.dts
> @@ -248,14 +248,42 @@ &nandc {
> status = "disabled";
> };
>
> -&nor_flash {
> - pinctrl-names = "default";
> - pinctrl-0 = <&spi_nor_pins>;
> - status = "disabled";
> +&bch {
> + status = "okay";
> +};
>
> +&snfi {
> + pinctrl-names = "default";
> + pinctrl-0 = <&serial_nand_pins>;
> + status = "okay";
> flash@0 {
> - compatible = "jedec,spi-nor";
> + compatible = "spi-nand";
> reg = <0>;
> + spi-tx-bus-width = <4>;
> + spi-rx-bus-width = <4>;
> + nand-ecc-engine = <&snfi>;
> + partitions {
> + compatible = "fixed-partitions";
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + partition@0 {
> + label = "bl2";
> + reg = <0x0 0x80000>;
> + read-only;
> + };
> +
> + partition@80000 {
> + label = "fip";
> + reg = <0x80000 0x200000>;
> + read-only;
> + };
> +
> + ubi: partition@280000 {
> + label = "ubi";
> + reg = <0x280000 0x7d80000>;
> + };
> + };
> };
> };
>
>
> base-commit: 13961ef828cbc254cc272221b7fc54851caa39a7
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-05-29 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 19:15 [PATCH 1/2] arm64: dts: mt7622: declare SPI-NAND present on BPI-R64 Daniel Golle
2023-05-29 14:23 ` Matthias Brugger [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=64b7c2ed-ccbe-8313-8a46-1adf57deb0df@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=robh+dt@kernel.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