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

- Measure the voltage on the SD/OE pin on a functioning board.
- 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.


Sean Anderson (2):
  arm64: dts: renesas: salvator-xs: Add SD/OE pin properties
  arm64: dts: renesas: ulcb: Add SD/OE pin properties

 arch/arm64/boot/dts/renesas/salvator-xs.dtsi | 2 ++
 arch/arm64/boot/dts/renesas/ulcb.dtsi        | 2 ++
 2 files changed, 4 insertions(+)

-- 
2.35.1.1320.gc452695387.dirty

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
> 
> - Measure the voltage on the SD/OE pin on a functioning board.
> - 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.

+CC the people I meant to CC in the first place

On Thu, Sep 26, 2024 at 1:24 PM Sean Anderson <sean.anderson@linux.dev> 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

Without any of the patches from this series, for the Beacon RZ/G2 Boards:

grep 10: /sys/kernel/debug/regmap/*-006a/registers
/sys/kernel/debug/regmap/2-006a/registers:10: a0
/sys/kernel/debug/regmap/4-006a/registers:10: a0

> >
> > - Measure the voltage on the SD/OE pin on a functioning board.
> > - Inspect (or send me) the schematic to determine the state of the SD/OE
> >   pin during normal operation.

The SD/OE pins on the Beacon boards are not tied high by default.
They have an optional pull-up resistor, but it is not populated by
default.

adam
> >
> > 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.
>
> +CC the people I meant to CC in the first place

Hi Adam,

On Fri, Sep 27, 2024 at 2:20 PM Adam Ford <aford173@gmail.com> wrote:
> On Thu, Sep 26, 2024 at 1:24 PM Sean Anderson <sean.anderson@linux.dev> wrote:
> > > - Inspect (or send me) the schematic to determine the state of the SD/OE
> > >   pin during normal operation.
>
> The SD/OE pins on the Beacon boards are not tied high by default.
> They have an optional pull-up resistor, but it is not populated by
> default.

Whoops, this "np" suffix is really tiny! I had completely missed it :-(

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

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

On Fri, Sep 27, 2024 at 7:38 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> Hi Adam,
>
> On Fri, Sep 27, 2024 at 2:20 PM Adam Ford <aford173@gmail.com> wrote:
> > On Thu, Sep 26, 2024 at 1:24 PM Sean Anderson <sean.anderson@linux.dev> wrote:
> > > > - Inspect (or send me) the schematic to determine the state of the SD/OE
> > > >   pin during normal operation.
> >
> > The SD/OE pins on the Beacon boards are not tied high by default.
> > They have an optional pull-up resistor, but it is not populated by
> > default.
>
> Whoops, this "np" suffix is really tiny! I had completely missed it :-(

I have worked at Beacon/Logic PD for 10 years and I still miss the
'np' at times.  It's done that way, so when the bill-of-material is
generated from the schematic, the system throws away anything with an
'np' suffix, but it makes it really easy to enable it and know what
the part should be.

adam
>
> Gr{oetje,eeting}s,
>
>                         Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> 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

Hi Sean,

On Thu, Sep 26, 2024 at 8:24 PM Sean Anderson <sean.anderson@linux.dev> 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@linux-m68k.org

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