u-boot.git/drivers, branch v2020.10-rc5

Merge tag 'efi-2020-10-rc5-2' of https://gitlab.denx.de/u-boot/custodians/u-boot-efi

2020-09-19T12:35:20+00:00

Pull request for UEFI sub-system for efi-2020-10-rc5 (2)

The following bugs are fixed:

* incorrect online help for setenv and env
* description of function efi_mem_carve_out()
* replace printf() by log_err() in stm32mp1_rng driver

A unit test is provided to check that the boot hart id is provided in the
RISC-V device-tree.

rng: stm32mp1: use log() instead of printf()

2020-09-18T20:23:58+00:00

The logging system provides flexible filtering and enhanced output.

Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Sughosh Ganu

mmc: fsl_esdhc_imx: check the clock stable status after config the clock rate.

2020-09-17T12:41:07+00:00

Currently, after config the clock rate, delay 10ms, this is quite a rough
method. Check the clock stable status in the present status register is
enough.

Tested-by: Ji Luo 
Signed-off-by: Haibo Chen

mmc: xenon_sdhci: Add missing common host capabilities

2020-09-15T02:15:56+00:00

Use mmc_of_parse() to set the common host properties. That includes
"bus-width", so parsing it can be removed from the driver.

But more importantly, "non-removable" is now respected, which fixes
the usage of eMMC.

Signed-off-by: Andre Heider 
Reviewed-by: Konstantin Porotchkin 
Tested-by: Marek Behún

mmc: msm_sdhci: Use mmc_of_parse for setting host_caps

2020-09-15T02:13:37+00:00

Since the introduction of 'get_cd' callback in sdhci core,
dragonboard410c's MMC interface is broken. It turns out that 'get_cd'
callback checks for the host_caps for validating the chip select. And
since the msm_sdhci driver is not parsing the host_caps from DT, not
all of the cababilities are parsed properly. This results in the MMC
interfaces to be broken.

Hence, fix this by adding a call to 'mmc_of_parse' during driver probe.

Signed-off-by: Manivannan Sadhasivam 
Tested-by: Aníbal Limón 
Reviewed-By: Ramon Fried 
Reviewed-by: Jaehoon Chung

mtd: nand: Fix nand write error with bad block addresses above 32-bit

2020-09-11T21:13:56+00:00

Nand writes should skip the bad blocks with "nand write" command.
In case of bad blocks with above 32-bit address, nand_block_isbad()
returns false due to truncated bad block address.

In below code segment,

	if (nand_block_isbad(mtd, offset & ~(mtd->erasesize - 1)))

offset is 64-bit and mtd->erasesize is 32-bit, hence the truncation is
happening. Cast 'mtd->erasesize' with loff_t to fix this issue.

Signed-off-by: T Karthik Reddy 
Signed-off-by: Michal Simek

PCI: mediatek: Release the resource when PCIe enable port fail

2020-09-10T19:32:09+00:00

On the mt7623 platform, if one port enable fail and other port
enable succeed. It will hang on when using pci enum
because the resource was not released correctly.

Signed-off-by: Chuanjia Liu 
Tested-by: Frank Wunderlich

bcmgenet: Add support for rgmii-rxid

2020-09-08T14:43:48+00:00

The commit 57805f2270c4 ("net: bcmgenet: Don't set ID_MODE_DIS when
not using RGMII") needed to be extended for the case of using the
rgmii-rxid.  The latest version of the Rasbperry Pi4 dtb files for the
5.4 now specify the rgmii-rxid.

Signed-off-by: Jason Wessel 
Tested-by: Petr Tesarik 
Signed-off-by: Matthias Brugger

bcmgenet: fix DMA buffer management

2020-09-08T14:43:02+00:00

This commit fixes a serious issue occurring when several network
commands are run on a raspberry pi 4 board: for instance a "dhcp"
command and then one or several "tftp" commands. In this case,
packet recv callbacks were called several times on the same packets,
and send function was failing most of the time.

note: if the boot procedure is made of a single network
command, the issue is not visible.

The issue is related to management of the packet ring buffers
(producer / consumer) and DMA.
Each time a packet is received, the ethernet device stores it
in the buffer and increments an index called RDMA_PROD_INDEX.
Each time the driver outputs a received packet, it increments
another index called RDMA_CONS_INDEX.

Between each pair of network commands, as part of the driver
'start' function, previous code tried to reset both RDMA_CONS_INDEX
and RDMA_PROD_INDEX to 0. But RDMA_PROD_INDEX cannot be written from
driver side, thus its value was actually not updated, and only
RDMA_CONS_INDEX was reset to 0. This was resulting in a major
synchronization issue between the driver and the device. Most
visible behavior was that the driver seemed to receive again the
packets from the previous commands (e.g. DHCP response packets
"received" again when performing the first TFTP command).

This fix consists in setting RDMA_CONS_INDEX to the same
value as RDMA_PROD_INDEX, when resetting the driver.

The same kind of fix was needed on the TX side, and a few variables
had to be reset accordingly (c_index, tx_index, rx_index).

The rx_index and tx_index have only 256 entries so the bottom 8 bits
must be masked off.

Originated-by: Etienne Dublé 
Signed-off-by: Jason Wessel 
Tested-by: Petr Tesarik 
Signed-off-by: Matthias Brugger

phy: marvell: a3700: add sata comphy on lane 2 with invert option

2020-09-04T12:02:00+00:00

- This patch moves sata phy powerup from dedicate phy to compphy
  and adds invert option for sata powerup routine.

Change-Id: I1b4e8753e2b2c14c6efa97bca2ffc7d2553d8a90
Signed-off-by: zachary 
Signed-off-by: Ken Ma 
Reviewed-on: http://vgitil04.il.marvell.com:8080/53601
Reviewed-by: Igal Liberman 
Tested-by: Igal Liberman 
[a.heider: adapt to mainline]
Signed-off-by: Andre Heider 
Tested-by: Pali Rohár 
Reviewed-by: Stefan Roese