Hi Ulf, On Fri, May 26, 2017 at 6:08 AM, Ulf Hansson <ulf.hansson@xxxxxxxxxx> wrote: > Hi Linus, > > Here are a couple of mmc and arm64-dts fixes intended for v4.12 rc3. > They are based on v4.12-rc2. > > Details are as usual found in the signed tag. Please pull this in! > > Kind regards > Ulf Hansson > > > The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d: > > Linux 4.12-rc2 (2017-05-21 19:30:23 -0700) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git tags/mmc-v4.12-rc2 > > for you to fetch changes up to ea452678734eb782126f999bf5c4fb3e71d3b196: > > arm64: dts: hikey: Fix WiFi support (2017-05-23 14:18:10 +0200) > > ---------------------------------------------------------------- > This pull request contains fixes to make the WiFi work again for the ARM64 > Hikey board. Together with a couple of DTS updates for the Hikey board we have > also extended the mmc pwrseq_simple, to support a new power-off-delay-us DT > property, as that was required to enable a graceful power off sequence for the > WiFi chip. > > ---------------------------------------------------------------- > Daniel Lezcano (2): > mfd: dts: hi655x: Add clock binding for the pmic > arm64: dts: hikey: Add clock for the pmic mfd > > Ulf Hansson (6): > mmc: dt: pwrseq-simple: Invent power-off-delay-us > mmc: pwrseq_simple: Parse DTS for the power-off-delay-us property > arm64: dts: hi6220: Move the fixed_5v_hub regulator to the hikey dts > arm64: dts: hikey: Add the SYS_5V and the VDD_3V3 regulators > arm64: dts: hi6220: Move board data from the dwmmc nodes to hikey dts > arm64: dts: hikey: Fix WiFi support These are a lot of changes to fix a regression. How was it introduced? It would also have been useful if you pointed out the DT contents was already acked by Arnd (I had to go look at the contents since you only looped him in, and no other ARM-SoC maintainers). -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
