Pine64+ 2GB and RPI3 (A64 examples): Any general idea on what/when to expect for the return of USB support to head?

[Mark Millard]

[I historically use a ufs USB SSD for a (head) root file
system on a Pine64+ 2GB and a RPI3. Thus the question
below.]

Context for question (note the "USB not working for now"
in the Log Message):

> Revision 320612
> 
> Author:
> manu
> Date:
> Mon Jul 3 19:30:03 2017 UTC (4 weeks, 1 day ago)
> Changed paths:
> 5
> Log Message:
> allwinner: Add A64 ccung support
> 
> Upstream DTS for A64 SoC doesn't provide a /clocks node as Linux switched
> to ccu-ng
> This commit adds the necessary bits to boot on pine64 with latest DTS from
> upstream.
> USB is not working for now and some node aren't present in the DTS (like the
> PMU, Power Management Unit).
> 
> Tested on: Pine64
> 
> Changed paths
> Path
> Details
> head/sys/arm/allwinner/a10_mmc.c
> modified , text changed
> head/sys/arm/allwinner/clkng/aw_ccung.c
> modified , text changed
> head/sys/arm/allwinner/clkng/ccu_a64.c
> added
> head/sys/arm/allwinner/clkng/ccu_a64.h
> added
> head/sys/conf/files.arm64
> modified , text changed

/head/sys/arm/allwinner/clkng/ccu_a64.c shows an
empty "USBPHY clk sel" section:

553	/* USBPHY clk sel */
554	
555	/* DRAM needs update bit */

tending to confirm the log message.


The questions:

Does anyone have a general idea that they can report for
what/when to expect for the return of USB support for
Pine64+ 2GB, RPI3, and the like A64 based contexts?

Should I just ignore updating the Pine64+ 2GB and RPI3 for
a few months more? (Because I do self-hosted builds on them
I want the USB file system to be used for such activity.)


===
Mark Millard
markmi at dsl-only.net