summaryrefslogtreecommitdiff
path: root/.rustfmt.toml
diff options
context:
space:
mode:
authorChristian Lamparter <chunkeey@gmail.com>2023-06-08 18:36:27 +0300
committerFlorian Fainelli <florian.fainelli@broadcom.com>2023-06-09 01:30:48 +0300
commita6a1a156f5debaebf9f61850d111b966e9be9ee9 (patch)
treeb456ba08eecfae9f84a9c661732566bc28341c09 /.rustfmt.toml
parent7121458ec0e140feb95e9e65a9a4971cbd063c00 (diff)
downloadlinux-a6a1a156f5debaebf9f61850d111b966e9be9ee9.tar.xz
ARM: dts: BCM5301X: MR26: MR32: remove bogus nand-ecc-algo property
| bcm53015-meraki-mr26.dtb: nand-controller@18028000: | nand@0:nand-ecc-algo:0: 'hw' is not one of ['hamming', 'bch', 'rs'] | From schema: Documentation/[...]/nand-controller.yaml | bcm53016-meraki-mr32.dtb: nand-controller@18028000: | nand@0:nand-ecc-algo:0: 'hw' is not one of ['hamming', 'bch', 'rs'] | From schema: Documentation/[...]/nand-controller.yaml original ECC values for these old Merakis are sadly not provided by the vendor. It looks like Meraki just stuck with what Broadcom's SDK was doing... which left this up to the proprietary nand driver. Note: The invalid setting was and is handled by brcmnand. It falls back to "bch" in brcmnand_setup_dev() when ecc.algo is set to NAND_ECC_ALGO_UNKNOWN (since "hw" is not in the list above). A correct nand-ecc-algo = "bch"; is already specified in the included "bcm5301x-nand-cs0-bch8.dtsi". So this line can be dropped. Reported-by: Rafał Miłecki <zajec5@gmail.com> (per Mail) Fixes: 935327a73553 ("ARM: dts: BCM5301X: Add DT for Meraki MR26") Fixes: ec88a9c344d9 ("ARM: BCM5301X: Add DT for Meraki MR32") Signed-off-by: Christian Lamparter <chunkeey@gmail.com> Link: https://lore.kernel.org/r/2c4d00dd40124c2ddc0b139cbce7531b108f9052.1686238550.git.chunkeey@gmail.com Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com>
Diffstat (limited to '.rustfmt.toml')
0 files changed, 0 insertions, 0 deletions