USB: add generic onboard USB HUB driver
Get series with b4
b4 am 1827708.e1pfN6rEID@wuerfelVersions newest first · linked by author and title
- v2 Latest posting 2/20 of 3 patches 0 repliesNew
- v2 posting 1/20 of 3 patches 0 repliesSuperseded
- v13 patches 0 repliesSuperseded
Patches in v2 posting 2/2 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/3] USB: add generic onboard USB HUB driver
Quoted 12 lines · On Wednesday 16 December 2015 16:59:39 Rob Herring wrote:
Quoted 1 line · Arnd Bergmann
On Monday 14 December 2015 15:26:11 Peter Chen wrote:
I agree on doing it properly, but am not sure that pwrseq binding for MMC is proper. The pwrseq binding is fairly limited and working around the driver model IMO. Hubs may also need I2C setup which I don't think could be done generically other than some defined sequence of i2c transactions. The current project I'm working on needs to use I2C to configure the hub to use HSIC mode for example. I really think we need a pre-probe driver hook to handle this. That would allow device specific setup to live in the driver.
Quoted 4 lines
Perhaps a more simple approach would be just forcing driver probe if a DT node is present. I'm not all that familiar with USB drivers, but presumably there is some setup before probe like setting the USB device address. We'd have to allow doing that later during probe.
Yes, good idea. I was also advocating that approach for MMC at some point, but the power sequencing made it in the end.
Arnd