1. 11 Jun, 2008 16 commits
  2. 10 Jun, 2008 10 commits
  3. 09 Jun, 2008 2 commits
  4. 04 Jun, 2008 1 commit
  5. 03 Jun, 2008 11 commits
    • Wolfgang Denk's avatar
    • Tor Krill's avatar
      Fix incorrect switch for IF_TYPE in part.c · 8ec6e332
      Tor Krill authored
      Use correct field in block_dev_desc_t when writing interface type in
      dev_print. Error introduced in 574b3195
      Also added fix from Martin Krause
      Signed-off-by: default avatarTor Krill <tor@excito.com>
    • Andre Schwarz's avatar
    • Peter Tyser's avatar
      Additional fix to readline_into_buffer() with CONFIG_CMDLINE_EDITING before relocating · 35ef877f
      Peter Tyser authored
      Removed unneeded command line history initialization.  Also, the original
      code would access the 'initted' variable before relocation to SDRAM
      which resulted in erratic behavior since the bss is not initialized when
      executing from flash.
      Signed-off-by: default avatarPeter Tyser <ptyser@xes-inc.com>
    • Grant Erickson's avatar
      PPC4xx: Simplified post_word_{load, store} · 22f371b6
      Grant Erickson authored
      This patch simplifies post_word_{load,store} by using the preprocessor
      to eliminate redundant, copy-and-pasted code.
      Signed-off-by: default avatarGrant Erickson <gerickson@nuovations.com>
    • Stefan Roese's avatar
      DTT: Issue one-shot command on AD7414 (LM75 code) to read temp · 4d91d1df
      Stefan Roese authored
      On AD7414 the first value upon bootup is not read correctly.
      This is most likely because of the 800ms update time of the
      temp register in normal update mode. To get current values
      each time we issue the "dtt" command including upon powerup
      we switch into one-short mode.
      This patch fixes the problem on AD7414 equipped boards (Sequoia,
      Canyonlands etc), that temp value printed in the bootup log was
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
    • Haavard Skinnemoen's avatar
      Add support for environment in SPI flash · 8c66497e
      Haavard Skinnemoen authored
      This is pretty incomplete...it doesn't handle reading the environment
      before relocation, it doesn't support redundant environment, and it
      doesn't support embedded environment. But apart from that, it does
      seem to work.
      Signed-off-by: default avatarHaavard Skinnemoen <haavard.skinnemoen@atmel.com>
    • Haavard Skinnemoen's avatar
      SPI Flash: Add "sf" command · b6368467
      Haavard Skinnemoen authored
      This adds a new command, "sf" which can be used to manipulate SPI
      flash. Currently, initialization, reading, writing and erasing is
      Signed-off-by: default avatarHaavard Skinnemoen <haavard.skinnemoen@atmel.com>
    • Haavard Skinnemoen's avatar
      SPI Flash subsystem · d25ce7d2
      Haavard Skinnemoen authored
      This adds a new SPI flash subsystem.
      Currently, only AT45 DataFlash in non-power-of-two mode is supported,
      but some preliminary support for other flash types is in place as
      Signed-off-by: default avatarHaavard Skinnemoen <haavard.skinnemoen@atmel.com>
    • Hans-Christian Egtvedt's avatar
      atmel_spi: Driver for the Atmel SPI controller · 60445cb5
      Hans-Christian Egtvedt authored
      This adds a driver for the SPI controller found on most AT91 and AVR32
      chips, implementing the new SPI API.
      Changed in v4:
        - Update to new API
        - Handle zero-length transfers appropriately. The user may send a
          zero-length SPI transfer with SPI_XFER_END set in order to
          deactivate the chip select after a series of transfers with chip
          select active. This is useful e.g. when polling the status
          register of DataFlash.
      Signed-off-by: default avatarHaavard Skinnemoen <hskinnemoen@atmel.com>
    • Haavard Skinnemoen's avatar
      SPI API improvements · d255bb0e
      Haavard Skinnemoen authored
      This patch gets rid of the spi_chipsel table and adds a handful of new
      functions that makes the SPI layer cleaner and more flexible.
      Instead of the spi_chipsel table, each board that wants to use SPI
      gets to implement three hooks:
        * spi_cs_activate(): Activates the chipselect for a given slave
        * spi_cs_deactivate(): Deactivates the chipselect for a given slave
        * spi_cs_is_valid(): Determines if the given bus/chipselect
          combination can be activated.
      Not all drivers may need those extra functions however. If that's the
      case, the board code may just leave them out (assuming they know what
      the driver needs) or rely on the linker to strip them out (assuming
      --gc-sections is being used.)
      To set up communication parameters for a given slave, the driver needs
      to call spi_setup_slave(). This returns a pointer to an opaque
      spi_slave struct which must be passed as a parameter to subsequent SPI
      calls. This struct can be freed by calling spi_free_slave(), but most
      driver probably don't want to do this.
      Before starting one or more SPI transfers, the driver must call
      spi_claim_bus() to gain exclusive access to the SPI bus and initialize
      the hardware. When all transfers are done, the driver must call
      spi_release_bus() to make the bus available to others, and possibly
      shut down the SPI controller hardware.
      spi_xfer() behaves mostly the same as before, but it now takes a
      spi_slave parameter instead of a spi_chipsel function pointer. It also
      got a new parameter, flags, which is used to specify chip select
      behaviour. This may be extended with other flags in the future.
      This patch has been build-tested on all powerpc and arm boards
      involved. I have not tested NIOS since I don't have a toolchain for it
      installed, so I expect some breakage there even though I've tried
      fixing up everything I could find by visual inspection.
      I have run-time tested this on AVR32 ATNGW100 using the atmel_spi and
      DataFlash drivers posted as a follow-up. I'd like some help testing
      other boards that use the existing SPI API.
      But most of all, I'd like some comments on the new API. Is this stuff
      usable for everyone? If not, why?
      Changed in v4:
        - Build fixes for various boards, drivers and commands
        - Provide common struct spi_slave definition that can be extended by
        - Pass a struct spi_slave * to spi_cs_activate and spi_cs_deactivate
        - Make default bus and mode build-time configurable
        - Override default SPI bus ID and mode on mx32ads and imx31_litekit.
      Changed in v3:
        - Add opaque struct spi_slave for controller-specific data associated
          with a slave.
        - Add spi_claim_bus() and spi_release_bus()
        - Add spi_free_slave()
        - spi_setup() is now called spi_setup_slave() and returns a
          struct spi_slave
        - soft_spi now supports four SPI modes (CPOL|CPHA)
        - Add bus parameter to spi_setup_slave()
        - Convert the new i.MX32 SPI driver
        - Convert the new MC13783 RTC driver
      Changed in v2:
        - Convert the mpc8xxx_spi driver and the mpc8349emds board to the
          new API.
      Signed-off-by: default avatarHaavard Skinnemoen <hskinnemoen@atmel.com>
      Tested-by: default avatarGuennadi Liakhovetski <lg@denx.de>