Hi Sean, On Thu, Sep 26, 2024 at 8:24 PM Sean Anderson <sean.anderson@xxxxxxxxx> wrote: > On 9/26/24 14:09, Sean Anderson wrote: > > Linux can configure almost every part of this clock generator without > > relying on the OTP settings. However, the correct configuration for the > > SD/OE pin cannot be determined automatically. Therefore, add the > > appropriate properties to configure this pin. > > > > I have CC'd some people who appear to have access to the following > > boards which use the versaclock5: > > > > - Salvator-X > > - HiHope RZ/G2[MN] Main Board > > - Beacon Embedded Works RZ/G2N Development Kit > > > > as I could not find schematics for these boards. You can help me out by > > (pick one): > > > > - Run the following command and send me the output: > > > > $ grep 10: /sys/kernel/debug/regmap/*-006a/registers On Salvator-X (5p49v5923) and ULCB (5p49v5925): 82 On Salvator-XS (5p49v6901): 8a > > - Inspect (or send me) the schematic to determine the state of the SD/OE > > pin during normal operation. > > > > My suspicion is that all of these boards use the same configuration > > (SD/OE pin tied high) owing to their common design heritage. Thanks in > > advance. According to the schematics, the SD/OE pin is indeed strapped high on all of the Salvator-X(S), ULCB, HiHope, and Renesom base and SoM boards. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds