From: Mike Rapoport <mike@compulab.co.il>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: eric.miao@marvell.com, linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.arm.linux.org.uk,
Ben Dooks <ben-linux@fluff.org>
Subject: Re: [PATCH] MTD: NAND: pxa3xx_nand: allow building as module
Date: Tue, 20 Jan 2009 09:21:11 +0200 [thread overview]
Message-ID: <49757B67.8040101@compulab.co.il> (raw)
In-Reply-To: <f17812d70901191916u3891547ds393942a4e444a351@mail.gmail.com>
Eric Miao wrote:
> On Mon, Jan 19, 2009 at 7:40 PM, Ben Dooks <ben-linux@fluff.org> wrote:
>> On Mon, Jan 19, 2009 at 01:27:11PM +0200, Mike Rapoport wrote:
>>> Signed-off-by: Mike Rapoport <mike@compulab.co.il>
>>> ---
>>> drivers/mtd/nand/Kconfig | 2 +-
>>> drivers/mtd/nand/pxa3xx_nand.c | 10 ++++++++++
>>> 2 files changed, 11 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/drivers/mtd/nand/Kconfig b/drivers/mtd/nand/Kconfig
>>> index 8b12e6e..d3966d0 100644
>>> --- a/drivers/mtd/nand/Kconfig
>>> +++ b/drivers/mtd/nand/Kconfig
>>> @@ -334,7 +334,7 @@ config MTD_NAND_ATMEL_ECC_NONE
>>> endchoice
>>>
>>> config MTD_NAND_PXA3xx
>>> - bool "Support for NAND flash devices on PXA3xx"
>>> + tristate "Support for NAND flash devices on PXA3xx"
>>> depends on MTD_NAND && PXA3xx
>>> help
>>> This enables the driver for the NAND flash device found on
>>> diff --git a/drivers/mtd/nand/pxa3xx_nand.c b/drivers/mtd/nand/pxa3xx_nand.c
>>> index cc55cbc..628ba08 100644
>>> --- a/drivers/mtd/nand/pxa3xx_nand.c
>>> +++ b/drivers/mtd/nand/pxa3xx_nand.c
>>> @@ -123,6 +123,7 @@ struct pxa3xx_nand_info {
>>>
>>> struct clk *clk;
>>> void __iomem *mmio_base;
>>> + struct resource *res;
>>>
>>> unsigned int buf_start;
>>> unsigned int buf_count;
>>> @@ -1079,6 +1080,7 @@ static int pxa3xx_nand_probe(struct platform_device *pdev)
>>>
>>> this = &info->nand_chip;
>>> mtd->priv = info;
>>> + mtd->owner = THIS_MODULE;
>>>
>>> info->clk = clk_get(&pdev->dev, NULL);
>>> if (IS_ERR(info->clk)) {
>>> @@ -1125,6 +1127,7 @@ static int pxa3xx_nand_probe(struct platform_device *pdev)
>>> goto fail_put_clk;
>>> }
>>>
>>> + info->res = r;
>>> info->mmio_base = ioremap(r->start, r->end - r->start + 1);
>>> if (info->mmio_base == NULL) {
>>> dev_err(&pdev->dev, "ioremap() failed\n");
>>> @@ -1199,6 +1202,13 @@ static int pxa3xx_nand_remove(struct platform_device *pdev)
>>> info->data_buff, info->data_buff_phys);
>>> } else
>>> kfree(info->data_buff);
>>> +
>>> + iounmap(info->mmio_base);
>>> + release_mem_region(info->res->start, info->res->end - info->res->start + 1);
>> resource_size() is probably better for the second argument.
>>
>
> And maybe we don't even need to introduce the 'info->res', which is
> always valid by platform_get_resource() again in _remove().
Ok.
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2009-01-20 7:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 11:27 [PATCH] MTD: NAND: pxa3xx_nand: allow building as module Mike Rapoport
2009-01-19 11:40 ` Ben Dooks
2009-01-20 3:16 ` Eric Miao
2009-01-20 7:21 ` Mike Rapoport [this message]
2009-01-20 7:33 ` Mike Rapoport
2009-01-20 7:33 ` [PATCH] MTD: NAND: pxa3xx_nand: use resource_size instead of 'r->end - r->start + 1' Mike Rapoport
2009-01-20 7:33 ` [PATCH] MTD: NAND: pxa3xx_nand: allow building as module Mike Rapoport
2009-01-20 7:33 ` [PATCH] MTD: NAND: pxa3xx_nand: add ability to keep controller settings defined by OBM/bootloader Mike Rapoport
2009-01-22 7:06 ` Mike Rapoport
2009-01-22 8:03 ` Eric Miao
2009-01-20 9:01 ` [PATCH] MTD: NAND: pxa3xx_nand: allow building as module Eric Miao
2009-01-20 9:01 ` [PATCH] MTD: NAND: pxa3xx_nand: use resource_size instead of 'r->end - r->start + 1' Eric Miao
-- strict thread matches above, loose matches on Subject: below --
2009-02-17 11:54 pxa3xx_nand improvements Mike Rapoport
2009-02-17 11:54 ` [PATCH] MTD: NAND: pxa3xx_nand: allow building as module Mike Rapoport
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=49757B67.8040101@compulab.co.il \
--to=mike@compulab.co.il \
--cc=ben-linux@fluff.org \
--cc=eric.miao@marvell.com \
--cc=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-mtd@lists.infradead.org \
/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