On Thu, Oct 01, 2015 at 12:58:49PM -0500, Felipe Balbi wrote: > Hi, > > On Thu, Oct 01, 2015 at 06:43:08PM +0100, Mark Brown wrote: > > On Thu, Oct 01, 2015 at 12:29:32PM -0500, Felipe Balbi wrote: > > > > > Frankly, I wanted all of this to be decided in userland with the > > > kernel just providing notification and basic safety checks (we don't > > > want to allow a bogus userspace daemon frying anybody's devices). > > > > What's the advantage of pushing this to userspace? By the time we > > provide enough discoverability to enable userspace to configure itself > > it seems like we'd have enough information to do the job anyway. > > you're going to be dealing with a setup where each vendor does one thing > differently. Some will have it all in the SoC part of a single IP (dwc3 can be > configured that way), some will push it out to companion IC, some might even use oh, and as for dwc3 itself: it *can* be configured that way, but all those charging blocks are optional :-) So you will even have setups where the very same IP works differently because SoC vendor A configured it differently from SoC vendor B. -- balbi
Attachment:
signature.asc
Description: PGP signature
