On 15:47-20200917, Kishon Vijay Abraham I wrote: [..] > > Thanks, good point. I am not sure if WIZ should even be used.. It is > > a TI internal prefix for various serdes solutions, but I agree that > > SERDES0 is too generic a terminology. That said, we should cleanup > > include/dt-bindings/mux/mux-j721e-wiz.h as well, prior to introducing > > j7200 changes. > > WIZ is defined in public TRM (https://www.ti.com/lit/pdf/spruiu1). > " Maybe give the TRM team a feedback to use a little more human readable naming? if I just ctrl+f "wiz" in the 10,000 page trm the first match is: "CA bits can be swizzled between any bit positions via the DDRSS_PHY_1053[23-0] PHY_ADR_ADDR_SEL_0 field" (it is not even in the table of contents?) However, if I search for serdes, and then go down to page 7773, "WIZ: The WIZ acts as a wrapper for the SerDes, and can both send control signals to and report status signals from the SerDes, and muxes SerDes to peripherals" just call it ti-k3-serdes-mux (since there are other TI serdes muxes..)? You dont want to be on the brunt of something like [1] caused by, your's truely.. Also this is never going to scale with the number of devices we are spinning out.. one header per SoC? makes no sense to me. [1] https://groups.google.com/forum/#!msg/linux.kernel/fcntv48yoOc/35bAdI1eaiUJ -- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
