27 Feb, 2014

1 commit


26 Feb, 2014

1 commit


25 Feb, 2014

2 commits

  • Use first four characters for phy_type comparison. Strcmp() should not
    be used to check the phy_type string which maybe parsed by hwconfig_subarg().
    Hwconfig_subarg() returns part of hwconfig string starting from
    phy_type value till the end of the string. Since phy_type could be
    either "utmi" or "ulpi", strncmp() should be used so that a comparison
    of "utmi;fsl_ddr:bank_intlv=auto" with "utmi" will succeed.

    Signed-off-by: Shaohui Xie
    Signed-off-by: Nikhil Badola
    Reviewed-by: York Sun

    Nikhil Badola
     
  • Function "genphy_parse_link()" used "if (mii_reg & BMSR_ANEGCAPABLE)" before
    while "if (phydev->supported & SUPPORTED_Autoneg)" now.
    So assign "phydev->supported" to "phydev->drv->features" for ar8031/8033
    to enable autonegotiation.

    Signed-off-by: Zhao Qiang
    Reviewed-by: York Sun

    Zhao Qiang
     

24 Feb, 2014

1 commit


23 Feb, 2014

3 commits


22 Feb, 2014

4 commits

  • This patch fixes the following warning messages coming out of
    'drivers/net/smc91111.h' when compiled for 'vexpress_aemv8a':

    warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]

    Currently this issue seems to surface when SMSC is compiled for 64-bit
    ARMv8 platforms, so the change is protected under CONFIG_ARM64, so that
    it doesn't break other existing platforms.

    In addition this patch tries to fix some checkpatch errors and warnings
    (others related to camel-casing and volatile usage will be addressed
    by a later patch).

    This fix has been tested on both ARMv8 foundation model v1 and v2.

    Signed-off-by: Bhupesh Sharma

    Bhupesh Sharma
     
  • Freescale LayerScape SoCs support controller interleaving on 256 byte size.
    This interleaving is mandoratory.

    Signed-off-by: York Sun

    York Sun
     
  • DDR base address has been the same from the view of core and DDR
    controllers. This has changed for Freescale ARM-based SoCs. Controllers
    setup DDR memory in a contiguous space and cores view it at separated
    locations.

    Signed-off-by: York Sun

    York Sun
     
  • Initially it was believed the DDR controller on Freescale ARM would have
    big endian. But some platform will have little endian.

    Signed-off-by: York Sun

    York Sun
     

21 Feb, 2014

7 commits


20 Feb, 2014

14 commits

  • Conflicts:
    Makefile
    drivers/net/npe/Makefile

    These two conflicts arise from commit 0b2d3f20
    ("ARM: NET: Remove the IXP NPE ethernet driver") and are
    resolved by deleting the drivers/net/npe/Makefile file
    and removing the CONFIG_IXP4XX_NPE line from Makefile.

    Albert ARIBAUD
     
  • As soon as all boards have their CONFIG_SYS_I2C_BASE defined in
    configuration files instead of "asm/arch/hardware.h" it's safe to remove
    the inclusion in question and make driver platform-independent.

    Cc: Tom Rini
    Cc: Heiko Schocher
    Cc: Stefan Roese
    Cc: Vipin Kumar
    Cc: Armando Visconti

    Signed-off-by: Alexey Brodkin

    Alexey Brodkin
     
  • Adds support for set-speed on the OMAP24xx I2C Adapter.

    Changes to omap24_i2c_write(...) for polling ARDY Bit from IRQ-Status.
    Otherwise on a subsequent call the transfer of last byte from the
    predecessor is aborted and therefore lost. For exmaple when
    i2c_write(...) is followed by a i2c_setspeed(...) (which has to
    deactivate and activate master for changing psc,...).

    Minor cosmetical changes.

    Signed-off-by: Hannes Petermaier
    Cc: Heiko Schocher

    Hannes Petermaier
     
  • Make sure the I2C write queue is empty before leaving the mxs_i2c_write().
    If we start and I2C write and only wait for ACK, the MXS I2C IP block may
    enter next operation while still processing the write aftermath internally.
    This will in turn disrupt one or more subsequent transfer(s).

    A testcase for this issue is as such. This testcase is also interesting because
    the first I2C_WRITE which becomes disruptive happens in the 'i2c read' command.
    The 'i2c read' command first uses I2C_WRITE to send I2C address of the chip and
    then uses I2C_READ to read data from the chip. After this command completes, the
    'i2c probe' will use sequence of I2C_WRITE commands to probe the I2C bus. The
    problem is that the first I2C_WRITE disrupted the I2C IP block operation and
    this sideeffect propagates all the way to this next I2C_WRITE used by the 'i2c
    probe' call. The result is the 'i2c probe' receives an ACK on I2C address 0x00,
    even if this ACK was owned by the previous I2C_WRITE operation. Note that the
    'i2c read' command must read from a valid I2C chip address.

    Wrong:
    > i2c probe
    Valid chip addresses: 50 51
    > i2c read 0x50 0x0.2 0x10 0x42000000
    > i2c probe
    Valid chip addresses: 00 50 51

    With this patch
    > i2c probe
    Valid chip addresses: 50 51
    > i2c read 0x50 0x0.2 0x10 0x42000000
    > i2c probe
    Valid chip addresses: 50 51

    Signed-off-by: Marek Vasut
    Cc: Heiko Schocher
    Cc: Fabio Estevam

    Marek Vasut
     
  • Enhance the DesignWare I2C driver to support address length more
    than 1 byte. This enhancement is required as some I2C slave
    device such as EEPROM chip might have 16 bit address byte.

    Signed-off-by: Chin Liang See
    Acked-by: Alexey Brodkin
    Cc: Tom Rini
    cc: Armando Visconti
    Cc: Stefan Roese
    Cc: Albert ARIBAUD
    Cc: Heiko Schocher

    Chin Liang See
     
  • add support for bootcounter on an i2c device. And add a
    README for all bootcounter options.

    Signed-off-by: Heiko Schocher

    Heiko Schocher
     
  • The ADI twi peripheral is not binding to Blackfin processor only.
    Access i2c registers by standard io functions.
    Fix coding style.

    Signed-off-by: Scott Jiang
    Signed-off-by: Sonic Zhang

    Scott Jiang
     
  • The ADI twi peripheral is not binding to Blackfin processor only.
    Change to a generic name.

    Signed-off-by: Sonic Zhang

    Sonic Zhang
     
  • Signed-off-by: Sonic Zhang

    Sonic Zhang
     
  • Signed-off-by: Sonic Zhang

    Sonic Zhang
     
  • Initialize the second i2c controller.

    Signed-off-by: Michael Burr
    Signed-off-by: Michal Simek

    Michael Burr
     
  • Fixed bug with alen == 0 in 'i2c_write', 'i2c_read'
    Further minor corrections:
    - Write 'address' register before 'data' register.
    - Write 'transfer_size' register before 'address' register.

    Signed-off-by: Michael Burr
    Signed-off-by: Michal Simek

    Michael Burr
     
  • Now we are ready to switch over to real Kbuild.

    This commit disables temporary scripts:
    scripts/{Makefile.build.tmp, Makefile.host.tmp}
    and enables real Kbuild scripts:
    scripts/{Makefile.build,Makefile.host,Makefile.lib}.

    This switch is triggered by the line in scripts/Kbuild.include
    -build := -f $(if $(KBUILD_SRC),$(srctree)/)scripts/Makefile.build.tmp obj
    +build := -f $(if $(KBUILD_SRC),$(srctree)/)scripts/Makefile.build obj

    We need to adjust some build scripts for U-Boot.
    But smaller amount of modification is preferable.

    Additionally, we need to fix compiler flags which are
    locally added or removed.

    In Kbuild, it is not allowed to change CFLAGS locally.
    Instead, ccflags-y, asflags-y, cppflags-y,
    CFLAGS_$(basetarget).o, CFLAGS_REMOVE_$(basetarget).o
    are prepared for that purpose.

    Signed-off-by: Masahiro Yamada
    Tested-by: Gerhard Sittig

    Masahiro Yamada
     
  • This commit changes the working directory
    where the build process occurs.

    Before this commit, build process occurred under the source
    tree for both in-tree and out-of-tree build.

    That's why we needed to add $(obj) prefix to all generated
    files in makefiles like follows:
    $(obj)u-boot.bin: $(obj)u-boot

    Here, $(obj) is empty for in-tree build, whereas it points
    to the output directory for out-of-tree build.

    And our old build system changes the current working directory
    with "make -C " syntax when descending into the
    sub-directories.

    On the other hand, Kbuild uses a different idea
    to handle out-of-tree build and directory descending.

    The build process of Kbuild always occurs under the output tree.
    When "O=dir/to/store/output/files" is given, the build system
    changes the current working directory to that directory and
    restarts the make.

    Kbuild uses "make -f $(srctree)/scripts/Makefile.build obj="
    syntax for descending into sub-directories.
    (We can write it like "make $(obj)=" with a shorthand.)
    This means the current working directory is always the top
    of the output directory.

    Signed-off-by: Masahiro Yamada
    Tested-by: Gerhard Sittig

    Masahiro Yamada
     

19 Feb, 2014

7 commits