Brian Norris | 1 Jun 2011 01:31
Picon

[PATCH 6/8] mtd: nand: rename CREATE_EMPTY bbt flag with proper prefix

According to our new prefix rules, we should rename NAND_CREATE_EMPTY_BBT
with a NAND_BBT prefix, i.e., NAND_BBT_CREATE_EMPTY.

Signed-off-by: Brian Norris <computersforpeace <at> gmail.com>
---
 drivers/mtd/nand/nand_bbt.c |    2 +-
 include/linux/mtd/bbm.h     |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/mtd/nand/nand_bbt.c b/drivers/mtd/nand/nand_bbt.c
index 2e4e259..9af703d 100644
--- a/drivers/mtd/nand/nand_bbt.c
+++ b/drivers/mtd/nand/nand_bbt.c
 <at>  <at>  -970,7 +970,7  <at>  <at>  static int check_create(struct mtd_info *mtd, uint8_t *buf, struct nand_bbt_desc
 			continue;

 		/* Create the table in memory by scanning the chip(s) */
-		if (!(this->bbt_options & NAND_CREATE_EMPTY_BBT))
+		if (!(this->bbt_options & NAND_BBT_CREATE_EMPTY))
 			create_bbt(mtd, buf, bd, chipsel);

 		td->version[i] = 1;
diff --git a/include/linux/mtd/bbm.h b/include/linux/mtd/bbm.h
index 3cf4a8a..0fa030a 100644
--- a/include/linux/mtd/bbm.h
+++ b/include/linux/mtd/bbm.h
 <at>  <at>  -92,7 +92,7  <at>  <at>  struct nand_bbt_descr {
  * layout or if this information is already purged. Must be used in conjunction
  * with NAND_BBT_CREATE.
  */
(Continue reading)

Brian Norris | 1 Jun 2011 01:31
Picon

[PATCH 5/8] mtd: nand: move NAND_CREATE_EMPTY_BBT flag

The NAND_CREATE_EMPTY_BBT flag was added by commit:
  453281a973c10bce941b240d1c654d536623b16b
  mtd: nand: introduce NAND_CREATE_EMPTY_BBT
This flag is not used within the kernel and not explained well, so I
took the liberty to edit its comments.

Also, this is a BBT-related flag (and closely tied with NAND_BBT_CREATE)
so I'm moving it to bbm.h next to NAND_BBT_CREATE, thus requiring that
we use the flag in nand_chip.bbt_options, *not* in nand_chip.options.

Signed-off-by: Brian Norris <computersforpeace <at> gmail.com>
---
 drivers/mtd/nand/nand_bbt.c |    2 +-
 include/linux/mtd/bbm.h     |    7 +++++++
 include/linux/mtd/nand.h    |    2 --
 3 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/drivers/mtd/nand/nand_bbt.c b/drivers/mtd/nand/nand_bbt.c
index dfea9fd..2e4e259 100644
--- a/drivers/mtd/nand/nand_bbt.c
+++ b/drivers/mtd/nand/nand_bbt.c
 <at>  <at>  -970,7 +970,7  <at>  <at>  static int check_create(struct mtd_info *mtd, uint8_t *buf, struct nand_bbt_desc
 			continue;

 		/* Create the table in memory by scanning the chip(s) */
-		if (!(this->options & NAND_CREATE_EMPTY_BBT))
+		if (!(this->bbt_options & NAND_CREATE_EMPTY_BBT))
 			create_bbt(mtd, buf, bd, chipsel);

 		td->version[i] = 1;
(Continue reading)

Brian Norris | 1 Jun 2011 01:31
Picon

[PATCH 3/8] mtd: nand: consolidate redundant flash-based BBT flags

This patch works with the following three flags from two headers (nand.h
and bbm.h):
  (1) NAND_USE_FLASH_BBT (nand.h)
  (2) NAND_USE_FLASH_BBT_NO_OOB (nand.h)
  (3) NAND_BBT_NO_OOB (bbm.h)

These flags are all related and interdependent, yet they were in
different headers. Flag (2) is simply the combination of (1) and (3) and
can be eliminated.

This patch accomplishes the following:
  * eliminate NAND_USE_FLASH_BBT_NO_OOB (i.e., flag (2))
  * move NAND_USE_FLASH_BBT (i.e., flag (1)) to bbm.h

It's important to note that because (1) and (3) are now both found in
bbm.h, they should NOT be used in the "nand_chip.options" field.

I removed a small section from the mtdnand DocBook because it referes to
NAND_USE_FLASH_BBT in nand.h, which has been moved to bbm.h.

Signed-off-by: Brian Norris <computersforpeace <at> gmail.com>
---
 Documentation/DocBook/mtdnand.tmpl             |    5 +----
 arch/arm/mach-davinci/board-da830-evm.c        |    2 +-
 arch/arm/mach-davinci/board-da850-evm.c        |    2 +-
 arch/arm/mach-davinci/board-dm355-evm.c        |    2 +-
 arch/arm/mach-davinci/board-dm355-leopard.c    |    2 +-
 arch/arm/mach-davinci/board-dm365-evm.c        |    2 +-
 arch/arm/mach-davinci/board-dm644x-evm.c       |    2 +-
 arch/arm/mach-davinci/board-mityomapl138.c     |    3 ++-
(Continue reading)

Brian Norris | 1 Jun 2011 01:31
Picon

[PATCH 8/8] mtd: nand: improve comment on NAND_BBT_DYNAMIC_STRUCT

In an attempt to improve the documentation of the BBT code, I am expanding
the comments I left in commit:
    58373ff0afff4cc8ac40608872995f4d87eb72ec
    mtd: nand: more BB Detection refactoring and dynamic scan options

Signed-off-by: Brian Norris <computersforpeace <at> gmail.com>
---
 include/linux/mtd/bbm.h |    6 +++++-
 1 files changed, 5 insertions(+), 1 deletions(-)

diff --git a/include/linux/mtd/bbm.h b/include/linux/mtd/bbm.h
index 57d6a8d..c4eec22 100644
--- a/include/linux/mtd/bbm.h
+++ b/include/linux/mtd/bbm.h
 <at>  <at>  -113,7 +113,11  <at>  <at>  struct nand_bbt_descr {
 /* Do not store flash based bad block table in OOB area; store it in-band */
 #define NAND_BBT_NO_OOB		0x00040000

-/* The nand_bbt_descr was created dynamicaly and must be freed */
+/*
+ * Flag set by nand_create_default_bbt_descr(), marking that the nand_bbt_descr
+ * was allocated dynamicaly and must be freed in nand_release(). Has no meaning
+ * in nand_chip.bbt_options.
+ */
 #define NAND_BBT_DYNAMICSTRUCT	0x80000000

 /* The maximum number of blocks to scan for a bbt */
--

-- 
1.7.0.4
(Continue reading)

Brian Norris | 1 Jun 2011 01:31
Picon

[PATCH 1/8] mtd: nand: remove NAND_BBT_SCANBYTE1AND6 option

This patch reverts most of:
    commit 58373ff0afff4cc8ac40608872995f4d87eb72ec
    mtd: nand: more BB Detection refactoring and dynamic scan options

According to the discussion at:
    http://lists.infradead.org/pipermail/linux-mtd/2011-May/035696.html
the NAND_BBT_SCANBYTE1AND6 flag, although technically valid, can break
some existing ECC layouts that use the 6th byte in the OOB for ECC data.
Furthermore, we apparently do not need to scan both bytes 1 and 6 in
the OOB region of the devices under consideration; instead, we only need
to scan one or the other.

Thus, the NAND_BBT_SCANBYTE1AND6 flag is at best unnecessary and at
worst a regression.

Signed-off-by: Brian Norris <computersforpeace <at> gmail.com>
---
 drivers/mtd/nand/nand_base.c |   29 +++++------------------------
 drivers/mtd/nand/nand_bbt.c  |   32 +-------------------------------
 include/linux/mtd/bbm.h      |    2 --
 3 files changed, 6 insertions(+), 57 deletions(-)

diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
index a46e9bb..456fb34 100644
--- a/drivers/mtd/nand/nand_base.c
+++ b/drivers/mtd/nand/nand_base.c
 <at>  <at>  -410,10 +410,11  <at>  <at>  static int nand_default_block_markbad(struct mtd_info *mtd, loff_t ofs)
 	else {
 		nand_get_device(chip, mtd, FL_WRITING);

(Continue reading)

Brian Norris | 1 Jun 2011 01:31
Picon

[PATCH 0/8] clean-up NAND / BBT code, flags

Hello,

This patch series handles several issues with NAND chip flags and BBT
flags, especially those related to the nand_chip.options and
nand_bbt_descr.options fields. This topic was discussed and reviewed a
bit on the linux-mtd thread found here:
    http://lists.infradead.org/pipermail/linux-mtd/2011-April/035146.html

These changes have affected many drivers in relatively small ways, so
I copied all the maintainers/contributors given by the
scripts/getmaintainer.pl scripts. FYI, this patch set is based on the
mtd-2.6.git repository from linux-mtd.

Also, the first patch:
    mtd: nand: remove NAND_BBT_SCANBYTE1AND6 option
solves the regression issues discussed here:
    http://lists.infradead.org/pipermail/linux-mtd/2011-May/035696.html

Thanks for the review.

Brian

Brian Norris (8):
  mtd: nand: remove NAND_BBT_SCANBYTE1AND6 option
  mtd: nand: separate chip options / bbt_options
  mtd: nand: consolidate redundant flash-based BBT flags
  mtd: nand: rename NAND_USE_FLASH_BBT
  mtd: nand: move NAND_CREATE_EMPTY_BBT flag
  mtd: nand: rename CREATE_EMPTY bbt flag with proper prefix
  mtd: nand: renumber the reorganized flags in nand.h / bbm.h
(Continue reading)

Grant Likely | 1 Jun 2011 01:28
Picon

Re: [PATCH] gpio: ep93xx: move driver to drivers/gpio

On Tue, May 31, 2011 at 4:37 PM, H Hartley Sweeten
<hartleys <at> visionengravers.com> wrote:
> On Tuesday, May 31, 2011 1:41 PM, Grant Likely wrote:
>> On Tue, May 31, 2011 at 1:49 PM, H Hartley Sweeten wrote:
>>> The GPIO driver should reside in drivers/gpio.
>>>
>>> Signed-off-by: H Hartley Sweeten <hsweeten <at> visionengravers.com>
>>> Cc: Ryan Mallon <ryan <at> bluewatersys.com>
>>> Cc: Grant Likely <grant.likely <at> secretlab.ca>
>>>
>>> ---
>>>
>>> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
>>> index 342d634..7307302 100644
>>> --- a/drivers/gpio/Kconfig
>>> +++ b/drivers/gpio/Kconfig
>>>  <at>  <at>  -86,6 +86,13  <at>  <at>  config GPIO_IT8761E
>>>        help
>>>          Say yes here to support GPIO functionality of IT8761E super I/O chip.
>>>
>>> +config GPIO_EP93XX
>>> +       bool "Cirrus EP93xx GPIO support"
>>> +       depends on ARCH_EP93XX
>>> +       default y
>>> +       help
>>> +         Say yes here to support the Cirrus EP93xx GPIO peripheral.
>>> +
>>
>> Do you really want a user-visible Kconfig symbol here?  If it cannot
>> be built as a module, then I suspect that for most on-chip gpio
(Continue reading)

H Hartley Sweeten | 1 Jun 2011 01:36
Favicon

[PATCH v2] gpio: ep93xx: mode driver to drivers/gpio

The GPIO driver should reside in drivers/gpio.

Signed-off-by: H Hartley Sweeten <hsweeten <at> visionengravers.com>
Cc: Ryan Mallon <ryan <at> bluewatersys.com>
Cc: Grant Likely <grant.likely <at> secretlab.ca>

---

v2: Make the Kconfig symbol a silent option, dependent on ARCH_EP93XX

diff --git a/arch/arm/mach-ep93xx/Makefile b/arch/arm/mach-ep93xx/Makefile
index 33ee2c8..6b7c41d 100644
--- a/arch/arm/mach-ep93xx/Makefile
+++ b/arch/arm/mach-ep93xx/Makefile
 <at>  <at>  -1,7 +1,7  <at>  <at> 
 #
 # Makefile for the linux kernel.
 #
-obj-y			:= core.o clock.o dma-m2p.o gpio.o
+obj-y			:= core.o clock.o dma-m2p.o
 obj-m			:=
 obj-n			:=
 obj-			:=
diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
index 342d634..5f87cad 100644
--- a/drivers/gpio/Kconfig
+++ b/drivers/gpio/Kconfig
 <at>  <at>  -86,6 +86,11  <at>  <at>  config GPIO_IT8761E
 	help
 	  Say yes here to support GPIO functionality of IT8761E super I/O chip.
(Continue reading)

Will Drewry | 1 Jun 2011 05:10

[PATCH v3 07/13] arm: select HAVE_SECCOMP_FILTER

Enable support for CONFIG_SECCOMP_FILTER by selecting HAVE_SECCOMP_FILTER by
default.

Signed-off-by: Will Drewry <wad <at> chromium.org>
---
 arch/arm/Kconfig |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 377a7a5..4725fbc 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
 <at>  <at>  -16,6 +16,7  <at>  <at>  config ARM
 	select HAVE_FTRACE_MCOUNT_RECORD if (!XIP_KERNEL)
 	select HAVE_DYNAMIC_FTRACE if (!XIP_KERNEL)
 	select HAVE_FUNCTION_GRAPH_TRACER if (!THUMB2_KERNEL)
+	select HAVE_SECCOMP_FILTER
 	select HAVE_GENERIC_DMA_COHERENT
 	select HAVE_KERNEL_GZIP
 	select HAVE_KERNEL_LZO
--

-- 
1.7.0.4
Bryan Wu | 1 Jun 2011 05:43
Favicon

[RFC] Consolidation: Replace all led drivers in arch/arm to leds trigger drivers

Russell,

After a quick review the led drivers in arch/arm, I found most of them
are based on arch/arm/kernel/leds.c driver, which is a specific led
event driver.
In mainline 3.0-rc1:
--
linux-2.6$ find arch/arm/ -name *led*
arch/arm/mach-ks8695/leds.c
arch/arm/mach-sa1100/leds.c
arch/arm/mach-sa1100/leds-cerf.c
arch/arm/mach-sa1100/leds-lart.c
arch/arm/mach-sa1100/leds-hackkit.c
arch/arm/mach-sa1100/leds.h
arch/arm/mach-sa1100/leds-assabet.c
arch/arm/mach-sa1100/leds-simpad.c
arch/arm/mach-sa1100/leds-badge4.c
arch/arm/mach-integrator/leds.c
arch/arm/include/asm/leds.h
arch/arm/mach-s3c2410/include/mach/leds-gpio.h
arch/arm/mach-omap1/leds.c
arch/arm/mach-omap1/leds.h
arch/arm/mach-omap1/leds-h2p2-debug.c
arch/arm/mach-omap1/leds-osk.c
arch/arm/mach-omap1/leds-innovator.c
arch/arm/mach-pxa/leds.c
arch/arm/mach-pxa/leds-mainstone.c
arch/arm/mach-pxa/leds-lubbock.c
arch/arm/mach-pxa/leds-idp.c
arch/arm/mach-pxa/leds.h
(Continue reading)


Gmane