linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Richard Weinberger <richard@nod.at>
Cc: dwmw2@infradead.org, kyungmin.park@samsung.com,
	artem.bityutskiy@linux.intel.com, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MTD: Refine HAS_IOMEM dependency
Date: Tue, 31 Jan 2012 23:46:01 +0100	[thread overview]
Message-ID: <4F286F29.2010605@nod.at> (raw)
In-Reply-To: <1327512102-22447-1-git-send-email-richard@nod.at>

Am 25.01.2012 18:21, schrieb Richard Weinberger:
> Making the entire mtd subsystem depend on HAS_IOMEM is a bit overkill.
> HAS_IOMEM is only needed for real devices drivers.
> nandsim and friends are perfectly usable on systems without IO memory.
>
> I'm my case I'm using nandsim on UML to do some UBI and JFFS2 development.
>
> Signed-off-by: Richard Weinberger<richard@nod.at>
> ---
>   drivers/mtd/Kconfig         |    1 -
>   drivers/mtd/devices/Kconfig |    1 +
>   drivers/mtd/maps/Kconfig    |    1 +
>   drivers/mtd/nand/Kconfig    |    2 ++
>   drivers/mtd/onenand/Kconfig |    1 +
>   5 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig
> index 1be6218..bfbd62c 100644
> --- a/drivers/mtd/Kconfig
> +++ b/drivers/mtd/Kconfig
> @@ -1,6 +1,5 @@
>   menuconfig MTD
>   	tristate "Memory Technology Device (MTD) support"
> -	depends on HAS_IOMEM
>   	help
>   	  Memory Technology Devices are flash, RAM and similar chips, often
>   	  used for solid state file systems on embedded devices. This option
> diff --git a/drivers/mtd/devices/Kconfig b/drivers/mtd/devices/Kconfig
> index 37b05c3..8d3dac4 100644
> --- a/drivers/mtd/devices/Kconfig
> +++ b/drivers/mtd/devices/Kconfig
> @@ -1,5 +1,6 @@
>   menu "Self-contained MTD device drivers"
>   	depends on MTD!=n
> +	depends on HAS_IOMEM
>
>   config MTD_PMC551
>   	tristate "Ramix PMC551 PCI Mezzanine RAM card support"
> diff --git a/drivers/mtd/maps/Kconfig b/drivers/mtd/maps/Kconfig
> index 6c5c431..8af67cf 100644
> --- a/drivers/mtd/maps/Kconfig
> +++ b/drivers/mtd/maps/Kconfig
> @@ -1,5 +1,6 @@
>   menu "Mapping drivers for chip access"
>   	depends on MTD!=n
> +	depends on HAS_IOMEM
>
>   config MTD_COMPLEX_MAPPINGS
>   	bool "Support non-linear mappings of flash chips"
> diff --git a/drivers/mtd/nand/Kconfig b/drivers/mtd/nand/Kconfig
> index 31b034b..80de7b3 100644
> --- a/drivers/mtd/nand/Kconfig
> +++ b/drivers/mtd/nand/Kconfig
> @@ -246,6 +246,7 @@ config MTD_NAND_BCM_UMI_HWCS
>   config MTD_NAND_DISKONCHIP
>   	tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
>   	depends on EXPERIMENTAL
> +	depends on HAS_IOMEM
>   	select REED_SOLOMON
>   	select REED_SOLOMON_DEC16
>   	help
> @@ -431,6 +432,7 @@ config MTD_NAND_GPMI_NAND
>
>   config MTD_NAND_PLATFORM
>   	tristate "Support for generic platform NAND driver"
> +	depends on HAS_IOMEM
>   	help
>   	  This implements a generic NAND driver for on-SOC platform
>   	  devices. You will need to provide platform-specific functions
> diff --git a/drivers/mtd/onenand/Kconfig b/drivers/mtd/onenand/Kconfig
> index 772ad29..91467bb 100644
> --- a/drivers/mtd/onenand/Kconfig
> +++ b/drivers/mtd/onenand/Kconfig
> @@ -1,6 +1,7 @@
>   menuconfig MTD_ONENAND
>   	tristate "OneNAND Device Support"
>   	depends on MTD
> +	depends on HAS_IOMEM
>   	help
>   	  This enables support for accessing all type of OneNAND flash
>   	  devices. For further information see

Ping?

Thanks,
//richard

  reply	other threads:[~2012-01-31 22:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 17:21 [PATCH] MTD: Refine HAS_IOMEM dependency Richard Weinberger
2012-01-31 22:46 ` Richard Weinberger [this message]
2012-02-02  9:07 ` Artem Bityutskiy
2012-02-02  9:11   ` Richard Weinberger

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=4F286F29.2010605@nod.at \
    --to=richard@nod.at \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).