1. 14 Jul, 2009 1 commit
  2. 13 May, 2009 1 commit
    • Carl-Daniel Hailfinger's avatar
      There are various reasons why a SPI command can fail · 3e9dbea1
      Carl-Daniel Hailfinger authored
      
      Among others, I have seen the following problems: - The SPI opcode is
      not supported by the controller. ICH-style controllers exhibit this if
      SPI config is locked down. - The address in in a prohibited area. This
      can happen on ICH for any access (BBAR) and for writes in chipset write
      protected areas. - There is no SPI controller.
      
      Introduce separate error codes for unsupported opcode and prohibited
      address.
      
      Add the ability to adjust REMS and RES addresses to the minium supported
      read address with the help of spi_get_valid_read_addr(). That function
      needs to call SPI controller specific functions like reading BBAR on
      ICH.
      
      Corresponding to flashrom svn r500.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarUwe Hermann <uwe@hermann-uwe.de>
      3e9dbea1
  3. 28 Nov, 2008 3 commits
  4. 15 Nov, 2008 1 commit
    • Carl-Daniel Hailfinger's avatar
      The AT25 and AT26 series SPI chips from Atmel are plain EEPROMs · d54ef6e7
      Carl-Daniel Hailfinger authored
      
      The AT45 series SPI chips are DataFlash EEPROMs which means they have
      odd (non-power-of-two) sector sizes, but some of the DataFlash chips can
      be configured or ordered with power-of-two sector sizes.
      
      Add probe support for the following Atmel SPI chips:
      AT25DF021
      AT25DF041A
      AT25DF081
      AT25DF161
      AT25DF321A
      AT25DF641
      AT25F512B
      AT25FS010
      AT25FS040
      AT26DF041
      AT26DF081A
      AT26DF161
      AT26DF161A
      AT26DF321
      AT26F004
      AT45CS1282
      AT45DB011D
      AT45DB021D
      AT45DB041D
      AT45DB081D
      AT45DB161D
      AT45DB321C
      AT45DB321D
      AT45DB642D
      
      Add an explanation why the following chips can't be probed:
      AT45BR3214B
      AT45D011
      AT45D021A
      AT45D041A
      AT45D081A
      AT45D161
      AT45DB011
      AT45DB011B
      AT45DB021A
      AT45DB021B
      AT45DB041A
      AT45DB081A
      AT45DB161
      AT45DB161B
      AT45DB321
      AT45DB321B
      AT45DB642
      
      Add the ID, but no probing function for this chip:
      AT25F512A
      
      Corresponding to flashrom svn r342 and coreboot v2 svn r3754.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Tested-by: default avatarJesse Brandeburg <jesse.brandeburg@intel.com>
      Tested-by: default avatarAndriy Gapon <avg@icyb.net.ua>
      Acked-by: default avatarMyles Watson <mylesgw@gmail.com>
      d54ef6e7
  5. 07 Jul, 2008 1 commit
    • Peter Stuge's avatar
      Trivial SPI cleanups · f83221b6
      Peter Stuge authored
      
      While writing a new SPI driver I fixed some things in the SPI code:
      All calls to spi_command() had unneccessary #define duplications, and in some
      cases the read count define could theoretically become harmful because NULL was
      passed for the read buffer. Avoid a crash, should someone change the #defines.
      
      I also noticed that the only caller of spi_page_program() was the it87 driver,
      and spi_page_program() could only call back into the it87 driver. Removed the
      function for easier-to-follow code and made it8716f_spi_page_program() static.
      The ichspi driver's static page functions are already static.
      
      Corresponding to flashrom svn r302 and coreboot v2 svn r3418.
      Signed-off-by: default avatarPeter Stuge <peter@stuge.se>
      Acked-by: default avatarPeter Stuge <peter@stuge.se>
      f83221b6
  6. 15 May, 2008 1 commit
  7. 13 May, 2008 1 commit