> > That's part of the driver structuring - qed is responsible for > > accessing HW so it implements api functions for accessing PTP-related > > configuration, while qede is responsible for the network interface and > > thus is the one to register the clock and implements its API. > > But there is only one 'qed', and so the separation is just busy work. > Or is there another kind of qed that I missed?
One 'qed'? We have 2 distinct models - QED which provides core functionality and supports several other modules as well [qedi, qedr and soon qedf], and QEDE which contain the Ethernet networking logic. It's true that there's a one-to-one mapping of instances [ each qede device is connected to a single qed device], but there's a division of logic between the two.
