> It sounds like your suggestion is to just put the HW description in > the DT bindings, but move the dirty details into the driver. > > Keep in DT: > > +- clocks: Most controllers only have 1 clock source per channel. However, on > + some variations of this controller, the internal card detection > + logic that exists in this controller is sectioned off to be run by a > + separate second clock source to allow the main core clock to be turned > + off to save power. > + If 2 clocks are specified by the hardware, you must name them as > + "core" and "cd". > + If the controller only has 1 clock, naming is not required. > > > > Move somewhere in the driver (maybe where the 2nd clock is detected): > > + Unfortunately, the existing driver architecture > + does not support such a separation of clocks. "such" is not explained. Maybe "does not support a seperation of clocks. It doesn't work with Runtime PM because ..."? > + Additionally, it is prohibited to supply a clock to the core but not > + to the card detect circuit. That leaves you with if separate clocks > + are presented, you must treat them both as 1. > > > Is this what you were thinking? Exactly.
Attachment:
signature.asc
Description: PGP signature
