Home
last modified time | relevance | path

Searched full:onenand (Results 1 – 25 of 36) sorted by relevance

12

/linux-6.12.1/drivers/mtd/nand/onenand/
Donenand_samsung.c3 * Samsung S3C64XX/S5PC1XX OneNAND driver
19 #include <linux/mtd/onenand.h>
143 static struct s3c_onenand *onenand; variable
147 return readl(onenand->base + offset); in s3c_read_reg()
152 writel(value, onenand->base + offset); in s3c_write_reg()
157 return readl(onenand->ahb_addr + cmd); in s3c_read_cmd()
162 writel(value, onenand->ahb_addr + cmd); in s3c_write_cmd()
172 (unsigned int) onenand->base + i, in s3c_dump_reg()
218 struct onenand_chip *this = onenand->mtd->priv; in s3c_onenand_readw()
219 struct device *dev = &onenand->pdev->dev; in s3c_onenand_readw()
[all …]
DKconfig3 tristate "OneNAND Device Support"
6 This enables support for accessing all type of OneNAND flash
12 bool "Verify OneNAND page writes"
15 OneNAND flash device internally checks only bits transitioning
21 tristate "OneNAND Flash device via platform device driver"
23 Support for OneNAND flash via platform device driver.
26 tristate "OneNAND on OMAP2/OMAP3 support"
31 Support for a OneNAND flash device connected to an OMAP2/OMAP3 SoC
36 tristate "OneNAND on Samsung SOC controller support"
39 Support for a OneNAND flash device connected to Samsung S3C64XX
[all …]
Dgeneric.c7 * This is a device driver for the OneNAND flash for generic boards.
14 #include <linux/mtd/onenand.h>
21 * This version of the driver is named "onenand-flash" and takes struct
23 * with the name "onenand" used to take struct flash_platform_data.
25 #define DRIVER_NAME "onenand-flash"
29 struct onenand_chip onenand; member
49 info->onenand.base = ioremap(res->start, size); in generic_onenand_probe()
50 if (!info->onenand.base) { in generic_onenand_probe()
55 info->onenand.mmcontrol = pdata ? pdata->mmcontrol : NULL; in generic_onenand_probe()
61 info->onenand.irq = err; in generic_onenand_probe()
[all …]
Donenand_omap2.c3 * OneNAND driver for OMAP2 / OMAP3
14 #include <linux/mtd/onenand.h>
29 #define DRIVER_NAME "omap2-onenand"
39 struct onenand_chip onenand; member
61 return readw(c->onenand.base + reg); in read_reg()
67 writew(value, c->onenand.base + reg); in write_reg()
456 memset((__force void *)c->onenand.base, 0, ONENAND_BUFRAM_SIZE); in omap2_onenand_shutdown()
484 c->onenand.base = devm_platform_get_and_ioremap_resource(pdev, 0, &res); in omap2_onenand_probe()
485 if (IS_ERR(c->onenand.base)) in omap2_onenand_probe()
486 return PTR_ERR(c->onenand.base); in omap2_onenand_probe()
[all …]
Donenand_base.c13 * Flex-OneNAND support
27 #include <linux/mtd/onenand.h>
39 /* Default Flex-OneNAND boundary and lock respectively */
43 MODULE_PARM_DESC(flex_bdry, "SLC Boundary information for Flex-OneNAND"
50 /* Default OneNAND/Flex-OneNAND OTP options*/
54 MODULE_PARM_DESC(otp, "Corresponding behaviour of OneNAND in OTP"
63 * flexonenand_oob_128 - oob info for Flex-Onenand with 4KB page
96 * onenand_oob_128 - oob info for OneNAND with 4KB page
99 * 4Gb M-die OneNAND Flash (KFM4G16Q4M, KFN8G16Q4M). Rev. 1.3, Apr. 2010
194 * onenand_readw - [OneNAND Interface] Read OneNAND register
[all …]
DMakefile3 # Makefile for the OneNAND MTD
7 obj-$(CONFIG_MTD_ONENAND) += onenand.o
14 onenand-objs = onenand_base.o onenand_bbt.o
Donenand_bbt.c3 * Bad Block Table support for the OneNAND driver
16 #include <linux/mtd/onenand.h>
104 printk(KERN_INFO "OneNAND eraseblock %d is an " in create_bbt()
139 * onenand_isbad_bbt - [OneNAND Interface] Check if a block is bad
168 * onenand_scan_bbt - [OneNAND Interface] scan, find, read and maybe create bad block table(s)
223 * onenand_default_bbt - [OneNAND Interface] Select a default bad block table for the device
Dsamsung.h10 * OneNAND Controller
/linux-6.12.1/Documentation/devicetree/bindings/mtd/
Dsamsung,s5pv210-onenand.yaml4 $id: http://devicetree.org/schemas/mtd/samsung,s5pv210-onenand.yaml#
7 title: Samsung S5Pv210 SoC OneNAND Controller
15 - samsung,s5pv210-onenand
20 - description: OneNAND interface nCE[0]
21 - description: OneNAND interface nCE[1]
29 - const: onenand
51 compatible = "samsung,s5pv210-onenand";
56 clock-names = "bus", "onenand";
Dti,gpmc-onenand.yaml4 $id: http://devicetree.org/schemas/mtd/ti,gpmc-onenand.yaml#
7 title: OneNAND over Texas Instruments GPMC bus.
14 GPMC connected OneNAND (found on OMAP boards) are represented
19 pattern: "^onenand@[0-9],[0,9]$"
22 const: ti,omap2-onenand
28 OneNAND register window.
65 ranges = <0 0 0x01000000 0x01000000>, /* 16 MB for OneNAND */
68 onenand@0,0 {
69 compatible = "ti,omap2-onenand";
/linux-6.12.1/include/linux/mtd/
Donenand.h3 * linux/include/linux/mtd/onenand.h
21 /* Scan and identify a OneNAND device */
23 /* Free resources held by the OneNAND device */
27 * struct onenand_bufferram - OneNAND BufferRAM Data
35 * struct onenand_chip - OneNAND Private Flash Chip Data
36 * @base: [BOARDSPECIFIC] address to access OneNAND
37 * @dies: [INTERN][FLEX-ONENAND] number of dies on chip
38 * @boundary: [INTERN][FLEX-ONENAND] Boundary of the dies
39 * @diesize: [INTERN][FLEX-ONENAND] Size of the dies
41 * FIXME For Flex-OneNAND, chipsize holds maximum possible
[all …]
Donenand_regs.h5 * OneNAND Register header file
25 * OneNAND Registers
Dbbm.h140 /* OneNAND BBT interface */
/linux-6.12.1/arch/arm/boot/dts/ti/omap/
Domap3430-sdp.dts52 <2 0 0x20000000 0x1000000>; /* CS2: 16MB for OneNAND */
150 onenand@2,0 {
154 compatible = "ti,omap2-onenand";
175 label = "xloader-onenand";
179 label = "bootloader-onenand";
183 label = "params-onenand";
187 label = "kernel-onenand";
191 label = "filesystem-onenand";
Domap3-gta04a5one.dts9 model = "Goldelico GTA04A5/Letux 2804 with OneNAND";
33 * according to TRM. OneNAND seems to require PIN_INPUT on clock.
42 /* switch inherited setup to OneNAND */
44 ranges = <0 0 0x04000000 0x1000000>; /* CS0: 16MB for OneNAND */
50 onenand@0,0 {
54 compatible = "ti,omap2-onenand";
Domap2420-n8x0-common.dtsi48 ranges = <0 0 0x04000000 0x1000000>; /* CS0: 16MB for OneNAND */
52 onenand@0,0 {
55 compatible = "ti,omap2-onenand";
107 label = "omap2-onenand";
Domap3-n950-n9.dtsi359 ranges = <0 0 0x04000000 0x1000000>; /* CS0: 16MB for OneNAND */
361 onenand@0,0 {
364 compatible = "ti,omap2-onenand";
370 * and N9 devices (OneNAND Manufacturer: Samsung):
440 label = "omap2-onenand";
Domap3-igep.dtsi39 /* OneNAND seems to require PIN_INPUT on clock. */
140 onenand@0,0 {
141 compatible = "ti,omap2-onenand";
Domap3-n900.dts256 * according to TRM. OneNAND seems to require PIN_INPUT on clock.
848 ranges = <0 0 0x01000000 0x01000000>, /* 16 MB for OneNAND */
854 onenand@0,0 {
857 compatible = "ti,omap2-onenand";
863 * (OneNAND Manufacturer: Samsung):
/linux-6.12.1/drivers/mtd/nand/
DMakefile7 obj-y += onenand/
DKconfig8 source "drivers/mtd/nand/onenand/Kconfig"
/linux-6.12.1/arch/arm/include/asm/mach/
Dflash.h20 * mmcontrol: method called to enable or disable Sync. Burst Read in OneNAND
/linux-6.12.1/arch/arm/boot/dts/samsung/
Ds5pv210.dtsi75 onenand: nand-controller@b0600000 { label
76 compatible = "samsung,s5pv210-onenand";
83 clock-names = "bus", "onenand";
/linux-6.12.1/Documentation/driver-api/memory-devices/
Dti-gpmc.rst46 multiple onenand's and tusb6010 peripherals.
/linux-6.12.1/drivers/memory/
DKconfig112 memory drives like NOR, NAND, OneNAND, SRAM.

12