Commit 3bde6888c0d74d716af7381c2ad9faee77aaec8f

Authored by Masahiro Yamada
Committed by Tom Rini
1 parent 90b7caaf55

README: remove description about driver model configuration options (again)

The Driver Model description in README was removed by commit
65eb659e56fa (README: remove description about driver model
configuration options), and was revived by mistake by commit
b79dadf846e5 when resolving the conflict.

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Tom Rini <trini@konsulko.com>
Acked-by: Simon Glass <sjg@chromium.org>

Showing 1 changed file with 0 additions and 113 deletions Side-by-side Diff

... ... @@ -705,119 +705,6 @@
705 705 impossible actions will be skipped if the CPU is in NS mode,
706 706 such as ARM architectural timer initialization.
707 707  
708   -- Driver Model
709   - Driver model is a new framework for devices in U-Boot
710   - introduced in early 2014. U-Boot is being progressively
711   - moved over to this. It offers a consistent device structure,
712   - supports grouping devices into classes and has built-in
713   - handling of platform data and device tree.
714   -
715   - To enable transition to driver model in a relatively
716   - painful fashion, each subsystem can be independently
717   - switched between the legacy/ad-hoc approach and the new
718   - driver model using the options below. Also, many uclass
719   - interfaces include compatibility features which may be
720   - removed once the conversion of that subsystem is complete.
721   - As a result, the API provided by the subsystem may in fact
722   - not change with driver model.
723   -
724   - See doc/driver-model/README.txt for more information.
725   -
726   - CONFIG_DM
727   -
728   - Enable driver model. This brings in the core support,
729   - including scanning of platform data on start-up. If
730   - CONFIG_OF_CONTROL is enabled, the device tree will be
731   - scanned also when available.
732   -
733   - CONFIG_CMD_DM
734   -
735   - Enable driver model test commands. These allow you to print
736   - out the driver model tree and the uclasses.
737   -
738   - CONFIG_DM_DEMO
739   -
740   - Enable some demo devices and the 'demo' command. These are
741   - really only useful for playing around while trying to
742   - understand driver model in sandbox.
743   -
744   - CONFIG_SPL_DM
745   -
746   - Enable driver model in SPL. You will need to provide a
747   - suitable malloc() implementation. If you are not using the
748   - full malloc() enabled by CONFIG_SYS_SPL_MALLOC_START,
749   - consider using CONFIG_SYS_MALLOC_SIMPLE. In that case you
750   - must provide CONFIG_SYS_MALLOC_F_LEN to set the size.
751   - In most cases driver model will only allocate a few uclasses
752   - and devices in SPL, so 1KB should be enable. See
753   - CONFIG_SYS_MALLOC_F_LEN for more details on how to enable
754   - it.
755   -
756   - CONFIG_DM_SERIAL
757   -
758   - Enable driver model for serial. This replaces
759   - drivers/serial/serial.c with the serial uclass, which
760   - implements serial_putc() etc. The uclass interface is
761   - defined in include/serial.h.
762   -
763   - CONFIG_DM_GPIO
764   -
765   - Enable driver model for GPIO access. The standard GPIO
766   - interface (gpio_get_value(), etc.) is then implemented by
767   - the GPIO uclass. Drivers provide methods to query the
768   - particular GPIOs that they provide. The uclass interface
769   - is defined in include/asm-generic/gpio.h.
770   -
771   - CONFIG_DM_SPI
772   -
773   - Enable driver model for SPI. The SPI slave interface
774   - (spi_setup_slave(), spi_xfer(), etc.) is then implemented by
775   - the SPI uclass. Drivers provide methods to access the SPI
776   - buses that they control. The uclass interface is defined in
777   - include/spi.h. The existing spi_slave structure is attached
778   - as 'parent data' to every slave on each bus. Slaves
779   - typically use driver-private data instead of extending the
780   - spi_slave structure.
781   -
782   - CONFIG_DM_SPI_FLASH
783   -
784   - Enable driver model for SPI flash. This SPI flash interface
785   - (spi_flash_probe(), spi_flash_write(), etc.) is then
786   - implemented by the SPI flash uclass. There is one standard
787   - SPI flash driver which knows how to probe most chips
788   - supported by U-Boot. The uclass interface is defined in
789   - include/spi_flash.h, but is currently fully compatible
790   - with the old interface to avoid confusion and duplication
791   - during the transition parent. SPI and SPI flash must be
792   - enabled together (it is not possible to use driver model
793   - for one and not the other).
794   -
795   - CONFIG_DM_CROS_EC
796   -
797   - Enable driver model for the Chrome OS EC interface. This
798   - allows the cros_ec SPI driver to operate with CONFIG_DM_SPI
799   - but otherwise makes few changes. Since cros_ec also supports
800   - I2C and LPC (which don't support driver model yet), a full
801   - conversion is not yet possible.
802   -
803   -
804   - ** Code size options: The following options are enabled by
805   - default except in SPL. Enable them explicitly to get these
806   - features in SPL.
807   -
808   - CONFIG_DM_WARN
809   -
810   - Enable the dm_warn() function. This can use up quite a bit
811   - of space for its strings.
812   -
813   - CONFIG_DM_STDIO
814   -
815   - Enable registering a serial device with the stdio library.
816   -
817   - CONFIG_DM_DEVICE_REMOVE
818   -
819   - Enable removing of devices.
820   -
821 708 - Linux Kernel Interface:
822 709 CONFIG_CLOCKS_IN_MHZ
823 710