> +- 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. Unfortunately, the existing driver architecture > + does not support such a separation of clocks. > + 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. > + 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. I know we are not perfect in this area, but DT binding should be OS agnostic and should refrain from specifying Linux internals. So, I'd think the comments about driver architecture should be put into the driver, not into the bindings. It is ultimately Ulf's decision, of course.
Attachment:
signature.asc
Description: PGP signature
