May 2018 - U-Boot

[U-Boot] [PATCH v2 0/6] Iotrace improvements
by Ramon Fried 28 May '18

28 May '18

These set of patches add few improvements to iotrace. * Region limiting - allows setting an address and size where only io operations that falls into that address are logged. * Timestamping - Timestamp every iotrace record with current timestamp * dumping - iotrace dump command for dumping all records from buffer in a readable fashion. In terms of backwards compatibility, the timestamp is not backward compatible as it changes the iotrace record. so if one developed an offline parsing tool it will be broken. I though of adding #ifdef specific for that, but eventually I didn't. v2: * fixed printf format * added a fix when the buffer is full Ramon Fried (6): cmd: iotrace: add set region command iotrace: add IO region limit common: iotrace: add timestamp to iotrace records iotrace: move record definitons to header file cmd: iotrace: add dump trace command common: iotrace: fix behaviour when buffer is full cmd/iotrace.c | 58 ++++++++++++++++++++++++++++++++++++++++++++++- common/iotrace.c | 55 ++++++++++++++++++++++++-------------------- include/iotrace.h | 52 ++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 139 insertions(+), 26 deletions(-) -- 2.17.0

2 17

[U-Boot] [PATCH 1/1] efi_loader: efi_allocate_pages is too restrictive
by Heinrich Schuchardt 28 May '18

28 May '18

When running on the sandbox the stack is not necessarily at a higher memory address than the highest free memory. There is no reason why the checking of the highest memory address should be more restrictive for EFI_ALLOCATE_ANY_PAGES than for EFI_ALLOCATE_MAX_ADDRESS. Signed-off-by: Heinrich Schuchardt <xypron.glpk(a)gmx.de> --- lib/efi_loader/efi_memory.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/efi_loader/efi_memory.c b/lib/efi_loader/efi_memory.c index cc271e0709d..0efbb973231 100644 --- a/lib/efi_loader/efi_memory.c +++ b/lib/efi_loader/efi_memory.c @@ -294,7 +294,7 @@ efi_status_t efi_allocate_pages(int type, int memory_type, switch (type) { case EFI_ALLOCATE_ANY_PAGES: /* Any page */ - addr = efi_find_free_memory(len, gd->start_addr_sp); + addr = efi_find_free_memory(len, (uint64_t)-1); if (!addr) { r = EFI_NOT_FOUND; break; -- 2.14.2

2 6

[U-Boot] [PATCH v4 00/32] Introduce TPMv2.0 support
by Miquel Raynal 28 May '18

28 May '18

Current U-Boot supports TPM v1.2 specification. The new specification (v2.0) is not backward compatible and renames/introduces several functions. This series introduces the support for TPMv2.x chips. First, some cleaning is done in TPM-related code. Then, the code is split in two categories: generic code (common for both specifications) and specific code (only used by one specification). Then, basic functionalities are introduced one by one for the v2.x specification. TPMv1 vs TPMv2 commands/support distinction is done with Kconfig options. Drivers of only one specification can be selected at a time. A new SPI driver following the TPM v2.x specification is introduced. It has been tested on a ST TPM but should be usable with others v2.0 compliant chips. Finally a full Python test suite is added, as well as a Sandbox driver. Regular testing may be done through the test/py/ framework when using real hardware as well as the Sandbox driver. The following test has run more than 300 times without failing with my setup: test/py/test.py --bd <board> -k tpm2 Available commands for v2.0 TPMs are: * STARTUP * SELF TEST * CLEAR * PCR EXTEND * PCR READ * GET CAPABILITY * DICTIONARY ATTACK LOCK RESET * DICTIONARY ATTACK CHANGE PARAMETERS * HIERARCHY CHANGE AUTH Two commands have been written but could not be tested (unsupported by the TPM chosen): * PCR CHANGE AUTH POLICY * PCR CHANGE AUTH VALUE With this set of function, minimal TPMv2.0 handling is possible with the following sequence. * First, initialize the TPM stack in U-Boot. > tpm init * Then send the STARTUP command to the TPM. The flag is slightly different between the revisions. > tpm startup TPM2_SU_CLEAR * To enable full TPM capabilities, continue the tests (or do them all again). It seems like self_test_full always waits for the operation to finish, while continue_self_test returns a busy state if called to early. > tpm self_test full > tpm self_test continue * Manage passwords (force_clear also resets a lot of internal stuff). Olderly, TAKE OWNERSHIP == CLEAR + CHANGE AUTH. LOCKOUT is an example, ENDORSEMENT and PLATFORM hierarchies are available too: > tpm clear TPM2_RH_LOCKOUT [<pw>] > tpm change_auth TPM2_RH_LOCKOUT <new_pw> [<old_pw>] * Dictionary Attack Mitigation (DAM) parameters can be changed. It is possible to reset the failure counter and disable the lockout (values erased after a CLEAR). It is then possible to check the parameters have been correctly applied. > tpm dam_reset [<pw>] > tpm dam_parameters 0xffff 1 0 [<pw>] > tpm get_capability 0x0006 0x020e 0x4000000 4 * PCR policy may be changed (untested). PCR can be extended (no protection against packet replay yet). PCR can be read (the counter with the number of "extensions" is also given). > tpm pcr_setauthpolicy 0 12345678901234567890123456789012 [<pw>] > tpm pcr_read 0 0x4000000 > tpm pcr_extend 0 0x4000000 Thanks, Miquèl Changes since v3: ================= * Added Simon Glass's RB tags. * Moved all the small fixes about lines, alignments, spellings, etc out of the big commit splitting the TPM code structure. Multiple commits have been made for these changes. Now the split is still done in one commit, but it is supposed to be only code moves and headers changes. * Used map_sysmem() calls to let Sandbox run TPM commands instead of my hack (allocating memory on the go). * Updated the documentation to use the new way of declaring parameters: s/@param x: y/@x: y/. * Added two parameters in the chip private structure to store the number of PCRs and the minimum number of bytes needed to address one in a TPM command. This should fit all the TIS TPM2 compliant modules. * The above change removes some (wrongly) hardcoded values. * Changed the error path as suggested in tpm2_get_capability(). * Minor rephrasing. * Explained in tpm2_get_capability() the offset '19'. * Removed useless reset of rx_buf[0] in tpm_tis_spi_xfer(). * Changed the way spi_xfer return code is checked: error out on any value != 0 instead of just negative ones. * Removed unused functions flagged __maybe_unused as well as well as the __maybe_unused flags themselves when not needed. * Simplified the validity check of the GPIO as suggested. * Updated the compatible property for the SPI modules (as well as the bindings docuementation) to be simply "tis,tpm2-spi" which should work with most compliant chips. Data is linked to this generic compatible in the TPM driver, other values may be added if needed in the future to fit other chips that would use different values than the current ones (used by Infineon SLB 9670 and ST ST33TPHF20 modules, for instance). Changes since v2: ================= * Wrote a full sandbox driver that passes _all_ the Python tests. * Added changes in the library to support running in Sandbox. * Did not rename the former I2C driver. Instead, will prefix new ones by "tpm2_" to make the distinction. * Updated the Kconfig menu to have a clear separated view of the different drivers/specifications. CMD_TPM is now selected by a TPM_DRIVER_SELECTED boolean that is selected automatically when one driver at least is selected. One driver can only be selected if only one specification was precised (1.x or 2.x). * Removed the styling fixes in the TPMv1.x command file as another one will be created. * Removed the buffer length variable renaming as there is no need for it anymore. * Split the whole architecture: for commands and library files, one tpm-common.c file plus one tpm-v<x>.c per specification. Same split for the header files. Some prototypes have been moved to lib/tpm-utils.h and cmd/tpm-user-utils.h depending on their use. This removed the need for an initialization with the right specification and the boilerplate coming with it. * Commented all the TPMv2 enumerations. * Renamed the macro U<XX>_TO_ARRAY into tpm_u<xx> as suggested. * Dropped the buffer length name change as the files are split, there is no more need for such a rename. * Added RB/AB tags. * Used the new logging mechanism. * Added documentation (bindings) for both drivers. * Add the reset by GPIO in the SPI TPMv2.0 driver. * Added a delay in the tests between the pcr_extend and the read_pcr. * Ran the test suite a saw random errors sometimes, with a "LIB_ERROR". I wonder what produces these. Added traces to try to detect where it comes from. * Some checkpatch.pl warnings have been left intentionally. Changes since v1: ================= * Complete test suite for the TPMv2 commands in test/py/. * s/STRINGIFY<X>/U<X>_TO_ARRAY/ (the macros had nothing to do with actual "stringification"). * Changed/fixed some comments. Miquel Raynal (32): tpm: remove redundant blank line tpm: remove extra spaces between a function and its opening bracket tpm: substitute deprecated uint<x>_t types with their u<x> equivalent tpm: align arguments with open parenthesis tpm: use the BIT() macro where applicable tpm: fix spelling tpm: add extra blank lines between declarations and code tpm: add Revision ID field in the chip structure tpm: prepare introduction of TPMv2.x support in Kconfig tpm: disociate TPMv1.x specific and generic code tpm: add missing parameter in private data structure description tpm: prepare support for TPMv2.x commands tpm: add macros to enhance TPM commands readability tpm: add possible traces to analyze buffers returned by the TPM tpm: report driver error code to upper layer tpm: add TPM2_Startup command support tpm: add TPM2_SelfTest command support tpm: add TPM2_Clear command support tpm: add TPM2_PCR_Extend command support tpm: add TPM2_PCR_Read command support tpm: add TPM2_GetCapability command support tpm: add dictionary attack mitigation commands support tpm: add TPM2_HierarchyChangeAuth command support tpm: add PCR authentication commands support tpm: add support for TPMv2.x SPI modules tpm: add the possibility to reset the chip with a gpio doc: device-tree-bindings: add TIS TPMv2.0 SPI module info test/py: add TPMv2.x test suite tpm: add a Sandbox TPMv2.x driver doc: device-tree-bindings: add Sandbox TPMv2.0 module info sandbox: dts: add Sandbox TPMv2.x node configs: add TPMv2.x support in Sandbox arch/sandbox/dts/sandbox.dts | 4 + arch/sandbox/dts/sandbox64.dts | 4 + arch/sandbox/dts/test.dts | 4 + cmd/Kconfig | 24 +- cmd/Makefile | 4 +- cmd/tpm-common.c | 289 +++++++++++ cmd/tpm-user-utils.h | 25 + cmd/{tpm.c => tpm-v1.c} | 488 ++++-------------- cmd/tpm-v2.c | 389 ++++++++++++++ cmd/tpm_test.c | 2 +- configs/sandbox64_defconfig | 1 + configs/sandbox_defconfig | 1 + configs/sandbox_flattree_defconfig | 1 + configs/sandbox_noblk_defconfig | 1 + configs/sandbox_spl_defconfig | 1 + doc/device-tree-bindings/tpm2/sandbox.txt | 11 + doc/device-tree-bindings/tpm2/tis-tpm2-spi.txt | 18 + drivers/tpm/Kconfig | 83 ++- drivers/tpm/Makefile | 3 + drivers/tpm/tpm-uclass.c | 6 +- drivers/tpm/tpm2_tis_sandbox.c | 626 +++++++++++++++++++++++ drivers/tpm/tpm2_tis_spi.c | 681 +++++++++++++++++++++++++ drivers/tpm/tpm_atmel_twi.c | 2 +- drivers/tpm/tpm_tis.h | 1 + drivers/tpm/tpm_tis_infineon.c | 2 +- drivers/tpm/tpm_tis_lpc.c | 2 +- drivers/tpm/tpm_tis_sandbox.c | 2 +- drivers/tpm/tpm_tis_st33zp24_i2c.c | 2 +- drivers/tpm/tpm_tis_st33zp24_spi.c | 2 +- include/tpm-common.h | 218 ++++++++ include/{tpm.h => tpm-v1.h} | 296 ++--------- include/tpm-v2.h | 262 ++++++++++ lib/Makefile | 4 +- lib/tpm-common.c | 198 +++++++ lib/tpm-utils.h | 102 ++++ lib/{tpm.c => tpm-v1.c} | 600 +++++++--------------- lib/tpm-v2.c | 419 +++++++++++++++ test/py/tests/test_tpm2.py | 234 +++++++++ 38 files changed, 3936 insertions(+), 1076 deletions(-) create mode 100644 cmd/tpm-common.c create mode 100644 cmd/tpm-user-utils.h rename cmd/{tpm.c => tpm-v1.c} (64%) create mode 100644 cmd/tpm-v2.c create mode 100644 doc/device-tree-bindings/tpm2/sandbox.txt create mode 100644 doc/device-tree-bindings/tpm2/tis-tpm2-spi.txt create mode 100644 drivers/tpm/tpm2_tis_sandbox.c create mode 100644 drivers/tpm/tpm2_tis_spi.c create mode 100644 include/tpm-common.h rename include/{tpm.h => tpm-v1.h} (60%) create mode 100644 include/tpm-v2.h create mode 100644 lib/tpm-common.c create mode 100644 lib/tpm-utils.h rename lib/{tpm.c => tpm-v1.c} (59%) create mode 100644 lib/tpm-v2.c create mode 100644 test/py/tests/test_tpm2.py -- 2.14.1

3 111

[U-Boot] [UBOOT PATCH] env: mmc: Fix misaligned buffer address when saving envvars to FAT
by Vipul Kumar 27 May '18

27 May '18

From: Gary Mussar <gmussar(a)ciena.com> When doing a u-boot saveenv with the environment in FAT we see the following warning: ZynqMP> saveenv Saving Environment to FAT... writing uboot.env FAT: Misaligned buffer address (000000007deb9b60) done This can be eliminated by aligning the environment to an appropriate boundary. Signed-off-by: Gary Mussar <gmussar(a)ciena.com> Signed-off-by: Vipul Kumar <vipul.kumar(a)xilinx.com> --- include/environment.h | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/include/environment.h b/include/environment.h index 50c62c5..d6c530d 100644 --- a/include/environment.h +++ b/include/environment.h @@ -150,7 +150,11 @@ typedef struct environment_s { unsigned char flags; /* active/obsolete flags */ #endif unsigned char data[ENV_SIZE]; /* Environment data */ -} env_t; +} env_t +#ifdef ARCH_DMA_MINALIGN +__aligned(ARCH_DMA_MINALIGN) +#endif +; #ifdef ENV_IS_EMBEDDED extern env_t environment; -- 2.7.4 This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

4 3

[U-Boot] Initialization of TI AM335x MII connected to Marvell's 88e6341 switch
by Avner Flesch 27 May '18

27 May '18

Hi, I have costume board based on Beagle Bone Black board except the networking - instead of Ethernet PHY, we put a Marvell switch 88e6341 (The CPU port connected with MII). So, I need the u-boot source modification for it If someone can point me to a reference or send me the files, I will really appreciate it Thanks Avner

1 0

[U-Boot] [PATCH v2 0/3] efi_loader: allow writing to FAT
by Heinrich Schuchardt 27 May '18

27 May '18

Running the UEFI Self-Certifcation Test (SCT) will require to support writing to a FAT file system. Writing to the FAT root directory from EFI fails because the leading slash of the file path is interpreted as part of the filename. With the 1st patch we can write to the root directory. A unit test for writing a new file to the FAT root directory is supplied. v2 Avoid use after free due to calline root->close(root) too often. Use ISDIRDELIM() to identify (back-)slashes. Heinrich Schuchardt (3): fs: fat: cannot write to subdirectories efi_selftest: imply FAT, FAT_WRITE efi_selftest: test writing to file fs/fat/fat_write.c | 16 ++++- lib/efi_selftest/Kconfig | 2 + lib/efi_selftest/efi_selftest_block_device.c | 66 ++++++++++++++++++++ 3 files changed, 83 insertions(+), 1 deletion(-) -- 2.17.0

1 3

[U-Boot] [PATCH 1/1] efi_loader: efi_mem_carve_out should return s64
by Heinrich Schuchardt 27 May '18

27 May '18

efi_mem_carve_out() is used to remove memory pages from a mapping. As the number of pages to be removed is a 64bit type the return type should be 64bit too. Signed-off-by: Heinrich Schuchardt <xypron.glpk(a)gmx.de> --- lib/efi_loader/efi_memory.c | 32 ++++++++++++++++++-------------- 1 file changed, 18 insertions(+), 14 deletions(-) diff --git a/lib/efi_loader/efi_memory.c b/lib/efi_loader/efi_memory.c index 4ea25c03053..d5b5fc16070 100644 --- a/lib/efi_loader/efi_memory.c +++ b/lib/efi_loader/efi_memory.c @@ -68,23 +68,27 @@ static void efi_mem_sort(void) list_sort(NULL, &efi_mem, efi_mem_cmp); } -/* - * Unmaps all memory occupied by the carve_desc region from the - * list entry pointed to by map. +/** efi_mem_carve_out - unmap memory region + * + * @map: memory map + * @carve_desc: memory region to unmap + * @overlap_only_ram: the carved out region may only overlap RAM + * Return Value: the number of overlapping pages which have been + * removed from the map, + * EFI_CARVE_NO_OVERLAP, if the regions don't overlap, + * EFI_CARVE_OVERLAPS_NONRAM, if the carve and map overlap, + * and the map contains anything but free ram + * (only when overlap_only_ram is true), + * EFI_CARVE_LOOP_AGAIN, if the mapping list should be + * traversed again, as it has been altered. * - * Returns EFI_CARVE_NO_OVERLAP if the regions don't overlap. - * Returns EFI_CARVE_OVERLAPS_NONRAM if the carve and map overlap, - * and the map contains anything but free ram. - * (only when overlap_only_ram is true) - * Returns EFI_CARVE_LOOP_AGAIN if the mapping list should be traversed - * again, as it has been altered - * Returns the number of overlapping pages. The pages are removed from - * the mapping list. + * Unmaps all memory occupied by the carve_desc region from the list entry + * pointed to by map. * * In case of EFI_CARVE_OVERLAPS_NONRAM it is the callers responsibility - * to readd the already carved out pages to the mapping. + * to re-add the already carved out pages to the mapping. */ -static int efi_mem_carve_out(struct efi_mem_list *map, +static s64 efi_mem_carve_out(struct efi_mem_list *map, struct efi_mem_desc *carve_desc, bool overlap_only_ram) { @@ -183,7 +187,7 @@ uint64_t efi_add_memory_map(uint64_t start, uint64_t pages, int memory_type, carve_again = false; list_for_each(lhandle, &efi_mem) { struct efi_mem_list *lmem; - int r; + s64 r; lmem = list_entry(lhandle, struct efi_mem_list, link); r = efi_mem_carve_out(lmem, &newlist->desc, -- 2.17.0

1 0

[U-Boot] RFC: Alternative boot_jump_linux() function
by Ramon Fried 27 May '18

27 May '18

Hi. I'm currently working on snapdragon bootloader support and in the particular case where U-boot is running in Aarch32 and the kernel is Aarch64 the specific implementation is to jump to Linux through SCM call. I try to find the best possible way to provide an alternative boot function. Adding #ifdef ARCH_SNAPDRAGON will just be too specific in arm/lib/bootm.c in my opinion and I'm thinking of introducing kind of a callback function in gd. that if exists will jump there instead of executing boot_jump_linux(). What do you think ? Waiting for your thoughts on the subject. Warm regards, Ramon.

4 10

[U-Boot] [PATCH] patman: add option for limiting the Cc list
by Chris Packham 27 May '18

27 May '18

Many mailing-lists consider a long Cc list a sign of spam and will either drop the message or mark it for moderation. Because patman automatically invokes get_maintainer.pl the Cc list can expand unexpectedly. Allow the user to specify a limit for the Cc list. This limit is applied after removing any known bouncing addresses. By default no limit is applied. Signed-off-by: Chris Packham <judge.packham(a)gmail.com> --- I've fallen foul of the u-boot ML Cc limit a few times recently. I'm not sure what the actual limit is so I've left patman's default behaviour unlimited. tools/patman/patman.py | 4 +++- tools/patman/series.py | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/tools/patman/patman.py b/tools/patman/patman.py index 8d2c78235a7e..7dd7a1c7b61a 100755 --- a/tools/patman/patman.py +++ b/tools/patman/patman.py @@ -38,6 +38,8 @@ parser.add_option('-i', '--ignore-errors', action='store_true', parser.add_option('-m', '--no-maintainers', action='store_false', dest='add_maintainers', default=True, help="Don't cc the file maintainers automatically") +parser.add_option('-l', '--limit-cc', dest='limit', type='int', + default=0, help='Limit the cc list to LIMIT entries [default: %default]') parser.add_option('-n', '--dry-run', action='store_true', dest='dry_run', default=False, help="Do a dry run (create but don't email patches)") parser.add_option('-p', '--project', default=project.DetectProject(), @@ -157,7 +159,7 @@ else: cc_file = series.MakeCcFile(options.process_tags, cover_fname, not options.ignore_bad_tags, - options.add_maintainers) + options.add_maintainers, options.limit) # Email the patches out (giving the user time to check / cancel) cmd = '' diff --git a/tools/patman/series.py b/tools/patman/series.py index d526d4ee91d3..2066b97e73ff 100644 --- a/tools/patman/series.py +++ b/tools/patman/series.py @@ -202,7 +202,7 @@ class Series(dict): print(col.Color(col.RED, str)) def MakeCcFile(self, process_tags, cover_fname, raise_on_error, - add_maintainers): + add_maintainers, limit=0): """Make a cc file for us to use for per-commit Cc automation Also stores in self._generated_cc to make ShowActions() faster. @@ -238,6 +238,8 @@ class Series(dict): print(col.Color(col.YELLOW, 'Skipping "%s"' % x)) cc = set(cc) - set(settings.bounces) cc = [m.encode('utf-8') if type(m) != str else m for m in cc] + if limit > 0: + cc = cc[:limit] all_ccs += cc print(commit.patch, ', '.join(set(cc)), file=fd) self._generated_cc[commit.patch] = cc -- 2.17.0

2 2

[U-Boot] [PATCH v6 00/11] Add support for DM_USB and DM_USB_DEV for TI's DRA7 EVMs and AM57 EVMs platforms.
by Jean-Jacques Hiblot 27 May '18

27 May '18

Moving to DM_USB and DM_USB_DEV brings some benefits: - it is required to support DM_ETH and USB network adapters with the same binary. - support for USB3 on AM57x comes almost for free - removal of platform code related to USB Tested on: - dra76 evm - AM572 evm This series applies on top of the master branch of the u-boot USB tree (git://git.denx.de/u-boot-usb.git master) Changes in v6: - ti-pipe3-phy: take PLL out of IDLE in pipe3_init(). The PLL may have been put into idle by pipe3_exit() - DRA7 configs: enable DM_USB and DM_USB_DEV. Use DWC3_GENERIC in place of DWC3_OF_SIMPLE. disable non DM USB options - AM57 configs: enable DM_USB and DM_USB_DEV. Use DWC3_GENERIC in place of DWC3_OF_SIMPLE. disable non DM USB options - Supports DM USB for peripherals - Removed DTS changes that disabled USB1 on DRA7 because DM_USB_DEV is now supported Changes in v5: - Rebased on latest u-boot - Removed patches that have already been merged Changes in v4: - Fix word missing in commit log - Remove dependency on MISC - Renamed the commit (DM_USB is already enabled, the only missing option is for the USB2 phy driver) - Remove dependency on MISC - Remove omap specific glue layer and use dwc3-of-simple glue layer Changes in v3: - in syscon_regmap_lookup_by_phandle(), use dev_dbg() instead of printf() - added unit test for syscon_regmap_lookup_by_phandle() Changes in v2: - Add USB3 support to ti-pipe3-phy driver - omap-usb2-phy: Implement power_on and power_off callbacks - am57xx boards: when DM_USB is used, turn on the required USB clocks - split dts changes in 2 commits: one for binding the children of ocp2scp@4a080000, and one to disable USB1 on all DRA7 EVMs - Enable DM_USB in am57xx_evm_defconfig. USB3 (super speed) is supported. Jean-Jacques Hiblot (9): syscon: dm: Add a new method to get a regmap from DTS phy: Add a new driver for OMAP's USB2 PHYs dwc3-generic: Add support for the TI DWC3 glue board: ti: dra7xx-evm: turn on USB clocks in late init stage dts: dra7x: make ocp2scp@4a080000 compatible with simple-bus configs: enable DM_USB and DM_USB_DEV for all DRA7 platforms configs: am57xx_evm: Enable DM_USB and DM_USB_DEV board: ti: dra7-evm: remove USB platform code board: ti: am57xx: remove USB platform code Vignesh R (2): phy: ti-pip3-phy: Add support for USB3 PHY board; ti: am57xx: turn on USB clocks arch/arm/dts/omap5-u-boot.dtsi | 4 + arch/sandbox/dts/test.dts | 6 +- board/ti/am57xx/board.c | 106 ++++------------------ board/ti/dra7xx/evm.c | 123 ++++--------------------- configs/am57xx_evm_defconfig | 10 +- configs/dra7xx_evm_defconfig | 8 +- configs/dra7xx_hs_evm_defconfig | 8 +- drivers/core/syscon-uclass.c | 23 +++++ drivers/phy/Kconfig | 8 ++ drivers/phy/Makefile | 1 + drivers/phy/omap-usb2-phy.c | 196 ++++++++++++++++++++++++++++++++++++++++ drivers/phy/ti-pipe3-phy.c | 32 +++++-- drivers/usb/dwc3/dwc3-generic.c | 86 ++++++++++++++++++ include/syscon.h | 13 +++ test/dm/syscon.c | 29 ++++++ 15 files changed, 441 insertions(+), 212 deletions(-) create mode 100644 drivers/phy/omap-usb2-phy.c -- 2.7.4

2 12