2005-04-17 06:20:36 +08:00
|
|
|
/*
|
|
|
|
* Normal mappings of chips in physical memory
|
|
|
|
*
|
|
|
|
* Copyright (C) 2003 MontaVista Software Inc.
|
|
|
|
* Author: Jun Sun, jsun@mvista.com or jsun@junsun.net
|
|
|
|
*
|
|
|
|
* 031022 - [jsun] add run-time configure and partition setup
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/types.h>
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/slab.h>
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
#include <linux/device.h>
|
|
|
|
#include <linux/platform_device.h>
|
2005-04-17 06:20:36 +08:00
|
|
|
#include <linux/mtd/mtd.h>
|
|
|
|
#include <linux/mtd/map.h>
|
|
|
|
#include <linux/mtd/partitions.h>
|
2005-11-29 22:49:38 +08:00
|
|
|
#include <linux/mtd/physmap.h>
|
2008-02-01 22:26:54 +08:00
|
|
|
#include <linux/mtd/concat.h>
|
2008-11-26 18:26:29 +08:00
|
|
|
#include <linux/io.h>
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2008-02-01 22:26:54 +08:00
|
|
|
#define MAX_RESOURCES 4
|
|
|
|
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
struct physmap_flash_info {
|
2008-02-01 22:26:54 +08:00
|
|
|
struct mtd_info *mtd[MAX_RESOURCES];
|
|
|
|
struct mtd_info *cmtd;
|
|
|
|
struct map_info map[MAX_RESOURCES];
|
2012-03-07 22:12:08 +08:00
|
|
|
spinlock_t vpp_lock;
|
|
|
|
int vpp_refcnt;
|
2005-04-17 06:20:36 +08:00
|
|
|
};
|
|
|
|
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
static int physmap_flash_remove(struct platform_device *dev)
|
|
|
|
{
|
|
|
|
struct physmap_flash_info *info;
|
|
|
|
struct physmap_flash_data *physmap_data;
|
2008-02-01 22:26:54 +08:00
|
|
|
int i;
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
|
|
|
|
info = platform_get_drvdata(dev);
|
|
|
|
if (info == NULL)
|
|
|
|
return 0;
|
|
|
|
platform_set_drvdata(dev, NULL);
|
|
|
|
|
|
|
|
physmap_data = dev->dev.platform_data;
|
|
|
|
|
2009-10-21 00:23:33 +08:00
|
|
|
if (info->cmtd) {
|
2011-05-23 17:22:45 +08:00
|
|
|
mtd_device_unregister(info->cmtd);
|
2009-10-21 00:23:33 +08:00
|
|
|
if (info->cmtd != info->mtd[0])
|
|
|
|
mtd_concat_destroy(info->cmtd);
|
|
|
|
}
|
2008-02-01 22:26:54 +08:00
|
|
|
|
|
|
|
for (i = 0; i < MAX_RESOURCES; i++) {
|
2009-02-12 05:12:17 +08:00
|
|
|
if (info->mtd[i] != NULL)
|
2008-02-01 22:26:54 +08:00
|
|
|
map_destroy(info->mtd[i]);
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
}
|
2011-05-18 17:51:48 +08:00
|
|
|
|
|
|
|
if (physmap_data->exit)
|
|
|
|
physmap_data->exit(dev);
|
|
|
|
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
return 0;
|
2005-04-17 06:20:36 +08:00
|
|
|
}
|
|
|
|
|
2011-05-18 17:51:55 +08:00
|
|
|
static void physmap_set_vpp(struct map_info *map, int state)
|
|
|
|
{
|
|
|
|
struct platform_device *pdev;
|
|
|
|
struct physmap_flash_data *physmap_data;
|
2012-03-07 22:12:08 +08:00
|
|
|
struct physmap_flash_info *info;
|
|
|
|
unsigned long flags;
|
2011-05-18 17:51:55 +08:00
|
|
|
|
|
|
|
pdev = (struct platform_device *)map->map_priv_1;
|
|
|
|
physmap_data = pdev->dev.platform_data;
|
|
|
|
|
2012-03-07 22:12:08 +08:00
|
|
|
if (!physmap_data->set_vpp)
|
|
|
|
return;
|
|
|
|
|
|
|
|
info = platform_get_drvdata(pdev);
|
|
|
|
|
|
|
|
spin_lock_irqsave(&info->vpp_lock, flags);
|
|
|
|
if (state) {
|
|
|
|
if (++info->vpp_refcnt == 1) /* first nested 'on' */
|
|
|
|
physmap_data->set_vpp(pdev, 1);
|
|
|
|
} else {
|
|
|
|
if (--info->vpp_refcnt == 0) /* last nested 'off' */
|
|
|
|
physmap_data->set_vpp(pdev, 0);
|
|
|
|
}
|
|
|
|
spin_unlock_irqrestore(&info->vpp_lock, flags);
|
2011-05-18 17:51:55 +08:00
|
|
|
}
|
|
|
|
|
2008-12-17 02:22:39 +08:00
|
|
|
static const char *rom_probe_types[] = {
|
|
|
|
"cfi_probe",
|
|
|
|
"jedec_probe",
|
|
|
|
"qinfo_probe",
|
|
|
|
"map_rom",
|
|
|
|
NULL };
|
2011-05-18 17:51:55 +08:00
|
|
|
static const char *part_probe_types[] = { "cmdlinepart", "RedBoot", "afs",
|
2011-05-18 17:51:48 +08:00
|
|
|
NULL };
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
|
|
|
|
static int physmap_flash_probe(struct platform_device *dev)
|
2005-04-17 06:20:36 +08:00
|
|
|
{
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
struct physmap_flash_data *physmap_data;
|
|
|
|
struct physmap_flash_info *info;
|
|
|
|
const char **probe_type;
|
2011-12-05 23:08:09 +08:00
|
|
|
const char **part_types;
|
2008-02-01 22:26:54 +08:00
|
|
|
int err = 0;
|
|
|
|
int i;
|
|
|
|
int devices_found = 0;
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
|
|
|
|
physmap_data = dev->dev.platform_data;
|
|
|
|
if (physmap_data == NULL)
|
|
|
|
return -ENODEV;
|
|
|
|
|
2008-11-26 18:26:29 +08:00
|
|
|
info = devm_kzalloc(&dev->dev, sizeof(struct physmap_flash_info),
|
|
|
|
GFP_KERNEL);
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
if (info == NULL) {
|
|
|
|
err = -ENOMEM;
|
|
|
|
goto err_out;
|
|
|
|
}
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2011-05-18 17:51:48 +08:00
|
|
|
if (physmap_data->init) {
|
|
|
|
err = physmap_data->init(dev);
|
|
|
|
if (err)
|
|
|
|
goto err_out;
|
|
|
|
}
|
|
|
|
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
platform_set_drvdata(dev, info);
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2008-02-01 22:26:54 +08:00
|
|
|
for (i = 0; i < dev->num_resources; i++) {
|
|
|
|
printk(KERN_NOTICE "physmap platform flash device: %.8llx at %.8llx\n",
|
2010-06-15 00:57:54 +08:00
|
|
|
(unsigned long long)resource_size(&dev->resource[i]),
|
2008-02-01 22:26:54 +08:00
|
|
|
(unsigned long long)dev->resource[i].start);
|
|
|
|
|
2008-11-26 18:26:29 +08:00
|
|
|
if (!devm_request_mem_region(&dev->dev,
|
|
|
|
dev->resource[i].start,
|
2010-06-15 00:57:54 +08:00
|
|
|
resource_size(&dev->resource[i]),
|
2008-12-23 18:00:14 +08:00
|
|
|
dev_name(&dev->dev))) {
|
2008-02-01 22:26:54 +08:00
|
|
|
dev_err(&dev->dev, "Could not reserve memory region\n");
|
|
|
|
err = -ENOMEM;
|
|
|
|
goto err_out;
|
|
|
|
}
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2008-12-23 18:00:14 +08:00
|
|
|
info->map[i].name = dev_name(&dev->dev);
|
2008-02-01 22:26:54 +08:00
|
|
|
info->map[i].phys = dev->resource[i].start;
|
2010-06-15 00:57:54 +08:00
|
|
|
info->map[i].size = resource_size(&dev->resource[i]);
|
2008-02-01 22:26:54 +08:00
|
|
|
info->map[i].bankwidth = physmap_data->width;
|
2011-05-18 17:51:55 +08:00
|
|
|
info->map[i].set_vpp = physmap_set_vpp;
|
2008-12-17 02:22:39 +08:00
|
|
|
info->map[i].pfow_base = physmap_data->pfow_base;
|
2011-05-18 17:51:55 +08:00
|
|
|
info->map[i].map_priv_1 = (unsigned long)dev;
|
2008-02-01 22:26:54 +08:00
|
|
|
|
2008-11-26 18:26:29 +08:00
|
|
|
info->map[i].virt = devm_ioremap(&dev->dev, info->map[i].phys,
|
|
|
|
info->map[i].size);
|
2008-02-01 22:26:54 +08:00
|
|
|
if (info->map[i].virt == NULL) {
|
|
|
|
dev_err(&dev->dev, "Failed to ioremap flash region\n");
|
2009-11-12 04:47:06 +08:00
|
|
|
err = -EIO;
|
2008-02-01 22:26:54 +08:00
|
|
|
goto err_out;
|
|
|
|
}
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
|
2008-02-01 22:26:54 +08:00
|
|
|
simple_map_init(&info->map[i]);
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2008-02-01 22:26:54 +08:00
|
|
|
probe_type = rom_probe_types;
|
2010-01-15 15:50:14 +08:00
|
|
|
if (physmap_data->probe_type == NULL) {
|
|
|
|
for (; info->mtd[i] == NULL && *probe_type != NULL; probe_type++)
|
|
|
|
info->mtd[i] = do_map_probe(*probe_type, &info->map[i]);
|
|
|
|
} else
|
|
|
|
info->mtd[i] = do_map_probe(physmap_data->probe_type, &info->map[i]);
|
|
|
|
|
2008-02-01 22:26:54 +08:00
|
|
|
if (info->mtd[i] == NULL) {
|
|
|
|
dev_err(&dev->dev, "map_probe failed\n");
|
|
|
|
err = -ENXIO;
|
|
|
|
goto err_out;
|
|
|
|
} else {
|
|
|
|
devices_found++;
|
|
|
|
}
|
|
|
|
info->mtd[i]->owner = THIS_MODULE;
|
2009-03-26 15:42:50 +08:00
|
|
|
info->mtd[i]->dev.parent = &dev->dev;
|
2008-02-01 22:26:54 +08:00
|
|
|
}
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
|
2008-02-01 22:26:54 +08:00
|
|
|
if (devices_found == 1) {
|
|
|
|
info->cmtd = info->mtd[0];
|
|
|
|
} else if (devices_found > 1) {
|
|
|
|
/*
|
|
|
|
* We detected multiple devices. Concatenate them together.
|
|
|
|
*/
|
2008-12-23 18:00:14 +08:00
|
|
|
info->cmtd = mtd_concat_create(info->mtd, devices_found, dev_name(&dev->dev));
|
2008-02-01 22:26:54 +08:00
|
|
|
if (info->cmtd == NULL)
|
|
|
|
err = -ENXIO;
|
2005-04-17 06:20:36 +08:00
|
|
|
}
|
2008-02-01 22:26:54 +08:00
|
|
|
if (err)
|
|
|
|
goto err_out;
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2012-03-07 22:12:08 +08:00
|
|
|
spin_lock_init(&info->vpp_lock);
|
|
|
|
|
2011-12-05 23:08:09 +08:00
|
|
|
part_types = physmap_data->part_probe_types ? : part_probe_types;
|
|
|
|
|
mtd: do not use plain 0 as NULL
The first 3 arguments of 'mtd_device_parse_register()' are pointers,
but many callers pass '0' instead of 'NULL'. Fix this globally. Thanks
to coccinelle for making it easy to do with the following semantic patch:
@@
expression mtd, types, parser_data, parts, nr_parts;
@@
(
-mtd_device_parse_register(mtd, 0, parser_data, parts, nr_parts)
+mtd_device_parse_register(mtd, NULL, parser_data, parts, nr_parts)
|
-mtd_device_parse_register(mtd, types, 0, parts, nr_parts)
+mtd_device_parse_register(mtd, types, NULL, parts, nr_parts)
|
-mtd_device_parse_register(mtd, types, parser_data, 0, nr_parts)
+mtd_device_parse_register(mtd, types, parser_data, NULL, nr_parts)
)
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
2012-03-10 01:24:26 +08:00
|
|
|
mtd_device_parse_register(info->cmtd, part_types, NULL,
|
2011-06-02 21:59:58 +08:00
|
|
|
physmap_data->parts, physmap_data->nr_parts);
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
return 0;
|
|
|
|
|
|
|
|
err_out:
|
|
|
|
physmap_flash_remove(dev);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
2006-09-22 05:16:48 +08:00
|
|
|
#ifdef CONFIG_PM
|
|
|
|
static void physmap_flash_shutdown(struct platform_device *dev)
|
|
|
|
{
|
|
|
|
struct physmap_flash_info *info = platform_get_drvdata(dev);
|
2008-02-01 22:26:54 +08:00
|
|
|
int i;
|
|
|
|
|
2008-03-29 05:16:09 +08:00
|
|
|
for (i = 0; i < MAX_RESOURCES && info->mtd[i]; i++)
|
2011-12-30 23:15:59 +08:00
|
|
|
if (mtd_suspend(info->mtd[i]) == 0)
|
|
|
|
mtd_resume(info->mtd[i]);
|
2006-09-22 05:16:48 +08:00
|
|
|
}
|
2008-02-04 04:56:03 +08:00
|
|
|
#else
|
|
|
|
#define physmap_flash_shutdown NULL
|
2006-09-22 05:16:48 +08:00
|
|
|
#endif
|
|
|
|
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
static struct platform_driver physmap_flash_driver = {
|
|
|
|
.probe = physmap_flash_probe,
|
|
|
|
.remove = physmap_flash_remove,
|
2006-09-22 05:16:48 +08:00
|
|
|
.shutdown = physmap_flash_shutdown,
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
.driver = {
|
|
|
|
.name = "physmap-flash",
|
2008-04-19 04:44:26 +08:00
|
|
|
.owner = THIS_MODULE,
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
},
|
|
|
|
};
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
2008-12-02 06:23:40 +08:00
|
|
|
#ifdef CONFIG_MTD_PHYSMAP_COMPAT
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
static struct physmap_flash_data physmap_flash_data = {
|
|
|
|
.width = CONFIG_MTD_PHYSMAP_BANKWIDTH,
|
|
|
|
};
|
2005-04-17 06:20:36 +08:00
|
|
|
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
static struct resource physmap_flash_resource = {
|
|
|
|
.start = CONFIG_MTD_PHYSMAP_START,
|
2006-06-27 21:38:15 +08:00
|
|
|
.end = CONFIG_MTD_PHYSMAP_START + CONFIG_MTD_PHYSMAP_LEN - 1,
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
.flags = IORESOURCE_MEM,
|
|
|
|
};
|
2005-04-17 06:20:36 +08:00
|
|
|
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
static struct platform_device physmap_flash = {
|
|
|
|
.name = "physmap-flash",
|
|
|
|
.id = 0,
|
|
|
|
.dev = {
|
|
|
|
.platform_data = &physmap_flash_data,
|
|
|
|
},
|
|
|
|
.num_resources = 1,
|
|
|
|
.resource = &physmap_flash_resource,
|
|
|
|
};
|
|
|
|
#endif
|
2005-04-17 06:20:36 +08:00
|
|
|
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
static int __init physmap_init(void)
|
|
|
|
{
|
|
|
|
int err;
|
|
|
|
|
|
|
|
err = platform_driver_register(&physmap_flash_driver);
|
2008-12-02 06:23:40 +08:00
|
|
|
#ifdef CONFIG_MTD_PHYSMAP_COMPAT
|
2010-04-03 06:46:30 +08:00
|
|
|
if (err == 0) {
|
|
|
|
err = platform_device_register(&physmap_flash);
|
|
|
|
if (err)
|
|
|
|
platform_driver_unregister(&physmap_flash_driver);
|
|
|
|
}
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
#endif
|
|
|
|
|
|
|
|
return err;
|
2005-04-17 06:20:36 +08:00
|
|
|
}
|
|
|
|
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
static void __exit physmap_exit(void)
|
|
|
|
{
|
2008-12-02 06:23:40 +08:00
|
|
|
#ifdef CONFIG_MTD_PHYSMAP_COMPAT
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
platform_device_unregister(&physmap_flash);
|
|
|
|
#endif
|
|
|
|
platform_driver_unregister(&physmap_flash_driver);
|
|
|
|
}
|
2005-04-17 06:20:36 +08:00
|
|
|
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-08 00:16:36 +08:00
|
|
|
module_init(physmap_init);
|
|
|
|
module_exit(physmap_exit);
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
MODULE_LICENSE("GPL");
|
|
|
|
MODULE_AUTHOR("David Woodhouse <dwmw2@infradead.org>");
|
|
|
|
MODULE_DESCRIPTION("Generic configurable MTD map driver");
|
2008-04-19 04:44:26 +08:00
|
|
|
|
|
|
|
/* legacy platform drivers can't hotplug or coldplg */
|
2008-12-02 06:23:40 +08:00
|
|
|
#ifndef CONFIG_MTD_PHYSMAP_COMPAT
|
2008-04-19 04:44:26 +08:00
|
|
|
/* work with hotplug and coldplug */
|
|
|
|
MODULE_ALIAS("platform:physmap-flash");
|
|
|
|
#endif
|