[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aad92eb5-00ed-5071-c206-491eff243537@rock-chips.com>
Date: Mon, 13 Jan 2020 09:55:28 +0800
From: Shawn Lin <shawn.lin@...k-chips.com>
To: Johan Jonker <jbx6244@...il.com>, miquel.raynal@...tlin.com
Cc: shawn.lin@...k-chips.com, mark.rutland@....com,
devicetree@...r.kernel.org, vigneshr@...com, richard@....at,
linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org,
robh+dt@...nel.org, linux-mtd@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, heiko@...ech.de,
赵仪峰 <yifeng.zhao@...k-chips.com>
Subject: Re: [RFC PATCH v1 00/10] Enable RK3066 NANDC for MK808【请注意,邮件由linux-rockchip-bounces+shawn.lin=rock-chips.com@...ts.infradead.org代发】
+ Yifeng Zhao
On 2020/1/9 4:53, Johan Jonker wrote:
> DISCLAIMER: Use at your own risk.
> Status: For testing only!
>
> Version: V1
>
> Title: Enable RK3066 NANDC for MK808.
>
> The majority of Rockchip devices use a closed source FTL driver
> to reduce wear leveling. This patch serie proposes
> an experimental raw NAND controller driver for basic tasks
> in order to get the bindings and the nodes accepted for in the dts files.
>
> What does it do:
>
> On module load this driver will reserve its resources.
> After initialization the MTD framework will then try to detect
> the type and number of NAND chips. When all conditions are met,
> it registers it self as MTD device.
> This driver is then ready to receive user commands
> such as to read and write NAND pages.
>
> Test examples:
>
> # dd if-/dev/mtd0 of=dd.bin bs=8192 count=4
>
> # nanddump -a -l 32768 -f nanddump.bin /dev/mtd0
>
> Not tested:
>
> NANDC version 9.
> NAND raw write.
> RK3066 still has no support for Uboot.
> Any write command would interfere with data structures made by the boot loader.
>
> Etc.
>
> Problems:
>
> No bad block support. Most devices use a FTL bad block map with tags
> that must be located on specific page locations which is outside
> the scope of the raw MTD framework.
>
Hi Johan,
I loop in the author of the original NANDC driver who is now gonna to
develop a new version of NANDC driver in near future that supports more
features like bad block supoort. Maybe he could share his TODO.
> No partition support. A FTL driver will store at random locations and
> a linear user specific layout does not fit within
> the generic character of this basic driver.
>
> Etc.
>
> Chris Zhong (1):
> ARM: dts: rockchip: add nandc node for rk3066a/rk3188
>
> Dingqiang Lin (2):
> arm64: dts: rockchip: add nandc node for px30
> arm64: dts: rockchip: add nandc node for rk3308
>
> Jianqun Xu (1):
> ARM: dts: rockchip: add nandc nodes for rk3288
>
> Johan Jonker (2):
> dt-bindings: mtd: add rockchip nand controller bindings
> ARM: dts: rockchip: rk3066a-mk808: enable nandc node
>
> Jon Lin (1):
> ARM: dts: rockchip: add nandc node for rv1108
>
> Wenping Zhang (1):
> ARM: dts: rockchip: add nandc node for rk322x
>
> Yifeng Zhao (1):
> mtd: nand: raw: add rockchip nand controller driver
>
> Zhaoyifeng (1):
> arm64: dts: rockchip: add nandc node for rk3368
>
> .../devicetree/bindings/mtd/rockchip,nandc.yaml | 78 ++
> arch/arm/boot/dts/rk3066a-mk808.dts | 9 +
> arch/arm/boot/dts/rk322x.dtsi | 11 +
> arch/arm/boot/dts/rk3288.dtsi | 24 +
> arch/arm/boot/dts/rk3xxx.dtsi | 11 +
> arch/arm/boot/dts/rv1108.dtsi | 11 +
> arch/arm64/boot/dts/rockchip/px30.dtsi | 15 +
> arch/arm64/boot/dts/rockchip/rk3308.dtsi | 11 +
> arch/arm64/boot/dts/rockchip/rk3368.dtsi | 12 +
> drivers/mtd/nand/raw/Kconfig | 8 +
> drivers/mtd/nand/raw/Makefile | 1 +
> drivers/mtd/nand/raw/rockchip_nandc.c | 1224 ++++++++++++++++++++
> 12 files changed, 1415 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mtd/rockchip,nandc.yaml
> create mode 100644 drivers/mtd/nand/raw/rockchip_nandc.c
>
> --
> 2.11.0
>
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
>
>
>
Powered by blists - more mailing lists