On Thu, Jun 18, 2020 at 2:09 PM Wesley Cheng <wcheng@xxxxxxxxxxxxxx> wrote: > > > On 6/18/2020 11:33 AM, Rob Herring wrote: > > On Wed, Jun 17, 2020 at 12:02 PM Wesley Cheng <wcheng@xxxxxxxxxxxxxx> wrote: > > > > You are duplicating everything in usb-connector.yaml. You should have > > a $ref to it. > > > > Hi Rob, > > Sure, I will add a reference to that doc. > > > > > This is wrong. The connector binding says port 0 is the connection the > > USB HS controller. > > > > What's a type C mux node? Is there a binding for that? There's an > > ongoing discussion with the CrOS folks on how to describe Alt mode > > mux/switches. > > I reviewed the connector binding previously, and couldn't seem to come > up with a model which fit a design where the type C controller (ie the > entity which does the CC orientation and role detection) does not have > the SS lane mux included. The SS lane mux is the HW which handles the > selection of the SS lanes to utilize based on cable orientation. The intent was the controller would be the parent node of the connector. How the SS lane mux is represented is what needs to be figured out. I don't know what that looks like, but it needs to be something that works for multiple designs. Ideally, that's an extension of the existing 'usb-c-connector' binding, but if there's good reasons to redesign it that can happen. Rob
