Eric Lee / smarc-uboot

01 Aug, 2017

1 commit

  • 7b3c4c3a5   dm: console: Check for serial devices properly ... Browse Code »

    With driver model the serial device is often not called "serial". Mark
    driver-model stdio devices so that they can be detected and we can look up
    the uclass. This is a more reliable way of finding out whether the console
    is connected to a serial device or not.

    Signed-off-by: Simon Glass

    Simon Glass
     

24 Oct, 2016

1 commit

05 Nov, 2015

2 commits

06 Mar, 2015

1 commit

  • 5294e9783   stdio: extend "name" to 32 symbols ... Browse Code »

    With limit of 16 symbols very simple device names derived drom device
    tree description could not be displayed correctly.

    For example "serial0@0xc0fc1000" will be truncated to sensless
    "serial0@0xc0fc10" - note dropped tariling zeros.

    Signed-off-by: Alexey Brodkin
    Cc: Simon Glass
    Cc: Tom Rini
    Reviewed-by: Simon Glass

    Alexey Brodkin
     

06 Oct, 2014

1 commit

11 Sep, 2014

1 commit

  • 9fb02491f   dm: Make driver model available before board_init() ... Browse Code »

    For some boards board_init() will change GPIOs, so we need to have driver
    model available before then. Adjust the board init to arrange this, but
    enable it for driver model only, just to be safe.

    This does create additional #ifdef logic, but it is safer than trying to
    make a pervasive change which may cause some boards to break.

    Signed-off-by: Simon Glass

    Simon Glass
     

23 Jul, 2014

2 commits

  • d97143a67   stdio: Provide functions to add/remove devices using stdio_dev ... Browse Code »

    The current functions for adding and removing devices require a device name.
    This is not convenient for driver model, which wants to store a pointer to
    the relevant device. Add new functions which provide this feature and adjust
    the old ones to call these.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • 709ea543b   stdio: Pass device pointer to stdio methods ... Browse Code »
    44

    At present stdio device functions do not get any clue as to which stdio
    device is being acted on. Some implementations go to great lengths to work
    around this, such as defining a whole separate set of functions for each
    possible device.

    For driver model we need to associate a stdio_dev with a device. It doesn't
    seem possible to continue with this work-around approach.

    Instead, add a stdio_dev pointer to each of the stdio member functions.

    Note: The serial drivers have the same problem, but it is not strictly
    necessary to fix that to get driver model running. Also, if we convert
    serial over to driver model the problem will go away.

    Code size increases by 244 bytes for Thumb2 and 428 for PowerPC.

    22: stdio: Pass device pointer to stdio methods
    arm: (for 2/2 boards) all +244.0 bss -4.0 text +248.0
    powerpc: (for 1/1 boards) all +428.0 text +428.0

    Signed-off-by: Simon Glass
    Acked-by: Marek Vasut
    Reviewed-by: Marek Vasut

    Simon Glass
     

13 Aug, 2013

1 commit

24 Jul, 2013

1 commit

04 Feb, 2013

1 commit

  • e70fb539a   serial: arm_dcc: Remove CONFIG_ARM_DCC_MULTI option ... Browse Code »

    CONFIG_ARM_DCC_MULTI should be also removed in the patch
    "serial: Remove CONFIG_SERIAL_MULTI from serial drivers"
    (sha1: a3827250606895ec2dd4b8d867342b7cabf3692f)
    Because the driver defines serial_* functions
    which cause conflict with serial.c (multiple definition of serial_*)

    Removing CONFIG_SERIAL_MULTI function also require to define
    default_serial_console for cases where another serial driver
    is not available in the system.

    Signed-off-by: Michal Simek
    Acked-by: Marek Vasut

    Michal Simek
     

01 Dec, 2012

1 commit

  • 98ab435f7   x86: Add CBMEM console driver for coreboot ... Browse Code »

    This patch builds upon the recently introduced CBMEM console
    feature of coreboot.

    CBMEM console uses a memry area allocated by coreboot to store
    the console output. The memory area has a certain structure,
    which allows to determine where the buffer is, the buffer size
    and the location of the pointer in the buffer. This allows
    different phases of the firmware (rom based coreboot, ram based
    coreboot, u-boot after relocation with this change) to keep
    adding text to the same buffer.

    Note that this patch introduces a new console driver and adds the
    driver to the list of drivers to be used for console output, i.e.
    it engages only after u-boot relocates. Usiong CBMEM console for
    capturing the pre-relocation console output will be done under a
    separate change.

    >From Linux, run the cbmem.py utility (which is a part of the coreboot
    package) to see the output, e.g.:

    vvvvvvvvvvvvvvvvv
    SCSI: AHCI 0001.0300 32 slots 6 ports ? Gbps 0xf impl SATA mode
    flags: 64bit ilck stag led pmp pio
    ...
    Magic signature found
    Kernel command line: "cros_secure quiet loglevel=1 console=tty2...
    ^^^^^^^^^^^^^^^^^

    Note that the entire u-boot output fits into the buffer only if
    the coreboot log level is reduced from the most verbose. Ether
    the buffer size will have to be increased, or the coreboot
    verbosity permanently reduced.

    Signed-off-by: Vadim Bendebury
    Signed-off-by: Simon Glass

    Vadim Bendebury
     

23 Jun, 2011

1 commit

  • 566e5cf45   ARM: drop unsupported 'trab' board ... Browse Code »

    The 'trab' board configuration is broken, and there is nobody who is
    interested and willing to fix it. Drop it.

    This includes support for VFD displays which have always been used by
    this board only.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

29 Nov, 2010

1 commit

19 Jul, 2009

1 commit

18 Jul, 2009

1 commit

  • 52cb4d4fb   stdio/device: rework function naming convention ... Browse Code »

    So far the console API uses the following naming convention:

    ======Extract======
    typedef struct device_t;

    int device_register (device_t * dev);
    int devices_init (void);
    int device_deregister(char *devname);
    struct list_head* device_get_list(void);
    device_t* device_get_by_name(char* name);
    device_t* device_clone(device_t *dev);
    =======

    which is too generic and confusing.

    Instead of using device_XX and device_t we change this
    into stdio_XX and stdio_dev

    This will also allow to add later a generic device mechanism in order
    to have support for multiple devices and driver instances.

    Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD

    Edited commit message.

    Signed-off-by: Wolfgang Denk

    Jean-Christophe PLAGNIOL-VILLARD