From: Shawn Lin <shawn.lin@rock-chips.com>
To: Johan Jonker <jbx6244@gmail.com>, miquel.raynal@bootlin.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
vigneshr@ti.com, richard@nod.at, shawn.lin@rock-chips.com,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh+dt@kernel.org, linux-mtd@lists.infradead.org,
赵仪峰 <yifeng.zhao@rock-chips.com>,
linux-arm-kernel@lists.infradead.org, heiko@sntech.de
Subject: Re: [RFC PATCH v1 00/10] Enable RK3066 NANDC for MK808【请注意,邮件由linux-rockchip-bounces+shawn.lin=rock-chips.com@lists.infradead.org代发】
Date: Mon, 13 Jan 2020 09:55:28 +0800 [thread overview]
Message-ID: <aad92eb5-00ed-5071-c206-491eff243537@rock-chips.com> (raw)
In-Reply-To: <20200108205338.11369-1-jbx6244@gmail.com>
+ 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@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
>
>
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-01-13 1:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 20:53 [RFC PATCH v1 00/10] Enable RK3066 NANDC for MK808 Johan Jonker
2020-01-08 20:53 ` [RFC PATCH v1 01/10] dt-bindings: mtd: add rockchip nand controller bindings Johan Jonker
2020-01-15 1:57 ` Rob Herring
2020-01-08 20:53 ` [RFC PATCH v1 02/10] mtd: nand: raw: add rockchip nand controller driver Johan Jonker
2020-01-10 11:05 ` Miquel Raynal
2020-01-12 17:26 ` Johan Jonker
2020-01-13 14:15 ` Miquel Raynal
2020-01-08 20:53 ` [RFC PATCH v1 03/10] ARM: dts: rockchip: add nandc node for rk3066a/rk3188 Johan Jonker
2020-01-08 20:53 ` [RFC PATCH v1 04/10] ARM: dts: rockchip: add nandc node for rk322x Johan Jonker
2020-01-08 20:53 ` [RFC PATCH v1 05/10] ARM: dts: rockchip: add nandc nodes for rk3288 Johan Jonker
2020-01-08 20:53 ` [RFC PATCH v1 06/10] ARM: dts: rockchip: add nandc node for rv1108 Johan Jonker
2020-01-08 20:53 ` [RFC PATCH v1 07/10] arm64: dts: rockchip: add nandc node for px30 Johan Jonker
2020-01-08 20:53 ` [RFC PATCH v1 08/10] arm64: dts: rockchip: add nandc node for rk3308 Johan Jonker
2020-01-08 20:53 ` [RFC PATCH v1 09/10] arm64: dts: rockchip: add nandc node for rk3368 Johan Jonker
2020-01-08 20:53 ` [RFC PATCH v1 10/10] ARM: dts: rockchip: rk3066a-mk808: enable nandc node Johan Jonker
2020-01-13 1:55 ` Shawn Lin [this message]
2020-01-13 18:33 ` [RFC PATCH v1 00/10] Enable RK3066 NANDC for MK808【请注意,邮件由linux-rockchip-bounces+shawn.lin=rock-chips.com@lists.infradead.org代发】 Johan Jonker
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=aad92eb5-00ed-5071-c206-491eff243537@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
--cc=yifeng.zhao@rock-chips.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;
as well as URLs for NNTP newsgroup(s).