Quoting Aradhya Bhatia (2022-12-26 01:57:44) > Add "ti,k3-am62-oldi-clk-div" to the fixed factor clock compatible enum > list. > > "ti,k3-am62-oldi-clk-div" is a fixed-factor clock that helps the TI > display subsystem request a pixel clock for itself and a corresponding > serial clock for its OLDI Transmitters. The serial clock is 7 times the > pixel clock. This clock needs the clock set rate request to be > propagated to the parent clock provider. > > Signed-off-by: Aradhya Bhatia <a-bhatia1@xxxxxx> > --- > Documentation/devicetree/bindings/clock/fixed-factor-clock.yaml | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Documentation/devicetree/bindings/clock/fixed-factor-clock.yaml b/Documentation/devicetree/bindings/clock/fixed-factor-clock.yaml > index 8f71ab300470..0696237530f7 100644 > --- a/Documentation/devicetree/bindings/clock/fixed-factor-clock.yaml > +++ b/Documentation/devicetree/bindings/clock/fixed-factor-clock.yaml > @@ -14,6 +14,7 @@ properties: > compatible: > enum: > - fixed-factor-clock > + - ti,k3-am62-oldi-clk-div I don't see this compatible anywhere in the kernel tree. Is there a patch that adds a node using this? I wonder why the display subsystem can't add this fixed factor clk directly in the driver. Does the OLDI Transmitter send a clk to the display subsystem? I'm asking all these questions because we got rid of vendor compatibles here in hopes of simplifying the logic. Maybe the problem can be approached differently, but I don't know all the details.
