1. 05 4月, 2013 2 次提交
    • A
      mtd: onenand: remove OneNAND simulator · 75d0c374
      Artem Bityutskiy 提交于
      This commit remove OneNAND simulator on the basis that it is useless.
      Signed-off-by: NArtem Bityutskiy <artem.bityutskiy@linux.intel.com>
      Acked-by: NKyungmin Park <kyungmin.park@samsung.com>
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      75d0c374
    • A
      mtd: merge mtdchar module with mtdcore · 660685d9
      Artem Bityutskiy 提交于
      The MTD subsystem has historically tried to be as configurable as possible. The
      side-effect of this is that its configuration menu is rather large, and we are
      gradually shrinking it. For example, we recently merged partitions support with
      the mtdcore.
      
      This patch does the next step - it merges the mtdchar module to mtdcore. And in
      this case this is not only about eliminating too fine-grained separation and
      simplifying the configuration menu. This is also about eliminating seemingly
      useless kernel module.
      
      Indeed, mtdchar is a module that allows user-space making use of MTD devices
      via /dev/mtd* character devices. If users do not enable it, they simply cannot
      use MTD devices at all. They cannot read or write the flash contents. Is it a
      sane and useful setup? I believe not. And everyone just enables mtdchar.
      
      Having mtdchar separate is also a little bit harmful. People sometimes miss the
      fact that they need to enable an additional configuration option to have
      user-space MTD interfaces, and then they wonder why on earth the kernel does
      not allow using the flash? They spend time asking around.
      
      Thus, let's just get rid of this module and make it part of mtd core.
      
      Note, mtdchar had additional configuration option to enable OTP interfaces,
      which are present on some flashes. I removed that option as well - it saves a
      really tiny amount space.
      
      [dwmw2: Strictly speaking, you can mount file systems on MTD devices just
              fine without the mtdchar (or mtdblock) devices; you just can't do
              other manipulations directly on the underlying device. But still I
              agree that it makes sense to make this unconditional. And Yay! we
              get to kill off an instance of checking CONFIG_foo_MODULE, which is
              an abomination that should never happen.]
      Signed-off-by: NArtem Bityutskiy <artem.bityutskiy@linux.intel.com>
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      660685d9
  2. 25 3月, 2012 1 次提交
  3. 25 5月, 2011 1 次提交
  4. 22 2月, 2011 1 次提交
  5. 25 10月, 2010 1 次提交
  6. 02 8月, 2010 1 次提交
  7. 14 5月, 2010 1 次提交
  8. 09 11月, 2009 1 次提交
  9. 20 9月, 2009 1 次提交
    • M
      mtd: onenand: make onenand/generic.c more generic · 778dbcc1
      Magnus Damm 提交于
      Remove the ARM dependency from the generic "onenand" platform device
      driver.  This change makes the driver useful for other architectures as
      well.  Needed for the SuperH kfr2r09 board.
      
      Apart from the obvious Kconfig bits, the most important change is the move
      away from ARM specific includes and platform data.  Together with this
      change the only in-tree board code gets an update, and the driver name is
      also changed gracefully break potential out of tree drivers.
      
      The driver is also updated to allow NULL as platform data together with a
      few changes to make use of resource_size() and dev_name().
      Signed-off-by: NMagnus Damm <damm@igel.co.jp>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Kyungmin Park <kmpark@infradead.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      778dbcc1
  10. 04 9月, 2009 1 次提交
  11. 12 8月, 2008 1 次提交
  12. 02 8月, 2008 1 次提交
  13. 30 6月, 2007 2 次提交
  14. 25 4月, 2007 1 次提交
  15. 20 4月, 2007 1 次提交
  16. 04 10月, 2006 1 次提交
  17. 26 9月, 2006 1 次提交
  18. 12 5月, 2006 1 次提交
    • K
      OneNAND: One-Time Programmable (OTP) support · 493c6460
      Kyungmin Park 提交于
      One Block of the NAND Flash Array memory is reserved as
      a One-Time Programmable Block memory area.
      Also, 1st Block of NAND Flash Array can be used as OTP.
      
      The OTP block can be read, programmed and locked using the same
      operations as any other NAND Flash Array memory block.
      OTP block cannot be erased.
      
      OTP block is fully-guaranteed to be a valid block.
      Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com>
      493c6460
  19. 07 11月, 2005 8 次提交